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

Code lists in Schema v0.0.3The list is ordered alphabetically.

Each code list has been embedded in the guidance of the corresponding requirement.


 Legend [+]

The list name may have a suffix indicating the status

  • "" = not processed yet
  • FRn = For nth Review
  • UW = underwork

Colour code

  • black is the original content
  • blue is new / updated content

Code lists

CodeAccessAndUseConditionType - SWIM-SERV-013 Access and use conditions

Descr: A code listing access and use conditions.

NewDescr: A code listing the types of access and use conditions.

Reqt: SWIM-SERV-013 Access and use conditions


Properties:

  • LEGAL_CONSTRAINT 

                TBD

  • SERVICE_POLICY 

                A constraint governing one or more services.

  • SERVICE_CONSUMPTION_CONSTRAINT 

                TBD

  • SECURITY_CONSTRAINT 

                TBD

  • OTHER 

                TBD


CodeApplicationMessageExchangePatternType - SWIM-SERV-017 Message exchange pattern

A code listing types of application message exchange patterns.

Properties:

  • REQUEST_REPLY 

                An application MEP consisting of a consumer sending a request to an information service, the service then executing the request and providing a reply to the consumer.

  • ONE_WAY 

                An application MEP consisting of a consumer sending a message to an information service without any requisite response from the information service.

  • PUBLISH_SUBSCRIBE 

                An application MEP consisting of a consumer sending a subscription request to an information service, the service then providing the consumer with means to access the subscribed information.

  • FAN_OUT 

                An application MEP consisting of a consumer sending sequentially a message to multiple information service according to the One-Way application MEP.

  • SYNCHRONOUS_REQUEST_REPLY 

                A Request/Reply application MEP requiring that the consumer wait for the information service to provide a response, and is unable to send/receive any other requests/responses until the initial response is received.

  • ASYNCHRONOUS_REQUEST_REPLY 

                A Request/Reply application MEP that does not restrict the consumer from completing other operations while waiting for the information service to respond.

  • PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM 

                A Publish/Subscribe pattern whereby the information service sends necessary updates (publish) to the consumer, in accordance with the subscription.

  • PUBLISH_SUBSCRIBE_WITH_PULL_MECHANISM 

                A Publish/Subscribe pattern whereby the information service keeps necessary updates available to the consumer, in accordance with the subscription.

  • BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM 

                A Publish/Subscribe pattern with push mechanism introducing a layer of decoupling between the publisher and subscribers by means of a broker.

CodeBusinessActivityType - SWIM-REG-0004 Service categorization

A code listing the types of business activities.

Properties:

  • AERODROME_OPERATION 

                Planning, execution and analysis of airport airside activities, including, but not limited to, how the aerodrome operators provide the needed ground infrastructure and precise surface guidance to improve safety and maximize aerodrome capacity in all weather conditions.

  • AIRSPACE_ORGANISATION_AND_MANAGEMENT 

                how airspace organizations establish airspace structures in order to accommodate the different types of air activity, volume of traffic and differing levels of service, and about the process by which airspace options are selected and applied to meet the needs of the ATM community.

  • AIRSPACE_USER_OPERATIONS 

                The ATM-related aspect of flight operations.

  • CONFLICT_MANAGEMENT 

                - the strategic conflict management through airspace organization and management, demand and capacity balancing, and traffic synchronization;

- separation provision;

- and collision avoidance.

  • DEMAND_AND_CAPACITY_BALANCING 

                the strategic evaluation of the system-wide traffic flows and aerodrome capacities to allow airspace users to determine when, where and how they operate, while mitigating conflicting needs for airspace and aerodrome capacity.

  • INFORMATION_MANAGEMENT 

                TBD

  • SERVICE_DELIVERY_MANAGEMENT 

                TBD

  • TRAFFIC_SYNCHRONISATION 

                TBD

CodeDirectionType - SWIM-SERV-021 Service operations

A code that indicates whether the message is "input" or "output".

Properties:

  • IN 

                Message data is entered into the system.

  • OUT 

                Message data is transferred out of the system.


CodeDocumentType  - Guidance on serviceDocument

A code describing types of documents.

Guidance: Select SERVICE_SPECIFICATION for any other kind of document.


Properties:

  • SERVICE_STANDARD 

                TBD

SWIM-SERV-010 Service standard reference

Guidance: Avoid using this code. Prefer using the implementedStandard.reference field for providing a link to the service standard.


Requirement ... (from Registry CCB) on SWIM spec conformance

Guidance:  Use this code for conformance assessment report(s) concerning the SWIM specifications. 

  • POLICY_DOCUMENT 

                TBD

SWIM-SERV-013 Access and use conditions

Guidance: Use this code for any document in relation to access and use conditions

  • QUALITY_OF_SERVICE_DOCUMENT 

                TBD

SWIM-SERV-014 Quality of service

Guidance: Use this code for any document in relation to quality of service

  • PROTOCOL_SPECIFICATION 

                TBD

SWIM-SERV-019 Protocols and data format

Guidance: Use this code for any document in relation to protocols 

  • MACHINE_READABLE_SERVICE_DESCRIPTION 

                TBD

SWIM-SERV-020 Machine-readable interface (only appearance of this requirement)

Guidance: Use this code for machine readable document

  • INFORMATION_DEFINITION 

                TBD

SWIM-SERV-022 Information definition

Guidance: Use this code for information definition document(s)

  • AIRM_TRACE

                TBD

SWIM-SERV-022 Information definition

Guidance: Use this code for the semantic correspondence is a separate document from the information definition 

Evolution: Consider renaming SEMANTIC_CORRESPONDENCE.

  • SERVICE_BEHAVIOUR_DESCRIPTION 

                TBD

SWIM-SERV-025 Service behaviour

Guidance: Use this code for a document on service behaviour (eg with sequence diagrams)

  • SERVICE_MODEL 

                TBD

SWIM-SERV-026 Model view (only appearance of this requirement)

Guidance: Use this code for service model file(s). 

  • SERVICE_VALIDATION_REPORT 

                TBD

SWIM-SERV-027 Service validation

Guidance: Use this code a service validation report

  • CODE_EXAMPLE 

                TBD

SWIM-SERV-029 Examples of code  (only appearance of this requirement)

  • MESSAGE_EXAMPLE 

                TBD

Guidance: Avoid using this code. Prefer using the code CODE_EXAMPLE even for examples of messages

  • SERVICE_SPECIFICATION 

                TBD

Guidance: Select this code for any other use of documents. 

In particular this could be used for extra information describing the service such as a User Manual, a Reference Manual, etc. 

  • SERVICE_CERTIFICATION 

                TBD

Guidance: Avoid using this code.

Note: For provider certification (as in SWIM-SERV-008 Service provider, see providerDescription field)

CodeIdempotencyType - SWIM-SERV-021 Service operations

A code indicating whether the operation is "idempotent" or "non-idempotent".

Properties:

  • IDEMPOTENT 

                A type of operation in which receiving duplicates of a given message will not cause any undesirable effect.

  • NON_IDEMPOTENT 

                A type of operation in which receiving duplicates of a given message may cause an undesirable effect.

CodeInformationExchangeCategory - SWIM-REG-0004 Service categorization

Properties:

  • AERONAUTICAL_INFORMATION_EXCHANGE 

                TBD

  • METEOROLOGICAL_INFORMATION_EXCHANGE 

                TBD

  • COOPERATIVE_NETWORK_INFORMATION_EXCHANGE 

                TBD

  • FLIGHT_INFORMATION_EXCHANGE 

                TBD

  • SWIM_INFRASTRUCTURE_EXCHANGE 

                TBD

CodeInterfaceSideType - SWIM-SERV-016 Service interfaces

An indication that the interface is a provider side interface or a consumer side interface.

Properties:

  • PROVIDER_SIDE_INTERFACE 

                An interface provided by the service provider.

  • CONSUMER_SIDE_INTERFACE 

                An interface provided by the service consumer.

CodeLifeCycleStepType - SWIM-REG-0004 Service categorization

A classification of services based on their current, past, or future availability for provisioning.

Properties:

  • OPERATIONAL 

                The status indicating that the service is employed in its operational environment.

  • PROSPECTIVE 

                The status indicating that the service is being designed, developed, or tested for operational activities and is expected to be available in the future.

  • RETIRED 

                The status indicating that active support for the service has been withdrawn, the service has been partially or totally replaced by a new service, or an upgraded service has been installed.

CodeNetworkInterfaceBindingType - SWIM-SERV-018 TI Profile and bindings

A code listing the interface bindings that enable the SWIM TI to exchange data with the network.

Properties:

  • IPV4_UNICAST 

                See chapter 3.1.2.1 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • IPV4_SECURE_UNICAST 

                See chapter 3.1.2.2 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • IPV6_UNICAST 

                See chapter 3.1.2.3 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • IPV6_SECURE_UNICAST 

                See chapter 3.1.2.4 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

CodePrimitiveMessageExchangePatternType - SWIM-SERV-016 Service interfaces

A code listing types of primitive message exchange patterns.

Properties:

  • FIRE_AND_FORGET 

                A primitive MEP consisting of a message being sent from one infrastructure service to another.

  • SYNCHRONOUS_REQUEST_RESPONSE 

                A primitive MEP consisting of 1) a message (request) being sent from a consumer infrastructure service to a provider infrastructure service, 2) the consumer infrastructure service remaining blocked awaiting for a response and the provider infrastructure service remaining blocked processing the response and 3) a message (response) being sent from the provider infrastructure service to the consumer infrastructure service.

CodeSecurityMechanismType - SWIM-SERV-019 Protocols and data format

A code listing the types of service mechanisms.

Properties:

  • AUDIT 

                TBD

  • AUTHENTICATION 

                A security functionality enabling the verification of the validity of credentials and their correspondence with an identity.

  • AUTHORIZATION 

                TBD

  • INTEGRITY 

                TBD

  • IDENTITY_MANAGEMENT 

                A security functionality enabling the management of identities (e.g. identity creation, identity validation, federated identity retrieval).

  • MONITORING 

                TBD

  • POLICY_ENFORCEMENT 

                TBD

  • CONFIDENTIALITY  [1] :

                TBD

CodeServiceInterfaceBindingType - SWIM-SERV-018 TI Profile and bindings

A code listing the interface bindings that enable services to exchange data with consuming applications.

Properties:

  • SWIM_TI_YP_1_0_WS_LIGHT 

                See chapter 3.1.1.1 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS_SOAP 

                See chapter 3.1.1.2 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS_SOAP_WITH_BASIC_MESSAGE_SECURITY 

                See chapter 3.1.1.3 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS_SOAP_WITH_MESSAGE_SECURITY 

                See chapter 3.1.1.4 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS_SOAP_WITH_FEDERATED_SECURITY 

                See chapter 3.1.1.5 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS-N_SOAP 

                See chapter 3.1.1.6 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS-N_SOAP_WITH_BASIC_MESSAGE_SECURITY 

                See chapter 3.1.1.7 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS-N_SOAP_WITH_MESSAGE_SECURITY 

                See chapter 3.1.1.8 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_WS-N_SOAP_WITH_FEDERATED_SECURITY 

                See chapter 3.1.1.9 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

  • SWIM_TI_YP_1_0_AMQP_MESSAGING 

                See chapter 3.1.1.10 of the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.

CodeServiceStandardType - SWIM-SERV-010 Service standard reference

A code listing types of service standards.

Properties:

  • EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION 

                EUROCONTROL Specification for SWIM Service Description

  • EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION 

                EUROCONTROL Specification for SWIM Information Definition

  • EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE 

                EUROCONTROL Specification for SWIM Technical Infrastructure

  • SERVICE_STANDARD 

             

CodeServiceValidationType - SWIM-SERV-027 Service validation


A code listing types of service validations.


Properties:

  • COLLABORATIVE_VALIDATION 

                A validation of service jointly carried out by the service provider together with service users.

  • INDEPENDENT_VALIDATION 

                A validation of service carried out by an independent authority.

  • SELF_VALIDATION 

                A validation of service carried out by the service provider.

  • USER_VALIDATION 

                A validation of service carried out by service users.

CodeStakeholderType - SWIM-REG-0004 Service categorization


A code listing types of stakeholders.


Properties:

  • CIVIL_AIRSPACE_USER 

                TBD

  • MILITARY_AIRSPACE_USER 

                TBD

  • CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER 

                TBD

  • MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER 

                TBD

  • AIR_TRAFFIC_SERVICE_PROVIDER 

                TBD

  • REGULATED_METEOROLOGICAL_SERVICE_PROVIDER 

                TBD

  • AERONAUTICAL_INFORMATION_SERVICE_PROVIDER 

                TBD

  • COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER 

                TBD

  • PROVIDER_OF_DATA_SERVICES 

                TBD

  • NETWORK_MANAGER 

                TBD

  • AIRPORT_OPERATOR 

                TBD

  • AIRSIDE_GROUND_HANDLER 

                TBD

  • MILITARY_DEFENCE_CENTRE 

                TBD

CodeSWIMServiceConformanceStatusType - SWIM-REG-0004 Service categorization


An indication of the status of the service with regard to SWIM Service conformance.

Evolution: Consider splitting notions conformance status from service type

Evolution: Consider a shorter name (eg CodeConformanceStatusType or CodeServiceTypeType).


Properties:

  • SWIM_COMPLIANT 

                TBD

Guidance: Select this code for a service instance that is operational and that is conformant to the 3 SWIM specifications. 

  • SWIM_CANDIDATE 

                TBD

Guidance: Select this code for a service instance  that is not meeting the criteria for SWIM_COMPLIANT

  • DEFINITION 

                TBD

Guidance Select this code for a service definition.

CodeSynchronicityType - SWIM-SERV-021 Service operations


A code indicating whether the operation is "synchronous" or "asynchronous".


Properties:

  • SYNCHRONOUS 

                A type of operation whose message exchange pattern describes temporally coupled or "lock-step" interactions, e.g., remote procedure call (RPC)-style request-response interactions.

  • ASYNCHRONOUS 

                A type of operation whose message exchange pattern allows messages to be sent without precise sequencing, e.g., a flow of sensor event messages which need not be individually acknowledged.

CodeTechnicalResourceType - SWIM-SERV-016 Service interfaces


A code listing types of technical resources.


Properties:

  • QUEUE 

                A staging area that contains messages that have been sent and are waiting to be read.

  • REST_RESOURCE 

                TBD

  • SERVICE_REQUEST_LISTENER 

                TBD

  • TOPIC 

                TBD

  

  • No labels

1 Comment

  1. Typically a Code List is more than an enumerated list, but contains a structure consisting of a code, label(s) and a definition, and also versioned.

    Example: https://www.hl7.org/fhir/valueset-list-example-codes.html

    I am wondering if these "codes" can also follow this model?