Last modified by Helena K. on 2026/06/08 15:19
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SDMX 3.1 Standards. Section 1. Summary of MajorChanges andNewFunctionality1 +SDMX 3.1 Standards. Section 1. Summary of major changes and new functionality - Content
-
... ... @@ -11,28 +11,27 @@ 11 11 12 12 = 1. Overview = 13 13 14 +SDMX 3.1 is a minor revision to the SDMX 3.0 Standard which introduces a limited set of changes, which cover the following: 14 14 15 - [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data andmetadata exchange.WebHome]] 3.1is a minor revisionto the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 3.0 Standard which introduces alimited set of changes, which cover the following:16 +Information Model 16 16 17 -**Information Model** 18 +* Support for Dataflows to reference a subset of Dimensions from a Data Structure Definition 19 +* Simplification to Data Constraints 20 +* Addition of Availability Constraints 18 18 19 -* Support for [[Dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] to reference a subset of [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] from a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] 20 -* Simplification to Data [[Constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] 21 -* Addition of Availability [[Constraints>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] 22 +1. Documentation 22 22 23 - **Documentation**24 +Registering Reference Metadata removed from documentation, to align with XML Registration object which is unable to reference a Metadata Provision, and REST API which is unable to query for registered reference metadata sources. 24 24 25 - Registering [[Reference Metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] removed from documentation, to alignwithXML Registrationobject which is unable to reference a Metadata Provision, and REST API which is unable to query for registered [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] sources.26 +Breaking Changes 26 26 27 -**Breaking Changes** 28 +* Remove version property on Categorisation 29 +* Removal of Advanced Release Calendar 28 28 29 -* Remove [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] property on [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] 30 -* Removal of Advanced [[Release Calendar>>doc:sdmx:Glossary 2\.1.Release policy - release calendar.WebHome]] 31 +Content of the Document 31 31 32 - **Content of theDocument**33 +The remainder of this document contains a summary of the changes. More detailed information can be found in the SDMX 3.1 Technical Specifications, in particular: 33 33 34 -The remainder of this document contains a summary of the changes. More detailed information can be found in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 3.1 Technical Specifications, in particular: 35 - 36 36 Section 2 – Information Model 37 37 38 38 Section 5 – Registry Specification ... ... @@ -39,7 +39,7 @@ 39 39 40 40 Section 6 – Technical Notes 41 41 42 - [[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]TWG GitHub for the REST API and the XML and JSON formats41 +SDMX TWG GitHub for the REST API and the XML and JSON formats 43 43 44 44 = 2. Summary of Breaking Changes in 3.1 = 45 45 ... ... @@ -47,57 +47,57 @@ 47 47 48 48 == 2.1 Removal of Advanced Release Calendar == 49 49 50 -The Data [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]was simplified to become a cohesive structural[[artefact>>doc:sdmx:Glossary2\.1.Artefact.WebHome]] focussed solely on the restriction of values that can be reported. As part of this remodelling the Advanced[[Release Calendar>>doc:sdmx:Glossary2\.1.Release policy - release calendar.WebHome]]was removed as it does not play a restrictive role.49 +The Data Constraint was simplified to become a cohesive structural artefact focussed solely on the restriction of values that can be reported. As part of this remodelling the Advanced Release Calendar was removed as it does not play a restrictive role. 51 51 52 52 //Guidance for Implementors// 53 -[[Reference Metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] reported against a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and / or [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] can be used as an alternative to the Advanced [[Release Calendar>>doc:sdmx:Glossary 2\.1.Release policy - release calendar.WebHome]]. 54 54 53 +Reference Metadata reported against a Dataflow and / or Provision Agreement can be used as an alternative to the Advanced Release Calendar. 54 + 55 55 == 2.2 Removal of Version on Categorisation == 56 56 57 -The [[Categorisation>>doc:sdmx:Glossary2\.1.Categorisation.WebHome]] structural[[artefact>>doc:sdmx:Glossary2\.1.Artefact.WebHome]]has no use case for undergoing[[version>>doc:sdmx:Glossary2\.1.Version.WebHome]]changes, the[[version>>doc:sdmx:Glossary2\.1.Version.WebHome]]was therefore removed.57 +The Categorisation structural artefact has no use case for undergoing version changes, the version was therefore removed. 58 58 59 -//Guidance for Implementors// 60 -If multiple [[versions>>doc:sdmx:Glossary 2\.1.Version.WebHome]] of a [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] exist where the source or target differs, these [[Categorisations>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] should be given a unique ID. 59 +Guidance for Implementors 61 61 61 +If multiple versions of a Categorisation exist where the source or target differs, these Categorisations should be given a unique ID. 62 + 62 62 = 3. Information Model = 63 63 64 64 The changes to the information model support two distinct use cases: 65 65 66 -1. Horizontally complex [[Data Structure Definitions>>doc:sdmx:Glossary2\.1.Data structure definition.WebHome]](DSDs)67 -1. Additional cohesion to the Data [[Constraints>>doc:sdmx:Glossary2\.1.Constraint.WebHome]] model67 +1. Horizontally complex Data Structure Definitions (DSDs) 68 +1. Additional cohesion to the Data Constraints model 68 68 69 69 These changes are described in below. 70 70 71 71 == 3.1 Horizontally Complex Data Structure Definitions == 72 72 73 -An explanation of this use case, with additional details can be found under Section 6 - Technical Notes, under heading ‘10.3 [[Dimension>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]’.74 +An explanation of this use case, with additional details can be found under Section 6 - Technical Notes, under heading ‘10.3 Dimension Constraint’. 74 74 75 75 The following changes to the model have been made to satisfy this use case. 76 76 77 - **Data Structure Definition**78 +Data Structure Definition 78 78 79 -The [[Data Structure Definition>>doc:sdmx:Glossary2\.1.Data structure definition.WebHome]]has a new ‘evolving structure’ property, this is a Boolean property, when set to ‘true’ it indicates to the users of the[[DSD>>doc:sdmx:Glossary2\.1.Data structure definition.WebHome]] that new[[Dimensions>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] may be added without the[[DSD>>doc:sdmx:Glossary2\.1.Data structure definition.WebHome]] undergoing a change to its major[[version>>doc:sdmx:Glossary2\.1.Version.WebHome]] number.80 +The Data Structure Definition has a new ‘evolving structure’ property, this is a Boolean property, when set to ‘true’ it indicates to the users of the DSD that new Dimensions may be added without the DSD undergoing a change to its major version number. 80 80 81 - **Dataflow**82 +Dataflow 82 82 83 -The [[Dataflow>>doc:sdmx:Glossary2\.1.Dataflow.WebHome]]has a new[[Dimension>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]property, which is used to reference a subset of[[Dimensions>>doc:sdmx:Glossary2\.1.Dimension.WebHome]]which it uses from the referenced[[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]].84 +The Dataflow has a new Dimension Constraint property, which is used to reference a subset of Dimensions which it uses from the referenced DSD. 84 84 85 -The [[Dimension>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]fixes the[[Dimensions>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] of the[[Dataflow>>doc:sdmx:Glossary2\.1.Dataflow.WebHome]] enabling the referenced[[DSD>>doc:sdmx:Glossary2\.1.Data structure definition.WebHome]]tohave new[[Dimensions>>doc:sdmx:Glossary2\.1.Dimension.WebHome]]added without the need to change the major[[version>>doc:sdmx:Glossary2\.1.Version.WebHome]] number.86 +The Dimension Constraint fixes the Dimensions of the Dataflow enabling the referenced DSD to have new Dimensions added without the need to change the major version number. 86 86 87 -The [[Dimension>>doc:sdmx:Glossary2\.1.Dimension.WebHome]] [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]property is only required if the[[DSD>>doc:sdmx:Glossary2\.1.Datastructuredefinition.WebHome]]setsthe evolving structure property to true.88 +The Dimension Constraint property is only required if the DSD sets the evolving structure property to true. 88 88 89 89 == 3.2 Constraint Cohesion == 90 90 91 -The [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]] model in[[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]3.1 has been made more cohesive by separating the Data[[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]into two distinct structures; the Data[[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]which describes reporting restrictions, and the Availability[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]], which describes data content from a[[data source>>doc:sdmx:Glossary 2\.1.Datasource.WebHome]].In[[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]3.0 these distinctions were made using the ‘type’ property on a Data[[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]].92 +The Constraint model in SDMX 3.1 has been made more cohesive by separating the Data Constraint into two distinct structures; the Data Constraint which describes reporting restrictions, and the Availability Constraint, which describes data content from a data source. In SDMX 3.0 these distinctions were made using the ‘type’ property on a Data Constraint. 92 92 93 - **Data Constraint**94 +Data Constraint 94 94 95 -The Data [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]has had the ‘type’ property removed; the Data[[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]in [[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]3.1 is always used to describe restrictions on content for data reporting purposes.96 +The Data Constraint has had the ‘type’ property removed; the Data Constraint in SDMX 3.1 is always used to describe restrictions on content for data reporting purposes. 96 96 97 -The attachment of the Data [[Constraint>>doc:sdmx:Glossary2\.1.Constraint.WebHome]]in [[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]3.0 included[[Data Sources>>doc:sdmx:Glossary 2\.1.Data source.WebHome]], in[[SDMX>>doc:sdmx:Glossary2\.1.Statistical data and metadata exchange.WebHome]]3.1 these attachments have been removed as these are not relevant for restricting reported data.98 +The attachment of the Data Constraint in SDMX 3.0 included Data Sources, in SDMX 3.1 these attachments have been removed as these are not relevant for restricting reported data. 98 98 99 - **Availability Constraint**100 +Availability Constraint 100 100 101 -The Availability [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]] is a new Structure introduced to describe data that exists, it is generated in the response to the Availability REST API. It is not a maintained structure, and as such has no [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]], identity or [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] 102 - 103 - 102 +The Availability Constraint is a new Structure introduced to describe data that exists, it is generated in the response to the Availability REST API. It is not a maintained structure, and as such has no maintenance agency, identity or version
- SKMS.Methodology.Code.MethodologyClass[0]
-
- SUZ.Methodology.Code.MethodologyClass[0]
-