Welcome

1400

Update on tasks

Any other business

Close

1530

Support

FAQ

• The FAQ on HTTP error codes was made live.

SWIM service ecosystem

Service Categories

• Reference website (https://reference.swim.aero/information-services/service-categories.html) is in the process of being updated.

Artefacts to describe services

Service Definitions supporting material

• no updates yet. A3SG will start to use the templates soon. (See

https://ext.eurocontrol.int/swim_confluence/display/ASW/Identified+Services for the work they are doing.)

Service Descriptions supporting material

• Comments to be resolved

  • SWIM-SERV-240 Service interfaces - If the fully qualified network address is not provided for e.g. security reasons, what text should be used?

  • If you have ideas please send them to the group.

Support

Conformance/compliance assessment report templates

• At the next meeting we will decide if we want to engage in preparing templates like this.

• The templates can be completed by service providers to have evidence that they have undertaken activities for conformance to the SWIM specifications and compliance to EU regulation.

• initial drafts:

FAQ

• Questions to be addressed:

  • How do I describe a service that uses GraphQL?

  • If you have ideas please send them to the group.

SWIM service ecosystem

Documenting the use of standardised implementations

• The existing comments were reviewed and the pages will be updated accordingly.

• Comments made during the meeting will be added to the pages.

• The comments are of different natures:

  • ensuring proper documentation in a service description

  • ensuring harmonised design/implementation

Design/Implementation comments

• The group discussed the best approach to the service design/implementation related comments.

  • The current pages will be refactored to reflect the difference in the comments.

  • At the next meeting we can decide if we want, e.g., a section called "supporting service activities" or to cover the comments as part of service definition work.

• Other inputs to review:

  • was made available.

  • ISRM -  https://www.sesarju.eu/sites/default/files/documents/transversal/08.03.10_D45_ISRM_Modelling_Guidelines.docx. 

• The group should review these to see how best to use them.

High-level architecture

• The group pointed out that AMQP, WFS, REST, etc. can be used by the same service. For example, an AMQP message may contain a link to data to be accessed over WFS. There may be a need to build some guidance on how to document these composite services (e.g. as different interfaces in the same service).

Service Categories - Using the Service Type

• was used as a brief introduction to the service types category. It had been presented to the A3SG.

• A meeting will be organised to continue the work.

• There is a chance to benefit from the other groups doing similar work.

Service Portfolio and Service Categories - Service Type

• Open request:

  • provide examples of the typical exchanges that can be mapped to a given category e.g. what falls under “Capacity, demand and flow information”.

  • Hopefully the work on service categories will help answer this.