Skip to Content
Last modified by Artur on 2025/09/13 19:50
From version 1.4
edited by Helena
on 2025/07/01 17:53
Change comment: There is no comment for this version
To version 1.2
edited by Helena
on 2025/07/01 17:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -52,15 +52,17 @@
52 52  
53 53  Reference Metadata reported against a Dataflow and / or Provision Agreement can be used as an alternative to the Advanced Release Calendar.
54 54  
55 -== 2.2 Removal of Version on Categorisation ==
55 +1. //2.2 Removal of Version on Categorisation//
56 56  
57 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 60  
60 +//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  
63 -= 3. Information Model =
64 +1.
65 +11. Information Model
64 64  
65 65  The changes to the information model support two distinct use cases:
66 66  
... ... @@ -69,17 +69,23 @@
69 69  
70 70  These changes are described in below.
71 71  
72 -== 3.1 Horizontally Complex Data Structure Definitions ==
74 +1. //3.1 Horizontally Complex Data Structure Definitions//
73 73  
74 74  An explanation of this use case, with additional details can be found under Section 6 - Technical Notes, under heading ‘10.3 Dimension Constraint’.
75 75  
76 76  The following changes to the model have been made to satisfy this use case.
77 77  
78 -Data Structure Definition
80 +1.
81 +11.
82 +111.
83 +1111. Data Structure Definition
79 79  
80 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.
81 81  
82 -Dataflow
87 +1.
88 +11.
89 +111.
90 +1111. Dataflow
83 83  
84 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.
85 85  
... ... @@ -87,16 +87,22 @@
87 87  
88 88  The Dimension Constraint property is only required if the DSD sets the evolving structure property to true.
89 89  
90 -== 3.2 Constraint Cohesion ==
98 +1. //3.2 Constraint Cohesion//
91 91  
92 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.
93 93  
94 -Data Constraint
102 +1.
103 +11.
104 +111.
105 +1111. Data Constraint
95 95  
96 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.
97 97  
98 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.
99 99  
100 -Availability Constraint
111 +1.
112 +11.
113 +111.
114 +1111. Availability Constraint
101 101  
102 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