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 6
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
The same 6-weekly schedule is kept. Meeting updates have been sent.
| 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?
- 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 that uses GraphQL?
|
| Service Metadata Schema | Change request to add support for more than one reference to an information definition. Main reason is use of an *XM model and one or more of its extensions.
This will impact examples.
| old | new |
|---|
"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
}
] |
|
| 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?
|
| Service Categories - Service Type | - More meetings focusing on FF-ICE services and AMQP are needed.
|
| Service Portfolio | |
Meeting schedule is maintained at SSCONE-SITCOM Meetings.
Next progress meeting is 13 March 2023.