Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 17
Next »
Item | Time |
|---|
| Welcome | 1400 |
Update on tasks |
|
Any other business |
|
| Close | 1530 |
Objectives of this meeting are:
| Task | Notes |
|---|
Artefacts to describe services
|
| Service Definitions supporting material | - no updates yet. A3SG will start to use the templates soon. (See
https://ext.eurocontrol.int/swim_confluence/display/ASW/Identified+Services for the work they are doing.) |
| Service Descriptions supporting material | - Comments to be resolved
- SWIM-SERV-240 Service interfaces - If the fully qualified network address is not provided for e.g. security reasons, what text should be used?
- If you have ideas please send them to the group.
|
| Support |
| Conformance/compliance assessment report templates | - decide if we want to engage in preparing templates like this.
- initial drafts:
|
| FAQ | - Questions to be addressed:
- How do I describe a that uses GraphQL?
- If you have ideas please send them to the group.
|
| SWIM service ecosystem |
| Standardised Implementations | - comments to review. Seem to be in two forms:
- ensuring proper documentation in a service description
- the design/implementation related comments
- positioning: service design/implementation v service description
- do we want section called "supporting service activities" or covered as part of service definition work..?
- 20191104 Controlled verbs for Application Functions V.1.1.pdf
- can be added to supporting material as examples.
- See also the ISRM
|
| Service Categories - Service Type | - Discuss - explain, understand, plan.
|
| Service Portfolio and Service Categories - Service Type | - provide examples of the typical exchanges that can be mapped to a given category e.g. what falls under “Capacity, demand and flow information”
|
Registry
- Integrating the new schema. Changes to the Registry will be presented at the next meeting so we can assess any impact on us.
Meeting schedule is maintained at SSCONE-SITCOM Meetings.
Next progress meeting is 11 November .