| 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 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 |
| 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.
|
| Service Metadata Schema | - News on Service Discovery Service?
|
| SWIM service ecosystem |
| Service Design Activities | - We will inform IMT on 18-19 April of the intention to look more at this.
- 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: CodeApplicationMessageExchangePatternTypeAdded guidance on the use of CodeApplicationMessageExchangePatternType e.g. PUBLISH_SUBSCRIBE etc. In general would expect on this page also categorisation related informationfor services built around AMQP 1.0.
|
| Service Categories - Service Type | - Arrange meetings focusing on FF-ICE services and AMQP are needed.
|
| Service Portfolio | - We will inform IMT on 18-19 April of the intention to look more at this.
- ...introduce the resources are available in order to start the activity.
|