Versions Compared

Version Old Version 1 New Version Current
Changes made by

WILSON Scott

WILSON Scott

Saved on

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

  • Updated examples based on new version of the schema. see SWIM-SERV-290 Information definition - minimum

Ongoing tasks

State Letter for PANS-IM is circulating so we can soon (probably Q4 2023)finish the handbook for service overviews and publish to the supporting material Monday 3rd April. Invitations will be sent soonA meeting focusing on FF-ICE services and AMQP will take place on
TaskNotes
Artefacts to describe services
Service DefinitionsService Overviews
  • ?


  • Service definitions are on the agenda for the ICAO WGI/S meeting in May.

  • We can launch the specification development process (see IMT/7 item below). This will use the EUROCONTROL ERAF and SSCONE-SITCOM will be used as the drafting group. This is similar to what has happened with the other SWIM specifications. Basic plan:
    • copy content from the SSCONE-SITCOM confluence page into the EUROCONTROL specification template
    • see if there is anything we want to change
    • we need to add somethings e.g. verification, rationale...
    • once we are happy (say late August) EUROCONTROL will launch the formal consultation process. That takes 3 months.
  • Work should start on this at the next meeting.


Service Overviews
  • Paused pending conclusion of State Letter process and PANS-IM publication.
Service Descriptions
  • no updates
Support
FAQService Discovery Service
  • ICAO Job Card on registry interoperability has started work. It recognises three levels of registry interaction:

    • interoperable - queries are sent between registries based on agreed metadata; interconnected; and integrated

    • The focus is on the interoperable level for now
    • Questions to be answered (send suggestions to the group):
      • How do I describe a service that uses GraphQL?
        • Some example of services that use GraphQL were presented. This highlighted some key points.
          • The schema is self documenting (the same goal as Open API).
          • The service uses HTTP - a query that embeds elements from the schema is sent to the server, JSON responses are returned.
          • The schema can be based on the semantics of AIXM/AIRM.
          • It is possible to query, post and subscribe using GraphQL.
          • In general, GraphQL is better suited for mobile and light-weight applications. The current tests have not fosused on system-to-system exchanges.
          • The approach seems acceptable under the SWIM TI Yellow Profile.
        • An answer will be drafted and made available to the group. (See Documenting the use of standardised implementations for inspiration on the content of the answer.)
    		Service Metadata Schema
    Service Metadata Schema
    • Registry interoperability is on the agenda for the ICAO WGI/S meeting in May.

    • Version 1.0.0 of the service description schema is available for testing. Some group members have implemented it in their systems.

      It will be made official once Registry CCB confirms it

      will be discussed/approved at the Registry CCB in May.

    SWIM service ecosystem
    Service Design Activities
    • We will inform IMT on 18-19 April of the intention to look more at thisIMT supported the continuation of this work.
    • Added guidance on the use of CodeApplicationMessageExchangePatternType e.g. PUBLISH_SUBSCRIBE for services built around AMQP 1.0.
    		Service Categories - Service Type
      • Agreed that it could be.
    /wiki/spaces/SCOI/pages/59606413
    • Workshop took place to consider how to integrate FF-ICE and NM flight information services. See 2023-04-03 Flight and Service Categories.
    • Similar patterns have been applied to the MET services. It was noted that even though a category exists, there may be no actual service that falls into it e.g. will there ever be a MeteorologicalInformationManagementService in the context of SWIM?
    • The result of the work has been applied and can be made live.
    Service Portfolio
    • We will inform IMT on 18-19 April of the intention to look more at thisIMT supported the continuation of this work.
    • The page was updated with some new sources identified by the group.
    • Work should start on this at the next meeting.

    Any other business

    Registry

    • There will be a Registry CCB in late April.

    ICAO Information Management Panel (IMP)

    • State Letter including PANS-IM has been circulated. Highlights:
      • The AIRM is explicitly mentioned. If you don’t use an already mapped XM, you will need to perform your own semantic correspondence.
      • The service chapter concentrated on the information service overview. This can be seen as a subset of the service description for describing running services.
      • The technical infrastructure yellow profile is mentioned in a note in the technical infrastructure section.

    Paper presented to IMT/7

    Next meetings

    Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

    Next progress meeting is24 April 5June 2023.