Ongoing discussions within the SWIM communities of interest

Skip to end of metadata
  • Created by Former user (Deleted) , last modified on 2020 Jan 29
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Venue

Date: 03 Feb 2020  1400-1530

webex link: https://eurocontrol-conferences.webex.com/join/wvanhamm   |  706 775 248     

Agenda 

ID

Title

startduration
1Welcome14:0010'
2Common elements14:1030'
3SITCOM tasks14:4020'
4SSCONE tasks15:0020'
5AOB15:2010'
6Close15:30-


Welcome

Objectives of this meeting are:

  • refine work plan
  • progress on tasks

Common elements

Feedback from previous meetings

2019-12-12 SWIM COI F2F

Reporting on actions

--possibly as tasks--


Handbooks version is currently 1.0.0 alpha. There is no need to maintain this at alpha.


A request is expressed to export all pages as a single pdf doc. This requires an add-on currently not installed for SWIM Confluence.

  • Investigate about exporting as a single pdf (action WILSON Scott )
  • Note that the "Full table of content" section of the ServDesc handbook or the InfoDefn handbook is a generated TOC listing all pages within the handbook. This is helps in knowing precisely what the content of the handbook is.


Participants opted for joint progress meetings on Monday 2pm every 6 week. Invitation will follow

See SSCONE-SITCOM Schedule. 

Update on common tasks

SWIM Supporting Material v1.0.0 

Update on SITCOM tasks

The updated task list is at SITCOM Tasks

SSCONE workplan

Evolving objectives & activities. Excerpt from F2F meeting.

presented slideElements flowing out of the discussions
  • Support effective implementation
    • support MET services … ?
    • support other services …
  • Being more practical
    • service description format (template / Schema)
    • service classification / categories
  • More ?
    • service definition
      • provider agnostic service descriptions that facilitate alignment and interoperability in the implementation of services
    • prospective service
      • •guidelines for describing services that are not operational yet (~candidate service)
  • other ideas?
  • Registry needs to be made live.
    • Risk exists however that it will be full of services that nobody uses.
  • Operational use may be slow to pick up at least in ATM. UTM may be quicker
    • geofencing initiatives may not be aligned
  • nice to look at WFS for METAR services
  • identify simple use cases where SWIM makes an impact (eg should we be starting with UTM?)
  • make the conformance evidence a stronger requirement
  • check the registry conforms to the specs
  • consider PANS - it will lead to service overviews
  • still focus on the "used effectively" part of the initial objectives. The word support is too strong, it is give advice and highlight advice.

More practical.

Working on a service description in structured notation. Starting from JSON Schema as being used by Registry.

→ task --Service Description Schema.


Update on SSCONE tasks


The updated task list is at SSCONE Tasks.


Any other business


  • Use of specifications

Questions:

  • Progress on use of the spec?
  • Difficulties encountered?

Examples to be shared, or to work on?

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Schedule. 

Next joint progress meeting on 16th Mar 1400.

Close meeting


  • No labels

Status: Working Material