Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.2
edited by Helena
on 2025/05/15 15:48
Change comment: Changed document title to [14 ANNEX Semantic Versioning].
To version 2.4
edited by Helena
on 2025/05/16 10:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= 14 ANNEX Semantic Versioning =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 14.1 Introduction to Semantic Versioning ==
4 4  
... ... @@ -6,9 +6,9 @@
6 6  
7 7  In systems with many dependencies, releasing new artefact versions can quickly become a nightmare. If the dependency specifications are too tight, you are in danger of version lock (the inability to upgrade an artefact without having to release new versions of every dependent artefact). If dependencies are specified too loosely, you will inevitably be bitten by version promiscuity (assuming compatibility with more future versions than is reasonable). Dependency hell is where you are when version lock and/or version promiscuity prevent you from easily and safely moving your data modelling forward.
8 8  
9 -As a very successful solution to the similar problem in software development, "Semantic Versioning" [[__semver.org__>>url:http://semver.org/]][[ >>url:http://semver.org/]]proposes a simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules make also perfect sense in the world of versioned data modelling and help to solve the "dependency hell" encountered with previous versions of SDMX. SDMX 3.0 applies thus the Semantic Versioning rules on all versioned SDMX artefacts. Once you release a versioned SDMX artefact, you communicate changes to it with specific increments to your version number.
11 +As a very successful solution to the similar problem in software development, "Semantic Versioning" [[__semver.org__>>https://semver.org/]] proposes a simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules make also perfect sense in the world of versioned data modelling and help to solve the "dependency hell" encountered with previous versions of SDMX. SDMX 3.0 applies thus the Semantic Versioning rules on all versioned SDMX artefacts. Once you release a versioned SDMX artefact, you communicate changes to it with specific increments to your version number.
10 10  
11 -**This SDMX 3.0(.0) specification inherits the original **[[__**semver.org**__>>url:https://semver.org/]]**[[ >>url:https://semver.org/]]2.0.0 wording (license: __[[Creative Commons >>url:http://creativecommons.org/licenses/by/3.0/]][[- >>url:http://creativecommons.org/licenses/by/3.0/]][[CC BY 3.0>>url:http://creativecommons.org/licenses/by/3.0/]]__[[)>>url:http://creativecommons.org/licenses/by/3.0/]] and applies it to versioned SDMX structural artefacts.** Under this scheme, version numbers and the way they change convey meaning about the underlying data structures and what has been modified from one version to the next.
13 +**This SDMX 3.0(.0) specification inherits the original **[[__**semver.org**__>>https://xwiki:semver.org]]** 2.0.0 wording (license: [[__Creative Commons - CC BY 3.0__>>https://creativecommons.org/licenses/by/3.0/]]) and applies it to versioned SDMX structural artefacts.** Under this scheme, version numbers and the way they change convey meaning about the underlying data structures and what has been modified from one version to the next.
12 12  
13 13  == 14.2 Semantic Versioning Specification for SDMX 3.0(.0) ==
14 14  
... ... @@ -43,78 +43,7 @@
43 43  
44 44  == 14.3 Backus–Naur Form Grammar for Valid SDMX 3.0(.0) Semantic Versions ==
45 45  
46 -|(((
47 -**<valid semver> ::= <version core>**
48 48  
49 -**| <version core> "-" <extension>**
50 -
51 -**<version core> ::= <major> "." <minor> "." <patch>**
52 -
53 -**<major> ::= <numeric identifier>**
54 -
55 -**<minor> ::= <numeric identifier>**
56 -
57 -**<patch> ::= <numeric identifier>**
58 -
59 -**<extension> ::= <dot-separated extension identifiers>**
60 -
61 -**<dot-separated extension identifiers> ::= <extension identifier>**
62 -
63 -**| <extension identifier> "." <dotseparated extension identifiers>**
64 -
65 -**<extension identifier> ::= <alphanumeric identifier>**
66 -
67 -**| <numeric identifier>**
68 -
69 -**<alphanumeric identifier> ::= <non-digit>**
70 -
71 -**| <non-digit> <identifier characters>**
72 -
73 -**| <identifier characters> <non-digit>**
74 -
75 -**| <identifier characters> <non-digit> <identifier characters>**
76 -
77 -**<numeric identifier> ::= "0"**
78 -
79 -**| <positive digit>**
80 -
81 -**| <positive digit> <digits>**
82 -
83 -**<identifier characters> ::= <identifier character>**
84 -
85 -**| <identifier character> <identifier characters>**
86 -)))
87 -
88 -**<identifier character> ::= <digit>**
89 -
90 -**| <non-digit>**
91 -
92 -**<non-digit> ::= <letter>**
93 -
94 -**| "-"**
95 -
96 -**<digits> ::= <digit>**
97 -
98 -**| <digit> <digits>**
99 -
100 -**<digit> ::= "0"**
101 -
102 -**| <positive digit>**
103 -
104 -**<positive digit> ::= "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"**
105 -
106 -**<letter> ::= "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" | "I" | "J"**
107 -
108 -**| "K" | "L" | "M" | "N" | "O" | "P" | "Q" | "R" | "S" | "T"**
109 -
110 -**| "U" | "V" | "W" | "X" | "Y" | "Z" | "a" | "b" | "c" | "d"**
111 -
112 -**| "e" | "f" | "g" | "h" | "i" | "j" | "k" | "l" | "m" | "n"**
113 -
114 -**| "o" | "p" | "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x"**
115 -
116 -**| "y" | "z"**
117 -
118 118  == 14.4 Dependency Management in SDMX 3.0(.0): ==
119 119  
120 120  MAJOR, MINOR or PATCH version parts in SDMX 3.0 artefact references CAN be wildcarded using "+" as extension:
... ... @@ -226,7 +226,7 @@
226 226  
227 227  One with named groups for those systems that support them (PCRE [Perl Compatible Regular Expressions, i.e. Perl, PHP and R], Python and Go).
228 228  
229 -Reduced version (without original SemVer "build metadata") from: [[__https:~~/~~/regex101.com/r/Ly7O1x/3/__>>url:https://regex101.com/r/Ly7O1x/3/]][[url:https://regex101.com/r/Ly7O1x/3/]]
160 +Reduced version (without original SemVer "build metadata") from: [[__https:~~/~~/regex101.com/r/Ly7O1x/3/__https:~~/~~/regex101.com/r/Ly7O1x/3/>>https://https:regex101.comrLy7O1x3https:regex101.comrLy7O1x3]]
230 230  
231 231  ^(?P<major>0|[1-9]\d*)\.(?P<minor>0|[1-9]\d*)\.(?P<patch>0|[1-
232 232  
... ... @@ -236,7 +236,7 @@
236 236  
237 237  And one with numbered capture groups instead (so cg1 = major, cg2 = minor, cg3 = patch and cg4 = extension) that is compatible with ECMA Script (JavaScript), PCRE (Perl Compatible Regular Expressions, i.e. Perl, PHP and R), Python and Go.
238 238  
239 -Reduced version (without original SemVer "build metadata") from: [[__https:~~/~~/regex101.com/r/vkijKf/1/__>>url:https://regex101.com/r/vkijKf/1/]][[url:https://regex101.com/r/vkijKf/1/]]
170 +Reduced version (without original SemVer "build metadata") from: [[__https:~~/~~/regex101.com/r/vkijKf/1/__https:~~/~~/regex101.com/r/vkijKf/1/>>https://https:regex101.comrvkijKf1https:regex101.comrvkijKf1]]
240 240  
241 241  ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-
242 242