Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Agenda 

Item

Time
Welcome1400

Update on tasks


Any other business


Close1530
Panel
borderColorlightgrey

Table of Contents
maxLevel2



Welcome

Objectives of this meeting are:

  • work on tasks

Update on tasks

Completed tasks

Service CategoriesWebsite in the process of being updated.

Task

Notes
Support
FAQ
  • The FAQ on HTTP error codes was made live.
SWIM service ecosystem
Service Categories

Ongoing tasks

TaskNotes
Artefacts to describe services
Service
definition
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
description
Descriptions supporting material
  • Comments to be resolved
    • SWIM-SERV-240 Service interfaces
:
    • - If the fully qualified network address is not
to 20191104 Controlled verbs for Application Functions V.1.1.pdfcan be added to supporting material as examples.
    • provided for e.g. security reasons, what text should be used?
SupportStandardised Implementations
  • positioning: service design/implementation v service description
  • comments to review.
      • If you have ideas please send them to the group.
    Support
    Conformance/compliance assessment report templates
    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
    Service Categories - Service TypeDiscuss - explain, understand, plan
    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

    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).
    /wiki/spaces/SCOI/pages/59606413
    • Service Concepts.pptx 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.

    Any other business

    • Registry

      • Integrating the new schema. Changes to the Registry will be presented at the next meeting so we can assess any impact on us.

    Next meetings

    Meeting schedule is maintained at SSCONE-SITCOM Meetings

    Next progress meeting is 11 7 November 2022.