Versions Compared

Version Old Version 6 New Version 7
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Agenda 

Item

Time
Welcome1400

Update on tasks


Any other business


Close1530
Panel
borderColorlightgrey

Table of Contents
maxLevel2


Welcome

Objectives of this meeting are:

  • discuss next year's arrangements
  • work on tasks

Next year

Keep to same 6-weekly schedule?

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

Update on tasks

Completed tasks

-

Ongoing tasks

TaskNotes
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 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 approach (see below).
Support
The interoperability goal
FAQ
  • Questions to be answered (send suggestions to the group):
    • How do I describe a service that uses GraphQL?
SWIM service ecosystem
Standardised Implementations

  • Documenting the use of standardised implementations: Finish and decide if it can move to supporting material.

  • Design aspects - we have no where to publish these as of yet.
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 implementation continues.
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.
    • 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.

Any other business

  • Registry

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

Next progress meeting is 30 January 2023.