Welcome

Objectives of this meeting are:

• progress on the tasks
• Finalise initial handbook
• ?? continue discussing the Change Request on the specification
• processing review comments

Feedback from previous meeting

Action list

Short-term actions identified during 2019-01-28 SSCONE webex.

• Webex moved from 22 to 23 Apr. 
• F2F re-scheduled to 21-23 May.

Update on tasks

The task list is at SSCONE Tasks.

Task /wiki/spaces/SCOI/pages/59606295

Comments received from : Sam, Steffen Beringer, and Oliver Krüger2 SSCONE members.

Comments are being processed... ==

Proposed conclusion: ==TBD

outcome: 

• Some actions recorded /wiki/spaces/SCOI/pages/

• 59606295
• rework needed for service categories
• update needed for XML example
• Access by SSCONE members to the artefacts from SWIM Governance Implementation Project: this will be resolved by the planned public website that would be available by Oct 2019.
• Should we restrict acccess to some pages before publishing first version of the handbook.
  • It is not a problem to go public with Open Questions or Work in Progress elements in web page.
• After updates, can be officially published as first version of service description handbook.

Task /wiki/spaces/SCOI/pages/59606173

Comments received from : -

Proposed conclusion: TBD

outcome: 

Conformance assessment

==recopy from tasks==

Task

Description

Status

Priority

Agenda point for F2F.

Question: anyone willing to prepare and present the compliance point of view from the SWIM Governance Implementation Project?

outcome: 

2 SSCONE members.

Comments are being processed

outcome:  

• A conformance matrix has been added for the Donlon example: Conformance assessment - Donlon example. This makes clear that the example service description is not complete (eg access and use conditions; eg example code)
• Example Code: probably not possible for the Donlon example. We will have to wait for an example of a service that is effectively implemented. 
• Making services using a specific data format (eg GRIB2) more discoverable. This could be resolved by making a field explicit in the Registry. This will be proposed to the Registry requirement gathering activity.
• Reordering of section for better readability (eg business experts, developers)
  • Expanding the Table of Content improves reading by making clear the structure of the document. 
  • Any suggestion for an improved reading (eg improved ordering of sections) is welcome.
• The idea of having a template for a textual service description that would generate an XML service description is not retained currently.
• Additional / better examples: One SSCONE member indicates that LFV has written full fledge Service Descriptions Documents (SDDs) for their services. These could become interesting examples.

• •  Check whether LFV would allow SSCONE to make use of their SDDs as examples.

Task /wiki/spaces/SCOI/pages/59606015

Agenda point for F2F.

Main discussion point is probably to choose between these 2 options

It is not the role of the the Service Description specification to enforce AIRM conformance.

AIRM conformance is key to semantic interoperability.

Interoperability is an essential goal to achieve.

AIRM conformance is already enforced through the Information Definition specification.

Redundant requirements may be create confusion.

Conformance to the Service Description specification does not imply AIRM conformance.

Conformance to the Information Definition specification implies AIRM conformance.

Change the specification.

see eg "revert back proposal"

Insist on AIRM conformance.

Make reference to change request and advice.

Insist on AIRM conformance.

Make clear that its enforcement is in the scope of the Information Definition specification.

• either "Should the Service Description specification enforce AIRM conformance"
• or "Should AIRM conformance enforcement beshould AIRM conformance is this fully

outcome: 

Added a table of discussion points about the 2 options. The main point of discussion is: which SWIM specification should require the AIRM conformance?The Information Definition specification? The Service Description specification? Or both? The answer may be crucial to handling the CR.

outcome: 

• This will be further discussed during F2F.

Task Conformance assessment

Agenda point for F2F (where someone from SWIM Governance Implementation Project will present the principles of SWIM Compliance)

Added example for Donlon: Conformance assessment - Donlon example.

outcome: 

• not discussed.

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 MeetingsMeeting Notes.
Next Webex on Tu 23 Apr 14:00.

Combined F2F

on 21-23 May

Agenda

• Day 1 (1300-1700) - SITCOM
• Day 2 (0900-1700) - SWIM Education Session (combined SSCONE, SITCOM & SWIM-TEC)
• Day 3 (0900-1600) - SSCONE

About SSCONE day

• Question: someone interested in presenting something? In sharing experience?
  Agenda points == (make visible the existing page)
  • Possibly on the suggested use of some MET-GATE services.

Close meeting