Presentations about the workshop that took place on 22nd May 2019.
Please find below the presentations of this workshop on SWIM using a simplified service development process on example services, focusing on service identification and service design, bringing education on AIRM, XMs, and TI.
- 1. Session Approach
- 2. Identify Services for A-CDM
- 2.a Define IER wih AIRM
- 2.b Define NFR
- 3. Design TOBT Setting Service
- 3.a Design MEP
- 3b Design Payload
- 3c Interface Binding
- 3d Registration
- 4. Design Flight Publication Service
- 4a Service Design
- 5. Session Conclusion
This specification contains requirements for describing implemented information services within the context of Initial System Wide Information Management (iSWIM). In order for service consumers to make good use of the available information services, it is essential that service descriptions cover the service consumers’ needs. Therefore, the requirements focus on the service description that a service provider makes available to service consumers.
More specifically, the requirements prescribe the minimum set of elements to be contained by a service description in order for a service consumer to discover a service, consider using a service, or implement a service consuming client.
The requirements ensure that a service description covers the information needs of business experts, operational experts and technical experts, more particularly in terms of: what a service does, how a service works, how to access a service, and other information for consuming a service.
- Service description authors
The Specification for SWIM Service Description sets out a number of requirements to be met by a service description. It provides some basic examples to illustrate the requirements. However, the specification does not give much detail on how to satisfy the requirements.
This handbook gives guidances to help service description authors to satisfy the requirements.
The guidance contained in the handbook promotes the creation of better service descriptions. It will lead to greater harmonisation in the implementation of the specification.
- Service description authors
This specification contains requirements for information definitions in the context of Initial System Wide Information Management (iSWIM) in Europe.
Information definitions, the formal descriptions of exchanged information, are produced or reused by operational stakeholders. They act as the means whereby the exchanged information is clearly defined, understood and harmonised between stakeholders. Examples of information definitions are the description of information exchanged by services, standardised information exchange models, data catalogues used to list details on the exchanged information, and information exchanges captured as part of a business process model.
The requirements come in two broad categories: general requirements for information definitions and requirements on how to document semantic correspondence to the ATM Information Reference Model (AIRM).
The general requirements include, for example, the need for an edition and a reference date.
The semantic correspondence requirements facilitate semantic interoperability, which is the ability of computer systems to exchange data with unambiguous, shared meaning. The requirements ensure that information definitions conform to the semantics of the AIRM, the common reference language for iSWIM.
The Specification for SWIM Information Definition sets out a number of requirements to be met by an information definition. It provides some basic examples to illustrate the requirements. However, the specification does not give exhaustive details on how to satisfy the requirements.
This handbook gives guidance to help information definition authors and AIRM conformance report authors to satisfy the requirements.
The guidance contained in the handbook promotes the creation of better information definitions. It will lead to greater harmonisation in the implementation of the specification.
- Information definition authors
- AIRM conformance report authors
- AIRM conformance report auditors and readers
This specification contains requirements for the implementation of technical infrastructure supporting information exchanges in Initial System Wide Information Management (iSWIM).
It enables technical interoperability by specifying standardised technical interfaces (e.g. protocols) and the capabilities required to enable a reliable, secure and efficient exchange of information.
This specification is modular and provides different implementation options based on mainstream technology, taking into account a wide range of information exchange needs (e.g. security).
This specification is intended for use by technical experts designing and implementing systems and services.
This document provides additional clarifications to EUROCONTROL specification for SWIM Technical Infrastructure Yellow Profile.
It aims at providing a better understanding of the SWIM Technical Infrastructure (TI), explaining the specification context in Europe, the principles that influence the specification, as well as the functional and non-functional scope covered by the SWIM TI.
This document intends to serve as implementation guidance of the Publish/Subscribe Push Message Exchange Pattern using SWIM-TI Yellow Profile Service Bindings. The document is structured as follows:
- In section 2, we provide a general overview of Publish/Subscribe services in a technology agnostic manner.
- In section 3, the technology agnostic service design is realised in a concrete implementation using WS-Light and AMQP Messaging Service Bindings .
The proposed service design and implementation is intended to provide a basic template for implementers that can be customised or complemented in multiple ways to suit specific needs.
This document provides a classification of the SWIM TI Yellow Profile Service Bindings catalogue according to the following criteria:
- Message Exchange Patterns
- Security characteristics
- Performance characteristics
This classification can be used by implementers as guidance for selecting the Service Binding or Service Bindings used to implement a service that matches the desired characteristics.
Document intended to facilitate the understanding of message exchange patterns from an application and Technical Infrastructure perspective.
The SWIM Registry is a directory of information that supports the discovery of SWIM services.
The SWIM Registry uses a formal registration process to store, catalogue and manage service metadata.
The SWIM Service Description JSON Schema provides a structured notation for Service Descriptions, aiming at enhanced harmonisation and processing by systems.
The European SWIM Registry uses this JSON Schema as the import/export format for Service Descriptions.
The forum of discussion of this schema is the SWIM Service Community of Interest (see collaboration environment for more info).