Venue
Date: 23rd May'19 0900-1600
ECTL HQ ; Neptune Room
Agenda
Item | Title |
Content |
Time |
0 |
Welcome | Welcome |
, Agenda |
, Introduction | 0900 |
1 | Change Request | Advice on handling CR 168/1 | 0920 |
2 | Sharing experience | Applying the spec to a Meteorological Data Service (MET Service) |
MET GATE services
(By Steffen Beringer) | 1020 C |
3 | Conformance to the spec | Terminology, Assessment, Resources. | 1150 L |
4 | SWIM Compliance | SWIM compliance (By Oliver Krüger) | 1320 |
5 | Basic steps to new services | Service Orientation Process, Interoperability Architecture, Service Overview |
Service Identification Document | 1400 | |
6 | Next steps | Potential tasks, Priorities |
. Voice your interests | 1440 C | ||
7 | Any other business | 1540 | |
- | Close | 1600 |
C & L: Coffee and Lunch Breaks are indicative.
| 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
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
Draft material from ICAO IMP . + other (SID)
Service Orientation Process
Interoperability Architecture
Service Overview
A "subset" of the service description. A few small gaps to be filled.
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
Open point for anyone that wants to share some experience relative to the use of the specifications. Including progress, difficulties, examples.
Applying SWIM Service Description Spec to a Meteorological Data Service (MET Service)
About the Service Description for the METAR Service and some background information.
- Meteorological data services (MET services) within SWIM
- Use case METAR service
- Describing the service using SWIM Service Description Spec
- Taking advantage of a XML scheme for Service Description
- How to assess conformance? Using a template for a conformance matrix
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 ?