Versions Compared

Version Old Version 5 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

Ongoing tasks

Comments to be resolved (send suggestions to the group).SWIM-SERV-240 Service interfaces and approach for withheld endpoints. We will wait on updated SWIM Registry documentation on the fields that can be hidden before reactivating our task.
TaskNotes
Artefacts to describe services
Service Definitions supporting material
  • No updates required.
  • It is beginning possible to merge with the service design activities below.
Service Descriptions supporting material
Service Overviews
  • 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.
Service Descriptions
  • no updates
Support
FAQ
  • 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
      will be presented.
      • 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
  • News on Service 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.

  • Version 1.0.0

    available for use?

    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.

SWIM service ecosystem
Service Design Activities
  • We will inform IMT on 18-19 April of the intention to look more at this.
  • Added guidance on the use of CodeApplicationMessageExchangePatternType e.g. PUBLISH_SUBSCRIBE for services built around AMQP 1.0.
Service Categories - Service TypeArrange meetings /wiki/spaces/SCOI/pages/59606413
  • A meeting focusing on FF-ICE services and AMQP are neededwill take place on Monday 3rd April. Invitations will be sent soon.
Service Portfolio
  • We will inform IMT on 18-19 April of the intention to look more at this.
  • The page was updated with some new sources identified by the group.

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.
.introduce the resources are available in order to start the activity.

Any other business

  • tbdHighlights:
    • 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.

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

Next progress meeting is 24 April 2023.