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

Summary

Details

Page properties
Content
... ... @@ -501,9 +501,11 @@
501 501  * 2010-M07 or later (any reporting year start day)
502 502  * 2010-W27 or later (reporting year start day ~-~-01-01)^^5^^
503 503  * 2010-D182 or later (reporting year start day ~-~-01-01)
504 -* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^ • 2010-D185 or later (reporting year start day ~-~-07-01)
505 -*1. Versioning
504 +* 2010-W28 or later (reporting year start day ~-~-07-01)^^6^^
505 +* 2010-D185 or later (reporting year start day ~-~-07-01)
506 506  
507 += 4.3 Versioning ==
508 +
507 507  Versioning operates at the level of versionable and maintainable objects in the SDMX information model. Within the SDMX Structure and MetadataSet messages, there is a well-defined pattern for artefact versioning and referencing. The artefact identifiers are qualified by their version numbers – that is, an object with an Agency of "A", and ID of "X" and a version of "1.0.0" is a different object than one with an Agency of "A", an ID of "X", and a version of "1.1.0".
508 508  
509 509  As of SDMX 3.0, the versioning rules are extended to allow for truly versioned artefacts through the implementation of the rules of the well-known practice called "Semantic Versioning" [[(>>url:http://semver.org/]][[http:~~/~~/semver.org>>url:http://semver.org/]][[)>>url:http://semver.org/]], in addition to the legacy non-restrictive versioning scheme. In addition, the "isFinal" property is removed from
... ... @@ -512,15 +512,13 @@
512 512  
513 513  ‘1.0’.
514 514  
515 -=== 4.2.14 Non-versioned artefacts ===
517 +=== 4.3.1 Non-versioned artefacts ===
516 516  
517 517  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’.
518 518  
519 519  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.
520 520  
521 -1.
522 -11.
523 -111. Semantically versioned artefacts
523 +=== 4.3.2 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  
... ... @@ -544,17 +544,13 @@
544 544  
545 545  The production versions of identifiable artefacts are assumed stable, i.e., they do not have an EXTENSION. This is because once in production, an artefact cannot change in any way, or it must change the version. For cases where an artefact is not static, like during the drafting, the version must indicate this by including an EXTENSION. Draft artefacts should not be used outside of a specific system designed to accommodate them. For most purposes, all artefacts should become stable before being used in production.
546 546  
547 -1.
548 -11.
549 -111. Legacy-versioned artefacts
547 +=== 4.3.3 Legacy-versioned artefacts ===
550 550  
551 551  Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for version numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new SDMX 3.0 standard does not add any strict rules or guarantees about changes in those artefacts, since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
552 552  
553 553  In order to make artefacts immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
554 554  
555 -1.
556 -11.
557 -111. Dependency management and references
553 +=== 4.3.4 Dependency management and references ===
558 558  
559 559  New flexible dependency specifications with wildcarding allow for easier data model maintenance and enhancements for semantically versioned SDMX artefacts. This allows implementing a smart referencing mechanism, whereby an artefact may reference:
560 560