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.9
edited by Helena
on 2025/06/08 23:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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  
... ... @@ -583,8 +583,7 @@
583 583  
584 584  Full details can be found in the SDMX RESTful web services specification.
585 585  
586 -1.
587 -11. Structural Metadata Querying Best Practices
582 +== 4.4 Structural Metadata Querying Best Practices ==
588 588  
589 589  When querying for structural metadata, the ability to state how references should be resolved is quite powerful. However, this mechanism is not always necessary and can create an undue burden on the systems processing the queries if it is not used properly.
590 590  
... ... @@ -592,7 +592,6 @@
592 592  
593 593  When the referenced object is not known, then the reference resolution mechanism could be used. For example, suppose one wanted to find all category schemes and the related categorisations for a given maintenance agency. In this case, one could query for the category scheme by the maintenance agency and specify that parent and sibling references should be resolved. This would result in the categorisations which reference the categories in the matched schemes to be returned, as well as the object which they categorise.
594 594  
595 -
596 596  ----
597 597  
598 598  [[~[1~]>>path:#_ftnref1]] Regular expressions, as specified in [[W3C XML Schema Definition Language (XSD)>>url:https://www.w3.org/TR/xmlschema11-2/]][[ >>url:https://www.w3.org/TR/xmlschema11-2/]][[1.1 Part 2: Datatypes>>url:https://www.w3.org/TR/xmlschema11-2/]][[.>>url:https://www.w3.org/TR/xmlschema11-2/]]