Versions Compared

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

Welcome

1400

Update on tasks

Any other business

Close

1530



Panel
borderColorlightgrey
Table of Contents
maxLevel2

Consider how to get service consumers involved

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

New tasks

  • Landing page - make it easier to find SWIM artefacts
    • This should be coordinated with SWIM-TEC. It has a meeting on 16 April that will discuss how to restructure the Foundation document to add links to other artefacts.
    • Confluence would be a good place to have the landing page
  • The need for the ecosystem was emphasised at the round table - snapshot of where we are so we can better understand the evolution
    • SWIM-TEC is considering something similar including: foundation, requirements, good practices and monitoring adherence to them

    • Ongoing tasks

    Task

    Notes

    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

    results

    • on

    how

    • 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

    • Agreed to move the following FAQs to the live page:
      • How is the quality of service documented at various service lifecycle stages?
      • How is the quality of data documented at various service lifecycle stages?
    Agreed: Based on Quantitative Volcanic Ash Information Subscription and Request Service - Service Definition add METEOROLOGICAL_COVERAGE_ACCESS_SERVICE to https://reference.swim.aero/information-services/service-categories/CodeServiceType.html

    • no updates

    SWIM service ecosystem

    Service Harmonisation Resources

  • Agreed: Based on PANS-IM, the information security category should be added to the list of categories on the reference website.

    • 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

    Image Added

    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.