In 2013 DDEX moved to a regular update cycle. This means that DDEX will wait for at least one year before issuing a new version of a particular standard.
There are two exceptions to this rule, however:
- Should an error be found in a DDEX standard, DDEX will publish a "corrigendum" as soon as possible.
- Should an urgent business requirement exist, DDEX may issue an interim version called a "Public Draft". These Public Drafts have standard quality but will be replaced once the next full version is published.
DDEX will make sure that two such versions are "forward-compatible" (i.e. the older versions can be processed with an implementation based on the newer version). This specifically applies to Public Drafts but not to corrigenda.
In cases where such compatibility cannot be achieved, a new major version number will be used.
- DDEX will wait for at least one year to issue a new version of a particular standard (e.g. before moving from version 3.5 to version 3.6)
- If forward-compatibility has to be broken, the major version number will be increased and the minor version number reset to zero (e.g. moving from 3.5 to 4.0)
- DDEX may issue a corrigendum whenever a bug is found (e.g. correcting version 3.5 to become 3.5.1)
- DDEX may issue a "Public Draft" to cater for urgent business requirements (e.g. issuing a "Public Draft of 3.6" when version 3.5 has been published in the last 12 months)
- While DDEX encourages implementers to always use the latest version, no DDEX standard will be removed from the DDEX website. There are two exceptions to this rule:
- When a corrigendum is issued, the corrected standard will be removed from the DDEX website
- Public Drafts will be removed as soon as the next "full" standard is published