Panel

borderColor	lightgrey

Table of Contents

maxLevel	2

Welcome

Objectives of this meeting are:

Next year

Keep to same 6-weekly schedule?

Any tasks to be put on the list in addition to current tasks?

-

Task	Notes
Artefacts to describe services
Service Definitions supporting material	No updates required.
Service Descriptions supporting material	Comments to be resolved (if you have ideas please send them to the group): SWIM-SERV-240 Service interfaces - If the fully qualified network addressis not provided for e.g. security reasons, what text should be used? The example will remain as it is for the moment until the registry CCB gets back with an answer.
Support
The interoperability goal	Good documentation on the need for interoperability is needed. What should we do? Is this not enough: https://reference.swim.aero/what-is-swim.html?
FAQ	Questions to be answered (if you have ideas please send them to the group): How do I describe a service that uses GraphQL?
SWIM service ecosystem
Standardised Implementations	Finish
Service Categories - Service Type	Update and Finish
Service Portfolio and Service Categories - Service Type	Open request: provide examples of the typical exchanges that can be mapped to a given category e.g. what falls under “Capacity, demand and flow information”. Hopefully the work on service categories will help answer this.
Registry changes	The registry CCB should be asked if it is possible to have authenticated and non-authenticated users. That would allow certain fields to be only seen by authenticated users. Non-authenticated users could see something like the /wiki/spaces/BOK/pages/59409601 fields only.

Meeting schedule is maintained at SSCONE-SITCOM Meetings.

Next progress meeting is tbd