Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Excerpt |
---|
This task will work on service categories in support ofof: 009 . It will reflect the more flexible approach that will be adopted
|
Table of Contents |
---|
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
No service category or value has this status at the moment.
Candidates for service category schemes
CodeStakeholderType
Status |
---|
See
- New: Best practices to harmonise content of service description fields
- SWIM-SERV-180 Quality of service
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).
capacity
The maximum rate at which a service can process transactions and the maximum message size of responses.
Note: Measurements can include the number of items that can be stored, the number of concurrent users, the communication bandwidth, throughput of transactions, and size of messages.
time behaviour
A measurement of the processing times of a service.
Note: This parameter may be expressed as an indication of a maximum time needed for the service provider to complete the request, measured from the time instant the service provider receives the request to the time instant the service provider sends the response or makes it available.
availability
The degree to which a service is operational and accessible when required for use.
recoverability
The degree to which, in the event of an interruption or a failure, the desired state of the service can be re-established.
confidentiality
The degree to which a service ensures that data are accessible only to those authorized to have access.
integrity
An expression of the assurance that a system, product or component prevents unauthorized access to, or modification of, an information service interface or information.
See
A list of security mechanism based on the SWIM Technical Infrastructure capability enabling secured information exchange.
A security mechanism ensuring that the identity of a subject can be proved to be the one claimed.
authorisation
A security mechanism for the granting of rights and, based on these rights, the granting of access.
See
- New: Best practices to harmonise content of service description fields
- SWIM-SERV-290 Information definition - minimum
A list of information exchange models created by communities of interest.
See
- New: Best practices to harmonise content of service description fields
- SWIM-SERV-260 Service interface protocols and data format
A list of data formats that can be used to exchange information over services.
GRIdded Binary. See: https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/
Hierarchical Data Format. See: http://codes.wmo.int/wmdr/DataFormat/hdf5
Abstract Syntax Notation One. See: https://www.itu.int/rec/T-REC-X.680/
This comes from the final version of the Information Service Overview fields - see Information Service Overviews Handbook v1.1.
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.
- RouteAndProcedure
- AerodromeInfrastructure
|
From older versions of Service Metadata Schema
"CodeDocumentType": {
"description": "A code describing types of documents.",
"type": "string",
"enum": [
"POLICY_DOCUMENT",
"SERVICE_STANDARD",
"QUALITY_OF_SERVICE_DOCUMENT",
"SERVICE_MODEL",
"SERVICE_CERTIFICATION",
"CODE_EXAMPLE",
"SERVICE_BEHAVIOUR_DESCRIPTION",
"PROTOCOL_SPECIFICATION",
"MACHINE_READABLE_SERVICE_DESCRIPTION",
"SERVICE_SPECIFICATION",
"MESSAGE_EXAMPLE",
"SERVICE_VALIDATION_REPORT",
"AIRM_TRACE",
"INFORMATION_DEFINITION"
]
},
From older versions of Service Metadata Schema
"CodeAccessAndUseConditionType": {
"description": "A code listing access and use conditions. [SWIM-SERV-150], [SWIM-SERV-160]",
"type": "string",
"enum": [
"LEGAL_CONSTRAINT",
"SERVICE_POLICY",
"SERVICE_CONSUMPTION_CONSTRAINT",
"SECURITY_CONSTRAINT",
"OTHER"
]
},
From older versions of Service Metadata Schema
"CodePrimitiveMessageExchangePatternType": {
"description": "A code listing types of primitive message exchange patterns.",
"type": "string",
"enum": [
"FIRE_AND_FORGET",
"SYNCHRONOUS_REQUEST_RESPONSE"
]
},
From older versions of Service Metadata Schema
"CodeServiceInterfaceBindingType": {
"description": "A code listing the interface bindings that enable services to exchange data with consuming applications.",
"type": "string",
"enum": [
"SWIM_TI_YP_1_0_WS_LIGHT",
"SWIM_TI_YP_1_1_WS_LIGHT",
"SWIM_TI_YP_1_0_WS_SOAP",
"SWIM_TI_YP_1_1_WS_SOAP",
"SWIM_TI_YP_1_0_WS_SOAP_WITH_BASIC_MESSAGE_SECURITY",
"SWIM_TI_YP_1_1_WS_SOAP_WITH_BASIC_MESSAGE_SECURITY",
"SWIM_TI_YP_1_0_WS_SOAP_WITH_MESSAGE_SECURITY",
"SWIM_TI_YP_1_1_WS_SOAP_WITH_MESSAGE_SECURITY",
"SWIM_TI_YP_1_0_WS_SOAP_WITH_FEDERATED_SECURITY",
"SWIM_TI_YP_1_1_WS_SOAP_WITH_FEDERATED_SECURITY",
"SWIM_TI_YP_1_0_WS-N_SOAP",
"SWIM_TI_YP_1_1_WS-N_SOAP",
"SWIM_TI_YP_1_0_WS-N_SOAP_WITH_BASIC_MESSAGE_SECURITY",
"SWIM_TI_YP_1_1_WS-N_SOAP_WITH_BASIC_MESSAGE_SECURITY",
"SWIM_TI_YP_1_0_WS-N_SOAP_WITH_MESSAGE_SECURITY",
"SWIM_TI_YP_1_1_WS-N_SOAP_WITH_MESSAGE_SECURITY",
"SWIM_TI_YP_1_0_WS-N_SOAP_WITH_FEDERATED_SECURITY",
"SWIM_TI_YP_1_1_WS-N_SOAP_WITH_FEDERATED_SECURITY",
"SWIM_TI_YP_1_0_AMQP_MESSAGING",
"SWIM_TI_YP_1_1_AMQP_MESSAGING"
]
},
From older versions of Service Metadata Schema
"CodeServiceValidationType": {
"description": "A code listing validation methods. [SWIM-SERV-200]",
"type": "string",
"enum": [
"COLLABORATIVE_VALIDATION",
"INDEPENDENT_VALIDATION",
"SELF_VALIDATION",
"USER_VALIDATION",
"NOT_VALIDATED"
]
},
See New: Best practices to harmonise content of service description fields
The direction des Services de la navigation aérienne (DSNA) is the agency in charge of air traffic control, communication and information for France. It is a part of the Ministry of Sustainable Development and was created by decree in February 2005.
Met Office
MetSafe
EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States.
EUROCONTROL Network Manager
|
Add a new value to CodeStakeholderType.
Service Category | Value | Definition | URL |
---|---|---|---|
CodeStakeholderType | |||
OVERSIGHT_AUTHORITY | An entity or body responsible for monitoring, regulating, and ensuring compliance with laws, policies and standards within a particular field or organisation. |
ICAO regulated
Status | ||||
---|---|---|---|---|
|
Service Category | Value | Definition | URL |
---|---|---|---|
CodeICAORegulationStatusType -> CodeICAOPublicationType | A categorisation of services based on the level of ICAO regulation. -> A categorisation of services based on the type of ICAO publication from which the operational need for the service can be derived. | ||
ANNEX | The service is aligned with statements found in an ICAO Annex. -> The operational need for the service is derived from an ICAO Annex. | ||
PANS | The operational need for the service is derived from an ICAO PANS. | ||
GUIDANCE | The operational need for the service is derived from an ICAO guidance document. |
lifecycle stage
Status | ||||
---|---|---|---|---|
|
This will build upon https://reference.swim.aero/information-services/service-categories/CodeLifeCycleStageType.html to cover other lifecycle stages e.g. draft and experimental.
Service Category | Value | Definition |
---|
URL |
---|
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.
Aerodrome Operations
- Information from/to Airport Landside Operations
- Airport Situational Awareness Provision
- Surface Guidance & Routing
Airspace Organisation and Management
- Airspace Design
- Airspace Management
Airspace User Operations
- Flight Prioritisation
- Execute Trajectory
Conflict Management
- Separation Management
- Collision Avoidance
CNS
- CNS Resource/Asset Management
- CNS Infrastructure Performance Management
- CNS Integration
- Communication
- Navigation
- Surveillance
Demand and Capacity Balancing
- Demand and Capacity Balancing (airport)
- Demand and Capacity Balancing (airspace)
Information Management
- Aeronautical and Meteorological Information Management
- Information Infrastructure Management
- Information to/from Other Essential Services
- ATM Data Management
Service Delivery Management
- ATM Service Management
- Trajectory Management
- ATC Team Resource Management
Traffic Synchronisation
- Sequencing & Merging
CodeLifeCycleStageType | |||
DRAFT | The status indicating that the service is... | ||
EXPERIMENTAL | The status indicating that the service uses new ideas or methods, and might be modified later if it is unsuccessful. It is made available in order to be assessed for future development. |