|
The recommendation is to provide a model view as it is useful in understanding a service. However, a model view is not mandatory in order not to exclude services for which no such model exists. |
Completeness | Check that: [ ] The service description includes or refers to a model view. [ ] The notation is declared. [ ] The model view fully covers the service interfaces. [ ] The model view fully covers the service operations. [ ] The model view fully covers the service behaviour. [ ] The model view fully covers the exchanged information. |
Consistency | Check that: [ ] The model view is consistent with the service description (e.g. same service operation name) |
Correctness | Check that: [ ] The model view is aligned with the declared notation. |
The following example shows the content as a table.
model view | public:/2019-09/TOBT_Model.xmi |
---|
The following example shows an extract of the content of a JSON file that conforms to the Service Metadata Schema
"references": { "serviceDocument": [{ "documentType": "SERVICE_MODEL", "title": "TOBT Model", "version": "1.0", "description": "XMI 2.1", "reference": { "url": "public:/2019-09/TOBT_Model.xmi" } }] } |
Complete examples are available at Example service description.