Versions Compared

Version Old Version 8 New Version 9
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

The same 6-weekly schedule is kept. Meeting updates have been sent.

Update on tasks

Completed tasks

Ongoing tasks

TaskNotes
Artefacts to describe services
Service Definitions supporting material
  • No updates required.
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?
      • There is now a need to clarify if the use case for hiding the endpoint is still valid given the existence of authenticated users in the registry.
Support
The interoperability goal
  • We should check if the Registry has a "flag" for conformance checking based on req-120. 
    • It has a lifecycle status coming from the SWIM Governance Implementing Project.
    • There is no flag as such.
FAQ
  • Questions to be answered (send suggestions to the group):
    • How do I describe a service that uses GraphQL?
Service Metadata Schema

Change

request

made to add support for more than one reference to an information definition.

Main reason is use of

The justification was to allow those who use an *XM model and one or more of its extensions to refer to them all.

This will impact the examples used in our supporting material.

schema

oldnew
"informationDefinition": {
  "description": "A formal representation of information concepts or data concepts. [SWIM-SERV-290]",
  "oneOf": [
{
  "type": "object",
  "properties": {
"reference": {
  "$ref": "#/definitions/Reference"
}
  }
},
{
  "type": "array",
  "items": {
"$ref": "#/definitions/InformationDefinition"
  },
  "minItems": 1
}
]		"informationDefinition": {
  "description": "A formal representation of information concepts or data concepts. [SWIM-SERV-290]",
  "oneOf": [
{
  "type": "object",
  "properties": {
"reference": {
  "type": "array",
  "items": {
  "$ref": "#/definitions/Reference"
},
"minItems": 1
}
  }   
},
{
  "type": "array",
  "items": {
"$ref": "#/definitions/InformationDefinition"
  },
  "minItems": 1
}
]

example becomes

Code Block
languagejs
"informationDefinition": { 
    "reference": [{
     "description": "Aeronautical Information Exchange Model (AIXM) 5.1.1",
     "url": "https://www.aixm.aero/schema/5.1.1/AIXM_Features.xsd"
    },
    {
     "description": "Event Extension for AIXM 5.1.1",
     "url": "https://www.aixm.aero/schema/5.1.1/event/version_5.1.1-i/Event_Features.xsd"
    }]
   }
SWIM service ecosystem
Service Design Activities
  • We have no where to publish these as of yet. Comments were made directly on the page. What approach is preferred?
  • Still to do: To describe an implemented service that uses AMQP 1.0 in an harmonised way it would be good to visit the categorisation schemes and indicate which of the elements in the relevant schemes are expected to be used. For instance: CodeApplicationMessageExchangePatternType. PUBLISH_SUBSCRIBE etc..in general would expect on this page also categorisation related information.
Service Categories - Service Type
  • More meetings focusing on FF-ICE services and AMQP are needed.
Service Portfolio
  • 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”.

    • What approach is preferred?

Any other business

  • none

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

Next progress meeting is 13 March 2023.