SDMX 3.0: implement "feature 007 Semantic versioning" for SDMX-JSON messages

[dosse]

https://metadatatechnology.com/sdmx3/designs/007/approved/SDMX%203.0(.0)%20Semantic%20Versioning%20%20Dependency%20Management%20v7.docx

[dosse]

In order to support the new requirement, it is proposed to:

structure message changes:

• extend the version definition of maintainable artefacts as defined by SDMX-SemVer (see below)
• remove the isFinal artefact property
• extend the version definition of all references to maintainable artefacts as defined by SDMX-SemVer (see below)

data message changes:

• extend the admissible version specification of dsds, dataflows and provision agreements in data messages as defined by SDMX-SemVer (see below)

The following version formats are possible:

• no version at all (the artefact or referenced artefact is not versioned)
• "x" or "x.y" (to support previous version numbers) all such artefacts are now considered "nonFinal"
• "x.y.z" (immutable artefacts)
• "x.y.z-ext" (mutable artefact)

The following additional version formats are also possible in all references to maintainable artefacts in structure messages :

• "x+.y.z", "x.y+.z", "x.y.z+" (immutable artefacts with one wildcard "+")

Notes:

• "x", "y" and "z" stand for version part numbers (integers) major, minor and patch
• "-ext" stands for the version extension part and "ext" can be any extension name (for its definition see the original SDMX SemVer document (Backus–Naur Form Grammar for Valid SDMX 3.0(.0) Semantic Versions) in the ticket description)

[dosse]

Released