Agenda
Item | Time |
---|---|
Welcome | 1400 |
Update on tasks | |
Any other business | |
Close | 1530 |
Panel | ||||
---|---|---|---|---|
| ||||
|
Welcome
Objectives of this meeting are:
- work on tasks
Update on tasks
Task list
The updated task list is at SSCONE-SITCOM Tasks.
Completed tasks
- tbd
Ongoing tasks
- /wiki/spaces/SCOI/pages/59605888
- See [WIP] SWIM Service Description Handbook v2.0
- Process comments
- Remove The comments received by the 24th June were reviewed. See 2022_06_24_supporting_material_comments.xlsx. Some resolutions have lead to extra work and the supporting material will be updated once the resolution is known.
- Some actions in /wiki/spaces/SCOI/pages/59605888 were can be marked as completed.
- It was agreed to remove the "WIP" status and enter maintenance phase.
- The focus should now be on standardised implementations as most remaining actions/comments/best practices depend on it.
- Service Metadata Schema
- Standardised Implementations.
- OGC services
- AMQP
- Service Categories
- New category See: https://github.com/eurocontrol-swim/service-metadata-schema/blob/sds-upgrade/compliantdescription/SRV-CMPDESC_SCHEMA.json
- New category See: https://github.com/eurocontrol-swim/service-metadata-schema/blob/sds-upgrade/compliantdescription/SRV-CMPDESC_SCHEMA.json
- New: Best practices to harmonise content of service description fields.
- Process comments
- Start work on standardised implementations
- Process comments
- The comments received by the 24th June were reviewed. See 2022_06_24_supporting_material_comments.xlsx. Some resolutions have lead to extra work and the supporting material will be updated once the resolution is known.
- A new structure has been put in place for the github repository and the schemas have been renamed.
- At the moment:
- service description schema is finished
- service definition schema will start - it will be a separate schema
- service candidate scheme will be derived from the service description schema by relaxing the number of required fields. It will be a separate schema.
- The schemas will be separate but the structures are aligned where feasible.
- Validation of files against the schemas can be done using various tools. No specific validation suite is foreseen.
- /wiki/spaces/SCOI/pages/59605387.
- Some rows have been marked as "Review and accept?". The group is asked to review these by the next meeting to ensure the proposed solution is accepted.
- Some rows have been marked as "Review and accept?". The group is asked to review these by the next meeting to ensure the proposed solution is accepted.
- See [WIP] SWIM Service Description Handbook v2.0
- SWIM service ecosystem
- Documenting the use of standardised implementations.
- Start work on standardised implementations based on the comments and input already received.
- The skeleton material will be available by the next meeting. The group will be informed as it is created.
- Service Categories
- The group is asked to review the mature schemes by the next meeting. If accepted, they will be published on the reference site:
- CodeDocumentType
- CodeAccessAndUseConditionType
- CodePrimitiveMessageExchangePatternType
- CodeServiceInterfaceBindingType
- CodeServiceValidationType
- quality of service
- security mechanisms
- information exchange models
- data formats (if needed in the end)
- Also:
- A new category (/wiki/spaces/SCOI/pages/59606413) has been added based on service type. This grew out of discussions in A3SG. It is used as a way to identify similarities in the services being discussed. We should discuss this at the next meeting. It overlaps with the discussion on standardised implementations.
- Added -
We were request to move items out of the Service Metadata Schema to the reference.swim.aero. These were:
DocumentType, Service Interface Bindings, CodeServiceValidationType, primitive MEPs, AccessAndUseConditionsType
- The group is asked to review the mature schemes by the next meeting. If accepted, they will be published on the reference site:
- Service definition template
- This has been added. It is draft material to help in the various *3SGs. We should discuss this at the next meeting.
- Documenting the use of standardised implementations.
Any other business
none
Next meetings
Meeting schedule is maintained at SSCONE-SITCOM Meetings.
Next progress meeting is 15August 5September 2022.