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.
Published service category schemes
The current published service categories are at: https://reference.swim.aero/information-services/service-categories.html
Mature and can be published
Service Category | Notes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | CodeDocumentType | Types of documents.
Note: From older versions of Service Metadata Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | CodeAccessAndUseConditionType | Types of restrictions on the access and use of a service.
Note: From older versions of Service Metadata Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | CodePrimitiveMessageExchangePatternType | Message exchange patterns that are directly related to the capability of the lower level protocols.
Note: From older versions of Service Metadata Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | CodeTIYPServiceInterfaceBindingType | Interface bindings that enable services to exchange data with consuming applications.
Note: From older versions of Service Metadata Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 | CodeServiceValidationType | Activities whereby a service is checked for conformance with the service objectives and requirements.
Note: From older versions of Service Metadata Schema | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 | CodeQualityOfServiceMeasureType | A categorisation of services based on the quality characteristics to be taken into account when evaluating the properties of a service. The scheme can be augmented based on ISO/IEC 25010 (https://iso25000.com/index.php/en/iso-25000-standards/iso-25010).
See | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 | CodeSecurityMechanismType | A list of security mechanism based on the SWIM Technical Infrastructure capability enabling secured information exchange.
See | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 | CodeInformationExchangeModelType | A list of information exchange models created by communities of interest.
See | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 | CodeDataFormatType | A list of data formats that can be used to exchange information over services.
See | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 | CodeLifeCycleStageType | This will build upon https://reference.swim.aero/information-services/service-categories/CodeLifeCycleStageType.html to cover other lifecycle stages e.g. draft and experimental.
|
Candidates for service category schemes
Potential service category | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | service providers / organisation | See /wiki/spaces/SCOI/pages/59605387
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | Information security category | This comes from the final version of the Information Service Overview fields - see Information Service Overviews Handbook v1.1.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | AIRM subjects (the packages within the AIRM also have URIs | This was raised in the context of datasets but is applicable to information service payloads in general and, e.g. tools like semantic NOTAM in particular. At the moment the packages are not published but should be. An AIRM change request has been raised. The following table is an extract to show the potential result.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 | More refined ATM Capability list | The EATMA Service Overview organises the services by ATM Capability. The first level is reflected in CodeBusinessActivityType. It is possible to add more levels from the ATM Capability Model. The table below includes the second level. Definitions are taken from https://www.eatmportal.eu/working/data/capabilities.
|