AIXM versioning policy
The maintenance and evolution objective is achieved through the release of new AIXM versions. These include both the core specification components (UML model, XML Schema, Temporality Concept) and also the associated documents (GML Profile, Feature Identification and Reference, etc.)
Future AIXM versions will be designated as follows:
- A new X.y.z release (such as 6.0.0) – introducing major conceptual changes, such as re-factoring a large part of the UML model, the use of a different data encoding syntax, etc. Forward data mapping is possible at the transition time but not on a continuous basis. Backward data mapping is limited.
- A new x.Y.z release (such as 5.2.0, 5.3.0) - introducing new features, properties (data elements) and capabilities, in support of new/changed operational concepts. These regular releases are aligned where necessary with the ICAO two-year cycle for SARPS updates. The data encoded according to the previous version can be fully forward mapped into the new version. Backward data mapping may be achieved through the use of extensions. Features and properties that are no longer used are marked as “Deprecated” and will effectively disappear in the next 5.#.0 version;
- A new x.y.Z release (such as 5.1.2, 5.2.1) - limited to bug fixing, clarification of definitions, documentation and minor changes for which the data can be fully forwards/backwards mapped between consecutive versions.
A proposal for aligning the versioning policy between the AIXM, FIXM, iWXXM, AIRM is being developed and will be submitted to the ICAO Information Management Panel in May 2017. This includes specific terms for each of the three version levels mentioned above (for example, Major/Minor/Patch, etc.) Once a common terminology is agreed, it will also be used for the AIXM version levels.