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

Summary

Details

Page properties
Content
... ... @@ -514,7 +514,7 @@
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  
... ... @@ -544,13 +544,17 @@
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 -=== 4.3.3 Legacy-versioned artefacts ===
547 +1.
548 +11.
549 +111. Legacy-versioned artefacts
548 548  
549 549  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.
550 550  
551 551  In order to make artefacts immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
552 552  
553 -=== 4.3.4 Dependency management and references ===
555 +1.
556 +11.
557 +111. Dependency management and references
554 554  
555 555  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:
556 556