DataModelVersioning

WIS » Documentation » ManualUpdates » ManualCodes3 » dataModelStatus » DataModelVersioning

Definition of terms used in versioning of data models

The following terms are used to describe the status of releases of representations derived from data models. Release candidates are withdrawn at the time of publication of the next release candidate or the final release is published.

Notation for release identifiers

The notation for release identifiers is model a.b.cRCn.

model: The model being used (for example iwxxm).

a: the major release number. Schemas corresponding to different major release numbers are not backwards compatible.

b: The minor release number. Schemas with the same major release number are backwards compatible - that is information written using the earlier release can be read by applications using a later schema provided the application ignores the release number when interpreting the schema. Similarly, an application using an earlier schema can read information encoded in a later schema provided that the release identifier is ignored and any information appearing only in the later schema is skipped by the application.

c: The patch number. Schemas with the same major and minor release numbers are compatible and an application can process both provided the application ignores the release identifier.

RCn: The release candidate number. For models under development, the first public draft is RC1 and the final number is incremented for each release candidate produced. Approved models do not have a release candidate component in the release identifier.

Namespaces for XML representations

Using the notation of the release identifiers, namespaces used for XML schemas have the form http://schemas.wmo.int/model/a.b. Schema compatibility means that it is not necessary to distinguish between the patch-level releases in the name of the schema.

Schema locations

Schemas and associated files are available from http://schemas.wmo.int/model/a.b.cRCn

Terms used to designate the status of a release

The terms used to designate the status of a release are defined below.

unavailable: development of the release is not sufficiently advanced for a draft the schemas to be available.

snapshot: the release is currently under development - the highest numbered release candidate should be used.

experimental: the highest numbered release candidate has been copied to a folder labelled with the release identifier (without an RC component) intended for the approved release. The release candidate is considered stable enough for exchanging information on an experimental basis between centres that are prepared to take the risk of the resulting documents not conforming to the approved release. At this stage the folder corresponding to the approved release is in draft form and the contents of the folder may change during the approvals process. The release is considered to be stable, but modifications to the schemas are introduced in the release and may be modified during the approvals process, as may other components of the release.

submitted: the highest numbered release candidate has been submitted for formal approval.

pre-operational: the highest numbered release candidate has been copied to a folder labelled with the release identifier (without an RC component) intended for the approved release. The release candidate is considered stable enough for exchanging information on routine basis between centres that are prepared to take the risk of the resulting documents not conforming to the approved release. At this stage the folder corresponding to the approved release is in draft and the contents of the folder may change during the approvals process. The release is considered to be stable and the approvals process is not expected to change the schemas (although it is still possible for them to be changed during the approvals process).

approved: the release has been approved, but the implementation date has not yet been reached.

operational: the release has been approved through the WMO approvals procedures. The folder labelled with the release identifier (without an RC component) for the formal release is authoritative.

deprecated: the formerly approved release is no longer suitable for exchange of information. The model is retained to allow access to archived information.