Working towards the next version of the SWIM Supporting Material
Page History
Excerpt |
---|
Released JSON Schemas, and related documents |
Panel | ||
---|---|---|
| ||
|
JSON Service Description Schema 0.0.3
The schema defined by Registry is v0.0.3b. It is used for Operational Registry since March 2020.
Info | ||
---|---|---|
| ||
The schema v0.0.3b lacks validation capability, so that new editions have been defined with validation capability. All editions share the same structure (same fields, same name, same organisation) they do however differ by validation capability. As the rules differ by serviceType, there may be three separate schemas per edition. |
Tip | ||
---|---|---|
| ||
Take the latest edition corresponding to your service type (compliant, candidate or definition) to allow for enhanced validation capability. |
version | version (date) | description |
---|---|---|
v0.0.3f | 20/07/20 | SWIMRegistrySchema_v0.0.3f.json - improved instance validation
This results in 1 schema. |
v0.0.3e | 15/04/20 | SWIMRegistrySchema_v0.0.3e.json - improved instance validation
This results in 3 schemas. |
v0.0.3d | 07/04/20 | Schema allowing to easily check a description of serviceType SWIM_CANDIDATE for the rules SWIM_COMPLIANT. |
v0.03d | 19/03/20 | SWIMRegistrySchema_v0.0.3d.json - improved instance validation
As mandatory fields are different according to the 3 service types, this results in 3 schemas.
The process and the implemented checks are explained in document Content Validation Criteria-for schema 3d.docx
|
v0.0.3c | 03/03/20 | SWIMRegistrySchema_v0.0.3c.json - improved instance validation
|
24/02/20 | SWIMRegistrySchema_v0.0.3b.json - used for Operational Registry (Mar 2020)
|
Incorrect, but kept for traceability reasons
v0.0.3 | Jan 2020 | Note on 24/02/20: This version is an incorrect release, as was not based on latest draft
|