#

Project: { } | : Public Note
Created: | 15/11/2022 09:06:32
Modified: | 29/11/2022 17:26:20
Project: |
Author: | TB
Version: | 1.0
Phase: | 1.0
Status: | Proposed
Complexity: | Easy
Difficulty: |
Priority: |
Multiplicity: |
Advanced: |
UUID: | {3FD53FB1-5D14-4f8f-B01E-C123C7D59226}
Appears In: | CommonExtension
The CommonExtension namespace is unusual in DATEX II because it remains open for addition during the lifecycle of one major revision of DATEX II.<br/>Specific namespaces may be added to DATEX II which each require new elements added to CommonExtension.<br/>The stability of CommonExtension elements is indicated by whether they appear in the Final or Draft packages.<br/><br/>If a specific namespace requiring a CommonExtension element is stable i.e. it has reached its stable form for the major revision and will not be changed in a way that would break the DATEX II backwards compatibility guarantee - then the elements it requires in CommonExtension are placed in the "Final" package and the backwards compatibility guarantee will apply.<br/><br/>Sometimes a DATEX II namespace is published as work in progress - with prominent warnings - before it is considered to have reached its stable form for the major revision. Where such a namespace requires new elements in CommonExtension, those elements are placed in the "Draft" package. When one of the namespaces using those elements becomes stable, those elements will be moved to "Final" and backwards compatibility guarantees will then apply.<br/><br/>Depending on the platform-specific mapping, the distinction between Draft and Final may not have any manifestation in an encoding. The distinction is primarily a signal to modellers.<br/>