Venue
Coordination: doodle poll by 28/11
Date: 10 Dec 2018 1400-1530
Location: Webex meeting Webex LINK
Input documents: if any
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 |
Invitation: [SWIM Service Community of Interest] - Project meeting
Agenda ...
Input material
- Sup Mat: initial pages!
- SCOI pages
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
Approved. Alignment between SSCONE & SITCOM in style and structure.
Example
Fictitious example common for the 3 SWIM specs: Donlon TOBT Setting example.
Material from SWIM Governance Implementation Project
material ... XML Schema ... (sent to those requesting)
Confluence tool
The SWIM instance of the Confluence tool is not fully working. It contains 2 spaces for our use.
the SWIM Supporting Material space
Space dedicated to the Supporting Material for the SWIM foundational specifications.
The space is available to all in read mode (fully public)
The space contains the supporting material as approved by the SWIM CoIs. In particular the SWIM Service Description Handbook from SSCONE.
the SWIM Community of Interest space
Space dedicated to the SWIM CoI.
The space is internal to the SWIM CoI, available to all SWIM CoIs members in read mode, and to authors in write mode.
The space contains working material needed by the SWIM CoI, such as meetings, tasks, or draft supporting material. In particular the SSCONE - SWIM Service Community of Interest pages.
This page exists in that space.
ACTION: You need to request access. HOW?
Managing material underwork
Material underwork should not be accessible to public.
Such material could
- either be stored in the SWIM CoI space nad be moved when ready for publication
- or be stored in the SWIM Supporting Material space, with access restricted to the SWIM CoI.
This depends how far practical. Will need be tried.
Currest Tasks
Initial handbook pages
review and confirm
Restrict access to pages where no agreement yet.
| 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 |
the Donlon example
(see as well Info Defn)
More examples from your side?
Priorities
Q: Scott / Dennis: need expressed to discuss compliance (what is our position?)
Discuss Change Request
Consulting the CoI in how to best handle the CR 168/1.
See /wiki/spaces/SCOI/pages/59606015.
Priorities & Next steps
content
: what to address
meetings
: webex and F2F (and when)
next year any way