Last modified by Helena on 2025/09/10 11:19

From version 41.2
edited by Artur
on 2025/06/06 13:16
Change comment: Update document after refactoring.
To version 41.4
edited by Elena
on 2025/06/18 11:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.arturkryazhev
1 +xwiki:XWiki.elenasemanticproorg
Content
... ... @@ -26,7 +26,7 @@
26 26  
27 27  Standard formats for the exchange of aggregated statistical data and metadata as prescribed in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] v3.0 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient.
28 28  
29 -As organisations migrate to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:Glossary.Artefact.WebHome]] will be produced (e.g., Data Structure, Metadata Structure, [[Code List>>doc:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)Concept(%%) definitions – often collectively called [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:Glossary.Artefact.WebHome]] between parties in a controlled and organized way.
29 +As organisations migrate to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:Glossary.Artefact.WebHome]] will be produced (e.g., [[Data Structure,>>doc:Glossary.Data structure definition.WebHome]] [[Metadata Structure>>doc:Glossary.Metadata structure definition.WebHome]], [[Code List>>doc:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) definitions – often collectively called [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:Glossary.Artefact.WebHome]] between parties in a controlled and organized way.
30 30  
31 31  This is the role of the registry.
32 32  
... ... @@ -40,7 +40,7 @@
40 40  
41 41  The registry services outlined in this specification are designed to help the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] assets and to support data sharing for reporting and dissemination.
42 42  
43 -= {{id name="_Toc93832"/}}2 Scope and Normative Status =
43 += 2 Scope and Normative Status =
44 44  
45 45  The scope of this document is to specify the logical interfaces for the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]] in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry.
46 46  
... ... @@ -57,9 +57,9 @@
57 57  
58 58  Note that although the term “authorised user” is used in this document, the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider.
59 59  
60 -= {{id name="_Toc93833"/}}3 Scope of the SDMX Registry/Repository =
60 += 3 Scope of the SDMX Registry/Repository =
61 61  
62 -== {{id name="_Toc93834"/}}3.1 Objective ==
62 +== 3.1 Objective ==
63 63  
64 64  The objective of the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold:
65 65  
... ... @@ -93,7 +93,7 @@
93 93  
94 94  In that context, the term “Metadata” refers to [[reference metadata>>doc:Glossary.Reference metadata.WebHome]].
95 95  
96 -== {{id name="_Toc93836"/}}3.3 Registration ==
96 +== 3.3 Registration ==
97 97  
98 98  Publishing the data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] involves the following steps for a Data/Metadata Provider:
99 99  
... ... @@ -104,13 +104,13 @@
104 104  
105 105  **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
106 106  
107 -== {{id name="_Toc93837"/}}3.4 Notification ==
107 +== 3.4 Notification ==
108 108  
109 109  Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] involves:
110 110  
111 111  * registry support of a [[subscription>>doc:Glossary.Subscription.WebHome]]-based [[notification>>doc:Glossary.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:Glossary.Subscription.WebHome]] request.
112 112  
113 -== {{id name="_Toc93838"/}}3.5 Discovery ==
113 +== 3.5 Discovery ==
114 114  
115 115  Discovering published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] resource:
116 116  
... ... @@ -122,9 +122,9 @@
122 122  
123 123  **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
124 124  
125 -= {{id name="_Toc93839"/}}4 SDMX Registry/Repository Architecture =
125 += 4 SDMX Registry/Repository Architecture =
126 126  
127 -== {{id name="_Toc93840"/}}4.1 Architectural Schematic ==
127 +== 4.1 Architectural Schematic ==
128 128  
129 129  The architecture of the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]]/repository is derived from the objectives stated above. It is a layered architecture that is founded by a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] required to drive these applications.
130 130  
... ... @@ -132,7 +132,7 @@
132 132  
133 133  **Figure 4: Schematic of the Registry Content and Services**
134 134  
135 -== {{id name="_Toc93841"/}}4.2 Structural Metadata Repository ==
135 +== 4.2 Structural Metadata Repository ==
136 136  
137 137  The basic layer is that of a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:Glossary.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]], Processes etc. This layer is supported by the Structure Submission and Query Service.
138 138  
... ... @@ -141,17 +141,17 @@
141 141  * Registration of data and metadata sources
142 142  * [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]]
143 143  
144 -As of the initial (% style="color:#e74c3c" %)version(%%) of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:Glossary.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Registry Interface messages, instead.
144 +As of the initial version of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:Glossary.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Registry Interface messages, instead.
145 145  
146 -== {{id name="_Toc93842"/}}4.3 Provisioning Metadata Repository ==
146 +== 4.3 Provisioning Metadata Repository ==
147 147  
148 148  The function of this repository is to support the definition of the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:Glossary.Data source.WebHome]]. These links can be specified for a data/metadata provider, for a specific data or [[metadata flow>>doc:Glossary.Metadataflow.WebHome]]. In the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model this is called the Provision or Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
149 149  
150 150  This layer is supported by the Data and Metadata Registration Service.
151 151  
152 -= {{id name="_Toc93843"/}}5 Registry Interfaces and Services =
152 += 5 Registry Interfaces and Services =
153 153  
154 -== {{id name="_Toc93844"/}}5.1 Registry Interfaces ==
154 +== 5.1 Registry Interfaces ==
155 155  
156 156  The Registry Interfaces are:
157 157  
... ... @@ -176,17 +176,17 @@
176 176  
177 177  It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous.
178 178  
179 -== {{id name="_Toc93845"/}}5.2 Registry Services ==
179 +== 5.2 Registry Services ==
180 180  
181 -=== {{id name="_Toc93846"/}}5.2.1 Introduction ===
181 +=== 5.2.1 Introduction ===
182 182  
183 183  The services described in this section do not imply that each is implemented as a discrete web service.
184 184  
185 -=== {{id name="_Toc93847"/}}5.2.2 Structure Submission Service ===
185 +=== 5.2.2 Structure Submission Service ===
186 186  
187 -The registry must support a mechanism for submitting [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://github.com/sdmx-twg/sdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], where changes at an Item (% style="color:#e74c3c" %)level(%%) is also possible (see next section on the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]]).
187 +The registry must support a mechanism for submitting [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://github.com/sdmx-twg/sdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], where changes at an Item [[level>>doc:Glossary.Level.WebHome]] is also possible (see next section on the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]]).
188 188  
189 -=== {{id name="_Toc93848"/}}5.2.3 Structure Query Service ===
189 +=== 5.2.3 Structure Query Service ===
190 190  
191 191  The registry must support a mechanism for querying for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://github.com/sdmx-twg/sdmx-rest]]). The registry response to this query mechanism is the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Structure message, which has as its root node:
192 192  
... ... @@ -196,20 +196,20 @@
196 196  
197 197  * [[data flows>>doc:Glossary.Dataflow.WebHome]] and [[metadata flows>>doc:Glossary.Metadataflow.WebHome]]
198 198  * [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:Glossary.Metadata structure definition.WebHome]]
199 -* [[code>>doc:Glossary.Code.WebHome]] lists
199 +* [[code lists>>doc:sdmx:Glossary.Code list.WebHome]]
200 200  * value lists
201 -* (% style="color:#e74c3c" %)concept(%%) schemes
201 +* [[concept schemes>>doc:Glossary.Concept scheme.WebHome]]
202 202  * reporting taxonomies
203 203  * [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] and metadata [[provision agreements>>doc:Glossary.Provision agreement.WebHome]]
204 204  * structure maps
205 205  * [[representation>>doc:Glossary.Representation.WebHome]] map
206 206  * organisation scheme map
207 -* (% style="color:#e74c3c" %)concept(%%) scheme map
207 +* [[concept scheme>>doc:Glossary.Concept scheme.WebHome]] map
208 208  * [[category>>doc:Glossary.Category.WebHome]] scheme map
209 209  * reporting taxonomy map
210 210  * processes
211 211  * hierarchies
212 -* (% style="color:#e74c3c" %)constraints
212 +* [[constraints>>doc:Glossary.Constraint.WebHome]]
213 213  * [[category>>doc:Glossary.Category.WebHome]] schemes
214 214  * categorisations and categorised objects (examples are categorised [[data flows>>doc:Glossary.Dataflow.WebHome]] and [[metadata flows>>doc:Glossary.Metadataflow.WebHome]], [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], [[metadata structure definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] registered [[data sources>>doc:Glossary.Data source.WebHome]] and metadata sources)
215 215  * organisation schemes ([[agency scheme>>doc:Glossary.Agency scheme.WebHome]], [[data provider scheme>>doc:Glossary.Data provider scheme.WebHome]], [[data consumer scheme>>doc:Glossary.Data consumer scheme.WebHome]], organisation unit scheme)
... ... @@ -223,7 +223,7 @@
223 223  * Ruleset schemes
224 224  * User defined operator schemes
225 225  
226 -=== {{id name="_Toc93849"/}}5.2.4 Data and Reference Metadata Registration Service ===
226 +=== 5.2.4 Data and Reference Metadata Registration Service ===
227 227  
228 228  This service must implement the following Registry Interfaces:
229 229  
... ... @@ -232,17 +232,17 @@
232 232  * QueryRegistrationRequest
233 233  * QueryRegistrationResponse
234 234  
235 -The Data and Metadata Registration Service allows [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant files and webaccessible databases containing published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:Glossary.Data set.WebHome]] or metadatasets, and MAY extract a concise [[representation>>doc:Glossary.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)concept(%%) values (e.g., values of the data [[attribute>>doc:Glossary.Attribute.WebHome]], [[dimension>>doc:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:Glossary.Data set.WebHome]] or metadata-set. These are called (% style="color:#e74c3c" %)Constraints(%%) in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-IM.
235 +The Data and Metadata Registration Service allows [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant files and webaccessible databases containing published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:Glossary.Data set.WebHome]] or metadatasets, and MAY extract a concise [[representation>>doc:Glossary.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) values (e.g., values of the data [[attribute>>doc:Glossary.Attribute.WebHome]], [[dimension>>doc:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:Glossary.Data set.WebHome]] or metadata-set. These are called [[Constraints>>doc:Glossary.Constraint.WebHome]] in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-IM.
236 236  
237 237  The Data and Metadata Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry:
238 238  
239 239  * that the data/metadata provider is allowed to register the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset;
240 -* that the content of the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset meets the validation (% style="color:#e74c3c" %)constraints(%%). This is dependent upon such (% style="color:#e74c3c" %)constraints(%%) being defined in the structural repository and which reference the relevant [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:Glossary.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]];
240 +* that the content of the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset meets the validation [[constraints>>doc:Glossary.Constraint.WebHome]]. This is dependent upon such [[constraints>>doc:Glossary.Constraint.WebHome]] being defined in the structural repository and which reference the relevant [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:Glossary.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]];
241 241  * that a queryable [[data source>>doc:Glossary.Data source.WebHome]] exists – this would necessitate the registration service querying the service to determine its existence;
242 242  * that a simple [[data source>>doc:Glossary.Data source.WebHome]] exists (i.e., a file accessible at a URL);
243 243  * that the correct [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] is used by the registered data;
244 244  * that the [[components>>doc:Glossary.Component.WebHome]] ([[Dimensions>>doc:Glossary.Dimension.WebHome]], [[Attributes>>doc:Glossary.Attribute.WebHome]], [[Measures>>doc:Glossary.Measure.WebHome]], Metadata [[Attributes>>doc:Glossary.Attribute.WebHome]], etc.) are consistent with the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]];
245 -* that the valid [[representations>>doc:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)concepts(%%) to which these [[components>>doc:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]. The Registration has an action [[attribute>>doc:Glossary.Attribute.WebHome]] which takes one of the following values:
245 +* that the valid [[representations>>doc:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) to which these [[components>>doc:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]. The Registration has an action [[attribute>>doc:Glossary.Attribute.WebHome]] which takes one of the following values:
246 246  
247 247  (% style="width:755.294px" %)
248 248  |(% style="width:187px" %)**Action Attribute Value**|(% style="width:566px" %)**Behaviour**
... ... @@ -261,7 +261,7 @@
261 261  )))
262 262  |(% style="width:191px" %)indexReportingPeriod|(% style="width:565px" %)A compliant indexing application must index the [[time period>>doc:Glossary.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:Glossary.Data set.WebHome]]. The validity period of the Metadatasets may also be indexed.
263 263  
264 -=== {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
264 +=== 5.2.5 Data and Reference Metadata Discovery ===
265 265  
266 266  The Data and Metadata Discovery Service implements the following Registry Interfaces:
267 267  
... ... @@ -268,7 +268,7 @@
268 268  * QueryRegistrationRequest
269 269  * QueryRegistrationResponse
270 270  
271 -=== {{id name="_Toc93851"/}}5.2.6 Subscription and Notification ===
271 +=== 5.2.6 Subscription and Notification ===
272 272  
273 273  The [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces:
274 274  
... ... @@ -280,7 +280,7 @@
280 280  
281 281  [[Subscription>>doc:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:Glossary.Subscription.WebHome]] request which contains:
282 282  
283 -* a query or (% style="color:#e74c3c" %)constraint(%%) expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific [[dataflow>>doc:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:Glossary.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]).
283 +* a query or [[constraint>>doc:Glossary.Constraint.WebHome]] expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific [[dataflow>>doc:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:Glossary.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]).
284 284  * a list of URIs or endpoints to which an XML [[notification>>doc:Glossary.Notification.WebHome]] message can be sent. Supported endpoint types will be email (mailto~: ) and HTTP POST (a normal http:~/~/ address);
285 285  * request for a list of submitted subscriptions;
286 286  * deletion of a [[subscription>>doc:Glossary.Subscription.WebHome]];
... ... @@ -287,11 +287,11 @@
287 287  
288 288  [[Notification>>doc:Glossary.Notification.WebHome]] requires that the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:Glossary.Subscription.WebHome]] request query), and to issue an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[notification>>doc:Glossary.Notification.WebHome]] document to the endpoints specified in the relevant subscriptions.
289 289  
290 -=== {{id name="_Toc93852"/}}5.2.7 Registry Behaviour ===
290 +=== 5.2.7 Registry Behaviour ===
291 291  
292 -The following table defines the behaviour of the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]]. Moreover, while the old versioning scheme is allowed, given there is no more a "final" flag, there is no way guaranteeing the consistency across (% style="color:#e74c3c" %)version(%%) of a Maintainable, unless semantic versioning is used.
292 +The following table defines the behaviour of the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]]. Moreover, while the old versioning scheme is allowed, given there is no more a "final" flag, there is no way guaranteeing the consistency across [[version>>doc:Glossary.Version.WebHome]] of a Maintainable, unless semantic versioning is used.
293 293  
294 -Given the above, the behaviour described in the following table concerns either draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:Glossary.Artefact.WebHome]] using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft [[Artefact>>doc:Glossary.Artefact.WebHome]] that follows semantic versioning, unless a newer (% style="color:#e74c3c" %)version(%%) is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft (% style="color:#e74c3c" %)versions(%%). It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:Glossary.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:Glossary.Artefact.WebHome]]. This means that any system may internally perform any change within a (% style="color:#e74c3c" %)version(%%) of an [[Artefact>>doc:Glossary.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then (as also explained in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”) the [[Artefacts>>doc:Glossary.Artefact.WebHome]] must adhere to the Semantic Versioning rules.
294 +Given the above, the behaviour described in the following table concerns either draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:Glossary.Artefact.WebHome]] using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft [[Artefact>>doc:Glossary.Artefact.WebHome]] that follows semantic versioning, unless a newer [[version>>doc:Glossary.Version.WebHome]] is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft [[versions>>doc:Glossary.Version.WebHome]]. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:Glossary.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:Glossary.Artefact.WebHome]]. This means that any system may internally perform any change within a [[version>>doc:Glossary.Version.WebHome]] of an [[Artefact>>doc:Glossary.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then (as also explained in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”) the [[Artefacts>>doc:Glossary.Artefact.WebHome]] must adhere to the Semantic Versioning rules.
295 295  
296 296  (% style="width:757.294px" %)
297 297  |(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
... ... @@ -299,26 +299,26 @@
299 299  1) If the action is set to “replace” (or a [[maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
300 300  2) Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
301 301  3) If the action is set to “delete” (or a [[maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must:
302 -a) Be a draft (% style="color:#e74c3c" %)version(%%).
302 +a) Be a draft [[version>>doc:Glossary.Version.WebHome]].
303 303  b) Not be explicitly{{footnote}}With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4-draft does not break integrity of the aforementioned DSD.{{/footnote}} referenced from any other object in the Registry.
304 304  
305 305  4) The semantic versioning rules in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] documentation MUST be obeyed.
306 306  )))
307 -|(% style="width:188px" %)Structure submission|(% style="width:542px" %)Structures are submitted at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]].
307 +|(% style="width:188px" %)Structure submission|(% style="width:542px" %)Structures are submitted at the [[level>>doc:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the [[level>>doc:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]].
308 308  |(% style="width:188px" %)SubmitRegistrationRequest|(% style="width:542px" %)If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean [[attributes>>doc:Glossary.Attribute.WebHome]] set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] data query.
309 309  
310 -= {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
310 += 6 Identification of SDMX Objects =
311 311  
312 -== {{id name="_Toc93854"/}}6.1 Identification, Versioning, and Maintenance ==
312 +== 6.1 Identification, Versioning, and Maintenance ==
313 313  
314 314  All major classes of the [[SDMX Information model>>doc:Glossary.SDMX Information Model.WebHome]] inherit from one of:
315 315  
316 316  * //**IdentifiableArtefact**// – this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations.
317 317  * //**NameableArtefact**// – this has all of the features of //IdentifiableArtefact// plus the ability to have a multi-lingual name and description.
318 -* //**VersionableArtefact**// – this has all of the above features plus a (% style="color:#e74c3c" %)version(%%) number, according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
318 +* //**VersionableArtefact**// – this has all of the above features plus a [[version>>doc:Glossary.Version.WebHome]] number, according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
319 319  * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object.
320 320  
321 -=== {{id name="_Toc93855"/}}6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
321 +=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
322 322  
323 323  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1683f36a.jpg||height="688" width="587"]]
324 324  
... ... @@ -338,7 +338,7 @@
338 338  |(% rowspan="4" %)//Annotable//|(% style="width:241px" %)AnnotationTitle|(% style="width:156px" %)C|string|(% style="width:457px" %)
339 339  |(% style="width:241px" %)AnnotationType|(% style="width:156px" %)C|string|(% style="width:457px" %)
340 340  |(% style="width:241px" %)AnnotationURN|(% style="width:156px" %)C|string|(% style="width:457px" %)
341 -|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have languagespecific variants
341 +|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have language specific variants
342 342  |(% rowspan="4" %)//Identifiable//|(% style="width:241px" %)All content as for //Annotable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
343 343  |(% style="width:241px" %)id|(% style="width:156px" %)M|string|(% style="width:457px" %)
344 344  |(% style="width:241px" %)uri|(% style="width:156px" %)C|string|(% style="width:457px" %)
... ... @@ -347,7 +347,7 @@
347 347  |(% style="width:241px" %)Name in the form of InternationalString|(% style="width:156px" %)M|string|(% style="width:457px" %)This can have language specific variants.
348 348  |(% style="width:241px" %)Description in the form of InternationalString|(% style="width:156px" %)C|string|(% style="width:457px" %)This can have language specific variants.
349 349  |(% rowspan="4" %)//Versionable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
350 -|(% style="width:241px" %)(% style="color:#e74c3c" %)version|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the (% style="color:#e74c3c" %)version(%%) number according to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules.
350 +|(% style="width:241px" %)[[version>>doc:Glossary.Version.WebHome]]|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the [[version>>doc:Glossary.Version.WebHome]] number according to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules.
351 351  |(% style="width:241px" %)validFrom|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
352 352  |(% style="width:241px" %)validTo|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
353 353  |//Maintainable//|(% style="width:241px" %)All content as for //Versionable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
... ... @@ -359,9 +359,9 @@
359 359  
360 360  **Table 1: Common Attributes of Object Types**
361 361  
362 -== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
362 +== 6.2 Unique identification of SDMX objects ==
363 363  
364 -=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
364 +=== 6.2.1 Agencies and Metadata Providers ===
365 365  
366 366  The [[Maintenance Agency>>doc:Glossary.Maintenance agency.WebHome]] in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
367 367  
... ... @@ -369,20 +369,20 @@
369 369  
370 370  **Figure 6: Agency Scheme Model**
371 371  
372 -The Agency in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top (% style="color:#e74c3c" %)level(%%) of this structure is maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top (% style="color:#e74c3c" %)level(%%) can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] has a fixed id and (% style="color:#e74c3c" %)version(%%) ((% style="color:#e74c3c" %)version(%%) ‘1.0’) and is never declared explicitly in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
372 +The Agency in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top level of this structure is maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] has a fixed id and [[version>>doc:Glossary.Version.WebHome]] ([[version>>doc:Glossary.Version.WebHome]]‘1.0’) and is never declared explicitly in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
373 373  
374 374  In order to achieve this [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules:
375 375  
376 376  * Agencies are maintained in an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme).
377 377  * The agency of the [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
378 -* The “top-(% style="color:#e74c3c" %)level(%%)” agency is [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-(% style="color:#e74c3c" %)level(%%)” [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
379 -* Agencies registered in the top-(% style="color:#e74c3c" %)level(%%) scheme can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] and so on.
380 -* The AgencyScheme has a fixed (% style="color:#e74c3c" %)version(%%), i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:Glossary.Artefact.WebHome]] follow.
378 +* The “top-level” agency is [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-level” [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
379 +* Agencies registered in the top-level scheme can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] and so on.
380 +* The AgencyScheme has a fixed [[version>>doc:Glossary.Version.WebHome]], i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:Glossary.Artefact.WebHome]] follow.
381 381  * There can be only one AgencyScheme maintained by any one Agency. It has a fixed id of AGENCIES.
382 382  * The /hierarchy of Organisation is not inherited by [[Maintenance Agency>>doc:Glossary.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] is a flat list of Maintenance Agencies.
383 -* The format of the agency identifier is agencyID.agencyID etc. The top-(% style="color:#e74c3c" %)level(%%) agency in this identification mechanism is the agency registered in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:Glossary.Agency scheme.WebHome]].
383 +* The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:Glossary.Agency scheme.WebHome]].
384 384  
385 -In other words, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] and is contained in the top-(% style="color:#e74c3c" %)level(%%) [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
385 +In other words, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] and is contained in the top-level [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
386 386  
387 387  This supports a hierarchical structure of agencyID.
388 388  
... ... @@ -413,7 +413,7 @@
413 413  
414 414  Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]], i.e., the Metadatasets; the latter are the containers of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] combined with a target that those metadata refer to.
415 415  
416 -=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
416 +=== 6.2.2 Universal Resource Name (URN) ===
417 417  
418 418  ==== 6.2.2.1 Introduction ====
419 419  
... ... @@ -430,9 +430,9 @@
430 430  
431 431  ~* this can repeat and may not be present (see explanation below)
432 432  
433 -Note that in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. For this reason, the only (% style="color:#e74c3c" %)version(%%) information that is allowed is for the maintainable object.
433 +Note that in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. For this reason, the only [[version>>doc:Glossary.Version.WebHome]] information that is allowed is for the maintainable object.
434 434  
435 -The [[Maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The (% style="color:#e74c3c" %)version(%%) information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning.
435 +The [[Maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The [[version>>doc:Glossary.Version.WebHome]] information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning.
436 436  
437 437  ==== 6.2.2.3 Explanation of the generic structure ====
438 438  
... ... @@ -457,11 +457,11 @@
457 457  
458 458  **maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object.
459 459  
460 -**maintainable-object-version** is the (% style="color:#e74c3c" %)version(%%), according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present.
460 +**maintainable-object-version** is the [[version>>doc:Glossary.Version.WebHome]], according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present.
461 461  
462 -**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a [[Code>>doc:Glossary.Code.WebHome]] is in a maintained object (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower (% style="color:#e74c3c" %)level(%%) in its [[hierarchy>>doc:Glossary.Hierarchy.WebHome]]. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure.
462 +**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a [[Code>>doc:Glossary.Code.WebHome]] is in a maintained object (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower [[level>>doc:Glossary.Level.WebHome]] in its [[hierarchy>>doc:Glossary.Hierarchy.WebHome]]. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure.
463 463  
464 -Note that although a [[Code>>doc:Glossary.Code.WebHome]] can have a parent [[Code>>doc:Glossary.Code.WebHome]] and a (% style="color:#e74c3c" %)Concept(%%) can have a parent (% style="color:#e74c3c" %)Concept(%%) these are maintained in a flat structure and therefore do not have a containerobject-id.
464 +Note that although a [[Code>>doc:Glossary.Code.WebHome]] can have a parent [[Code>>doc:Glossary.Code.WebHome]] and a (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have a parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) these are maintained in a flat structure and therefore do not have a containerobject-id.
465 465  
466 466  For example, the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
467 467