Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Excerpt |
---|
This page handles FAQ answers that are a work in progress. |
Table of Contents |
---|
Current FAQ
Updates
How do I define the list of topics for use in AMQP 1.0?
The role of topics is discussed in the TIYP supporting material. See the "Subject-based Filtering" section in https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.html. It discusses topic enumerations and topic trees. The getTopics operation allows a service consumer to request the list of topics available for subscription. The topics themselves should be based on the data that is exchanged, a common semantic reference such as the AIRM and the list of service categories.
How do I decide on the granularity of a service?
Granularity is tied to the business need, IERs, etc?
Granularity:
get all messages
get an individual message
can mean two things: the size of the service and the size of the data it exposes.
The size of the service is based on the operational needs of the service consumer. See:
- Service Orientation - in particular the Identify and Design steps are useful in understanding users and their needs.
The size of the data exposed (e.g. get all messages, get an individual message, get a property of a message..) is also driven by operational needs and the information exchange requirements. The Interoperability Architecture, in particular, the organisational view is most relevant here.