Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.7
edited by Helena
on 2025/06/08 23:30
Change comment: There is no comment for this version
To version 1.5
edited by Helena
on 2025/06/08 23:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -514,13 +514,15 @@
514 514  
515 515  ‘1.0’.
516 516  
517 -=== 4.3.1 Non-versioned artefacts ===
517 +=== 4.2.14 Non-versioned artefacts ===
518 518  
519 519  Indeed, some use cases do not need or are incompatible with versioning for some or all their structural artefacts, such as the Agency, Data Providers, Metadata Providers and Data Consumer Schemes. These artefacts follow the legacy versioning, with a fixed version set to ‘1.0’.
520 520  
521 521  Many existing organisation’s data management systems work with version-less structures and apply ad-hoc structural metadata governance processes. The new nonversioned artefacts will allow supporting those numerous situations, where organisations do not manage version numbers.
522 522  
523 -=== 4.3.2 Semantically versioned artefacts ===
523 +1.
524 +11.
525 +111. Semantically versioned artefacts
524 524  
525 525  Since the purpose of SDMX versioning is to allow communicating the structural artefact changes to data exchange partners and connected systems, SDMX 3.0 offers Semantic Versioning (aka SemVer) with a clear and unambiguous syntax to all semantically versioned SDMX 3.0 structural artefacts. Semantic versioning will thus better respond to situations where the SDMX standard itself is the only structural contract between data providers and data consumers and where changes in structures can only be communicated through the version number increases.
526 526