Venue
Date: 10 Dec 2018 1400-1530
Location: Webex https://eurocontrol-conferences.webex.com/join/wvanhamm | 706 775 248
Agenda
| Item | Title | Time |
|---|---|---|
| 1 | Welcome | |
| 2 | Feedback from F2F meeting | |
| 3 | Confluence tool | |
| 4 | Current tasks | |
| 5 | Priorities | |
| 6 | Discuss Change Request | |
| 7 | Next steps | |
| 8 | Any other business | |
| 9 | Close |
WW Do: Needs & FAQ
Agenda Items
Welcome
Objectives of this meeting are:
- progress on the handbook (incl feedback F2F, tooling, content)
- discuss Change Request on the specification
Feedback from 2018-10-03 SSCONE F2F
CoI name
SSCONE (SWIM Service Community of Interest).
Structure of the Handbook
The structure is approved. Alignment between SWIM Service Description Handbook and SWIM Information Definition Handbook in style and structure.
Example
Decision to use a common fictitious example (Donlon TOBT Setting example) for the supporting material of the 3 SWIM specifications.
Material from SWIM Governance Implementation Project
Sharing of material developed in the context of that project. As restrictions apply, the XML Schema is sent to those requesting.
Confluence tool
The SWIM instance of the Confluence tool is fully working. It contains 2 spaces for our use.
1) the SWIM Supporting Material space
Space dedicated to the Supporting Material for the SWIM foundational specifications.
The space contains the supporting material as approved by the SWIM CoIs, such as the SWIM Service Description Handbook from SSCONE.
The space is available to all in read mode (fully public).
SWIM CoI members can add review comments.
2) the SWIM Community of Interest space
Space dedicated to the SWIM CoI.
The space contains working material needed by the SWIM CoI, such as meetings, tasks, etc, such as the SSCONE - SWIM Service Community of Interest pages.
The space is internal to the SWIM CoI, available to all SWIM CoIs members in read mode, and to authors in write mode.
This page exists in that space.
As a SSCONE member, you should have received a mail inviting to join that space.
Managing material underwork
Material underwork should not be accessible to public.
Such material could
- either be stored in the SWIM CoI space and be moved to SWIM Supporting Material when ready for publication
- or be stored in the SWIM Supporting Material space, with specific naming and access (restricted to the SWIM CoI).
Depending on practicalities, either option might be used.
Current tasks
Finalise the initial handbook
1) Main changes in handbook since F2F
| page | change |
|---|---|
| SWIM Service Description Handbook | Updated and aligned to SITCOM |
| Introducing the specification | Updated according comments |
| requirements pages eg SWIM-SERV-009 Service categories | style updated to align with SITCOM |
| Some updates in relation with information definition | |
| Conformance matrix | many comments. Also Verification checklist for serv desc !! suppress the ++ |
2) Final review comments
3) Update according to review comments
4) Publication (pages where no agreement yet could be given a restricted access).
Review the Donlon example
/wiki/spaces/SCOI/pages/59606173 according a series of viewpoints. (see as well Info Defn)
(More examples from your side?)
Priorities
Q: Scott / Dennis: need expressed to discuss compliance (what is our position?)
Potential Tasks
source = FAQ ; Consultation; SSCONE kickoff survey (needs expressed)
Task | Description | Status | Priority |
|---|---|---|---|
| Conformance matrix vs Verification checklist for serv desc | What is actually needed and why? How is conformance assessed | ||
| List candidate topics beyond SSCONE's scope | |||
checklist with all steps for new services | |||
Discuss Change Request
Consulting the CoI in how to best handle the CR 168/1.
See /wiki/spaces/SCOI/pages/59606015.
Next steps
Meetings
Webexes: fixed agenda (as for SITCOM, every 6 weeks) vs ad hoc with doodle
F2F: around Mar-Apr 2019? Back-to-back with SITCOM? What about TI?
Summary of tasks
: what to address (see Prio)