Ongoing discussions within the SWIM communities of interest

Page tree

Ongoing discussions within the SWIM communities of interest

Skip to end of metadata
Go to start of metadata

Task Status

This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.



Service Type

A categorisation of services based on the nature of the service.

This category is used like the other service categories (e.g. for application message exchange patterns and security mechanisms) published at https://reference.swim.aero/information-services/service-categories.html. Some guidance on there use can be found at Using Service Categories. Like the other categories, it is possible to use as many values as applicable; this is especially important for composite services.


ValueDefinition
AeronauticalAerodromeMapAccessServiceA service that provides a client access to a aeronautical aerodrome maps. 
AeronauticalDataProductAccessServiceA service that allows access to and management of an aeronautical data product. 
AeronauticalFeatureAccessServiceA service that provides a client access to and management of an aeronautical feature store. 
AeronauticalInformationSubscriptionServiceA service to allow clients to register for notification about aeronautical events.
AMDBFeatureAccessService

A service that provides a client access to and management of an AMDB feature store. 
AMDBMapAccessServiceA service that provides a client access to a AMDB maps.

CatalogueServiceA service that provides discovery and management capabilities on a store of metadata about resources.
CoverageAccessServiceA service that provides a client access to and management of a coverage store. Coverage is considered as a special case of Feature. An access service may include a query that filters the data returned to the client.

NOTE ISO 19123 and ISO 19111 are relevant to coverage access.
DataProductAccessServiceA service that allows access to and management of a data product. 
FeatureAccessServiceA service that provides a client access to and management of a feature store. An access service may include a query that filters the data returned to the client.

NOTE ISO 19125, ISO 19142 and ISO 19143 are relevant to feature access.
FlightFeatureAccessServiceA service that provides a client access to and management of a flight feature store. 
InformationServiceA type of service that provides an ATM information sharing capability.
InfrastructureServiceA type of service that provides SWIM infrastructure capabilities such as interface management, request-reply and publish-subscribe messaging, service security, and enterprise service management.
MapAccessServiceA service that provides a client access to a geographic graphics, i.e. pictures of geographic data.

NOTE ISO 19128 is relevant to map access.
MessageQueueServiceA type of service whose main purpose is to publish messages by means of message queues.
MeteorologicalFeatureAccessServiceA service that provides a client access to and management of an meteorological feature store.
MeteorologicalInformationSubscriptionServiceA service to allow clients to register for notification about meteorological phenomena.
MeteorologicalMapAccessServiceA service that provides a client access to a aviation meteorological maps.
PortrayalServiceA service that provides or creates a portrayal.
PublicKeyInfrastructureServiceA service that enables issuance and management of the digital certificates to ensure confidentiality, integrity and non-repudiation of the data moving across systems.
RegistryA service that provides a discovery and management capabilities on a store of metadata about services.
RegistryInformationServiceA type of service that provides a service metadata sharing capability.
SubscriptionServiceA service to allow clients to register for notification about events. Events are defined by a service that performs an activity resulting in the event. Events are catalogued by the subscription service. Clients identify events of interest, e.g. receipt of data with a specific geographic extent. When an event occurs, the subscription service sends notification to all clients who have registered an interest in the event. Once an event occurs, a subscription service may cause an activity to occur, e.g. delivery of a product.

Explanation

The use of the prefix

  • Aeronautical points at the use of the applicable information exchange model such as AIXM 5.1.
  • AMDB means adhering to the industry standards ED99/ED119.

Working model

UML is used to discuss the service category and to build agreement. It is illustrative and is converted to a service category scheme for publication.

The UML diagram below shows the values. For example:

  • An AeronauticalFeatureAccessService is is a type of FeatureAccessService
  • A FeatureAccessService is a type of InformationService

  • No labels