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 7
Next »
Item | Time |
|---|
| Welcome | 1400 |
Update on tasks |
|
Any other business |
|
| Close | 1530 |
Objectives of this meeting are:
- discuss next year's arrangements
- work on tasks
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 | |
| Service Descriptions supporting material | - Comments to be resolved (send suggestions to the group):
- SWIM-SERV-240 Service interfaces - If the fully qualified network address is not provided for e.g. , what text should be used?
- The example will remain as it is for the moment until the registry CCB gets back with an approach (see below).
|
| Support |
| The interoperability goal | - Good documentation on the need for interoperability is needed. What should we do?
|
| FAQ | - Questions to be answered (send suggestions to the group):
- How do I describe a that uses GraphQL?
|
| SWIM service ecosystem |
| Standardised Implementations | |
| Service Categories - Service Type | - Decide if mature enough to publish on reference website?
- Dedicated meetings took place for this and the end result is now available. It is felt to be good enough to use for now but it is accepted that new values will be added as .
|
| Service Portfolio and Service Categories - Service Type | - Open request:
- provide examples of the 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.
- For 2023?
|
| Registry changes | - The registry CCB was asked if it is possible to have authenticated and non-authenticated users. That would allow certain fields to be only seen by authenticated users.
- Response: This is, in fact, the case already. It is possible to toggle the visibility of fields using the HTML based editor. This is often missed. Better documentation has been requested.
- Non-authenticated users could see something like the /wiki/spaces/BOK/pages/59409601 fields only.
- Response: The list of fields that can be toggled will be added to the documentation.
- Note: This does not help when the service provider wants to hide the endpoint from everyone including authenticated users.
|
Meeting schedule is maintained at SSCONE-SITCOM Meetings.
Next progress meeting is 30 January 2023.