Ongoing discussions within the SWIM Community of Interest
2019-10-07 SITCOM-SSCONE webex
Venue
Date: 07 Oct 2019 1400-1530
webex link: https://eurocontrol-conferences.webex.com/join/wvanhamm | 706 775 248
Agenda
Title | start | duration | |
|---|---|---|---|
| 1 | Welcome | 14:00 | 10' |
| 2 | Common elements | 14:10 | 30' |
| 3 | SITCOM tasks | 14:40 | 20' |
| 4 | SSCONE tasks | 15:00 | 25' |
| 5 | AOB | 15:25 | 5' |
| 6 | Close | 15:30 | - |
Welcome
Objectives of this meeting are:
new policy with Confluence access
Handbook Publication
Decide on December F2F
progress on SITCOM & SSCONE tasks
Common elements
Feedback from previous meetings
This is the first joint meeting. Previous meetings were not yet combined. The notes can be found in 2019-07-09-SITCOM and in 2019-07-15 SSCONE webex.
New policy with Confluence access
Changes in SSCONE area
some pages and pagetress will not become public, and stay with account access
Task pages: clearly mention the work is on going.
Meeting pages: anonymise (except for the presentations given at F2F) → remove attendance list (recently added)
SWIM Supporting Material v1.0.0 Alpha
Changes in SSCONE Handbook area
Futher preparation to become public
move pages not visible by public from Handbook area as tasks within the SSCONE area
Decide on F2F
Question: Should we hold a SWIM COI F2F on the day after the workshop (12 Dec)?
outcome:
A SWIM COI F2F will be organised. It will include plenary and SITCOM subjects. See tentative agenda at 2019-12-12 SWIM COI F2F.
Update on SITCOM tasks
The updated task list is at SITCOM Tasks
Review the changes marked as "implemented and to be reviewed" on https://ext.eurocontrol.int/swim_confluence/display/SCOI/Maintain+supporting+material. Email sent on 10th September to detail the changes. No comments received so the edits are accepted. The status of the items will change to "completed".
Discuss item 10:
https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-005+Information+definition+scope
After simplifying the scope statement it is now possible that it is too simple. It does not say what information is include. Basically it says "this scope of the service is this service"...
We need to agree the correct scope
Update on SSCONE tasks
The updated task list is at SSCONE Tasks.
Feedback on actions
The discussions on comments from Renato lead on a series of actions.
leading to updates to the handbook
SWIM-SERV-001 Description coverage : guidance has been added for the case of composed services
SWIM-SERV-003 Define abbreviations : a link will be added to a new webpage with the reference material. This has impacted every requiremenbts linking to reference material
SWIM-SERV-023 AIRM conformance : guidance has been added, 1° to make clearer the role of 023 vs 022, 2° to clarify the meaning of conformance in this context
leading to input to the European SWIM Registry CCB
SWIM-SERV-006 Service identification: The comment proposes have a URI to refer to the service description, as in following proof of concept https://airservicesaustralia.github.io/registry/service/M001.html.
SWIM-SERV-009 Service categories: The comment proposes to include both a label and a code (URI), as in the proof of concept above. Eg label = Meteorological Observation, code = urn:aero:airm:1.0.0:ConceptualModel:Subjects:Meteorology:MeteorologicalObservation
Other tasks
Task | Outline & status | Note | Priority |
|---|---|---|---|
Service Identification Document (SID) | Making the "A-CDM services identification document" available as an example. See -Service Identification Document Comment : This would be a good idea to work on. It relates to the Basic steps to new services, specifically to the identification step in the Service Orientation Process. It could result in a template for use by others.
outcome: No review comment. The SID example is decided to be good as is.
| can be closed | 2 |
outcome: No direct comment on the proposal. Comments open until newt webex (18/11).
| for your review |
| |
Related to requirement SWIM-SERV-009 Service categories
outcome: not discussed
| waiting freedback from Registry development | 2 | |
To be update with some of the questions raised during the meeting 2019-05-23 SSCONE F2F
outcome: not discussed |
| 2 | |
Comment on Conformance assessment | Receveid comment about "Recommended requirement not satisfied" within Conformance assessment report I would personally prefer to use a different symbol for this status. I would recommend the usage of a triangular sign with an exclamation mark in it. You can activate this in Confluence by typing ( ! ) without the spaces. The result would be Question: Is it ok to use instead of in conformance assessment. Impact on handbook: Conformance assessment report; Conformance assessment - Donlon example
outcome: No direct comment on the proposal. Comments open until newt webex (18/11).
| for your review |
|
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-SITCOM Meetings. Next Webex on 18th Nov 1400: combined SITCOM & SSCONE.
Note in particular
9-11 December (09/12 1330 - 11/12 1230): 2019-12-09 to 11 SWIM Service Implementation Workshop
11 Dec pm: AIRM CCB
12 Dec (0900-1600): 2019-12-12 SWIM COI F2F
Close meeting