| Excerpt |
|---|
JSON Schema for Service Description |
| Tip | ||
|---|---|---|
| ||
| Excerpt | ||
This page details the service metadata schemas. The schema support the following artefacts:
|
| Panel | ||
|---|---|---|
| ||
|
JSON Service Description Schema
| Info | ||
|---|---|---|
| ||
The current schema in use can be found at: https://reference.swim.aero/resources.html |
Other versions of this schema have been prepared to help users. They have the same structure (same fields, same name, same organisation) as the current schema in use. However, they contain validation rules to be used in specific scenarios. If your JSON service description is valid against these schemas it will be valid against the current schema in use.
- SWIMRegistrySchema_v0.0.3f.json - This has validation rules to check alignment with the requirements of the SWIM Service Description Handbook.
History
childrenVersions
In support of service descriptions
| version | details | link | supporting material |
|---|---|---|---|
| v2.0.0 | Updated to reflect the latest version of the SWIM service description specification. | https://github.com/eurocontrol-swim/service-metadata-schema/blob/v2/description/COMPLIANT-V2.json | Example service description |
| v0.0.3d | initial version used by the SWIM Registry Note: This version is no longer used. |
In support of service definitions
| version | details | link | supporting material |
|---|---|---|---|
| v2.0.0 | initial version used by the SWIM Registry | https://github.com/eurocontrol-swim/service-metadata-schema/blob/v2/definition/DEFINITION-V2.json | tbd |
The purpose of the service metadata schemas
The service metadata schemas provides a structured notation for describing services.
They aim to
- facilitate harmonisation in describing services and
- facilitate easier processing by systems. For example, the European SWIM Registry has developed functions to import and export service descriptions that use the schema.
The schemas
- benefit service providers in facilitating the production of service descriptions, including importing in registry and conformance to the SW specifications
- benefit service consumers with enhanced harmonisation of service descriptions
- allow service descriptions to be processed by systems - this includes upload into a system, exchange between systems and transformation (e.g. to service overview).