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

Last modified by Artur on 2025/09/30 13:28

From 12.1 to 11.1 From 22.4 to 22.3

From version 22.3

edited by Helena
on 2025/06/08 16:48

Change comment: There is no comment for this version

To version 12.1

edited by Helena
on 2025/06/08 16:26

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, 9 removed)

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+1 Introduction

Content

@@ -1,16 +5,15 @@
--{{box title="**Contents**"}}
--{{toc/}}
--{{/box}}
--
  **Revision History**
--(% style="width:824.835px" %)
--|(% style="width:184px" %)**Revision**|(% style="width:195px" %)**Date**|(% style="width:442px" %)**Contents**
--|(% style="width:184px" %)DRAFT 1.0|(% style="width:195px" %)December 2024|(% style="width:442px" %)Draft release updated for SDMX 3.1 for public consultation
--|(% style="width:184px" %)1.0|(% style="width:195px" %)May 2025|(% style="width:442px" %)Public release for SDMX 3.1
++:
--= 1 Introduction =
++(((
++|**Revision**|**Date**|**Contents**
++|DRAFT 1.0|December 2024|Draft release updated for SDMX 3.1 for public consultation
++|1.0|May 2025|Public release for SDMX 3.1
++)))
++= {{id name="_Toc90780"/}}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:
  * the availability of an abstract information model capable of supporting time series and cross-sectional data, structural metadata, and reference metadata (SDMX-IM)
@@ -31,13 +31,15 @@
  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.
--= 2 Scope and Normative Status =
++= {{id name="_Toc90781"/}}2 Scope and Normative Status =
  The scope of this document is to specify the logical interfaces for the SDMX registry in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry.
@@ -54,9 +54,9 @@
  Note that although the term “authorised user” is used in this document, the SDMX standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider.
--= 3 Scope of the SDMX Registry/Repository =
++= {{id name="_Toc90782"/}}3 Scope of the SDMX Registry/Repository =
--== 3.1 Objective ==
++=== {{id name="_Toc90783"/}}3.1 Objective ===
  The objective of the SDMX registry/repository is, in broad terms, to allow organisations to publish statistical data and reference metadata in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold:
@@ -63,7 +63,7 @@
 . To maintain and publish structural metadata that describes the structure and valid content of data and reference metadata sources such as databases, metadata repositories, data sets, metadata sets. This structural metadata enables software applications to understand and to interpret the data and reference metadata in these sources.
 . To enable applications, organisations, and individuals to share and to discover data and reference metadata. This facilitates data and reference metadata dissemination by implementing the data sharing vision of SDMX.
--== 3.2 Structural Metadata ==
++=== {{id name="_Toc90784"/}}3.2 Structural Metadata ===
  Setting up structural metadata and the exchange context (referred to as “data provisioning”) involves the following steps for maintenance agencies:
@@ -89,7 +89,7 @@
  In that context, the term “Metadata” refers to reference metadata.
--== 3.3 Registration ==
++=== {{id name="_Toc90785"/}}3.3 Registration ===
  Publishing the data and reference metadata involves the following steps for a Data/Metadata Provider:
@@ -100,13 +100,13 @@
  **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
--== 3.4 Notification ==
++=== {{id name="_Toc90786"/}}3.4 Notification ===
  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.
--== 3.5 Discovery ==
++=== {{id name="_Toc90787"/}}3.5 Discovery ===
  Discovering published data and reference metadata involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an SDMX-enabled data or reference metadata resource:
@@ -118,9 +118,9 @@
  **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
--= 4 SDMX Registry/Repository Architecture =
++= {{id name="_Toc90788"/}}4 SDMX Registry/Repository Architecture =
--== 4.1 Architectural Schematic ==
++=== {{id name="_Toc90789"/}}4.1 Architectural Schematic ===
  The architecture of the SDMX registry/repository is derived from the objectives stated above. It is a layered architecture that is founded by a structural metadata repository which supports a provisioning metadata repository which supports the registry services. These are all supported by the SDMX-ML schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the structural metadata required to drive these applications.
@@ -128,7 +128,7 @@
  **Figure 4: Schematic of the Registry Content and Services**
--== 4.2 Structural Metadata Repository ==
++=== {{id name="_Toc90790"/}}4.2 Structural Metadata Repository ===
  The basic layer is that of a structural metadata service which supports the lifecycle of SDMX structural metadata artefacts such as Maintenance Agencies, Data Structure Definitions, Metadata Structure Definitions, Provision Agreements, Processes etc. This layer is supported by the Structure Submission and Query Service.
@@ -139,15 +139,15 @@
  As of the initial version of SDMX 3.0 no messages are defined to support these artefacts; hence, users may need to use SDMX 2.1 Registry Interface messages, instead.
--== 4.3 Provisioning Metadata Repository ==
++=== {{id name="_Toc90791"/}}4.3 Provisioning Metadata Repository ===
  The function of this repository is to support the definition of the structural metadata that describes the various types of data-store which model SDMX-conformant databases or files, and to link to these data sources. These links can be specified for a data/metadata provider, for a specific data or metadata flow. In the SDMX model this is called the Provision or Metadata Provision Agreement.
  This layer is supported by the Data and Metadata Registration Service.
--= 5 Registry Interfaces and Services =
++= {{id name="_Toc90792"/}}5 Registry Interfaces and Services =
--== 5.1 Registry Interfaces ==
++=== {{id name="_Toc90793"/}}5.1 Registry Interfaces ===
  The Registry Interfaces are:
@@ -163,8 +163,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.
@@ -172,17 +172,17 @@
  It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the SDMX-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous.
--== 5.2 Registry Services ==
++=== {{id name="_Toc90794"/}}5.2 Registry Services ===
--=== 5.2.1 Introduction ===
++===== {{id name="_Toc90795"/}}5.2.1 Introduction =====
  The services described in this section do not imply that each is implemented as a discrete web service.
--=== 5.2.2 Structure Submission Service ===
++===== {{id name="_Toc90796"/}}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).
--=== 5.2.3 Structure Query Service ===
++===== {{id name="_Toc90797"/}}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>>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:
@@ -190,7 +190,7 @@
  The SDMX structural artefacts that may be queried are defined in the SDMX structure web service specification which is compatible with this release of the standard __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[rest/blob/master/doc/structures.md>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]]__[[url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]]
--=== 5.2.4 Data and Reference Metadata Registration Service ===
++===== {{id name="_Toc90798"/}}5.2.4 Data and Reference Metadata Registration Service =====
  This service must implement the following Registry Interfaces:
@@ -213,24 +213,23 @@
  The Registration has an action attribute which takes one of the following values:
--(% style="width:893.835px" %)
--|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour**
--|(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry
--|(% style="width:241px" %)Replace|(% style="width:650px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
--|(% style="width:241px" %)Delete|(% style="width:650px" %)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:896.835px" %)
--|**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”**
--|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys
--|indexDataSet|(% style="width:712px" %)(((
++|**Boolean Attribute**|**Behaviour if Value is “true”**
++|indexTimeSeries|A compliant indexing application must index all the time series keys
++|indexDataSet|(((
  A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset.
++
  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
  )))
--|indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
++|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
--=== 5.2.5 Data Discovery ===
++===== {{id name="_Toc90799"/}}5.2.5 Data Discovery =====
  The Data Discovery Service implements the following Registry Interfaces:
@@ -237,7 +237,7 @@
  * QueryRegistrationRequest
  * QueryRegistrationResponse
--=== 5.2.6 Subscription and Notification ===
++===== {{id name="_Toc90800"/}}5.2.6 Subscription and Notification =====
  The Subscription and Notification Service implements the following Registry Interfaces:
@@ -256,32 +256,34 @@
  Notification requires that the structural metadata repository and the provisioning metadata repository monitor any event which is of interest to a user (the object of a subscription request query), and to issue an SDMX notification document to the endpoints specified in the relevant subscriptions.
--=== 5.2.7 Registry Behaviour ===
++===== {{id name="_Toc90801"/}}5.2.7 Registry Behaviour =====
  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. It should be noted, though, that as of SDMX 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all Maintainable Artefacts. Moreover, while the old versioning scheme is allowed, given there is no more a "final" flag, there is no way guaranteeing the consistency across version of a Maintainable, unless semantic versioning is used.
  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:982.835px" %)
--|(% style="width:217px" %)**Interface**|(% style="width:763px" %)**Behaviour**
--|(% style="width:217px" %)All|(% style="width:763px" %)(((
++|**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:
--a) Be a draft version.
--b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
++1. Be a draft version.
++b) Not be explicitly^^[[^^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:217px" %)Structure submission|(% style="width:763px" %)(((
--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.
++|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.
  )))
--|(% style="width:217px" %)SubmitRegistrationRequest|(% style="width:763px" %)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.
++|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.
--= 6 Identification of SDMX Objects =
++= {{id name="_Toc90802"/}}6 Identification of SDMX Objects =
--== 6.1 Identification, Versioning, and Maintenance ==
++=== {{id name="_Toc90803"/}}6.1 Identification, Versioning, and Maintenance ===
  All major classes of the SDMX Information model inherit from one of:
@@ -290,7 +290,7 @@
  * //**VersionableArtefact**// – this has all of the above features plus a version number, according to the SDMX versioning rules in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
  * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object.
--=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
++===== {{id name="_Toc90804"/}}6.1.1 Identification, Naming, Versioning, and Maintenance Model =====
  [[image:SDMX 3.1 Section 5_en_4a9b2cfc.jpg||height="688" width="587"]]
@@ -299,58 +299,60 @@
  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
  * //Annotable//
--* //Identifiable//
--* //Nameable//
--* //Versionable//
--* //Maintainable//
--| |(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
--| |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
--| |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
--| |(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
--| |(% colspan="2" %)(((
++//Identifiable// • //Nameable//
++
++• //Versionable//
++
++• //Maintainable//
++
++||(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
++||(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
++||(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
++||(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
++||(% colspan="2" %)(((
  AnnotationText in the form of
  InternationalString
--)))|(% colspan="2" %)C|(% colspan="2" %) |(% colspan="2" %)This can have languagespecific variants
--| |(% colspan="2" rowspan="4" %)//Identifiable//|(% colspan="2" %)All content as for //Annotable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
--| |(% colspan="2" %)id|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)
--| |(% colspan="2" %)uri|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
--| |(% colspan="2" %)urn|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)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.
--| |(% colspan="2" rowspan="3" %)//Nameable//|(% colspan="2" %)(((
++)))|(% colspan="2" %)C|(% colspan="2" %)|(% colspan="2" %)This can have languagespecific variants
++||(% colspan="2" rowspan="4" %)//Identifiable//|(% colspan="2" %)All content as for //Annotable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
++||(% colspan="2" %)id|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)
++||(% colspan="2" %)uri|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
++||(% colspan="2" %)urn|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)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.
++||(% colspan="2" rowspan="3" %)//Nameable//|(% colspan="2" %)(((
  All content as for
  //Identifiable// plus
--)))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
--| |(% colspan="2" %)(((
++)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
++||(% colspan="2" %)(((
  Name in the form of
  InternationalString
  )))|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants.
--| |(% colspan="2" %)(((
++||(% colspan="2" %)(((
  Description in the form of
  InternationalString
  )))|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants.
--| |(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)(((
++||(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)(((
  All content as for
  //Identifiable// plus
--)))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
--| |(% colspan="2" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the version number according to SDMX versioning rules.
--| |(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
--| |(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
--|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) |
--|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)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.|
--|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.|
--|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.|
--|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.|
++)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
++||(% colspan="2" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the version number according to SDMX versioning rules.
++||(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
++||(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
++|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)|
++|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)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.|
++|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.|
++|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.|
++|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.|
  **Table 1: Common Attributes of Object Types**
--== 6.2 Unique identification of SDMX objects ==
++=== {{id name="_Toc90805"/}}6.2 Unique identification of SDMX objects ===
--=== 6.2.1 Agencies and Metadata Providers ===
++===== {{id name="_Toc90806"/}}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.
@@ -383,11 +383,14 @@
  The following organizations maintain an Agency Scheme.
--* SDMX – contains Agencies AA, BB
--* AA – contains Agencies CC, DD
--* BB – contains Agencies CC, DD
--* DD – Contains Agency EE
++• SDMX – contains Agencies AA, BB
++• AA – contains Agencies CC, DD
++
++• BB – contains Agencies CC, DD
++
++• DD – Contains Agency EE
++
  Each agency is identified by its full hierarchy excluding SDMX.
  e.g., the id of EE as an agencyID is AA.DD.EE
@@ -400,13 +400,13 @@
  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.
--=== 6.2.2 Universal Resource Name (URN) ===
++===== {{id name="_Toc90807"/}}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 //__Case Rules for URN__// ====
++**6.2.2.2 URN Structure //__Case Rules for URN__//**//&nbsp;//
  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
@@ -418,7 +418,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**.
@@ -497,103 +497,103 @@
  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.
--=== 6.2.3 Table of SDMX-IM Packages and Classes ===
++===== {{id name="_Toc90808"/}}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:750.835px" %)
--|(% style="width:222px" %)**Package**|(% style="width:526px" %)**URN class name (model class name where this is different)**
--|(% style="width:222px" %)base|(% style="width:526px" %)Agency
--|(% style="width:222px" %) |(% style="width:526px" %)AgencyScheme
--|(% style="width:222px" %) |(% style="width:526px" %)DataConsumer
--|(% style="width:222px" %) |(% style="width:526px" %)DataConsumerScheme
--|(% style="width:222px" %) |(% style="width:526px" %)DataProvider
--|(% style="width:222px" %) |(% style="width:526px" %)DataProviderScheme
--|(% style="width:222px" %) |(% style="width:526px" %)MetadataProvider
--|(% style="width:222px" %) |(% style="width:526px" %)MetadataProviderScheme
--|(% style="width:222px" %) |(% style="width:526px" %)OrganisationUnit
--|(% style="width:222px" %) |(% style="width:526px" %)OrganisationUnitScheme
--|(% style="width:222px" %) |(% style="width:526px" %)
--|(% style="width:222px" %)datastructure|(% style="width:526px" %)AttributeDescriptor
--|(% style="width:222px" %) |(% style="width:526px" %)DataAttribute
--|(% style="width:222px" %) |(% style="width:526px" %)Dataflow
--|(% style="width:222px" %) |(% style="width:526px" %)DataStructure (DataStructureDefinition)
--|(% style="width:222px" %) |(% style="width:526px" %)Dimension
--|(% style="width:222px" %) |(% style="width:526px" %)DimensionDescriptor
--|(% style="width:222px" %) |(% style="width:526px" %)GroupDimensionDescriptor
--|(% style="width:222px" %) |(% style="width:526px" %)Measure
--|(% style="width:222px" %) |(% style="width:526px" %)MeasureDescriptor
--|(% style="width:222px" %) |(% style="width:526px" %)TimeDimension
--|(% style="width:222px" %) |(% style="width:526px" %)
--|(% style="width:222px" %)metadatastructure|(% style="width:526px" %)MetadataAttribute
--|(% style="width:222px" %) |(% style="width:526px" %)MetadataAttributeDescriptor
--|(% style="width:222px" %) |(% style="width:526px" %)(((
++|**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)
  )))
++:
++
  (((
--(% style="width:751.835px" %)
--|(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)**
--|(% style="width:221px" %) |(% style="width:528px" %)Metadataflow
--|(% style="width:221px" %) |(% style="width:528px" %)MetadataSet
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)process|(% style="width:528px" %)Process
--|(% style="width:221px" %) |(% style="width:528px" %)ProcessStep
--|(% style="width:221px" %) |(% style="width:528px" %)Transition
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)registry|(% style="width:528px" %)DataConstraint
--|(% style="width:221px" %) |(% style="width:528px" %)MetadataConstraint
--|(% style="width:221px" %) |(% style="width:528px" %)MetadataProvisionAgreement
--|(% style="width:221px" %) |(% style="width:528px" %)ProvisionAgreement
--|(% style="width:221px" %) |(% style="width:528px" %)Subscription
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)structuremapping|(% style="width:528px" %)CategorySchemeMap
--|(% style="width:221px" %) |(% style="width:528px" %)ConceptSchemeMap
--|(% style="width:221px" %) |(% style="width:528px" %)OrganisationSchemeMap
--|(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomyMap
--|(% style="width:221px" %) |(% style="width:528px" %)RepresentationMap
--|(% style="width:221px" %) |(% style="width:528px" %)StructureMap
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)codelist|(% style="width:528px" %)Code
--|(% style="width:221px" %) |(% style="width:528px" %)Codelist
--|(% style="width:221px" %) |(% style="width:528px" %)HierarchicalCode
--|(% style="width:221px" %) |(% style="width:528px" %)Hierarchy
--|(% style="width:221px" %) |(% style="width:528px" %)HierarchyAssociation
--|(% style="width:221px" %) |(% style="width:528px" %)Level
--|(% style="width:221px" %) |(% style="width:528px" %)ValueList
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)categoryscheme|(% style="width:528px" %)Categorisation
--|(% style="width:221px" %) |(% style="width:528px" %)Category
--|(% style="width:221px" %) |(% style="width:528px" %)CategoryScheme
--|(% style="width:221px" %) |(% style="width:528px" %)ReportingCategory
--|(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomy
--|(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)**
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)conceptscheme|(% style="width:528px" %)Concept
--|(% style="width:221px" %) |(% style="width:528px" %)ConceptScheme
--|(% style="width:221px" %) |(% style="width:528px" %)
--|(% style="width:221px" %)transformation|(% style="width:528px" %)CustomType
--|(% style="width:221px" %) |(% style="width:528px" %)CustomTypeScheme
--|(% style="width:221px" %) |(% style="width:528px" %)NamePersonalisation
--|(% style="width:221px" %) |(% style="width:528px" %)NamePersonalisationScheme
--|(% style="width:221px" %) |(% style="width:528px" %)Ruleset
--|(% style="width:221px" %) |(% style="width:528px" %)RulesetScheme
--|(% style="width:221px" %) |(% style="width:528px" %)Transformation
--|(% style="width:221px" %) |(% style="width:528px" %)TransformationScheme
--|(% style="width:221px" %) |(% style="width:528px" %)UserDefinedOperator
--|(% style="width:221px" %) |(% style="width:528px" %)UserDefinedOperatorScheme
--|(% style="width:221px" %) |(% style="width:528px" %)VtlCodelistMapping
--|(% style="width:221px" %) |(% style="width:528px" %)VtlConceptMapping
--|(% style="width:221px" %) |(% style="width:528px" %)VtlDataflowMapping
--|(% style="width:221px" %) |(% style="width:528px" %)VtlMappingScheme
--|(% style="width:221px" %) |(% style="width:528px" %)
++|**Package**|**URN class name (model class name where this is different)**
++||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
++|**Package**|**URN class name (model class name where this is different)**
++||
++|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**
--=== 6.2.4 URN Identification components of SDMX objects ===
++===== {{id name="_Toc90809"/}}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.
@@ -601,56 +601,67 @@
  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--(% style="width:1272.83px" %)
--|(% style="width:290px" %)**Classname**|(% style="width:649px" %)**Ending URN pattern**|(% style="width:332px" %)**Example**
--|(% style="width:290px" %)Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|(% style="width:649px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:332px" %)ECB:**AGENCIES**(**1.0**).AA
--|(% style="width:290px" %)//AgencyScheme//|(% style="width:649px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:332px" %)ECB:**AGENCIES**(**1.0**)
--|(% style="width:290px" %)//Categorisation//|(% style="width:649px" %)categorisationAgencyId:categorisationId(version)|(% style="width:332px" %)IMF:cat001(1.0.0)
--|(% style="width:290px" %)Category|(% style="width:649px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:332px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
--|(% style="width:290px" %)//CategoryScheme//|(% style="width:649px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:332px" %)IMF:SDDS(1.0.0)
++|**Classname**|**Ending URN pattern**|**Example**
++|Agency^^[[^^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)
--|(% style="width:292px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:742px" %)**Example**
--|(% style="width:292px" %)//CategorySchemeMap//|(% style="width:647px" %)(((
--catSchemeMapAgencyId:catSchemeMapId(version)
--)))|(% style="width:742px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
--|(% style="width:292px" %)Code|(% style="width:647px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:742px" %)SDMX:CL_FREQ(1.0.0).Q
--|(% style="width:292px" %)//Codelist//|(% style="width:647px" %)codeListAgencyId:codeListId(version)|(% style="width:742px" %)SDMX:CL_FREQ(1.0.0)
--|(% style="width:292px" %)ComponentMap|(% style="width:647px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:742px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
--|(% style="width:292px" %)Concept|(% style="width:647px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:742px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
--|(% style="width:292px" %)//ConceptScheme//|(% style="width:647px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:742px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
--|(% style="width:292px" %)//ConceptSchemeMap//|(% style="width:647px" %)(((
--conceptSchemeMapAgencyId:conceptSchemeMap Id(version)
--)))|(% style="width:742px" %)SDMX:CONCEPT_MAP(1.0.0)
--|(% style="width:292px" %)CustomType|(% style="width:647px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:742px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
--|(% style="width:292px" %)//CustomTypeScheme//|(% style="width:647px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:742px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
--|(% style="width:292px" %)DataAttrribute|(% style="width:647px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
--|(% style="width:292px" %)//DataConstraint//|(% style="width:647px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:742px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0)
++|**Classname**|**Ending URN pattern**|**Example**
++|//CategorySchemeMap//|(((
++catSchemeMapAgencyId:catSchemeMapId(version
--|(% style="width:294px" %)**Classname**|(% style="width:645px" %)**Ending URN pattern**|(% style="width:742px" %)**Example**
--|(% style="width:294px" %)DataConsumer|(% style="width:645px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:742px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
--|(% style="width:294px" %)//DataConsumerScheme//|(% style="width:645px" %)(((
--dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**)
--)))|(% style="width:742px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
--|(% style="width:294px" %)//Dataflow//|(% style="width:645px" %)dataflowAgencyId:dataflowId(version)|(% style="width:742px" %)TFFS:CRED_EXT_DEBT(1.0.0)
--|(% style="width:294px" %)DataProvider|(% style="width:645px" %)(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId
--)))|(% style="width:742px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
--|(% style="width:294px" %)//DataProviderScheme//|(% style="width:645px" %)(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
--)))|(% style="width:742px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
--|(% style="width:294px" %)//DataStructure//|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0)
--|(% style="width:294px" %)Dimension|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).FREQ
--|(% style="width:294px" %)(((
++)
++)))|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)
++)))|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)
++
++|**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:645px" %)(((
++)))|(((
  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:742px" %)(((
++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
@@ -657,81 +657,83 @@
  TFFS:EXT_DEBT(1.0.0).AttributeDescriptor
  )))
--|(% style="width:294px" %)GroupDimensionDescriptor|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
--|(% style="width:294px" %)HierarchicalCode|(% style="width:645px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:742px" %)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
--|**Classname**|(% style="width:644px" %)**Ending URN pattern**|(% style="width:743px" %)**Example**
--|//Hierarchy//|(% style="width:644px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:743px" %)UNESCO:H-C-GOV(1.0.0)
--|//HierarchyAssociation//|(% style="width:644px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:743px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
--|Level|(% style="width:644px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:743px" %)UNESCO:H-C-GOV(1.0.0).LVL1
--|Measure|(% style="width:644px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:743px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
--|MetadataAttribute|(% style="width:644px" %)(((
++|**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:743px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
--|MetadataAttributeDescriptor|(% style="width:644px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:743px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
--|//MetadataConstraint//|(% style="width:644px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:743px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
--|//Metadataflow//|(% style="width:644px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:743px" %)IMF:SDDS_MDF(1.0.0)
--|MetadataProvider|(% style="width:644px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:743px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
--|//MetadataProviderScheme//|(% style="width:644px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:743px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
--|//MetadataProvisionAgreement//|(% style="width:644px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:743px" %)IMF:SDDS_MDF_AB(1.0.0)
--|//MetadataSet//|(% style="width:644px" %)metadataProviderId:metadataSetId(version)|(% style="width:743px" %)MD_PROVIDER:METADATASET(1.0.0)
--|//MetadataStructure//|(% style="width:644px" %)msdAgencyId:msdId(version)|(% style="width:743px" %)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:296px" %)**Classname**|(% style="width:646px" %)**Ending URN pattern**|(% style="width:739px" %)**Example**
--|(% style="width:296px" %)NamePersonalisation|(% style="width:646px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:739px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
--|(% style="width:296px" %)//NamePersonalisationScheme//|(% style="width:646px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:739px" %)ECB:PSN_SCHEME(1.0.0)
--|(% style="width:296px" %)//OrganisationSchemeMap//|(% style="width:646px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:739px" %)SDMX:AGENCIES_PROVIDERS(1.0.0)
--|(% style="width:296px" %)OrganisationUnit|(% style="width:646px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|(% style="width:739px" %)ECB:ORGANISATIONS(1.0.0).1F
--|(% style="width:296px" %)//OrganisationUnitScheme//|(% style="width:646px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:739px" %)ECB:ORGANISATIONS(1.0.0)
--|(% style="width:296px" %)//Process//|(% style="width:646px" %)processAgencyId:processId{version)|(% style="width:739px" %)BIS:PROCESS1(1.0.0)
--|(% style="width:296px" %)ProcessStep|(% style="width:646px" %)(((
++|**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:739px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1
--|(% style="width:296px" %)//ProvisionAgreement//|(% style="width:646px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:739px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0)
--|(% style="width:296px" %)ReportingCategory|(% style="width:646px" %)(((
++)))|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:739px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
--|(% style="width:296px" %)//ReportingTaxonomy//|(% style="width:646px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:739px" %)IMF:REP_1(1.0.0)
--|(% style="width:296px" %)//ReportingTaxonomyMap//|(% style="width:646px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:739px" %)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:297px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:737px" %)**Example**
--|(% style="width:297px" %)//RepresentationMap//|(% style="width:647px" %)repMapAgencyId:repMapId(version)|(% style="width:737px" %)SDMX:REF_AREA_MAPPING(1.0.0)
--|(% style="width:297px" %)Ruleset|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:737px" %)ECB:RULESET_23(1.0.0).SET111
--|(% style="width:297px" %)//RulesetScheme//|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:737px" %)ECB:RULESET_23(1.0.0)
--|(% style="width:297px" %)//StructureMap//|(% style="width:647px" %)structureMapAgencyId:structureMap(version)|(% style="width:737px" %)SDMX:BOP_STRUCTURES(1.0.0)
--|(% style="width:297px" %)Subscription|(% style="width:647px" %)(((
++|**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:737px" %)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:297px" %)TimeDimension|(% style="width:647px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:737px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
--|(% style="width:297px" %)Transformation|(% style="width:647px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:737px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
--|(% style="width:297px" %)//TransformationScheme//|(% style="width:647px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:737px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
--|(% style="width:297px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:737px" %)**Example**
--|(% style="width:297px" %)Transition|(% style="width:647px" %)(((
++)))|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:737px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
--|(% style="width:297px" %)UserDefinedOperator|(% style="width:647px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:737px" %)ECB:OS_CALC(1.2.0).OS267
--|(% style="width:297px" %)//UserDefinedOperatorScheme//|(% style="width:647px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:737px" %)ECB:OS_CALC(1.2.0)
--|(% style="width:297px" %)//ValueList//|(% style="width:647px" %)valuelistAgencyId:valuelistId(version)|(% style="width:737px" %)SDMX:VLIST(1.0.0)
--|(% style="width:297px" %)VtlCodelistMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:737px" %)ECB:CLIST_MP(2.0.0).ABZ
--|(% style="width:297px" %)VtlConceptMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).XYA
--|(% style="width:297px" %)VtlDataflowMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).MOQ
--|(% style="width:297px" %)//VtlMappingScheme//|(% style="width:647px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:737px" %)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**
--= 7 Implementation Notes =
++= {{id name="_Toc90810"/}}7 Implementation Notes =
--== 7.1 Structural Definition Metadata ==
++=== {{id name="_Toc90811"/}}7.1 Structural Definition Metadata ===
--=== 7.1.1 Introduction ===
++===== {{id name="_Toc90812"/}}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.)
@@ -747,40 +747,46 @@
  The following table lists the Maintainable Artefacts.
--(% style="width:825.835px" %)
--|(% colspan="2" style="width:455px" %)**Maintainable Artefacts**|(% style="width:367px" %)**Content**
--|(% style="width:160px" %)**Abstract Class**|(% style="width:295px" %)**Concrete Class**|(% style="width:367px" %)
--|(% style="width:160px" %)Item Scheme|(% style="width:295px" %)Codelist|(% style="width:367px" %)Code
--|(% style="width:160px" %) |(% style="width:295px" %)Concept Scheme|(% style="width:367px" %)Concept
--|(% style="width:160px" %) |(% style="width:295px" %)Category Scheme|(% style="width:367px" %)Category
--|(% style="width:160px" %) |(% style="width:295px" %)Organisation Unit Scheme|(% style="width:367px" %)Organisation Unit
--|(% style="width:160px" %) |(% style="width:295px" %)Agency Scheme|(% style="width:367px" %)Agency
--|(% style="width:160px" %) |(% style="width:295px" %)Data Provider Scheme|(% style="width:367px" %)Data Provider
--|(% style="width:160px" %) |(% style="width:295px" %)Metadata Provider Scheme|(% style="width:367px" %)Metadata Provider
--|(% style="width:160px" %) |(% style="width:295px" %)Data Consumer Scheme|(% style="width:367px" %)Data Consumer
--|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy|(% style="width:367px" %)Reporting Category
--|(% style="width:160px" %) |(% style="width:295px" %)Transformation Scheme|(% style="width:367px" %)Transformation
--|(% style="width:160px" %) |(% style="width:295px" %)Custom Type Scheme|(% style="width:367px" %)Custom Type
--|(% style="width:160px" %) |(% style="width:295px" %)Name Personalisation Scheme|(% style="width:367px" %)Name Personalisation
--|(% style="width:160px" %) |(% style="width:295px" %)Vtl Mapping Scheme|(% style="width:367px" %)Vtl Codelist Mapping Vtl Concept Mapping
--|(% style="width:160px" %) |(% style="width:295px" %)Ruleset Scheme|(% style="width:367px" %)Ruleset
--|(% style="width:160px" %) |(% style="width:295px" %)User Defined Operator Scheme|(% style="width:367px" %)User Defined Operator
--|(% style="width:160px" %)Enumerated List|(% style="width:295px" %)ValueList|(% style="width:367px" %)Value Item
--|(% style="width:160px" %)Structure|(% style="width:295px" %)Data Structure Definition|(% style="width:367px" %)(((
++|(% 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:160px" %) |(% style="width:295px" %)Metadata Structure Definition|(% style="width:367px" %)Metadata Attribute Descriptor Metadata Attribute
--|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)Dataflow|(% style="width:367px" %)
--|(% style="width:160px" %) |(% style="width:295px" %)Metadataflow|(% style="width:367px" %)
--|(% style="width:160px" %)None|(% style="width:295px" %)Process|(% style="width:367px" %)Process Step
--|(% style="width:160px" %)None|(% style="width:295px" %)Structure Map|(% style="width:367px" %)(((
++||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
++|Structure Usage|Dataflow|
++||Metadataflow|
++|None|Process|Process Step
++|None|Structure Map|(((
  Component Map
  Epoch Map
@@ -787,44 +787,44 @@
  Date Pattern Map
  )))
--|(% style="width:160px" %)None|(% style="width:295px" %)Representation Map|(% style="width:367px" %)Representation Mapping
--|(% style="width:160px" %)Item Scheme Map|(% style="width:295px" %)Organisation Scheme Map|(% style="width:367px" %)Item Map
--|(% style="width:160px" %) |(% style="width:295px" %)Concept Scheme Map|(% style="width:367px" %)Item Map
--|(% style="width:160px" %) |(% style="width:295px" %)Category Scheme Map|(% style="width:367px" %)Item Map
--|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy Map|(% style="width:367px" %)Item Map
--|(% style="width:160px" %)None|(% style="width:295px" %)Provision Agreement|(% style="width:367px" %)
--|(% style="width:160px" %)None|(% style="width:295px" %)Metadata Provision Agreement|(% style="width:367px" %)
--|(% style="width:160px" %)None|(% style="width:295px" %)Hierarchy|(% style="width:367px" %)Hierarchical Code
--|(% style="width:160px" %)None|(% style="width:295px" %)Hierarchy Association|(% style="width:367px" %)
--|(% style="width:160px" %)None|(% style="width:295px" %)Categorisation|(% style="width:367px" %)
--|(% style="width:160px" %)Constraint|(% style="width:295px" %)Data Constraint|(% style="width:367px" %)DataKeySet
--|(% style="width:160px" %) |(% style="width:295px" %) |(% style="width:367px" %)CubeRegion
--|(% style="width:160px" %)Constraint|(% style="width:295px" %)Metadata Constraint|(% style="width:367px" %)MetadataTargetRegion
++|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|
++|Constraint|Data Constraint|DataKeySet
++|||CubeRegion
++|Constraint|Metadata Constraint|MetadataTargetRegion
  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
--=== 7.1.2 Item Scheme, Structure ===
++===== {{id name="_Toc90813"/}}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)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
++* All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
  * All types of Structure Usage (Dataflow, Metadataflow)
--=== 7.1.3 Structure Usage ===
++===== {{id name="_Toc90814"/}}7.1.3 Structure Usage =====
--==== 7.1.3.1 Structure Usage: Basic Concepts ====
++**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.1 Section 5_en_9b750e13.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.1 Section 5_en_1c94cbe.jpg||height="548" width="578"]]
@@ -842,9 +842,9 @@
 *. Categorisation to Dataflow and Category
 *. Categorisation to Metadataflow and Category
--== 7.2 Data and Metadata Provisioning ==
++=== {{id name="_Toc90815"/}}7.2 Data and Metadata Provisioning ===
--=== 7.2.1 Provisioning Agreement: Basic concepts ===
++===== {{id name="_Toc90816"/}}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.
@@ -852,7 +852,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.
--=== 7.2.2 Provisioning Agreement Model – pull use case ===
++===== {{id name="_Toc90817"/}}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.
@@ -874,9 +874,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.
--== 7.3 Data and Metadata Constraints ==
++=== {{id name="_Toc90818"/}}7.3 Data and Metadata Constraints ===
--=== 7.3.1 Data and Metadata Constraints: Basic Concepts ===
++===== {{id name="_Toc90819"/}}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.
@@ -890,13 +890,13 @@
  In addition, DataAvailabilityConstraints can be extremely useful in a data visualisation system, such as dissemination of statistics on a website. In such a system a Cube Region can be used to specify the Dimension codes that actually exist in a data source (these can be used to build relevant selection tables).
--=== 7.3.2 Data and Metadata Constraints: Schematic ===
++===== {{id name="_Toc90820"/}}7.3.2 Data and Metadata Constraints: Schematic =====
  [[image:SDMX 3.1 Section 5_en_28d0cadc.jpg||height="326" width="580"]]
  **Figure 14: Schematic of the Constraint and the Artefacts that can be constrained**
--=== 7.3.3 Data and Metadata Constraints: Model ===
++===== {{id name="_Toc90821"/}}7.3.3 Data and Metadata Constraints: Model =====
  [[image:SDMX 3.1 Section 5_en_a3184f6a.jpg||height="298" width="579"]]
@@ -912,9 +912,9 @@
  The content of the Constraint can be found in the SDMX Information Model document.
--== 7.4 Data Registration ==
++=== {{id name="_Toc90822"/}}7.4 Data Registration ===
--=== 7.4.1 Basic Concepts ===
++===== {{id name="_Toc90823"/}}7.4.1 Basic Concepts =====
  A Data Provider has published a new dataset conforming to an existing Dataflow (and hence Data Structure Definition). This is implemented as either a web-accessible SDMXML file, or in a database which has a web-services interface capable of responding to an SDMX RESTful query with an SDMX-ML data stream.
@@ -924,15 +924,15 @@
  SDMX-RR supports dataset registration via the Registration Request, which can be created by the Data Provider (giving the Data Provider maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response.
--=== 7.4.2 The Registration Request ===
++===== {{id name="_Toc90824"/}}7.4.2 The Registration Request =====
--==== 7.4.2.1 Registration Request Schematic ====
++**7.4.2.1 Registration Request Schematic**
  [[image:SDMX 3.1 Section 5_en_293a2ea6.jpg||height="337" width="554"]]
  **Figure 16: Schematic of the Objects Concerned with Registration**
--==== 7.4.2.2 Registration Request Model ====
++**7.4.2.2 Registration Request Model**
  The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per dataset to be registered. The Registration can optionally have information, which has been extracted from the Registration:
@@ -944,11 +944,13 @@
  The Registration has an action attribute which takes one of the following values:
++:
++
  (((
--|(% style="width:224px" %)**Action Attribute Value**|(% style="width:1457px" %)**Behaviour**
--|(% style="width:224px" %)Append|(% style="width:1457px" %)Add this Registration to the registry
--|(% style="width:224px" %)Replace|(% style="width:1457px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
--|(% style="width:224px" %)Delete|(% style="width:1457px" %)Delete the existing Registration 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
++|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
  )))
  [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]]
@@ -967,24 +967,30 @@
  https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
++:
++
  (((
--(% style="width:918.835px" %)
--|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
--|indexTimeSeries|(% style="width:745px" %)Extract all the series keys and create a KeySet(s) Constraint.
--|indexDataSet|(% style="width:745px" %)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:745px" %)(((
++|**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.
  )))
--|indexAttributes|(% style="width:745px" %)(((
++|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
++
++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
  )))
--|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
--| |(% style="width:745px" %)SDMX-IM. Note that the content is not stored in the Selection Value.
++|**Indexing Required**|**Registration Process Activity**
++||SDMX-IM. Note that the content is not stored in the Selection Value.
  )))
  Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
@@ -991,7 +991,7 @@
  The Registration must reference the ProvisionAgreement to which it relates.
--=== 7.4.3 Registration Response ===
++===== {{id name="_Toc90825"/}}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”.
@@ -1003,7 +1003,7 @@
  **Figure 18: Logical class diagram showing the registration response**
--== 7.5 Subscription and Notification Service ==
++=== {{id name="_Toc90826"/}}7.5 Subscription and Notification Service ===
  The contents of the SDMX Registry/Repository will change regularly: new code lists and key families will be published and new datasets and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
@@ -1011,13 +1011,13 @@
  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”.
--=== 7.5.1 Subscription Logical Class Diagram ===
++===== {{id name="_Toc90827"/}}7.5.1 Subscription Logical Class Diagram =====
  [[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]]
  **Figure 19: Logical Class Diagram of the Subscription**
--=== 7.5.2 Subscription Information ===
++===== {{id name="_Toc90828"/}}7.5.2 Subscription Information =====
  Regardless of the type of registry/repository events being observed, a subscription always contains:
@@ -1026,16 +1026,18 @@
 . 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:1061.83px" %)
--|**Event Type**|(% style="width:660px" %)**Comment**
--|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
--|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
--|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
--|ALL_EVENTS|(% style="width:660px" %)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
  )))
--=== 7.5.3 Wildcard Facility ===
++===== {{id name="_Toc90829"/}}7.5.3 Wildcard Facility =====
  Subscription notification supports wildcarded identifier components URNs, which are identifiers which have some or all of their component parts replaced by the wildcard character `*`. Identifier components comprise:
@@ -1091,29 +1091,30 @@
  The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
--=== 7.5.4 Structural Repository Events ===
++===== {{id name="_Toc90830"/}}7.5.4 Structural Repository Events =====
  Whenever a maintainable artefact (data structure definition, concept scheme, codelist, metadata structure definition, category scheme, etc.) is added to, deleted from, or modified in the structural metadata repository, a structural metadata event is triggered. Subscriptions may be set up to monitor all such events, or focus on specific artefacts such as a Data Structure Definition.
--=== 7.5.5 Registration Events ===
++===== {{id name="_Toc90831"/}}7.5.5 Registration Events =====
  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:1082.83px" %)
--|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment**
--|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any datasets registered by the specified dataprovider will activate the notification.
--|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any datasets for the agreement will activate the notification.
--|(% style="width:230px" %)Dataflow|(% style="width:850px" %)Any datasets for the specified dataflow will activate the notification.
--|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
--|(% style="width:230px" %)Category|(% style="width:850px" %)Any datasets registered for those dataflows, provision agreements that are categorised by the category.
++|**Selector**|**Comment**
++|DataProvider|Any datasets registered by the specified dataprovider will activate the notification.
++|ProvisionAgreement|Any datasets for the agreement will activate the notification.
++|Dataflow|Any datasets for the specified dataflow will activate the notification.
++|DataStructureDefinition|Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
++|Category|Any datasets registered for those dataflows, 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 ==
++== {{id name="_Toc90832"/}}7.6 Notification ==
--=== 7.6.1 Logical Class Diagram ===
++==== {{id name="_Toc90833"/}}7.6.1 Logical Class Diagram ====
  [[image:SDMX 3.1 Section 5_en_8bc1b889.jpg||height="379" width="579"]]
@@ -1130,11 +1130,11 @@
  Additionally, supplementary information may be contained in the notification as detailed below.
--=== 7.6.2 Structural Event Component ===
++==== {{id name="_Toc90834"/}}7.6.2 Structural Event Component ====
  The notification will contain the MaintainableArtefact that triggered the event in a form similar to the SDMX-ML structural message (using elements from that namespace).
--=== 7.6.3 Registration Event Component ===
++==== {{id name="_Toc90835"/}}7.6.3 Registration Event Component ====
  The notification will contain the Registration.

SDMX 3.1 Section 5_en_293a2ea6.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_67b3555e.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_6c6c7b74.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_6e468656.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_8bc1b889.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_9b750e13.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_b08fd1a2.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_c63d10ab.jpg

Author

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

Size

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

Content

SDMX 3.1 Section 5_en_cdba03b5.jpg

Author

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

Size

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

Content