Welcome

Objectives of this meeting are:

• update progress on tasks
• identify any new service developments
• plan new tasks

Update on tasks

Task list

The updated task list is at SSCONE-SITCOM Tasks.

Completed tasks

• /wiki/spaces/SCOI/pages/59605531
  • Reviews finished
  • Discussed how to publish the reports with the various communities. They have agreed that we can upload the reports to airm.aero. The publication will be handled as part of the tooling task.
  • We need to raise change request for AIRM concerning the definition of "road"
• /wiki/spaces/SCOI/pages/59605512
  • /wiki/spaces/SCOI/pages/59605751.
    
    • The changes were presented to the Registry CCB on 29 September. All changes were accepted and will be implemented in an updated version of the schema.
    • Once the new schema version is available we will update the supporting material to reflect the changes. The good news is that we already have the guidance written, we just need to publish it.

Ongoing tasks

• /wiki/spaces/SCOI/pages/59606089. 
  • Work on tooling ongoing
• Example service developments
  • AIFS/AMIS Service Descriptions produced as part of Airport Toolkit project. These services used the SDDs produced as part of the SESAR solution. The service descriptions have been converted to Service Overviews as well.
  • Would members like more details on other service developments e.g. some sort of service development dashboard?

New tasks

• It is time to consider an update SWIM Service Description Specification.
  • Scope of the update:
    • leverage best practices/new content identified in schema walk-through and JSON Schema
      
    • align as much as possible the terms used in the specification with those on https://reference.swim.aero/glossary.html. 
      
  • Assumptions:
    • the specification still focuses on describing running services
• Geospatial support in JSON Schema
  • Coming from request to Registry CCB
  • Can be related to the update of the specification
• JSON Schema maintenance
  • At the moment we have several versions of the same schema. Is there another way to manage these? E.g. can we leave the checking of specific validation rules to the individual applications.
• Service definition
  • The https://reference.swim.aero/glossary.html includes a service definition. The Governance Implementing Project outlined requirements for this. Should we look at this artefact?

Any other business

-

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

Next progress meeting is on 23rd November.