Changes for page SDMX 2.1 Standards. Section 5. Registry Specification: Logical Interfaces

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

From 1.6 to 1.7 From 2.3 to 2.4

From version 1.7

edited by Helena
on 2025/05/21 13:49

Change comment: There is no comment for this version

To version 2.3

edited by Helena
on 2025/05/21 14:19

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -340,8 +340,8 @@
  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
--|(% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour**
--|(% style="width:143px" %)All|(% style="width:1729px" %)(((
++|(% style="width:244px" %)**Interface**|**Behaviour**
++|(% style="width:244px" %)All|(((
 ) 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:
  * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
@@ -365,11 +365,10 @@
 ) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
  )))
--|(% style="width:143px" %)SubmitStructureRequest|(% style="width:1729px" %)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.
--|(% style="width:143px" %)SubmitProvisioningRequest|(% style="width:1729px" %)No additional behaviour.
--|(% style="width:143px" %)Submit Registration Request|(% style="width:1729px" %)(((
++|(% 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.
++|(% style="width:244px" %)SubmitProvisioningRequest|No additional behaviour.
++|(% style="width:244px" %)Submit Registration Request|(((
  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.
--
  For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
  )))
@@ -470,9 +470,10 @@
  An example of this is shown in the XML snippet below.
--[[image:1747824123013-196.jpeg]]
++[[image:1747824123013-196.jpeg||height="309" width="446"]]
--==== Figure 8: Example Showing Use of Agency Identifiers ====
++(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
++**Figure 8: Example Showing Use of Agency Identifiers**
  Each of these maintenance agencies has an identical Code list with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
@@ -512,10 +512,8 @@
  **(maintainable-object-version)** is the version of the maintainable object and is enclosed in round brackets (). It will always be present.
--**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 is in a maintained object (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a
++**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 is in a maintained object (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor 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 Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure.
--URN, the id of the Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure.
--
  Note that although a Code can have a parent Code and a Concept can have a parent Concept these are maintained in a flat structure and therefore do not have a container-object-id.
  For example the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
@@ -522,30 +522,29 @@
  **object-id** is the identifier of the actual object unless the actual object is a maintainable object. If present it is always the last id and is not followed by any other character.
--===== //Generic Examples of the URN Structure// =====
++===== __**//Generic Examples of the URN Structure//**__ =====
++__Actual object is a maintainable__
--Actual object is a maintainable
--
  SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
--Actual object is contained in a maintained object with no intermediate containing object
++__Actual object is contained in a maintained object with no intermediate containing object__
  SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
--Actual object is contained in a maintained object with an intermediate containing object
++__Actual object is contained in a maintained object with an intermediate containing object__
  SDMXPrefix.SDMX-IM package name.classname=agency
  id:maintained-object-id(version).contained-object-id.object-id
--Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical
++__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__
  In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a Category Scheme. The Category is hierarchical and all intermediate Categories are shown as a contained object. The example below shows the generic structure for Category Scheme/Category/Category
  SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
--Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
++__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
  In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata Attribute where the contained objects are Report Structure (first contained object id) and Metadata Attribute (subsequent contained object Ids). The example below shows the generic structure for MSD/Report Structure/Metadata Attribute/Metadata Attribute