|
No guidance provided.
The guidance concerns JSON Schema v0.0.3 (see Schema releases).
|
Rules expressed for the cases as defined in Registry URD.
|
Two cases must be distinguished depending on whether code example is being provided or not.
Within "serviceDocument" field (itself within "serviceDescriptionReferences" field) create one or more instances of Document with type CODE_EXAMPLE.
See Guidance on serviceDocument on how to fill in documents.
Use document type CODE_EXAMPLE even for message examples. Usage of document type "MESSAGE_EXAMPLE is deprecated. |
Nothing to be mentioned in the JSON service description
"serviceDocument": [ { "documentType": "CODE_EXAMPLE" "title": "Example of messages", "version": "1.0", "description": "A set of message examples", "reference": "public:/2019-09/MessageExamples.txt", }, ... ] |
A complete JSON example is available in page JSON example - Donlon TOBT Setting service description.