Released JSON Schemas, and related documents
The schema defined by Registry is v0.0.3d.
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.
|In addition to the JSON, the structure and content of the schema can be viewed as a Model and as a text-only Glossary.|
Take the latest edition corresponding to your service type (compliant, candidate or definition) to allow for enhanced validation capability.
SWIMRegistrySchema_v0.0.3f.json - improved instance validation
This results in 1 schema.
SWIMRegistrySchema_v0.0.3e.json - improved instance validation
This results in 3 schemas.
Schema allowing to easily check a description of serviceType SWIM_CANDIDATE for the rules SWIM_COMPLIANT.
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
SWIMRegistrySchema_v0.0.3c.json - improved instance validation
SWIMRegistrySchema_v0.0.3b.json - used for Operational Registry (Mar 2020)
Incorrect, but kept for traceability reasons
Note on 24/02/20: This version is an incorrect release, as was not based on latest draft