Welcome

Objectives of this meeting are:

• refine work plan
• progress on tasks

Common elements

Update on SSCONE tasks

Service Description Schema

Evolving objectives & activities

Excerpt from F2F meeting.

• 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.

Proposed main task

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

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

outcome:

The Service Description Schema is our main task for the beginning of the year.

• Our starting point is the Schema being used by the EUR SWIM Services Registry.
• It is agreed that SSCONE is the forum to discuss the Schema.
• We'd like to serve several objectives with one Schema: Serv Desc spec conformance, Registry import/export, bridging to service overview, covering prospective services and service definitions. 

According to the comments raised, working sessions (webex initially) will be defined for detailed discussions

.

Proposed additional tasks

As not many services are already operational, there's a need to describe

• prospective services: service instances that are not operational yet (related to the notion of candidate service).
• service definitions.

These notions will be looked at more closely, in relation with the Schema and the Registry. Taking the service description specification in mind.Feedback received:

Comments from Renato:

• see task page

...

Outcome:

The updated task list is at SSCONE Tasks. 

Update on SITCOM tasks

The updated task list is at SITCOM Tasks.

The first task to start this year is Semantic correspondence training material. A call for interest will be sent to the COI to ask for participation in drafting the material. Work will be done by a series of review webexs.

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 progress meeting on 16th Mar 27th Apr 1400.Is there already a need to identify a face-to-face meeting?

Close meeting