Versions Compared

Version Old Version 5 New Version Current
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
children
Excerpt

This page gives the JSON Schema for Service Descriptions.

JSON Service Description Schema

Info
titleCurrent Schema

The current schema in use can be found at: https://reference.swim.aero/resources.html

Tip
titletip

Guidance for producing service descriptions using this schema is available at Guidance for JSON service descriptions

Panel
borderColorlightgrey

Table of Contents

Scenario specific schema

Other versions of the service description 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 schema it will be valid against the current schema in use.

History

details the service metadata schemas. The schema support the following artefacts:

  • service descriptions
  • service definitions
  • "candidate" service descriptions
Panel
borderColorlightgrey

Table of Contents

Versions

In support of service descriptions

versiondetailslinksupporting 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.jsonExample service description
v0.0.3d

initial version used by the SWIM Registry

Note: This version is no longer used.



In support of service definitions

versiondetailslinksupporting material
v2.0.0initial version used by the SWIM Registryhttps://github.com/eurocontrol-swim/service-metadata-schema/blob/v2/definition/DEFINITION-V2.jsontbd

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).