Changes for page SDMX 3.0 Standards. Section 5. Registry Specification: Logical Functionality

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

From 21.2 to 21.1 From 29.5 to 29.4

From version 29.4

edited by Helena
on 2025/05/16 14:10

Change comment: There is no comment for this version

To version 21.2

edited by Helena
on 2025/05/15 14:07

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, 1 removed)
- 1747307906944-697.png
Objects (0 modified, 0 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Content

@@ -11,7 +11,7 @@
  |(% style="width:188px" %)1.0|(% style="width:205px" %)October 2021|(% style="width:441px" %)Public release for SDMX 3.0
  )))
--= 1 Introduction =
++= {{id name="_Toc93831"/}}1 Introduction =
  The business vision for SDMX envisages the promotion of a “data sharing” model to facilitate low-cost, high-quality statistical data and metadata exchange. Data sharing reduces the reporting burden of organisations by allowing them to publish data once and let their counterparties “pull” data and related metadata as required. The scenario is based on:
@@ -33,10 +33,12 @@
  These architectural standards address the ‘how’, rather than the ‘what’, and are aimed at enabling existing SDMX standards to achieve their mission. The architectural standards address registry services, which initially comprise:
--* structural metadata repository
--* data and metadata registration
--* query
++• structural metadata repository
++• data and metadata registration
++
++• query
++
  The registry services outlined in this specification are designed to help the SDMX community manage the proliferation of SDMX assets and to support data sharing for reporting and dissemination.
  = {{id name="_Toc93832"/}}2 Scope and Normative Status =
@@ -79,8 +79,7 @@
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
--(% class="wikigeneratedid" id="HFigure1:SchematicoftheBasicStructuralArtefactsintheSDMX-IM" %)
--**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
++====== Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM ======
  Note that in Figure 1 (but also most of the relevant subsequent figures) terms that include both data and metadata have been used. For example:
@@ -107,7 +107,7 @@
  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
--* registry support of a subscription-based notification service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the subscription request.
++• registry support of a subscription-based notification service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the subscription request.
  == {{id name="_Toc93838"/}}3.5 Discovery ==
@@ -166,8 +166,9 @@
  The registry interfaces are invoked in one of two ways:
--1. The interface is the name of the root node of the SDMX-ML document
--1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
++*
++*1. The interface is the name of the root node of the SDMX-ML document
++*1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
  In addition to these interfaces the registry must support a mechanism for submitting and querying for structural metadata. This is detailed in sections 5.2.2 and 5.2.3.
@@ -183,11 +183,11 @@
  === {{id name="_Toc93847"/}}5.2.2 Structure Submission Service ===
--The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
++The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
  === {{id name="_Toc93848"/}}5.2.3 Structure Query Service ===
--The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
++The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__ [[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
  * Structure
@@ -243,22 +243,23 @@
  * that the components (Dimensions, Attributes, Measures, Metadata Attributes, 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. The Registration has an action attribute which takes one of the following values:
--(% style="width:755.294px" %)
--|(% style="width:187px" %)**Action Attribute Value**|(% style="width:566px" %)**Behaviour**
--|(% style="width:187px" %)Append|(% style="width:566px" %)Add this registration to the registry
--|(% style="width:187px" %)Replace|(% style="width:566px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
--|(% style="width:187px" %)Delete|(% style="width:566px" %)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 this Registration 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
  The Registration has three Boolean attributes which may be present to determine how an SDMX compliant dataset or metadataset indexing application must index the datasets or metadatasets upon registration. The indexing application behaviour is as follows:
--(% style="width:759.294px" %)
--|(% style="width:191px" %)**Boolean Attribute**|(% style="width:565px" %)**Behaviour if Value is “true”**
--|(% style="width:191px" %)indexTimeSeries|(% style="width:565px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
--|(% style="width:191px" %)indexDataSet|(% style="width:565px" %)(((
--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 Metadataset 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:191px" %)indexReportingPeriod|(% style="width:565px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
++|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset. The validity period of the Metadatasets may also be indexed.
  === {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
@@ -280,7 +280,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 endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~: ) and HTTP POST (a normal http:~/~/ address);
++* a list of URIs or endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address);
  * request for a list of submitted subscriptions;
  * deletion of a subscription;
@@ -292,9 +292,8 @@
  Given the above, the behaviour described in the following table concerns either draft Artefacts using semantic versioning or any Artefacts using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft Artefact that follows semantic versioning, unless a newer version is introduced according to the semantic versioning rules. Furthermore, even when draft Artefacts are submitted, the registry has to verify semantic versioning is respected against the previous non-draft versions. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned Artefacts applies to externally shared Artefacts. This means that any system may internally perform any change within a version of an Artefact, until the latter is shared outside of that system or becomes public. Then (as also explained in the SDMX Standards Section 6 “Technical Notes”) the Artefacts must adhere to the Semantic Versioning rules.
--(% style="width:757.294px" %)
--|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
--|(% style="width:188px" %)All|(% style="width:542px" %)(((
++|**Interface**|**Behaviour**
++|All|(((
 . If the action is set to “replace” (or a maintainable Artefact is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
 . 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.
 . If the action is set to “delete” (or a maintainable Artefact is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must:
@@ -301,12 +301,14 @@
  a) Be a draft version.
  )))
--|(% style="width:188px" %) |(% style="width:542px" %)(((
--b) Not be explicitly{{footnote}}With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4-draft does not break integrity of the aforementioned DSD.{{/footnote}} referenced from any other object in the Registry.
++|**Interface**|**Behaviour**
++| |(((
++b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
++
 ) The semantic versioning rules in the SDMX documentation MUST be obeyed.
  )))
--|(% style="width:188px" %)Structure submission|(% style="width:542px" %)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:188px" %)SubmitRegistrationRequest|(% style="width:542px" %)If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
++|Structure submission|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.
++|SubmitRegistrationRequest|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 data query.
  = {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
@@ -327,42 +327,43 @@
  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
--* //nnotable//
++* //Annotable//
  * //Identifiable//
  * //Nameable//
  * //Versionable//
  * //Maintainable//
++:
++
  (((
--(% style="width:1052.29px" %)
--|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
--|(% rowspan="4" %)//Annotable//|(% style="width:241px" %)AnnotationTitle|(% style="width:156px" %)C|string|(% style="width:457px" %)
--|(% style="width:241px" %)AnnotationType|(% style="width:156px" %)C|string|(% style="width:457px" %)
--|(% style="width:241px" %)AnnotationURN|(% style="width:156px" %)C|string|(% style="width:457px" %)
--|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have languagespecific variants
--|(% rowspan="4" %)//Identifiable//|(% style="width:241px" %)All content as for //Annotable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
--|(% style="width:241px" %)id|(% style="width:156px" %)M|string|(% style="width:457px" %)
--|(% style="width:241px" %)uri|(% style="width:156px" %)C|string|(% style="width:457px" %)
--|(% style="width:241px" %)urn|(% style="width:156px" %)C|string|(% style="width:457px" %)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.
--|(% rowspan="3" %)//Nameable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
--|(% style="width:241px" %)Name in the form of InternationalString|(% style="width:156px" %)M|string|(% style="width:457px" %)This can have language specific variants.
--|(% style="width:241px" %)Description in the form of InternationalString|(% style="width:156px" %)C|string|(% style="width:457px" %)This can have language specific variants.
--|(% rowspan="4" %)//Versionable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
--|(% style="width:241px" %)version|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the version number according to SDMX versioning rules.
--|(% style="width:241px" %)validFrom|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
--|(% style="width:241px" %)validTo|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
--|//Maintainable//|(% style="width:241px" %)All content as for //Versionable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
--| |(% style="width:241px" %)isExternalReference|(% style="width:156px" %)C|boolean|(% style="width:457px" %)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 structureURL, each of which must return a valid SDMX-ML file.
--| |(% style="width:241px" %)serviceURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the service that can be queried for this resource.
--| |(% style="width:241px" %)structureURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the resource.
--| |(% style="width:241px" %)(Maintenance) organisationId|(% style="width:156px" %)M|string|(% style="width:457px" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
++|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
++|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
++|AnnotationType|C|string|
++|AnnotationURN|C|string|
++|AnnotationText in the form of InternationalString|C| |This can have languagespecific variants
++|(% rowspan="4" %)//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.
++|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus| | |
++|Name in the form of InternationalString|M|string|This can have language specific variants.
++|Description in the form of InternationalString|C|string|This can have language specific variants.
++|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus| | |
++|version|M|string|This is the version number according to SDMX versioning rules.
++|validFrom|C|Date/time|
++|validTo|C|Date/time|
++|//Maintainable//|All content as for //Versionable// plus| | |
++| |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 structureURL, 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) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
  )))
  **Table 1: Common Attributes of Object Types**
--== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
++=== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ===
--=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
++===== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers =====
  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.
@@ -404,8 +404,32 @@
  An example of this is shown in the XML snippet below:
--[[image:1747307906944-697.png]]
++**<str:Codelists>**
++**<str:Codelist id="CL_FREQ" agencyID="SDMX" version="1.0.0">**
++
++**<com:Name xml:lang="en">Standard frequency Codelist</com:Name>**
++
++**</str:Codelist>**
++
++**<str:Codelist id="CL_FREQ" agencyID="AA" version="1.0.0">**
++
++**<com:Name xml:lang="en">Codelist maintained by agency AA</com:Name>**
++
++**</str:Codelist>**
++
++**<str:Codelist id="CL_FREQ" agencyID="AA.CC" version="1.0.0">**
++
++**<com:Name xml:lang="en">Codelist maintained by the AA unit CC</com:Name>**
++
++**</str:Codelist>**
++
++**<str:Codelist id="CL_FREQ" agencyID="BB.CC" version="1.0.0">**
++
++**<com:Name xml:lang="en">Codelist maintained by the BB unit CC</com:Name>**
++
++**</str:Codelist>**
++
  **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.
@@ -412,16 +412,14 @@
  Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of Maintainable Artefacts, i.e., the Metadatasets; the latter are the containers of reference metadata combined with a target that those metadata refer to.
--=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
++===== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) =====
--==== 6.2.2.1 Introduction ====
++**6.2.2.1 Introduction**
  To provide interoperability between SDMX Registry/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) SDMX-IM objects. Most of these unique identifiers are composite (containing maintenance agency, or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification components in the SDMX-RR APIs. In other words, the URN for any Identifiable Artefact is constructed from its component identifiers (agency, id, version etc.).
--==== 6.2.2.2 URN Structure ====
++**6.2.2.2 URN Structure //__Case Rules for URN__//**//&nbsp;//
--===== **//__Case Rules for URN__//** =====
--
  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
  SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-version).*containerobject-id.object-id
@@ -432,7 +432,7 @@
  The Maintenance agency identifier is separated from the maintainable artefact identifier by a colon ‘:’. All other identifiers in the SDMX URN syntax are separated by a period ‘.’. The version information is encapsulated in parentheses ‘()’ and adheres to the SDMX versioning rules, as explained in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning.
--==== 6.2.2.3 Explanation of the generic structure ====
++**6.2.2.3 Explanation of the generic structure**
  In the explanation below the actual object that is the target of the URN is called the **actual object**.
@@ -442,23 +442,10 @@
  The packages are:
--base
--codelist
--conceptscheme
--datastructure
--categoryscheme
--registry
--metadatastructure
--process
--structuremapping
--transformation
++base codelist conceptscheme datastructure categoryscheme registry metadatastructure process structuremapping transformation
--**maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object.
++**maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object. **maintainable-object-version** is the version, according to the SDMX versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always 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 (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower level 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 AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure.
--**maintainable-object-version** is the version, according to the SDMX versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always 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 (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower level 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 AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a Dimension/ TimeDimension, or a Measure.
--
  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 containerobject-id.
  For example, the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
@@ -465,7 +465,7 @@
  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__
@@ -491,27 +491,27 @@
  SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
--===== //__**Concrete Examples of the URN Structure**__// =====
++//__**Concrete Examples of the URN Structure**__//
  The Data Structure Definition CRED_EXT_DEBT of legacy version 2.1 maintained by the toplevel Agency TFFS would have the URN:
--       urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1)
++urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1)
  The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 of semantic version 1.0.0 would be:
--        urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0.0).AR
++urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0.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 of the semantic extended version 1.0.0draft would be:
--        urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
++urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
  The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA of semantic version 1.0.0 where the hierarchy of the Metadata Attribute is CONTACT_DETAILS/CONTACT_NAME would be:
--       urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribute=SDMX: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME
++urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribute=SDMX: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_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 of semantic version 1.0.0 would be:
--       urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
++urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
  The SDMX-RR MUST support this globally unique identification scheme. The SDMX-RR MUST be able to create the URN from the individual identification attributes submitted and to transform the URN to these identification attributes. The identification attributes are:
@@ -520,86 +520,85 @@
  The SDMX-RR MUST be able to resolve the unique identifier of an SDMX artefact and to produce an SDMX-ML rendering of that artefact if it is located in the Registry.
--=== {{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes ===
++===== {{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes =====
  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:651.294px" %)
--|(% style="width:134px" %)**Package**|(% style="width:502px" %)**URN class name (model class name where this is different)**
--|(% style="width:134px" %)base|(% style="width:502px" %)Agency
--|(% style="width:134px" %) |(% style="width:502px" %)AgencyScheme
--|(% style="width:134px" %) |(% style="width:502px" %)DataConsumer
--|(% style="width:134px" %) |(% style="width:502px" %)DataConsumerScheme
--|(% style="width:134px" %) |(% style="width:502px" %)DataProvider
--|(% style="width:134px" %) |(% style="width:502px" %)DataProviderScheme
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvider
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataProviderScheme
--|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnit
--|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnitScheme
--|(% style="width:134px" %)datastructure|(% style="width:502px" %)AttributeDescriptor
--|(% style="width:134px" %) |(% style="width:502px" %)DataAttribute
--|(% style="width:134px" %) |(% style="width:502px" %)Dataflow
--|(% style="width:134px" %) |(% style="width:502px" %)DataStructure (DataStructureDefinition)
--|(% style="width:134px" %) |(% style="width:502px" %)Dimension
--|(% style="width:134px" %) |(% style="width:502px" %)DimensionDescriptor
--|(% style="width:134px" %) |(% style="width:502px" %)GroupDimensionDescriptor
--|(% style="width:134px" %) |(% style="width:502px" %)Measure
--|(% style="width:134px" %) |(% style="width:502px" %)MeasureDescriptor
--|(% style="width:134px" %) |(% style="width:502px" %)TimeDimension
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)metadatastructure|(% style="width:502px" %)MetadataAttribute
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataAttributeDescriptor
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataStructure MetadataStructureDefinition)
--|(% style="width:134px" %) |(% style="width:502px" %)Metadataflow
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataSet
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)process|(% style="width:502px" %)Process
--|(% style="width:134px" %) |(% style="width:502px" %)ProcessStep
--|(% style="width:134px" %) |(% style="width:502px" %)Transition
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)registry|(% style="width:502px" %)DataConstraint
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataConstraint
--|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvisionAgreement
--|(% style="width:134px" %) |(% style="width:502px" %)ProvisionAgreement
--|(% style="width:134px" %) |(% style="width:502px" %)Subscription
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)structuremapping|(% style="width:502px" %)CategorySchemeMap
--|(% style="width:134px" %) |(% style="width:502px" %)ConceptSchemeMap
--|(% style="width:134px" %) |(% style="width:502px" %)OrganisationSchemeMap
--|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomyMap
--|(% style="width:134px" %) |(% style="width:502px" %)RepresentationMap
--|(% style="width:134px" %) |(% style="width:502px" %)StructureMap
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)codelist|(% style="width:502px" %)Code
--|(% style="width:134px" %) |(% style="width:502px" %)Codelist
--|(% style="width:134px" %) |(% style="width:502px" %)HierarchicalCode
--|(% style="width:134px" %) |(% style="width:502px" %)Hierarchy
--|(% style="width:134px" %) |(% style="width:502px" %)HierarchyAssociation
--|(% style="width:134px" %) |(% style="width:502px" %)Level
--|(% style="width:134px" %) |(% style="width:502px" %)ValueList
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)categoryscheme|(% style="width:502px" %)Categorisation
--|(% style="width:134px" %) |(% style="width:502px" %)Category
--|(% style="width:134px" %) |(% style="width:502px" %)CategoryScheme
--|(% style="width:134px" %) |(% style="width:502px" %)ReportingCategory
--|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomy
--|(% style="width:134px" %)conceptscheme|(% style="width:502px" %)Concept
--|(% style="width:134px" %) |(% style="width:502px" %)ConceptScheme
--|(% style="width:134px" %) |(% style="width:502px" %)
--|(% style="width:134px" %)transformation|(% style="width:502px" %)CustomType
--|(% style="width:134px" %) |(% style="width:502px" %)CustomTypeScheme
--|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisation
--|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisationScheme
--|(% style="width:134px" %) |(% style="width:502px" %)Ruleset
--|(% style="width:134px" %) |(% style="width:502px" %)RulesetScheme
--|(% style="width:134px" %) |(% style="width:502px" %)Transformation
--|(% style="width:134px" %) |(% style="width:502px" %)TransformationScheme
--|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperator
--|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperatorScheme
--|(% style="width:134px" %) |(% style="width:502px" %)VtlCodelistMapping
--|(% style="width:134px" %) |(% style="width:502px" %)VtlConceptMapping
--|(% style="width:134px" %) |(% style="width:502px" %)VtlDataflowMapping
--|(% style="width:134px" %) |(% style="width:502px" %)VtlMappingScheme
++|**Package**|**URN class name (model class name where this is different)**
++|base|Agency
++| |AgencyScheme
++| |DataConsumer
++| |DataConsumerScheme
++| |DataProvider
++| |DataProviderScheme
++| |MetadataProvider
++| |MetadataProviderScheme
++| |OrganisationUnit
++| |OrganisationUnitScheme
++|datastructure|AttributeDescriptor
++| |DataAttribute
++| |Dataflow
++| |DataStructure (DataStructureDefinition)
++| |Dimension
++| |DimensionDescriptor
++| |GroupDimensionDescriptor
++| |Measure
++| |MeasureDescriptor
++| |TimeDimension
++| |
++|metadatastructure|MetadataAttribute
++| |MetadataAttributeDescriptor
++| |MetadataStructure MetadataStructureDefinition)
++| |Metadataflow
++| |MetadataSet
++| |
++|process|Process
++| |ProcessStep
++| |Transition
++| |
++|registry|DataConstraint
++| |MetadataConstraint
++| |MetadataProvisionAgreement
++| |ProvisionAgreement
++| |Subscription
++| |
++|structuremapping|CategorySchemeMap
++| |ConceptSchemeMap
++| |OrganisationSchemeMap
++| |ReportingTaxonomyMap
++| |RepresentationMap
++| |StructureMap
++| |
++|codelist|Code
++| |Codelist
++| |HierarchicalCode
++| |Hierarchy
++| |HierarchyAssociation
++| |Level
++| |ValueList
++| |
++|categoryscheme|Categorisation
++| |Category
++| |CategoryScheme
++| |ReportingCategory
++| |ReportingTaxonomy
++|conceptscheme|Concept
++| |ConceptScheme
++| |
++|transformation|CustomType
++| |CustomTypeScheme
++| |NamePersonalisation
++| |NamePersonalisationScheme
++| |Ruleset
++| |RulesetScheme
++| |Transformation
++| |TransformationScheme
++| |UserDefinedOperator
++| |UserDefinedOperatorScheme
++| |VtlCodelistMapping
++| |VtlConceptMapping
++| |VtlDataflowMapping
++| |VtlMappingScheme
  **Table 2: SDMX-IM Packages and Contained Classes**
@@ -611,116 +611,136 @@
  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--(% style="width:1311.29px" %)
--|(% style="width:252px" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:418px" %)**Example**
--|(% style="width:252px" %)Agency{{footnote}}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. For example, a sub-agency of IMF is referred like this: IMF.SubAgency1{{/footnote}}|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**).AA
--|(% style="width:252px" %)//AgencyScheme//|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**)
--|(% style="width:252px" %)//Categorisation//|(% style="width:639px" %)categorisationAgencyId:categorisationId(version)|(% style="width:418px" %)IMF:cat001(1.0.0)
--|(% style="width:252px" %)Category|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:418px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
--|(% style="width:252px" %)//CategoryScheme//|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:418px" %)IMF:SDDS(1.0.0)
--|(% style="width:250px" %)//CategorySchemeMap//|(% style="width:639px" %)(((
--catSchemeMapAgencyId:catSchemeMapId(version)
--)))|(% style="width:1049px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
--|(% style="width:250px" %)Code|(% style="width:639px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0).Q
--|(% style="width:250px" %)//Codelist//|(% style="width:639px" %)codeListAgencyId:codeListId(version)|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0)
--|(% style="width:250px" %)ComponentMap|(% style="width:639px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:1049px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
--|(% style="width:250px" %)Concept|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
--|(% style="width:250px" %)//ConceptScheme//|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
--|(% style="width:250px" %)//ConceptSchemeMap//|(% style="width:639px" %)(((
++|**Classname**|**Ending URN pattern**|**Example**
++|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
++|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
++|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
++|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
++|//CategoryScheme//|categorySchemeAgencyId:categorySchemeId(versi on)|IMF:SDDS(1.0.0)
++
++|**Classname**|**Ending URN pattern**|**Example**
++|//CategorySchemeMap//|(((
++catSchemeMapAgencyId:catSchemeMapId(version
++
++)
++)))|SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
++|Code|codeListAgencyId:codelistId(version).codeId|SDMX:CL_FREQ(1.0.0).Q
++|//Codelist//|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0.0)
++|ComponentMap|structureMapAgencyId:structureMap(version).com ponentMapId|SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
++|Concept|conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
++|//ConceptScheme//|conceptSchemeAgencyId:conceptSchemeId(versio n)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
++|//ConceptSchemeMap//|(((
  conceptSchemeMapAgencyId:conceptSchemeMap
++
  Id(version)
--)))|(% style="width:1049px" %)SDMX:CONCEPT_MAP(1.0.0)
--|(% style="width:250px" %)CustomType|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:1049px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
--|(% style="width:250px" %)//CustomTypeScheme//|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:1049px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
--|(% style="width:250px" %)DataAttrribute|(% style="width:639px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:1049px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
--|(% style="width:250px" %)//DataConstraint//|(% style="width:639px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:1049px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0)
++)))|SDMX:CONCEPT_MAP(1.0.0)
++|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
++|//CustomTypeScheme//|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0.0)
++|DataAttrribute|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|TFFS:EXT_DEBT(1.0.0).OBS_STATUS
++|//DataConstraint//|dataConstraintAgencyId:dataConstraintId(version)|TFFS:CREDITOR_DATA_CONTENT(1.0.0)
--|(% style="width:248px" %)**Classname**|(% style="width:643px" %)**Ending URN pattern**|(% style="width:1047px" %)**Example**
--|(% style="width:248px" %)DataConsumer|(% style="width:643px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
--|(% style="width:248px" %)//DataConsumerScheme//|(% style="width:643px" %)(((
--dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**)
--)))|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
--|(% style="width:248px" %)//Dataflow//|(% style="width:643px" %)dataflowAgencyId:dataflowId(version)|(% style="width:1047px" %)TFFS:CRED_EXT_DEBT(1.0.0)
--|(% style="width:248px" %)DataProvider|(% style="width:643px" %)(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId
--)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
--|(% style="width:248px" %)//DataProviderScheme//|(% style="width:643px" %)(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
--)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
--|(% style="width:248px" %)//DataStructure//|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0)
--|(% style="width:248px" %)Dimension|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).FREQ
--|(% style="width:248px" %)(((
++|**Classname**|**Ending URN pattern**|**Example**
++|DataConsumer|dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
++|//DataConsumerScheme//|(((
++dataConsumerSchemeAgencyId:**DATA_CONSUME**
++
++**RS**(**1.0**)
++)))|SDMX:**DATA_CONSUMERS**(**1.0**)
++|//Dataflow//|dataflowAgencyId:dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0.0)
++|DataProvider|(((
++dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
++
++**1.0**).dataProviderId
++)))|SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
++|//DataProviderScheme//|(((
++dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
++
++**1.0**)
++)))|SDMX:**DATA_PROVIDERS**(**1.0**)
++|//DataStructure//|dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|TFFS:EXT_DEBT(1.0.0)
++|Dimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|TFFS:EXT_DEBT(1.0.0).FREQ
++|(((
  DimensionDescriptor
++
  MeasureDescriptor
++
  AttributeDescriptor
--)))|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(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:1047px" %)(((
++)))|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).componentListId where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)|(((
  TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
++
  TFFS:EXT_DEBT(1.0.0).MeasureDescriptor
++
  TFFS:EXT_DEBT(1.0.0).AttributeDescriptor
  )))
--|(% style="width:248px" %)GroupDimensionDescriptor|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
--|(% style="width:248px" %)HierarchicalCode|(% style="width:643px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:1047px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
++|GroupDimensionDescriptor|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|TFFS:EXT_DEBT(1.0.0).SIBLING
++|HierarchicalCode|hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
--|(% style="width:248px" %)**Classname**|(% style="width:646px" %)**Ending URN pattern**|(% style="width:1044px" %)**Example**
--|(% style="width:248px" %)//Hierarchy//|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0)
--|(% style="width:248px" %)//HierarchyAssociation//|(% style="width:646px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:1044px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
--|(% style="width:248px" %)Level|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0).LVL1
--|(% style="width:248px" %)Measure|(% style="width:646px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:1044px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
--|(% style="width:248px" %)MetadataAttribute|(% style="width:646px" %)(((
++|**Classname**|**Ending URN pattern**|**Example**
++|//Hierarchy//|hierarchyAgencyId:hierarchyId(version)|UNESCO:H-C-GOV(1.0.0)
++|//HierarchyAssociation//|hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|UNESCO:CL_EXP_SOURCE(1.0.0)
++|Level|hierarchyAgencyId:hierarchyId(version).level|UNESCO:H-C-GOV(1.0.0).LVL1
++|Measure|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|TFFS:EXT_DEBT(1.0.0).OBS_VALUE
++|MetadataAttribute|(((
  msdAgencyId:msdId(version).metadataAttributeId.
++
  metadataAttributeId
--)))|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
--|(% style="width:248px" %)MetadataAttributeDescriptor|(% style="width:646px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
--|(% style="width:248px" %)//MetadataConstraint//|(% style="width:646px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:1044px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
--|(% style="width:248px" %)//Metadataflow//|(% style="width:646px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:1044px" %)IMF:SDDS_MDF(1.0.0)
--|(% style="width:248px" %)MetadataProvider|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
--|(% style="width:248px" %)//MetadataProviderScheme//|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
--|(% style="width:248px" %)//MetadataProvisionAgreement//|(% style="width:646px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:1044px" %)IMF:SDDS_MDF_AB(1.0.0)
--|(% style="width:248px" %)//MetadataSet//|(% style="width:646px" %)metadataProviderId:metadataSetId(version)|(% style="width:1044px" %)MD_PROVIDER:METADATASET(1.0.0)
--|(% style="width:248px" %)//MetadataStructure//|(% style="width:646px" %)msdAgencyId:msdId(version)|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0)
++)))|IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
++|MetadataAttributeDescriptor|msdAgencyId:msdId(version).metadataAttributeDe scriptorId|IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
++|//MetadataConstraint//|metadataConstraintAgencyId:metadataConstraintI d(version)|TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
++|//Metadataflow//|metadataflowAgencyId:metadataflowId(version)|IMF:SDDS_MDF(1.0.0)
++|MetadataProvider|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
++|//MetadataProviderScheme//|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|SDMX:**METADATA_PROVIDERS**(**1.0**)
++|//MetadataProvisionAgreement//|metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|IMF:SDDS_MDF_AB(1.0.0)
++|//MetadataSet//|metadataProviderId:metadataSetId(version)|MD_PROVIDER:METADATASET(1.0.0)
++|//MetadataStructure//|msdAgencyId:msdId(version)|IMF:SDDS_MSD(1.0.0)
--|(% style="width:248px" %)**Classname**|(% style="width:629px" %)**Ending URN pattern**|(% style="width:1061px" %)**Example**
--|(% style="width:248px" %)NamePersonalisation|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
--|(% style="width:248px" %)//NamePersonalisationScheme//|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0)
--|(% style="width:248px" %)//OrganisationSchemeMap//|(% style="width:629px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:1061px" %)SDMX:AGENCIES_PROVIDERS(1.0.0)
--|(% style="width:248px" %)OrganisationUnit|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUnitSchemeId(version).organisationUnitId|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0).1F
--|(% style="width:248px" %)//OrganisationUnitScheme//|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0)
--|(% style="width:248px" %)//Process//|(% style="width:629px" %)processAgencyId:processId{version)|(% style="width:1061px" %)BIS:PROCESS1(1.0.0)
--|(% style="width:248px" %)ProcessStep|(% style="width:629px" %)(((
++|**Classname**|**Ending URN pattern**|**Example**
++|NamePersonalisation|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0.0).PSN1234
++|//NamePersonalisationScheme//|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0.0)
++|//OrganisationSchemeMap//|orgSchemeMapAgencyId:orgSchemeMapId(versio n)|SDMX:AGENCIES_PROVIDERS(1.0.0)
++|OrganisationUnit|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|ECB:ORGANISATIONS(1.0.0).1F
++|//OrganisationUnitScheme//|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|ECB:ORGANISATIONS(1.0.0)
++|//Process//|processAgencyId:processId{version)|BIS:PROCESS1(1.0.0)
++|ProcessStep|(((
  processAgencyId:processId(version).processStepId.
++
  processStepId
--)))|(% style="width:1061px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1
--|(% style="width:248px" %)//ProvisionAgreement//|(% style="width:629px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:1061px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0)
--|(% style="width:248px" %)ReportingCategory|(% style="width:629px" %)(((
++)))|BIS:PROCESS1(1.0.0).STEP1.STEP1_1
++|//ProvisionAgreement//|provisionAgreementAgencyId:provisionAgreement Id(version)|TFFS:CRED_EXT_DEBT_AB(1.0.0)
++|ReportingCategory|(((
  reportingTaxonomyAgencyId:
++
  reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId
--)))|(% style="width:1061px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
--|(% style="width:248px" %)//ReportingTaxonomy//|(% style="width:629px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:1061px" %)IMF:REP_1(1.0.0)
--|(% style="width:248px" %)//ReportingTaxonomyMap//|(% style="width:629px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:1061px" %)SDMX:RT_MAP(1.0.0)
++)))|IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
++|//ReportingTaxonomy//|reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|IMF:REP_1(1.0.0)
++|//ReportingTaxonomyMap//|repTaxonomyAgencyId:repTaxonomyId(version)|SDMX:RT_MAP(1.0.0)
--|(% style="width:247px" %)**Classname**|(% style="width:649px" %)**Ending URN pattern**|(% style="width:1042px" %)**Example**
--|(% style="width:247px" %)//RepresentationMap//|(% style="width:649px" %)repMapAgencyId:repMapId(version)|(% style="width:1042px" %)SDMX:REF_AREA_MAPPING(1.0.0)
--|(% style="width:247px" %)Ruleset|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:1042px" %)ECB:RULESET_23(1.0.0).SET111
--|(% style="width:247px" %)//RulesetScheme//|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:1042px" %)ECB:RULESET_23(1.0.0)
--|(% style="width:247px" %)//StructureMap//|(% style="width:649px" %)structureMapAgencyId:structureMap(version)|(% style="width:1042px" %)SDMX:BOP_STRUCTURES(1.0.0)
--|(% style="width:247px" %)Subscription|(% style="width:649px" %)(((
++|**Classname**|**Ending URN pattern**|**Example**
++|//RepresentationMap//|repMapAgencyId:repMapId(version)|SDMX:REF_AREA_MAPPING(1.0.0)
++|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0.0).SET111
++|//RulesetScheme//|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0.0)
++|//StructureMap//|structureMapAgencyId:structureMap(version)|SDMX:BOP_STRUCTURES(1.0.0)
++|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.
--)))|(% style="width:1042px" %)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 registry URN that is returned from the registry in the subscription response message.
--|(% style="width:247px" %)TimeDimension|(% style="width:649px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:1042px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
--|(% style="width:247px" %)Transformation|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:1042px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
--|(% style="width:247px" %)//TransformationScheme//|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:1042px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
--|(% style="width:247px" %)Transition|(% style="width:649px" %)(((
++)))|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 registry URN that is returned from the registry in the subscription response message.
++|TimeDimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
++|Transformation|transformationSchemeAgencyId transformationSchemeId(version) transformationId|ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
++|//TransformationScheme//|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0.0)
++|**Classname**|**Ending URN pattern**|**Example**
++|Transition|(((
  processAgencyId:processId(version).processStepId.
++
  transitionId
--)))|(% style="width:1042px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
--|(% style="width:247px" %)UserDefinedOperator|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:1042px" %)ECB:OS_CALC(1.2.0).OS267
--|(% style="width:247px" %)//UserDefinedOperatorScheme//|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:1042px" %)ECB:OS_CALC(1.2.0)
--|(% style="width:247px" %)//ValueList//|(% style="width:649px" %)valuelistAgencyId:valuelistId(version)|(% style="width:1042px" %)SDMX:VLIST(1.0.0)
--|(% style="width:247px" %)VtlCodelistMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0).ABZ
--|(% style="width:247px" %)VtlConceptMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).XYA
--|(% style="width:247px" %)VtlDataflowMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).MOQ
--|(% style="width:247px" %)//VtlMappingScheme//|(% style="width:649px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0)
++)))|BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
++|UserDefinedOperator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2.0).OS267
++|//UserDefinedOperatorScheme//|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2.0)
++|//ValueList//|valuelistAgencyId:valuelistId(version)|SDMX:VLIST(1.0.0)
++|VtlCodelistMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0.0).ABZ
++|VtlConceptMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0.0).XYA
++|VtlDataflowMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0.0).MOQ
++|//VtlMappingScheme//|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0.0)
  **Table 3: Table of identification components for SDMX Identifiable Artefacts**
@@ -728,7 +728,7 @@
  === {{id name="_Toc93862"/}}7.1 Structural Definition Metadata ===
--=== {{id name="_Toc93863"/}}7.1.1 Introduction ===
++===== {{id name="_Toc93863"/}}7.1.1 Introduction =====
  The SDMX Registry must have the ability to support agencies in their role of defining and disseminating structural metadata artefacts. These artefacts include data structure definitions, code lists, concepts etc. and are fully defined in the SDMX-IM. An authenticated agency may submit valid structural metadata definitions which must be stored in the registry. Note that the term “structural metadata” refers as a general term to all structural components (Data Structure Definitions, Metadata Structure Definitions, Code Lists, Concept Schemes, etc.)
@@ -744,79 +744,90 @@
  The following table lists the Maintainable Artefacts.
--(% style="width:881.294px" %)
--|(% colspan="2" style="width:522px" %)**Maintainable Artefacts**|(% style="width:490px" %)**Content**
--|(% style="width:198px" %)**Abstract Class**|(% style="width:324px" %)**Concrete Class**|(% style="width:490px" %)
--|(% style="width:198px" %)Item Scheme|(% style="width:324px" %)Codelist|(% style="width:490px" %)Code
--|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme|(% style="width:490px" %)Concept
--|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme|(% style="width:490px" %)Category
--|(% style="width:198px" %) |(% style="width:324px" %)Organisation Unit Scheme|(% style="width:490px" %)Organisation Unit
--|(% style="width:198px" %) |(% style="width:324px" %)Agency Scheme|(% style="width:490px" %)Agency
--|(% style="width:198px" %) |(% style="width:324px" %)Data Provider Scheme|(% style="width:490px" %)Data Provider
--|(% style="width:198px" %) |(% style="width:324px" %)Metadata Provider Scheme|(% style="width:490px" %)Metadata Provider
--|(% style="width:198px" %) |(% style="width:324px" %)Data Consumer Scheme|(% style="width:490px" %)Data Consumer
--|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy|(% style="width:490px" %)Reporting Category
--|(% style="width:198px" %) |(% style="width:324px" %)Transformation Scheme|(% style="width:490px" %)Transformation
--|(% style="width:198px" %) |(% style="width:324px" %)Custom Type Scheme|(% style="width:490px" %)Custom Type
--|(% style="width:198px" %) |(% style="width:324px" %)Name Personalisation Scheme|(% style="width:490px" %)Name Personalisation
--|(% style="width:198px" %) |(% style="width:324px" %)Vtl Mapping Scheme|(% style="width:490px" %)Vtl Codelist Mapping Vtl Concept Mapping
--|(% style="width:198px" %) |(% style="width:324px" %)Ruleset Scheme|(% style="width:490px" %)Ruleset
--|(% style="width:198px" %) |(% style="width:324px" %)User Defined Operator Scheme|(% style="width:490px" %)User Defined Operator
--|(% style="width:198px" %)Enumerated List|(% style="width:324px" %)ValueList|(% style="width:490px" %)Value Item
--|(% style="width:198px" %)Structure|(% style="width:324px" %)Data Structure Definition|(% style="width:490px" %)(((
++|(% colspan="2" %)**Maintainable Artefacts**|**Content**
++|**Abstract Class**|**Concrete Class**|
++|Item Scheme|Codelist|Code
++| |Concept Scheme|Concept
++| |Category Scheme|Category
++| |Organisation Unit Scheme|Organisation Unit
++| |Agency Scheme|Agency
++| |Data Provider Scheme|Data Provider
++| |Metadata Provider Scheme|Metadata Provider
++| |Data Consumer Scheme|Data Consumer
++| |Reporting Taxonomy|Reporting Category
++| |Transformation Scheme|Transformation
++| |Custom Type Scheme|Custom Type
++| |Name Personalisation Scheme|Name Personalisation
++| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
++| |Ruleset Scheme|Ruleset
++| |User Defined Operator Scheme|User Defined Operator
++|Enumerated List|ValueList|Value Item
++|Structure|Data Structure Definition|(((
  Dimension Descriptor
++
  Group Dimension Descriptor
++
  Dimension
++
  Time Dimension
++
  Attribute Descriptor
++
  Data Attribute
++
  Measure Descriptor
++
  Measure
  )))
--|(% style="width:198px" %) |(% style="width:324px" %)Metadata Structure Definition|(% style="width:490px" %)Metadata Attribute Descriptor Metadata Attribute
--|(% style="width:198px" %)Structure Usage|(% style="width:324px" %)Dataflow|(% style="width:490px" %)
--|(% style="width:198px" %) |(% style="width:324px" %)Metadataflow|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)Process|(% style="width:490px" %)Process Step
--|(% style="width:198px" %)None|(% style="width:324px" %)Structure Map|(% style="width:490px" %)(((
++| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
++|Structure Usage|Dataflow|
++| |Metadataflow|
++|None|Process|Process Step
++|None|Structure Map|(((
  Component Map
++
  Epoch Map
++
  Date Pattern Map
  )))
--|(% style="width:198px" %)None|(% style="width:324px" %)Representation Map|(% style="width:490px" %)Representation Mapping
--|(% style="width:198px" %)Item Scheme Map|(% style="width:324px" %)Organisation Scheme Map|(% style="width:490px" %)Item Map
--|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme Map|(% style="width:490px" %)Item Map
--|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme Map|(% style="width:490px" %)Item Map
--|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy Map|(% style="width:490px" %)Item Map
--|(% style="width:198px" %)None|(% style="width:324px" %)Provision Agreement|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)Metadata Provision Agreement|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy|(% style="width:490px" %)Hierarchical Code
--|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy Association|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)Categorisation|(% style="width:490px" %)
++|None|Representation Map|Representation Mapping
++|Item Scheme Map|Organisation Scheme Map|Item Map
++| |Concept Scheme Map|Item Map
++| |Category Scheme Map|Item Map
++| |Reporting Taxonomy Map|Item Map
++|None|Provision Agreement|
++|None|Metadata Provision Agreement|
++|None|Hierarchy|Hierarchical Code
++|None|Hierarchy Association|
++|None|Categorisation|
  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
--=== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
++===== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure =====
  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, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
--* All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}}
--* All types of Structure (Data Structure Definition, Metadata Structure Definition)
--* All types of Structure Usage (Dataflow, Metadataflow)
++• All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme, Agency Scheme, Data Provider Scheme, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
--=== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===
++• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
--==== 7.1.3.1 Structure Usage: Basic Concepts ====
++• All types of Structure (Data Structure Definition, Metadata Structure Definition)
++• All types of Structure Usage (Dataflow, Metadataflow)
++
++===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
++
++**7.1.3.1 Structure Usage: Basic Concepts**
++
  The Structure Usage defines, in its concrete classes of Dataflow and Metadataflow, which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more Category in one or more Category Scheme using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the Category Schemes.
--==== 7.1.3.2 Structure Usage Schematic ====
++**7.1.3.2 Structure Usage Schematic**
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_52097ab5.jpg||height="246" width="438"]]
  **Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
--==== 7.1.3.3 Structure Usage Model ====
++**7.1.3.3 Structure Usage Model**
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_302cc1a2.jpg||height="548" width="578"]]
@@ -832,9 +832,9 @@
  * Categorisation to Dataflow and Category
  * Categorisation to Metadataflow and Category
--== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ==
++=== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ===
--=== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts ===
++===== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts =====
  Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the SDMX-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service level agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and timeliness metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
@@ -842,7 +842,7 @@
  Although the Provision Agreement directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of structural metadata.
--=== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case ===
++===== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case =====
  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.
@@ -864,9 +864,9 @@
  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider or Metadata Provider and a Dataflow or Metadataflow Definition. The Data/Metadata Provider and the Dataflow/Metadataflow must exist already in order to set up a Metadata Provision or Provision Agreement.
--== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ==
++=== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ===
--=== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===
++===== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts =====
  Constraints are, effectively, lists of the valid or actual content of data and metadata. Constraints can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD. A Constraint can comprise a list of keys or a list of content (usually code values) of a specific component such as a dimension or attribute.
@@ -930,14 +930,17 @@
  The Registration has an action attribute which takes one of the following values:
++:
++
  (((
--(% style="width:761.294px" %)
--|(% style="width:196px" %)**Action Attribute Value**|(% style="width:561px" %)**Behaviour**
--|(% style="width:196px" %)Append|(% style="width:561px" %)Add this Registration to the registry
--|(% style="width:196px" %)Replace|(% style="width:561px" %)(((
--Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
++|**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 SubmitRegistrationRequest
  )))
--|(% style="width:196px" %)Delete|(% style="width:561px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
++|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
  )))
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_bc1dcdec.jpg||height="575" width="579"]]
@@ -954,20 +954,27 @@
  Information in the data or metadata set is extracted and placed in one or more //Constraint//s (see the //Constraint// 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 ProvisionAgreement or MetadataProvisionAgreement as shown in the table below.
++:
++
  (((
--(% style="width:678.294px" %)
--|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
--|indexTimeSeries|(% style="width:504px" %)Extract all the series keys and create a KeySet(s) Constraint.
--|indexDataSet|(% style="width:504px" %)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.
--|indexReportingPeriod|(% style="width:504px" %)(((
++|**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.
++|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.
  )))
--|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
--|indexAttributes|(% style="width:504px" %)(((
++|**Indexing Required**|**Registration Process Activity**
++|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
++
++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.
  )))
  )))
@@ -976,7 +976,7 @@
  The Registration must reference the ProvisionAgreement or MetadataProvisionAgreement to which it relates.
--=== {{id name="_Toc93876"/}}7.4.3 Registration Response ===
++===== {{id name="_Toc93876"/}}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 SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”.
@@ -1006,18 +1006,20 @@
  Regardless of the type of registry/repository events being observed, a subscription always contains:
--1.  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 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.
 . 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.
 . 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.
 . A selector which specifies which type of events are of interest. The set of event types is:
++:
++::
++
  (((
--(% style="width:856.294px" %)
--|(% style="width:320px" %)**Event Type**|(% style="width:532px" %)**Comment**
--|(% style="width:320px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:532px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
--|(% style="width:320px" %)DATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
--|(% style="width:320px" %)METADATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
--|(% style="width:320px" %)ALL_EVENTS|(% style="width:532px" %)All events of the specified EventType
++|**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
  )))
  === {{id name="_Toc93880"/}}7.5.3 Wildcard Facility ===
@@ -1084,14 +1084,15 @@
  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:1126.29px" %)
--|(% style="width:382px" %)**Selector**|(% style="width:740px" %)**Comment**
--|(% style="width:382px" %)DataProvider & MetadataProvider|(% style="width:740px" %)Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
--|(% style="width:382px" %)ProvisionAgreement & MetadataProvisionAgreement|(% style="width:740px" %)Any datasets or metadata sets registered for the agreement will activate the notification.
--|(% style="width:382px" %)Dataflow & Metadataflow|(% style="width:740px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
--|(% style="width:382px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification
--|(% style="width:382px" %)Category|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
++|**Selector**|**Comment**
++|DataProvider & MetadataProvider|Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
++|ProvisionAgreement & MetadataProvisionAgreement|Any datasets or metadata sets registered for the 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 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.
@@ -1123,6 +1123,10 @@
  The notification will contain the Registration.
------
++[[1>>path:#sdfootnote1anc||name="sdfootnote1sym"]] With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4draft does not break integrity of the aforementioned DSD.
--{{putFootnotes/}}
++[[2>>path:#sdfootnote2anc||name="sdfootnote2sym"]] 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. For example, a sub-agency of IMF is referred like this:
++
++IMF.SubAgency1
++
++[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.

1747307906944-697.png

Author

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

Size

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

Content

SUZ.Methodology.Code.MethodologyClass[0]