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

Task list

The updated task list is at SSCONE-SITCOM Tasks.

Completed tasks

Ongoing tasks

  • /wiki/spaces/SCOI/pages/59605387.
    • All rows marked as "Review and accept? were accepted with one exception: there is still a need to discuss the best approach for documenting withheld network addresses.
    • It was agreed to close the item concerning the names of service providers. The new service metadata structure is already an improvement as it split the name and the abbreviated name of the organisation.
    • All the other rows will be discussed as part of the standardised implementations task and can be closed.
  • Service Categories
    • It was accepted that there is no need for the CodeDataFormatType given the new approach in the service metadata schema.
    • The changes to CodeLifecyleStageType were not approved. This scheme will be discussed later.
    • The other mature schemes were approved and can be moved to the reference site.
      • OTHER will be added to CodeDocumentType
      • The phrase "based on the SWIM Technical Infrastructure capability" will be removed from the definition of CodeSecurityMechanismType.
    • swim-reference-categories.ttl - the updated skos representation of the service categories will also be made available.
  • FAQ
    • The FAQ on HTTP error codes was reviewed. It needs to be updated to better tie the behaviour of operations to the error message semantics. After the edits are made the FAQ can be moved to supporting material.
  • /wiki/spaces/SCOI/pages/59605888
    • Items 28, 36 and 48 can be closed. Item 36 will be discussed with the Registry CCB
  • Standardised Implementations.
    • The pages were reorganised based on the comments and input already received.
    • The community should review the pages by the next meeting and suggest what else needs to be done.
  • Service Categories - Service Type
    • Discuss - explain, understand, plan.
    • The community should review the pages by the next meeting so we can start to work on the content.
    • Service Definition Template
  • This will be used in the upcoming service definition work in A3SG and MET3SG. At the moment it is a translation of the requirements. Issues that arise when using the requirements/templates will be referred to SSCONE.
    • Note also the work that has been asked concerning conformance/compliance assessment report templates

    Completed tasks

    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 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 Descriptions supporting material
    • Comments to be resolved
      • SWIM-SERV-240 Service interfaces - If the fully qualified network address is not provided for e.g. security reasons, what text should be used?
      • 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
    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 26September 7 November 2022.