Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.3
edited by Helena
on 2025/05/21 15:27
Change comment: There is no comment for this version
To version 3.2
edited by Helena
on 2025/05/21 15:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -288,25 +288,27 @@
288 288  * that a queryable data source exists - this would necessitate the registration service querying the service to determine its existence
289 289  * that a simple data source exists (i.e. a file accessible at a URL)
290 290  * that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data that the components (Dimensions, Attributes, Measures, Identifier Components etc.) are consistent with the Data Structure Definition or Metadata Structure Definition
291 -* that the valid representations of the concepts to which these components correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
291 +* that the valid representations of the concepts to which these components 382 correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
292 292  
293 293  3The Registration has an action attribute which takes one of the following values:
294 294  
295 -(% style="margin-left:auto; margin-right:auto" %)
296 -|(% style="width:200px" %)(((
295 +|(% style="width:249px" %)(((
297 297  **Action Attribute Value**
298 -)))|(% style="width:1672px" %)**Behaviour**
299 -|(% style="width:200px" %)Append|(% style="width:1672px" %)Add this registration to the registry
300 -|(% style="width:200px" %)Replace|(% style="width:1672px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
301 -|(% style="width:200px" %)Delete|(% style="width:1672px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
297 +)))|(% style="width:1622px" %)**Behaviour**
298 +|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry
299 +|(% style="width:249px" %)Replace|(% style="width:1622px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
300 +|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
301 +
302 302  The Registration has three Boolean attributes which may be present to determine how an SDMX compliant Dataset or Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows:
303 -|(% style="width:200px" %)**Boolean Attribute**|(% style="width:1672px" %)**Behaviour if Value is “true”**
304 -|(% style="width:200px" %)indexTimeSeries|(% style="width:1672px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
305 -|(% style="width:200px" %)indexDataSet|(% style="width:1672px" %)(((
303 +
304 +|**Boolean Attribute**|**Behaviour if Value is “true”**
305 +|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
306 +|indexDataSet|(((
306 306  A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
308 +
307 307  Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
308 308  )))
309 -|(% style="width:200px" %)indexReportingPeriod|(% style="width:1672px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
311 +|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
310 310  
311 311  === 5.2.5 Data and Reference Metadata Discovery ===
312 312  
... ... @@ -338,8 +338,8 @@
338 338  
339 339  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
340 340  
341 -|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour**
342 -|(% style="width:227px" %)All|(% style="width:1644px" %)(((
343 +|(% style="width:244px" %)**Interface**|**Behaviour**
344 +|(% style="width:244px" %)All|(((
343 343  1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final attribute is set to “true” in which case the only changes that are allowed are to the following constructs:
344 344  
345 345  * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
... ... @@ -353,6 +353,7 @@
353 353  * isExternalReference
354 354  
355 355  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.
358 +
356 356  3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
357 357  
358 358  а) Not have the final attribute set to “true”
... ... @@ -359,11 +359,12 @@
359 359  b) Not be referenced from any other object in the Registry.
360 360  
361 361  4) The version rules in the SDMX Schema documentation MUST be obeyed.
365 +
362 362  5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
363 363  )))
364 -|(% style="width:227px" %)SubmitStructureRequest|(% style="width:1644px" %)Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
365 -|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour.
366 -|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)(((
368 +|(% style="width:244px" %)SubmitStructureRequest|Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
369 +|(% style="width:244px" %)SubmitProvisioningRequest|No additional behaviour.
370 +|(% style="width:244px" %)Submit Registration Request|(((
367 367  If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration.
368 368  For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
369 369  )))
... ... @@ -486,7 +486,7 @@
486 486  
487 487  The generic structure of the URN is as follows:
488 488  
489 ->SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
493 +SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
490 490  
491 491  ~* this can repeat and may not be present (see explanation below)
492 492  
... ... @@ -1170,7 +1170,7 @@
1170 1170  
1171 1171  [[image:1747824123025-411.jpeg]]
1172 1172  
1173 -**Figure 16: Schematic of the Objects Concerned with Registration**
1177 + **Figure 16: Schematic of the Objects Concerned with Registration**
1174 1174  
1175 1175  ==== 7.4.2.2 Registration Request Model ====
1176 1176