Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.7
edited by Helena
on 2025/05/16 11:01
Change comment: There is no comment for this version
To version 3.8
edited by Helena
on 2025/05/16 11:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -60,7 +60,7 @@
60 60  
61 61  Because both, wildcarded references and references to version-extended artefacts, allow for changes in the referenced artefacts, care needs to be taken when choosing the appropriate references in order to achieve the required limitation in the allowed scope of changes.
62 62  
63 -For references to non-dependent artefacts, MAJOR, MINOR or PATCH version parts in SDMX 3.0 artefact references CAN alternatively be wildcarded using "*" as replacement:
63 +For references to non-dependent artefacts, MAJOR, MINOR or PATCH version parts in SDMX 3.0 artefact references CAN alternatively be wildcarded using "*" as replacement:
64 64  
65 65  ~* means all available versions
66 66  
... ... @@ -76,11 +76,11 @@
76 76  
77 77  1. Complement the missing version parts with 0s to make the version number SemVer-compliant using the MAJOR.MINOR.PATCH-EXTENSION syntax:
78 78  
79 -Example: Version 2 becomes version 2.0.0 and version 3.1 becomes version 3.1.0.
79 + Example: Version 2 becomes version 2.0.0 and version 3.1 becomes version 3.1.0.
80 80  
81 81  1. Replace the "isFinal=false" property by the version extensions "-draft" (or alternatively "-unstable" or "-nonfinal" depending on the use case).
82 82  
83 -Example: Version 1.3 with isFinal=true becomes version 1.3.0 and version 1.3 with isFinal=false becomes version 1.3.0-draft.
83 + Example: Version 1.3 with isFinal=true becomes version 1.3.0 and version 1.3 with isFinal=false becomes version 1.3.0-draft.
84 84  
85 85  If artefact versioning is required but semantic versioning cannot be applied, then version strings used in previous versions of the Standard (e.g., version=1.2) may continue to be used.
86 86