| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Excerpt |
|---|
This page handles FAQ answers that are a work in progress. |
| Table of Contents |
|---|
Current FAQ
Updates
| Panel |
|---|
How do I describe a service that uses GraphQL?GraphQL is allowed using HTTP as the transport layer (i.e. using WS-Light binding in SWIM-SERV- |
250 SWIM TI Profile and interface bindings). GraphQL is an example of message-oriented service design (as opposed to operation-oriented or resource-oriented service design). |
For message-oriented services, the essential part is describing the data schema. GraphQL services do this in its own schema language “GraphQL Schema Language”. Work is being carried out at https://gist.github.com/kouak/8a13bb2730b91a797ca3354e56587f71 |
How is the quality of service documented at various service lifecycle stages?
How do I document quality of service in a service definition?
It can be left abstract. The service implementation that leads to a service description can give concrete parameters. This links to Formal Arrangements - Service Level Agreements.
It is acknowledged that the current requirements are abstract. Implementers have freedom to define their own concrete quality of service parameters. It is proposed to explain the options available to implementers using supporting material e.g. publishing exact figures or schedules of outages etc.