Ongoing discussions within the SWIM communities of interest

2023-01-30-SSCONE-SITCOM

Owned by WILSON Scott
Last updated: 2023 Jan 31

Agenda 

Item

Time
Welcome1400

Update on tasks


Any other business


Close1530





Welcome

Objectives of this meeting are:

  • work on tasks

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 and approach for withheld endpoints. We will wait on updated SWIM Registry documentation on the fields that can be hidden before reactivating our task.
Support
The interoperability goal
  • We checked if the Registry has a "flag" for conformance checking based on req-120. 
    • It has a lifecycle status field coming from the SWIM Governance Implementing Project.
    • There is no conformance checking flag as such.
  • There is not much more SSCONE-SITCOM can do in this area so the action will be closed.
FAQ
  • Questions to be answered (send suggestions to the group):
    • How do I describe a service that uses GraphQL? Some example of services that use GraphQL will be presented at a future meeting so that we can begin to see how it fits into the SWIM specifications.
Service Metadata Schema

Change made to the draft v1.0.0 service metadata schema to add support for more than one reference to an information definition.

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

Example of SWIM-SERV-290 using Service Metadata Schema
"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"
    }]
   }

Other examples will also need to be updated to reflect the use of the array.

SWIM service ecosystem
Service Design Activities
  • We have no where to publish pages on service design as of yet. What approach is preferred?
    • The group discussed this briefly. It is happy to engage more in this. It would be an expansion in our scope so there is a need to inform IMT.
  • 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.
/wiki/spaces/SCOI/pages/59606413
  • More meetings focusing on FF-ICE services and AMQP are needed.
    • Initial contact with the FF-ICE group made in order to get an understanding. Hopefully there will be an action plan by the next progress meeting.
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”.
    • The role of the portfolio was clarified: it is a consolidated list of service definitions that can drive the SOA.
    • The task will be better detailed at the next meeting. The first step is to identify what resources are available in order to start the activity.
    • The group discussed this briefly. It is happy to engage more in this. It would be an expansion in our scope so there is a need to inform IMT.

Any other business

  • Service Discovery Service. There is a new ICAO IMP Job Card concerning registry interoperability. It will look at service metadata taking into account e.g. our work on service descriptions, the SDCM and the new SMXS. The group will be informed of the activities on this to see where we can contribute ideas.

Next meetings

Meeting schedule is maintained at SSCONE-SITCOM Meetings. 

Next progress meeting is 13 March 2023.


Status: Working Material