Welcome

Objectives of this meeting are:

• refine work plan
• progress on tasks

Common elements

Feedback from previous

meeting

2019-12-12 SWIM COI F2F

Reporting on actions

• what went well / what could be improved
• evolving objectives and tasks

Handbook version

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

•  Update handbook version to 1.0.0 (action WILSON Scott or Former user (Deleted) )

Export as single PDF

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.

Meeting Schedule

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

•  Send webex invitation Former user (Deleted)

See SSCONE-SITCOM Schedule. 

Update on

SSCONE tasks

SWIM Supporting Material v1.0.0 

Initial work plan

Evolving objectives & activities

Excerpt from F2F meeting.

presented slide

Elements 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 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

Proposed main task

Practically applying the Service Description specification by having service descriptions in structured notation.

Starting from point is the JSON Schema as being used by SWIM Registry.→ task 

Proposed additional tasks

The updated task list is at SSCONE Tasks. **update with new tasks**

Update on SITCOM 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