Venue
Date: 23rd May'19 0900-1600
ECTL HQ ; Neptune Room
Agenda
| title | content | start | duration | |
|---|---|---|---|---|
| 1 | Introduction | Welcome; Round table; Agenda | 09:00 | 20' |
| 2 | Advice on CR | finalise
| 1h30' | |
| 3 | Conformance to the spec | 1) assessment | 30' | |
| 4 | 2) tooling | 30' | ||
| 5 | 3) SWIM compliance | 30' | ||
| 6 | Basic steps to new services | Service Oriented process | 20' | |
| 7 | Interoperability Architecture | 20' | ||
| 8 | Service Identification document | 40' | ||
| 9 | Sharing experience | MET GATE services By Steffen... TBC | 1h? | |
| 10 | ||||
| 11 | Next steps | List potential tasks (also see FAQ) Define priorities How to make interesting? | 30' | |
| 12 | AOB | 10' | ||
| 13 | Close | 16:00 | - |
Breaks
- coffee am - 20'
- lunch - 1h
- coffee pm - 20'
- ** check ppt last F2F
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Welcome
Objectives of this meeting are:
- share experience
- finalise advice on handling CR 168/1
- clarify the notions of conformance and compliance
- introduce to "basic steps" for a new service
- ?define next edition of the handbook?
Outcome:
Advice on Change Request to the specification
/wiki/spaces/SCOI/pages/59606015
==task row
Assess Conformance to the specification
Conformance assessment
Task | Description | Status | Priority | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| /wiki/spaces/SCOI/pages/59605293 |
| yes |
outcome 2019-01-28 SSCONE webex:
- There should be a focus on interoperability. In particular: Is the service sufficiently described? Is the description valid? Is it complete?
Conformance tooling
SWIM Compliance (from SWIM Gov IP)
The goal is to make clear the difference between conformance and compliance. Accordingly the presentation should focus on the principles, not the technical details.
I’m expecting a 15-20' presentation on the principles. Allowing for 10' questions and answers.
Basic steps for new services
Feedback from -2019-05-22 "Get into SWIM" Session
- perception,
- sharing the material
- improvements
Service Orientation Process
Interoperability Architecture
Service Identification Document (SID)
"The purpose of this Service identification document is to provide a description of services identified for A-CDM. The purpose is not to provide a complete design description of each service, but rather to describe the services to such a level that it is possible to make decisions on subsequent activities such as Design and Implement."
Sharing experience
MET-GATE services example...
Use of specifications
Progress on use of the spec?
Difficulties encountered?
Examples to be shared, or to work on?
Other active tasks and open actions
- align (copy) active tasks list before meeting
Tasks & Priorities
The status of potential tasks is maintained in SSCONE Tasks.
Go over the list of tasks and define priorities.
Listen to additional tasks / needs.
Outcome:
Next meetings
Regular webexes
- keeping mtg 3/6?
Next F2F ?