Versions Compared

Version Old Version 13 New Version 14
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 and identify new tasks
  • discuss round table meeting
    • Next round table planned for 26 June. Back-to-back with SWIM-TEC. Will take place in Brussels. Please raise topics to be discussed. So far:
      • message metadata
      • compliance of a service to CP1
      • overview of services in CP1 context
      • compliance with EU 373
      • Supervision/monitoring of services
    • These topics will be discussed with SWIM-TEC to ensure no overlap.

Update on tasks

Completed tasks

Ongoing tasks

TaskNotes
Artefacts to describe services
Service Definitions
  • Supporting material will be worked on over the summer.
Service Overviews
  • PANS-IM is ready for publication.
    • It contains the result of our hard work e.g. references to AIRM.
    • It contains the service overview fields for which we can now build supporting material
  • Supporting material will be worked on over the summer.
Service Descriptions
  • The results of the SWIM-TEC survey on tools to validate a service is available in the linked presentation: Service Validation-Testing.pptx
  • The group discussed the need for a machine-readable version of the SWIM specifications and their requirements.
    • The group saw the benefit as it eases traceability e.g. for compliance tracing.
    • Ways to do this will be explored - either an existing "mark-up" standard or using AI tools.
    • New page created: Machine-readable requirements
Service Metadata Schema
  • no updates
Support
FAQ
  • no updates
SWIM service ecosystem
Service Harmonisation Resources
  • Categories work has been done. Website will be updated soon.
  • The group discussed Service Message Metadata for routing/filtering purposes
    • During a recent trial SWIM participants had specified a particular way of using/encoding the AMPQ 1.0 application-properties to deal with the routing/filtering to relevant stakeholders without introducing custom code into the XML data stored in the body of the messages.
    • We should explore the need to
      • add a section to the Pub/Sub implementation guidance on “How to use the AMQP message”
        • application.properties is AMQP specific
      • add best practice along the lines of “use protocol means to facilitate information distribution without having to rely on parsing the payload” while remaining protocol agnostic at standard level
      • add a field to service description to cover this information.
Service Registry
  • ICAO
    • an update on the registry interoperability concept was presented. The initial target is illustrated below.
    • The concept says: the initial objective is that users discover service information from multiple registries that expose information in a harmonized manner. A common service definition that harmonizes how registries provide service information is a necessary step for facilitating global SWIM service discovery

Service Portfolio
  • no updates
  • Begin:
    • snapshot of where we are so we can better understand the evolution
    • Landing page - make it easier to find SWIM artefacts
Service Developments
  • no updates
Communication
  • Consider how to get service consumers involved

Any other business

  • Migration to new confluence site still to be done.

Next meetings

The meeting schedule is maintained at SSCONE-SITCOM Meetings.