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.3 to 1.2 From 9.4 to 9.3

From version 9.3

edited by Helena
on 2025/05/23 13:00

Change comment: There is no comment for this version

To version 1.3

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 11 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--SDMX 2.1 Standards. Section 5. Registry Specification – Logical Interfaces
++SDMX 2.1 Standards. Section. 5. Registry Specification – Logical Interfaces

Content

@@ -4,11 +4,10 @@
  **Revision History**
--(% style="width:833.294px" %)
--|(% style="width:122px" %)**Revision**|(% style="width:126px" %)**Date**|(% style="width:581px" %)**Contents**
--|(% style="width:122px" %) |(% style="width:126px" %)April 2011|(% style="width:581px" %)Initial release
--|(% style="width:122px" %)1.0|(% style="width:126px" %)July 2011|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011
--|(% style="width:122px" %)2.0|(% style="width:126px" %)July 2020|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
++|**Revision**|**Date**|**Contents**
++| |April 2011|Initial release
++|1.0|July 2011|Rectification of problems of the specifications dated April 2011
++|2.0|July 2020|Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
  **Corrigendum**
@@ -289,22 +289,27 @@
  * that a queryable data source exists - this would necessitate the registration service querying the service to determine its existence
  * that a simple data source exists (i.e. a file accessible at a URL)
  * 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
--* 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
++*  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
--The Registration has an action attribute which takes one of the following values:
++3The Registration has an action attribute which takes one of the following values:
--|(% style="width:219px" %)**Action Attribute Value**|(% style="width:1652px" %)**Behaviour**
--|(% style="width:219px" %)Append|(% style="width:1652px" %)Add this registration to the registry
--|(% style="width:219px" %)Replace|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
--|(% style="width:219px" %)Delete|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++|(% style="width:249px" %)(((
++**Action Attribute Value**
++)))|(% style="width:1622px" %)**Behaviour**
++|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry
++|(% 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
++|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
  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:
--|(% style="width:228px" %)**Boolean Attribute**|(% style="width:1644px" %)**Behaviour if Value is “true”**
--|(% style="width:228px" %)indexTimeSeries|(% style="width:1644px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
--|(% style="width:228px" %)indexDataSet|(% style="width:1644px" %)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.
++|**Boolean Attribute**|**Behaviour if Value is “true”**
++|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)
++|indexDataSet|(((
++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.
++
  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
--|(% style="width:228px" %)indexReportingPeriod|(% style="width:1644px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
++)))
++|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
  === 5.2.5 Data and Reference Metadata Discovery ===
@@ -326,7 +326,7 @@
  Subscription management involves a user submitting a subscription request which contains:
  * a query or 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, or for a domain category, or changes to a Data Structure Definition).
--* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
++* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address)
  * request for a list of submitted subscriptions
  * deletion of a subscription
@@ -336,12 +336,13 @@
  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
--|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour**
--|(% style="width:227px" %)All|(% style="width:1644px" %)(((
++|**Interface**|**Behaviour**
++|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.
  * Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
++
  * Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
  * validTo
  * validFrom
@@ -350,22 +350,26 @@
  * uri
  * isExternalReference
--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.
--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:
++1. 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.
++1. 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:
--а) Not have the final attribute set to “true”
--b) Not be referenced from any other object in the Registry.
++1. Not have the final attribute set to “true”
++1. Not be referenced from any other object in the Registry.
--4) The version rules in the SDMX Schema documentation MUST be obeyed.
--5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
++1. The version rules in the SDMX Schema documentation MUST be obeyed.
++
++* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
  )))
--|(% 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.
--|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour.
--|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)(((
++|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.
++|SubmitProvisioningRequest|No additional behaviour.
++|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.
  )))
++
++
  = 6 Identification of SDMX Objects =
  == 6.1 Identification, Versioning, and Maintenance ==
@@ -372,6 +372,7 @@
  All major classes of the SDMX Information model inherit from one of:
++
  * **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.
  * **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description,
  * **VersionableArtefact **– this has all of the above features plus a version number and a validity period.
@@ -379,8 +379,6 @@
  === 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
--[[image:1747824504225-229.png]]
--
  **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
@@ -391,34 +391,38 @@
  * Versionable
  * Maintainable
--(% style="width:935.294px" %)
--|**Object Type**|(% style="width:244px" %)**Data Attributes**|(% style="width:99px" %)**Status**|**Data type**|(% style="width:389px" %)**Notes**
--|Annotable|(% style="width:244px" %)AnnotationTitle|(% style="width:99px" %)C|string|(% style="width:389px" %)
--| |(% style="width:244px" %)AnnotationType|(% style="width:99px" %)C|string|(% style="width:389px" %)
--| |(% style="width:244px" %)AnnotationURN|(% style="width:99px" %)C|string|(% style="width:389px" %)
--| |(% style="width:244px" %)(((
--AnnotationText in the form of International String
--)))|(% style="width:99px" %)C| |(% style="width:389px" %)This can have languagespecific variants.
--|Identifiable|(% style="width:244px" %)all content as for Annotable plus|(% style="width:99px" %) | |(% style="width:389px" %)
--| |(% style="width:244px" %)id|(% style="width:99px" %)M|string|(% style="width:389px" %)
--| |(% style="width:244px" %)uri|(% style="width:99px" %)C|string|(% style="width:389px" %)
--| |(% style="width:244px" %)urn|(% style="width:99px" %)C|string|(% style="width:389px" %)Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
--|Nameable|(% style="width:244px" %)all content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
--| |(% style="width:244px" %)Name in the form of International String|(% style="width:99px" %)M|string|(% style="width:389px" %)This can have languagespecific variants.
--| |(% style="width:244px" %)(((
--Description in the form of International String
--)))|(% style="width:99px" %)C|string|(% style="width:389px" %)This can have languagespecific variants.
--|Versionable|(% style="width:244px" %)All content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
--| |(% style="width:244px" %)version|(% style="width:99px" %)C|string|(% style="width:389px" %)This is the version number. If not present the default is 1.0
--| |(% style="width:244px" %)validFrom|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
--| |(% style="width:244px" %)validTo|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
--|Maintainable|(% style="width:244px" %)All content as for Versionable plus|(% style="width:99px" %) | |(% style="width:389px" %)
--| |(% style="width:244px" %)final|(% style="width:99px" %) |boolean|(% style="width:389px" %)Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted.
--| |(% style="width:244px" %)isExternalReference|(% style="width:99px" %)C|boolean|(% style="width:389px" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURI, each of which must return a valid SDMX-ML file.
--| |(% style="width:244px" %)serviceURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the service that can be queried for this resource
--| |(% style="width:244px" %)structureURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the resource.
--| |(% style="width:244px" %)(Maintenance) agencyId|(% style="width:99px" %)M|string|(% style="width:389px" %)The object must be linked to a maintenance agency.
++|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
++|Annotable|AnnotationTitle|C|string|
++| |AnnotationType|C|string|
++| |AnnotationURN|C|string|
++| |(((
++AnnotationText in the form of
++International String
++)))|C| |This can have languagespecific variants.
++| | | | |
++|Identifiable|all content as for Annotable plus| | |
++| |id|M|string|
++| |uri|C|string|
++| |urn|C|string|Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
++|Nameable|all content as for Identifiable plus| | |
++| |Name in the form of International String|M|string|This can have languagespecific variants.
++| |(((
++Description in the form of International
++
++String
++)))|C|string|This can have languagespecific variants.
++|Versionable|All content as for Identifiable plus| | |
++| |version|C|string|This is the version number. If not present the default is 1.0
++| |validFrom|C|Date/time|
++| |validTo|C|Date/time|
++|Maintainable|All content as for Versionable plus| | |
++| |final| |boolean|Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted.
++| |isExternalReference|C|boolean|Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURI, each of which must return a valid SDMX-ML file.
++| |serviceURL|C|string|The url of the service that can be queried for this resource
++| |structureURL|C|string|The url of the resource.
++| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency.
++
  **Table 1: Common Attributes of Object Types**
  == 6.2 Unique identification of SDMX objects ==
@@ -427,8 +427,6 @@
  The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
--[[image:1747994320263-112.png]]
--
  **Figure 6: Agency Scheme Model**
  The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an n-level structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version and is never declared explicitly in the SDMX object identification mechanism.
@@ -450,7 +450,7 @@
  [[image:1747824123012-527.jpeg]]
--**Figure 7: Example of Hierarchic Structure of Agencies**
++==== Figure 7: Example of Hierarchic Structure of Agencies ====
  The following organizations maintain an Agency Scheme.
@@ -465,10 +465,11 @@
  An example of this is shown in the XML snippet below.
--[[image:1747832400104-286.png]]
--**Figure 8: Example Showing Use of Agency Identifiers**
++[[image:1747824123013-196.jpeg]]
++==== 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.
  === 6.2.2 Universal Resource Name (URN) ===
@@ -479,14 +479,13 @@
  ==== 6.2.2.2 URN Structure ====
--(% class="wikigeneratedid" id="HCaseRulesforURN" %)
--//Case Rules for URN//
++===== //Case Rules for URN// =====
  For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
  The generic structure of the URN is as follows:
-->SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
++SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
  ~* this can repeat and may not be present (see explanation below)
@@ -498,7 +498,7 @@
  In the explanation below the actual object that is the target of the URN is called the **//actual object//**.
--**SDMXPrefix:** urn:sdmx:org.
++**SDMXPrefix:** urn:sdmx:org.
  **SDMX-IM package name:** sdmx.infomodel.package=
@@ -508,8 +508,10 @@
  **(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 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.
++**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.
++
  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.
@@ -516,57 +516,58 @@
  **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__
--> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
++Actual object is a maintainable
--__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)
--> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
++Actual object is contained in a maintained object with no 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).object-id
--> SDMXPrefix.SDMX-IM package name.classname=agency
++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
++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
--> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
++SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
--===== __**//Concrete Examples of the URN Structure//**__ =====
++===== //Concrete Examples of the URN Structure// =====
  The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
--> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
++urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
  The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
--> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
++urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
  The URN for a category (id of 1) which has parent category (id of 2) maintained by SDMX in the category scheme SUBJECT_MATTER_DOMAINS version 1.0 would be:
--> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
++urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
  The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA version 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
  CONTACT_DETAILS/CONTACT_NAME would be:
--> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
++urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
  The TFFS defines ABC as a sub Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be:
--> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
++urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
  TERNAL_DEBT(1.0)
@@ -581,94 +581,112 @@
  The table below lists all of the packages in the SDMX-IM together with the concrete classes that are in these packages and whose objects have a URN.
--|(% style="width:127px" %)**Package**|(% style="width:1745px" %)(((
--**URN Classname (model classname where this is different)**
++|**Package**|(((
++**URN Classname (model classname**
++
++**where this is different)**
  )))
--|(% style="width:127px" %)base|(% style="width:45px" %)Agency
--|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnitScheme
--|(% style="width:127px" %) |(% style="width:45px" %)AgencyScheme
--|(% style="width:127px" %) |(% style="width:45px" %)DataProviderScheme
--|(% style="width:127px" %) |(% style="width:45px" %)DataConsumerScheme
--|(% style="width:127px" %) |(% style="width:45px" %)OrganisationUnit
--|(% style="width:127px" %) |(% style="width:45px" %)DataProvider
--|(% style="width:127px" %) |(% style="width:45px" %)DataConsumer
--|(% style="width:127px" %)datastructure|(% style="width:45px" %)DataStructure (DataStructureDefinition)
--|(% style="width:127px" %) |(% style="width:45px" %)AttributeDescriptor
--|(% style="width:127px" %) |(% style="width:45px" %)DataAttribute
--|(% style="width:127px" %) |(% style="width:45px" %)GroupDimensionDescriptor
--|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptor
--|(% style="width:127px" %) |(% style="width:45px" %)Dimension
--|(% style="width:127px" %) |(% style="width:45px" %)MeasureDimension
--|(% style="width:127px" %) |(% style="width:45px" %)TimeDimension
--|(% style="width:127px" %) |(% style="width:45px" %)MeasureDescriptor
--|(% style="width:127px" %) |(% style="width:45px" %)PrimaryMeasure
--|(% style="width:127px" %) |(% style="width:45px" %)Dataflow (DataflowDefinition)
--|(% style="width:127px" %)metadatastructure|(% style="width:45px" %)MetadataTarget
--|(% style="width:127px" %) |(% style="width:45px" %)DimensionDescriptorValueTarget
--|(% style="width:127px" %) |(% style="width:45px" %)IdentifiableObjectTarget
--|(% style="width:127px" %) |(% style="width:45px" %)ReportPeriodTarget
--|(% style="width:127px" %) |(% style="width:45px" %)DataSetTarget
--|(% style="width:127px" %) |(% style="width:45px" %)ReportStructure
--|(% style="width:127px" %) |(% style="width:45px" %)MetadataAttribute
--|(% style="width:127px" %) |(% style="width:45px" %)(((
++|base|Agency
++| |OrganisationUnitScheme
++| |AgencyScheme
++| |DataProviderScheme
++| |DataConsumerScheme
++| |OrganisationUnit
++| |DataProvider
++| |DataConsumer
++| |
++|datastructure|DataStructure (DataStructureDefinition)
++| |AttributeDescriptor
++| |DataAttribute
++| |GroupDimensionDescriptor
++| |DimensionDescriptor
++| |Dimension
++| |MeasureDimension
++| |TimeDimension
++| |MeasureDescriptor
++| |PrimaryMeasure
++| |Dataflow (DataflowDefinition)
++| |
++|metadatastructure|MetadataTarget
++| |DimensionDescriptorValueTarget
++| |IdentifiableObjectTarget
++| |ReportPeriodTarget
++| |DataSetTarget
++| |ReportStructure
++| |MetadataAttribute
++| |(((
  MetadataStructure
  (MetadataStructureDefinition)
  )))
--|(% style="width:127px" %) |(% style="width:45px" %)Metadataflow (MetadataflowDefinition)
--|(% style="width:127px" %)process|(% style="width:45px" %)Process
--|(% style="width:127px" %) |(% style="width:45px" %)ProcessStep
--|(% style="width:127px" %) |(% style="width:45px" %)Transition
--|(% style="width:127px" %)registry|(% style="width:45px" %)ProvisionAgreement
--|(% style="width:127px" %) |(% style="width:45px" %)AttachmentConstraint
--|(% style="width:127px" %) |(% style="width:45px" %)ContentConstraint
--|(% style="width:127px" %) |(% style="width:45px" %)Subscription
--|(% style="width:127px" %)mapping|(% style="width:45px" %)StructureMap
--|(% style="width:127px" %) |(% style="width:45px" %)StructureSet
--|(% style="width:127px" %) |(% style="width:45px" %)ComponentMap
--|(% style="width:127px" %) |(% style="width:1745px" %)ConceptSchemeMap
--|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationSchemeMap
--|(% style="width:127px" %) |(% style="width:1745px" %)CodelistMap
--|(% style="width:127px" %) |(% style="width:1745px" %)CategorySchemeMap
--|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomyMap
--|(% style="width:127px" %) |(% style="width:1745px" %)ConceptMap
--|(% style="width:127px" %) |(% style="width:1745px" %)OrganisationMap
--|(% style="width:127px" %) |(% style="width:1745px" %)CodeMap
--|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodelistMap
--|(% style="width:127px" %) |(% style="width:1745px" %)CategoryMap
--|(% style="width:127px" %) |(% style="width:1745px" %)HybridCodeMap
--|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategoryMap
--|(% style="width:127px" %)codelist|(% style="width:1745px" %)Codelist
--|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCodelist
--|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy
--|(% style="width:127px" %) |(% style="width:1745px" %)Hierarchy
--|(% style="width:127px" %) |(% style="width:1745px" %)Code
--|(% style="width:127px" %) |(% style="width:1745px" %)HierarchicalCode
--|(% style="width:127px" %) |(% style="width:1745px" %)Level
--|(% style="width:127px" %)categoryscheme|(% style="width:1745px" %)CategoryScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)Category
--|(% style="width:127px" %) |(% style="width:1745px" %)Categorisation
--|(% style="width:127px" %) |(% style="width:1745px" %)ReportingTaxonomy
--|(% style="width:127px" %) |(% style="width:1745px" %)ReportingCategory
--|(% style="width:127px" %)conceptscheme|(% style="width:1745px" %)ConceptScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)Concept
--|(% style="width:127px" %)transformation|(% style="width:1745px" %)TransformationScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)Transformation
--|(% style="width:127px" %) |(% style="width:1745px" %)CustomTypeScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)CustomType
--|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisationScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)NamePersonalisation
--|(% style="width:127px" %) |(% style="width:1745px" %)VtlCodelistMapping
--|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptMapping
--|(% style="width:127px" %) |(% style="width:1745px" %)VtlDataflowMapping
--|(% style="width:127px" %) |(% style="width:1745px" %)VtlConceptSchemeMapping
--|(% style="width:127px" %) |(% style="width:1745px" %)RulesetScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)Ruleset
--|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperatorScheme
--|(% style="width:127px" %) |(% style="width:1745px" %)UserDefinedOperator
++| |Metadataflow (MetadataflowDefinition)
++| |
++|process|Process
++| |ProcessStep
++| |Transition
++| |
++|registry|ProvisionAgreement
++| |AttachmentConstraint
++| |ContentConstraint
++| |Subscription
++| |
++|mapping|StructureMap
++| |StructureSet
++| |ComponentMap
++|**Package**|(((
++**URN Classname (model classname**
++**where this is different)**
++)))
++| |ConceptSchemeMap
++| |OrganisationSchemeMap
++| |CodelistMap
++| |CategorySchemeMap
++| |ReportingTaxonomyMap
++| |ConceptMap
++| |OrganisationMap
++| |CodeMap
++| |HybridCodelistMap
++| |CategoryMap
++| |HybridCodeMap
++| |ReportingCategoryMap
++| |
++|codelist|Codelist
++| |HierarchicalCodelist
++| |Hierarchy
++| |Hierarchy
++| |Code
++| |HierarchicalCode
++| |Level
++| |
++|categoryscheme|CategoryScheme
++| |Category
++| |Categorisation
++| |ReportingTaxonomy
++| |ReportingCategory
++| |
++|conceptscheme|ConceptScheme
++| |Concept
++| |
++|transformation|TransformationScheme
++| |Transformation
++| |CustomTypeScheme
++| |CustomType
++| |NamePersonalisationScheme
++| |NamePersonalisation
++| |VtlCodelistMapping
++| |VtlConceptMapping
++| |VtlDataflowMapping
++| |VtlConceptSchemeMapping
++| |RulesetScheme
++| |Ruleset
++| |UserDefinedOperatorScheme
++| |UserDefinedOperator
++| |
++
  **Table 2: SDMX-IM Packages and Contained Classes**
++
  === 6.2.4 URN Identification components of SDMX objects ===
  The table below describes the identification components for all SDMX object types that have identification. Note the actual attributes are all Id, but have been prefixed by their class name or multiple class names to show navigation, e.g. conceptSchemeAgencyId is really the Id attribute of the Agency class that is associated to the ConceptScheme.
@@ -677,50 +677,78 @@
  Note that for brevity the URN examples omit the prefix. All URNs have the prefix
--> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
++urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--(% style="width:1091.29px" %)
--|(% style="width:250px" %)**SDMX Class**|(% style="width:444px" %)**Key attribute(s)**|(% style="width:396px" %)**Example of URN**
--|(% style="width:250px" %)Agency|(% style="width:444px" %)The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|(% style="width:396px" %)(((
++
++|**SDMX Class**|**Key attribute(s)**|**Example of URN**
++|Agency|The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|(((
  IMF
++
++
  Sub agency in the IMF AGENCIES
++
++
  IMF.SubAgency1
  )))
--|(% style="width:250px" %)*ConceptScheme|(% style="width:444px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
--|(% style="width:250px" %)Concept|(% style="width:444px" %)conceptSchemeAgencyId:
--conceptSchemeId(version).conceptId|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
--|(% style="width:250px" %)*Codelist|(% style="width:444px" %)codeListAgencyId:codeListId(version)|(% style="width:396px" %)SDMX:CL_FREQ(1.0)
--|(% style="width:250px" %)Code|(% style="width:444px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:396px" %)SDMX:CL_FREQ(1.0).Q
--|(% style="width:250px" %)(((
--*Hierarchical Codelist
--)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
--UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
++|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
++|Concept|(((
++conceptSchemeAgencyId:
++
++conceptSchemeId(version).conceptId
++)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
++|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
++|Code|codeListAgencyId:codelistId(version).codeId|(((
++SDMX:CL_FREQ(1.0).Q
++
++
  )))
--|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
++
++
++
++|(((
++*Hierarchical
++
++Codelist
++)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
++UNESCO:CL_EXP_SOURCE(1.0)
++
++
++)))
++|Hierarchy|(((
  hierachicalcodeListAgencyId:
++
  hierarchicalcodelistId(version).Hierarchy
--)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
--H-C-GOV
--|(% style="width:250px" %)Level|(% style="width:444px" %)(((
++)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
++|Level|(((
  hierachicalcodeListAgencyId:
++
  hierarchicalcodelistId(version).Hierarchy.Level
--)))|(% style="width:396px" %)(((
++)))|(((
  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
++
++
  )))
--|(% style="width:250px" %)HierarchicalCode|(% style="width:444px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
--|(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
--|(% style="width:250px" %)(((
++|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
++|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
++|(((
  Dimension
++
  Descriptor
++
  Measure
++
  Descriptor
++
  Attribute
++
  Descriptor
--)))|(% style="width:444px" %)(((
++)))|(((
  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
++
  componentListId
++
  where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
--)))|(% style="width:396px" %)(((
++)))|(((
  TFFS:EXT_DEBT(1.0).DimensionDescriptor
  TFFS:EXT_DEBT(1.0).MeasureDescriptor
@@ -727,124 +727,181 @@
  TFFS:EXT_DEBT(1.0).AttributeDescriptor
  )))
--|(% style="width:250px" %)(((
++|(((
  GroupDimension
++
  Descriptor
--)))|(% style="width:444px" %)(((
++)))|(((
  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
++
  groupDimensionDescriptorId
--)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING
--|(% style="width:250px" %)Dimension|(% style="width:444px" %)(((
++)))|TFFS:EXT_DEBT(1.0).SIBLING
++|Dimension|(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
++
  dimensionId
--)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ
--|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)(((
++)))|TFFS:EXT_DEBT(1.0).FREQ
++|TimeDimension|(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
++
  timeDimensionId
--)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
--|(% style="width:250px" %)Measure Dimension|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
--measureDimensionId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
--|(% style="width:250px" %)DataAttrribute|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
--|(% style="width:250px" %)PrimaryMeasure|(% style="width:444px" %)(((
++)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
++|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
++
++
++
++| |measureDimensionId|
++|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
++|PrimaryMeasure|(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
++
  primaryMeasureId
--)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
--|(% style="width:250px" %)(((
--*Category Scheme
--)))|(% style="width:444px" %)categorySchemeAgencyId:
--categorySchemeId(version)|(% style="width:396px" %)IMF:SDDS(1.0)
--|(% style="width:250px" %)Category|(% style="width:444px" %)categorySchemeAgencyId:
--categorySchemeId(version).
--categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)(((
++)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
++|(((
++*Category
++
++Scheme
++)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
++|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
  IMF:SDDS(1.0):
++
  level_1_category.level_2_category …
  )))
--|(% style="width:250px" %)(((
--*Reporting Taxonomy
--)))|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:396px" %) IMF:REP_1(1.0)
--|(% style="width:250px" %)ReportingCategory|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:396px" %)(((
++|(((
++*Reporting
++
++Taxonomy
++)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
++|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
  IMF:REP_1(1.0):
++
  level_1_repcategory.level_2_repcategory …
  )))
--|(% style="width:250px" %)*Categorisation|(% style="width:444px" %)categorisationAgencyId: categorisationId(version)|(% style="width:396px" %)IMF:cat001(1.0)
--|(% style="width:250px" %)(((
--*Organisation Unit Scheme
--)))|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:396px" %)ECB:ORGANISATIONS(1.0)
--|(% style="width:250px" %)Organisation Unit|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:396px" %)ECB:ORGANISATIONS(1.0).1F
--|(% style="width:250px" %)*AgencyScheme|(% style="width:444px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:396px" %)ECB:AGENCIES(1.0)
++|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
++|(((
++*Organisation
--|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:1262px" %)ECB:AGENCY(1.0).AA
--|(% style="width:262px" %)(((
--*DataProvider Scheme
--)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0)
--|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
--|(% style="width:262px" %)(((
--*DataConsumer Scheme
--)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0)
--|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
--|(% style="width:262px" %)(((
--*Metadata Structure
--)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:1262px" %)IMF:SDDS_MSD(1.0)
--|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)(((
++Unit Scheme
++)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
++|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
++|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
++
++
++
++|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
++|(((
++*DataProvider
++
++Scheme
++)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
++|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
++|(((
++*DataConsumer
++
++Scheme
++)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
++|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
++|(((
++*Metadata
++
++Structure
++)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
++|MetadataTarget|(((
  MSDAgencyId:
++
  MSDId(version).metadataTargetId
--)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
--|(% style="width:262px" %)(((
++)))|IMF:SDDS_MSD(1.0).AGENCY
++|(((
  Dimension
++
  DescriptorValues
++
  Target
--)))|(% style="width:369px" %)(((
++)))|(((
  MSDAgencyId: MSDId(version).
++
  metadataTargetId.keyDescriptorValueTargetId
--)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
--|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)(((
--MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
--)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
--|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)(((
++)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
++|Identifiable ObjectTarget|(((
  MSDAgencyId:
--MSDId(version).metadataTargetId.dataSetTargetId
--)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
--|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)(((
--MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
--)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
--|(% style="width:251px" %)(((
++MSDId(version).metadataTargetId.identifiable
++
++ObjectTargetId
++)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
++|DataSetTarget|(((
++MSDAgencyId:
++
++MSDId(version).metadataTargetId.dataSet
++
++TargetId
++)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
++|PeportPeriod Target|(((
++MSDAgencyId:
++
++MSDId(version).metadataTargetId.reportPeriod
++
++TargetId
++)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
++
++
++
++|(((
  ReportStructure
--)))|(% style="width:442px" %)(((
--MSDAgencyId: MSDId(version).reportStructureId
--)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
--|(% style="width:251px" %)(((
--Metadata Attribute
--)))|(% style="width:442px" %)(((
--MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
--)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
--|(% style="width:251px" %)*Dataflow|(% style="width:442px" %)dataflowAgencyId: dataflowId(version)|(% style="width:1178px" %)TFFS:CRED_EXT_DEBT(1.0)
--|(% style="width:251px" %)*Provision Agreement|(% style="width:442px" %)(((
++
++
++)))|(((
++MSDAgencyId:
++
++MSDId(version).reportStructureId
++)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
++|(((
++Metadata
++
++Attribute
++)))|(((
++MSDAgencyId:
++
++MSDId(version).reportStructureId.metadataattri buteID
++)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
++|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
++|*Provision Agreement|(((
  provisionAgreementAgencyId:provisionAgreem entId(version)
--)))|(% style="width:1178px" %)(((
++
++
++)))|(((
  TFFS:CRED_EXT_DEBT_AB(1.0)
++
++
++
  )))
--|(% style="width:251px" %)(((
--*Content Constraint
--)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
--|(% style="width:251px" %)(((
--*Attachment Constraint
--)))|(% style="width:442px" %)(((
++|(((
++*Content
++
++Constraint
++)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
++|(((
++*Attachment
++
++Constraint
++)))|(((
  constraintAgencyId:
  attachmentConstraintId(version)
--)))|(% style="width:1178px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
--|(% style="width:251px" %)*Metadataflow|(% style="width:442px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:1178px" %)IMF:SDDS_FLOW(1.0)
--|(% style="width:251px" %)*StructureSet|(% style="width:442px" %)structureSetAgencyId: structureSetId(version)|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0)
--|(% style="width:251px" %)StructureMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
--|(% style="width:251px" %)Component Map|(% style="width:442px" %)(((
++)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
++|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
++|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
++|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
++|Component Map|(((
  structureSetAgencyId: structureSetId(version).
  structureMapId. componentMapId
--)))|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
--|(% style="width:251px" %)CodelistMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
--|(% style="width:251px" %)CodeMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version).|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
++)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
++|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
++|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
++
++
  | |(((
  codeListMapId.
@@ -851,7 +851,9 @@
  codeMapId
  )))|
  |(((
--CategorySchemeMap
++Category
++
++SchemeMap
  )))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
  |CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
  |Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
@@ -865,53 +865,71 @@
  structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
  conceptMapId
++
  )))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
  |(((
--ReportingTaxonomyMap
++Reporting
++
++TaxonomyMap
  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
  |(((
--ReportingCategoryMap
++Reporting
++
++CategoryMap
  )))|(((
  structureSetAgencyId: structureSetId(version).
++
  reportngCategoryId
  )))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
++
++
  |(((
--HybridCodelistMap
--)))|structureSetAgencyId: structureSetId(version).
--hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
++HybridCodelist
++
++Map
++)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
  |HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
  |*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
  |ProcessStep|(((
  processAgencyId: processId(version).
++
  processStepId
  )))|BIS:PROCESS1(1.0).STEP1
  |Transition|(((
  processAgencyId: processId(version).
++
  processStepId transitionId
  )))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
  |Subscription|The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message.
  |(((
--*Transformation Scheme
++*Transformation
++
++Scheme
  )))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
  |Transformation|(((
  transformationSchemeAgencyId transformationSchemeId(version)
++
  transformationId
  )))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
  |CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
++
++
  |CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
  |(((
  Name
++
  Personalisation
++
  Scheme
  )))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
  |(((
  Name
++
  Personalisation
--)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
--namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
++)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
  |VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
  |VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
  |VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
@@ -924,12 +924,15 @@
  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
  |(((
--UserDefinedOperatorScheme
++UserDefined
++
++OperatorScheme
  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
--**Table 3: Table of identification components for SDMX Identifiable Artefacts**
++7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
++
  = 7 Implementation Notes =
  == 7.1 Structural Definition Metadata ==
@@ -950,72 +950,109 @@
  The following table lists the Maintainable Artefacts.
--(% style="width:640.294px" %)
--|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content**
--|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %)
--|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code
--|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept
--|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category
--|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit
--|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency
--|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider
--|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer
--|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category
--|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation
--|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type
--|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation
--|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping
--|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping
--|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping
--|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset
--|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator
--|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator
--|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)(((
++|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
++|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
++|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
++|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
++|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
++|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
++|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
++|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
++|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
++|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
++|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
++|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
++| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
++| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
++| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
++| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
++| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
++| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
++| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
++Vtl       Concept       Scheme
++
++Mapping
++)))
++| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
++| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
++| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
++| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)(((
  Dimension Descriptor
++
  Group Dimension
++
  Descriptor
++
  Dimension
++
  Measure Dimension
++
  Time Dimension
++
  Attribute Descriptor
++
  Data Attribute
++
  Measure Descriptor
++
  Primary Measure
  )))
--|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
--Metadata Target, Dimension Descriptor
++| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
++Metadata Target,
++
++Dimension Descriptor
++
  Values Target Identifiable
++
  Object Target
++
  Report Period Target
++
  Data SetTarget
++
  Report Structure
++
  Metadata Attribute
  )))
--|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %)
--|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %)
--|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step
--|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)(((
++| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
++| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
++| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
++| |(% colspan="2" %)None|(% colspan="2" %)Structure Set|(% colspan="2" %)(((
  Component Map
++
  Concept Scheme Map
++
  Codelist Map
++
  Category Scheme Map
++
  Reporting Taxonomy Map
++
  Organisation Scheme Map
++
  Concept Map
++
  Code Map
++
  Category Map
++
  Organisation Map
++
  Reporting Category Map
++
  Hybrid Codelist Map
++
  Hybrid Code Map
  )))
--|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %)
--|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)(((
++| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
++| |(% colspan="2" %)None|(% colspan="2" %)Hierarchical Codelist|(% colspan="2" %)(((
  Hierarchy
++
  Hierarchical Code
  )))
++| | | | | | |
--**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
++**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
  === 7.1.2 Item Scheme, Structure ===
@@ -1022,7 +1022,10 @@
  The artefacts included in the structural definitions are:
  * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
--* All types of Structure (Data Structure Definition, Metadata Structure Definition)
++* All types of Structure (Data Structure Definition, Metadata Structure
++
++Definition)
++
  * All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
  === 7.1.3 Structure Usage ===
@@ -1041,8 +1041,6 @@
  ==== 7.1.3.3 Structure Usage Model ====
--[[image:1747829078194-749.png]]
--
  **Figure 10: SDMX-IM of links from Structure Usage to Category**
  In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
@@ -1069,10 +1069,10 @@
  An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
--[[image:1747829109466-595.png]]
  **Figure 11: SDMX-IM of the Data Provider**
++
  Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
  [[image:1747824123019-181.jpeg]]
@@ -1081,10 +1081,8 @@
  The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
--[[image:1747829139951-378.png]]
--(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
--**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
++==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
@@ -1112,12 +1112,13 @@
  === 7.3.3 Data and Metadata Constraints: Model ===
--[[image:1747829204737-370.png]]
--**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
--The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
++==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
++The     class    diagram          above shows that      DataProvider, DataflowDefinition, MetadataflowDefinition,         ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
++
++
  The content of the Constraint can be found in the SDMX Information Model document.
  == 7.4 Data and Metadata Registration ==
@@ -1138,7 +1138,7 @@
  [[image:1747824123025-411.jpeg]]
--**Figure 16: Schematic of the Objects Concerned with Registration**
++  **Figure 16: Schematic of the Objects Concerned with Registration**
  ==== 7.4.2.2 Registration Request Model ====
@@ -1152,14 +1152,11 @@
  The Registration has an action attribute which takes one of the following values:
--(% style="width:970.294px" %)
--|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
--|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
--|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
--|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++|**Action Attribute Value**|**Behaviour**
++|Append|Add this Registration to the registry
++|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
++|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
--[[image:1747829290890-122.png]]
--
  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
  The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
@@ -1174,19 +1174,25 @@
  Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below.
--|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
--|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
--|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
--Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
++|**Indexing Required**|**Registration Process Activity**
++|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
++|indexDataSet|(((
++Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube
++
++Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
  )))
--|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
++|indexReportingPeriod|(((
  This applies only to a registered dataset.
++
  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
  )))
--|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
++|indexAttributes|(((
  **Data Set**
++
  Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
++
  **Metadata Set**
++
  Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value.
  )))
@@ -1196,13 +1196,14 @@
  === 7.4.3 Registration Response ===
--After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
++After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to
++“Success”, “Warning” or “Failure”.
++
  If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service.
  The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
--[[image:1747829477882-750.png]]
  **Figure 18: Logical class diagram showing the registration response**
@@ -1212,12 +1212,15 @@
  A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
--When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
++When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a
--=== 7.5.1Subscription Logical Class Diagram ===
++“notification”.
--[[image:1747829554603-150.png]]
++ 7.5.1Subscription Logical Class Diagram
++
++[[image:1747824123028-257.png]]
++
  **Figure 19: Logical Class Diagram of the Subscription**
  === 7.5.2 Subscription Information ===
@@ -1224,58 +1224,73 @@
  Regardless of the type of registry/repository events being observed, a subscription always contains:
--1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
--1. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
--1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
--1. A selector which specifies which type of events are of interest. The set of event types is:
++~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
--|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
--|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
--|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
--|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
--|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
++2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
++3. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
++
++4. A selector which specifies which type of events are of interest. The set of event types is:
++
++|**Event Type**|**Comment**
++|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
++|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
++|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
++|ALL_EVENTS|All events of the specified EventType
++
  === 7.5.3 Wildcard Facility ===
  Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
--* agencyID
--* id
--* version
++         agencyID
++         id
++
++         version
++
  Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
--//AgencyID = %
++AgencyID = %
++
  Id = %
--Version = %//
++Version = %
++
  This subscribes to all Codelists of all versions for all agencies.
--//AgencyID = AGENCY1
++AgencyID = AGENCY1
++
  Id = CODELIST1
--Version = %//
++Version = %
++
  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
--//AGENCY1
++AGENCY1
++
  AgencyID = AGENCY1
++
  Id = %
--Version = %//
++Version = %
++
  This subscribes to all versions of all Codelist objects maintained by the agency
--//AGENCY1
++AGENCY1
++
  AgencyID = %
++
  Id = CODELIST1
--Version = %//
++Version = %
++
  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
--//AGENCY1//
++AGENCY1
  Note that if the subscription is to the latest version then this can be achieved by the * character
--//i.e. Version = *//
++i.e. Version = *
  Note that a subscription using the URN mechanism cannot use wildcard characters.
@@ -1287,15 +1287,16 @@
  Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
--|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
--|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
--|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
--|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
--|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
--|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
--|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification.
--|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
++|**Selector**|**Comment**
++|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
++|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
++|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
++|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
++|**Selector**|**Comment**
++| |activate the notification.
++|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
++
  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
  == 7.6 Notification ==
@@ -1302,10 +1302,8 @@
  === 7.6.1 Logical Class Diagram ===
--[[image:1747829675568-610.png]]
--(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
--**Figure 20: Logical Class Diagram of the Notification**
++==== Figure 20: Logical Class Diagram of the Notification ====
  A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
@@ -1325,3 +1325,5 @@
  === 7.6.3 Registration Event Component ===
  The notification will contain the Registration.
++
++

1747824504225-229.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-52.8 KB

Content

1747829078194-749.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-40.4 KB

Content

1747829109466-595.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-30.4 KB

Content

1747829139951-378.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-21.1 KB

Content

1747829204737-370.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-55.8 KB

Content

1747829290890-122.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-41.4 KB

Content

1747829477882-750.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-24.6 KB

Content

1747829554603-150.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-99.1 KB

Content

1747829675568-610.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-31.1 KB

Content

1747832400104-286.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-172.3 KB

Content

1747994320263-112.png

Author

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-13.9 KB

Content