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

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

From 29.2 to 29.1 From 41.5 to 41.4

From version 41.4

edited by Elena
on 2025/06/18 11:45

Change comment: There is no comment for this version

To version 29.2

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--SDMX 3.0 Standards. Section 5. Registry Specification: Logical Functionality
++SDMX STANDARDS: SECTION 5

Parent

...	...	@@ -1,1 +1,0 @@
1		-Methodology.WebHome

Author

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

Tags

...	...	@@ -1,1 +1,0 @@
1		-Artefact\|Attribute\|Category scheme\|Code list\|Component\|Data set\|Data structure definition\|Dataflow\|Dimension\|Maintenance agency\|Measure\|Metadata repository\|Metadata set\|Metadata structure definition\|Metadataflow\|Notification\|Provision agreement\|Reference metadata\|SDMX Information Model\|SDMX Registry\|SDMX-JSON\|SDMX-ML\|Statistical data and metadata exchange\|Structural metadata

Content

@@ -2,8 +2,7 @@
  {{toc/}}
  {{/box}}
--(% class="wikigeneratedid" id="HRevisionHistory" %)
--**Revision History**
++= Revision History =
  (((
  (% style="width:838.294px" %)
@@ -14,69 +14,69 @@
  = 1 Introduction =
--The business vision for [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] envisages the promotion of a “data sharing” model to facilitate low-cost, high-quality [[statistical data and metadata exchange>>doc:Glossary.Statistical data and metadata exchange.WebHome]]. 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 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>>doc:Glossary.Structural metadata.WebHome]], and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] ([[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]])
--* standardised XML and JSON schemas for the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.SDMX-JSON.WebHome]] formats derived from the model (XSD, JSON)
++* the availability of an abstract information model capable of supporting time series and cross-sectional data, structural metadata, and reference metadata (SDMX-IM)
++* standardised XML and JSON schemas for the SDMX-ML and SDMX-JSON formats derived from the model (XSD, JSON)
  * the use of web-services technology (XML, JSON, Open API)
--Such an architecture needs to be well organised, and the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]/Repository (SDMXRR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:Glossary.Component.WebHome]] required to support the data sharing vision.
++Such an architecture needs to be well organised, and the SDMX Registry/Repository (SDMXRR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the SDMX components required to support the data sharing vision.
--However, it is important to emphasise that the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR provides support for the submission and retrieval of all [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] and provisioning metadata. Therefore, the Registry not only supports the data-sharing scenario, but this metadata is also vital in order to provide support for data and metadata reporting/collection, and dissemination scenarios.
++However, it is important to emphasise that the SDMX-RR provides support for the submission and retrieval of all SDMX structural metadata and provisioning metadata. Therefore, the Registry not only supports the data-sharing scenario, but this metadata is also vital in order to provide support for data and metadata reporting/collection, and dissemination scenarios.
--Standard formats for the exchange of aggregated statistical data and metadata as prescribed in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] v3.0 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient.
++Standard formats for the exchange of aggregated statistical data and metadata as prescribed in SDMX v3.0 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient.
--As organisations migrate to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:Glossary.Artefact.WebHome]] will be produced (e.g., [[Data Structure,>>doc:Glossary.Data structure definition.WebHome]] [[Metadata Structure>>doc:Glossary.Metadata structure definition.WebHome]], [[Code List>>doc:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) definitions – often collectively called [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:Glossary.Artefact.WebHome]] between parties in a controlled and organized way.
++As organisations migrate to SDMX enabled systems, many XML, JSON (and conventional) artefacts will be produced (e.g., Data Structure, Metadata Structure, Code List and Concept definitions – often collectively called structural metadata – XML schemas generated from data structure definitions, XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The SDMX model supports interoperability, and it is important to be able to discover and share these artefacts between parties in a controlled and organized way.
  This is the role of the registry.
--With the fundamental [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] standards in place, a set of architectural standards are needed to address some of the processes involved in [[statistical data and metadata exchange>>doc:Glossary.Statistical data and metadata exchange.WebHome]], with an emphasis on maintenance, retrieval and sharing of the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. In addition, the architectural standards support the registration and discovery of data and referential metadata.
++With the fundamental SDMX standards in place, a set of architectural standards are needed to address some of the processes involved in statistical data and metadata exchange, with an emphasis on maintenance, retrieval and sharing of the structural metadata. In addition, the architectural standards support the registration and discovery of data and referential metadata.
--These architectural standards address the ‘how’, rather than the ‘what’, and are aimed at enabling existing [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] standards to achieve their mission. The architectural standards address registry services, which initially comprise:
++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>>doc:Glossary.Structural metadata.WebHome]] repository
++* structural metadata repository
  * data and metadata registration
  * query
--The registry services outlined in this specification are designed to help the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] assets and to support data sharing for reporting and dissemination.
++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="_Toc93832"/}}2 Scope and Normative Status =
--The scope of this document is to specify the logical interfaces for the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]] in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry.
++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.
  In this document, functions and behaviours of the Registry Interfaces are described in four ways:
  * in text
  * with tables
--* with UML diagrams excerpted from the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]])
--* with UML diagrams that are not a part of the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]] but are included here for clarity and to aid implementations (these diagrams are clearly marked as “Logical Class Diagram ...”)
++* with UML diagrams excerpted from the SDMX Information Model (SDMX-IM)
++* with UML diagrams that are not a part of the SDMX-IM but are included here for clarity and to aid implementations (these diagrams are clearly marked as “Logical Class Diagram ...”)
  Whilst the introductory section contains some information on the role of the registry, it is assumed that the reader is familiar with the uses of a registry in providing shared metadata across a community of counterparties.
--Note that chapters 5 and 6 below contain normative rules regarding the Registry Interface and the identification of registry objects. Further, the minimum standard for access to the registry is via a REST interface (HTTP or HTTPS), as described in the appropriate sections. The [[notification>>doc:Glossary.Notification.WebHome]] mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] specification (Section 3 of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standard). All other sections of this document are informative.
++Note that chapters 5 and 6 below contain normative rules regarding the Registry Interface and the identification of registry objects. Further, the minimum standard for access to the registry is via a REST interface (HTTP or HTTPS), as described in the appropriate sections. The notification mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the SDMX-ML specification (Section 3 of the SDMX Standard). All other sections of this document are informative.
--Note that although the term “authorised user” is used in this document, the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider.
++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="_Toc93833"/}}3 Scope of the SDMX Registry/Repository =
--== 3.1 Objective ==
++== {{id name="_Toc93834"/}}3.1 Objective ==
--The objective of the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] 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:
++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:
--1. To maintain and publish [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that describes the structure and valid content of data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sources such as databases, [[metadata repositories>>doc:Glossary.Metadata repository.WebHome]], [[data sets>>doc:Glossary.Data set.WebHome]], [[metadata sets>>doc:Glossary.Metadata set.WebHome]]. This [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] enables software applications to understand and to interpret the data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] in these sources.
--1. To enable applications, organisations, and individuals to share and to discover data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]]. This facilitates data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] dissemination by implementing the data sharing vision of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]].
++1. 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.
++1. 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.
  == {{id name="_Toc93835"/}}3.2 Structural Metadata ==
--Setting up [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] and the exchange context (referred to as “data provisioning”) involves the following steps for [[maintenance agencies>>doc:Glossary.Maintenance agency.WebHome]]:
++Setting up structural metadata and the exchange context (referred to as “data provisioning”) involves the following steps for maintenance agencies:
--* agreeing and creating a specification of the structure of the data (called a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[DSD>>doc:Glossary.Data structure definition.WebHome]] in this document but also known as “key family”), which defines the [[dimensions>>doc:Glossary.Dimension.WebHome]], [[measures>>doc:Glossary.Measure.WebHome]] and [[attributes>>doc:Glossary.Attribute.WebHome]] of a [[dataset>>doc:Glossary.Data set.WebHome]] and their valid value set;
--* if required, defining a subset or view of a [[DSD>>doc:Glossary.Data structure definition.WebHome]] which allows some restriction of content called a “[[dataflow>>doc:Glossary.Dataflow.WebHome]] definition”;
--* agreeing and creating a specification of the structure of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] ([[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]) which defines the metadata [[attributes>>doc:Glossary.Attribute.WebHome]] and their presentational arrangement in a Metadataset or as part of a [[Dataset>>doc:Glossary.Data set.WebHome]], and their valid values and content;
--* if required, defining a subset or view of an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:Glossary.Metadataflow.WebHome]]”;
--* defining which subject matter domains (specified as a [[Category Scheme>>doc:Glossary.Category scheme.WebHome]]) are related to the [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] to enable browsing;
++* agreeing and creating a specification of the structure of the data (called a Data Structure Definition or DSD in this document but also known as “key family”), which defines the dimensions, measures and attributes of a dataset and their valid value set;
++* if required, defining a subset or view of a DSD which allows some restriction of content called a “dataflow definition”;
++* agreeing and creating a specification of the structure of reference metadata (Metadata Structure Definition) which defines the metadata attributes and their presentational arrangement in a Metadataset or as part of a Dataset, and their valid values and content;
++* if required, defining a subset or view of an MSD which allows some restriction of content called a “metadataflow”;
++* defining which subject matter domains (specified as a Category Scheme) are related to the Dataflow and Metadataflow to enable browsing;
  * defining one or more lists of Data and Metadata Providers;
--* defining which Data/Metadata Providers have agreed to publish a given [[Dataflow>>doc:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] – this is called a [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] or Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], respectively.
++* defining which Data/Metadata Providers have agreed to publish a given Dataflow/Metadataflow – this is called a Provision Agreement or Metadata Provision Agreement, respectively.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
@@ -85,145 +85,145 @@
  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:
--* Structure Definition: refers to [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:Glossary.Data structure definition.WebHome]]) and [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] (MSD)
--* Flow: refers to [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]
--* [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]: refers to [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] (for data) and Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]
--* Provider Scheme: refers to [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]] and Metadata Provider Scheme
--* Provider: refers to [[Data Provider>>doc:Glossary.Data provider.WebHome]] and Metadata Provider
++* Structure Definition: refers to Data Structure Definition (DSD) and Metadata Structure Definition (MSD)
++* Flow: refers to Dataflow and Metadataflow
++* Provision Agreement: refers to Provision Agreement (for data) and Metadata Provision Agreement
++* Provider Scheme: refers to Data Provider Scheme and Metadata Provider Scheme
++* Provider: refers to Data Provider and Metadata Provider
--In that context, the term “Metadata” refers to [[reference metadata>>doc:Glossary.Reference metadata.WebHome]].
++In that context, the term “Metadata” refers to reference metadata.
--== 3.3 Registration ==
++== {{id name="_Toc93836"/}}3.3 Registration ==
--Publishing the data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] involves the following steps for a Data/Metadata Provider:
++Publishing the data and reference metadata involves the following steps for a Data/Metadata Provider:
--* making the [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]]/JSON conformant data files or databases (which respond to an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] query with data). The data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] files or databases must be web accessible, and must conform to an agreed [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] ([[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] subset);
--* registering the existence of published [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX registries>>doc:Glossary.SDMX Registry.WebHome]].
++* making the reference metadata and data available in SDMX-ML/JSON conformant data files or databases (which respond to an SDMX query with data). The data and reference metadata files or databases must be web accessible, and must conform to an agreed Dataflow or Metadataflow (Data Structure Definition or Metadata Structure Definition subset);
++* registering the existence of published reference metadata and data files or databases with one or more SDMX registries.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1edb9829.jpg||height="407" width="553"]]
  **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
--== 3.4 Notification ==
++== {{id name="_Toc93837"/}}3.4 Notification ==
--Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] involves:
++Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
--* registry support of a [[subscription>>doc:Glossary.Subscription.WebHome]]-based [[notification>>doc:Glossary.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:Glossary.Subscription.WebHome]] 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.
--== 3.5 Discovery ==
++== {{id name="_Toc93838"/}}3.5 Discovery ==
--Discovering published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] 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>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] resource:
++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:
--* optionally browsing a subject matter domain [[category scheme>>doc:Glossary.Category scheme.WebHome]] to find [[Dataflows>>doc:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]]) and [[Metadataflows>>doc:Glossary.Metadataflow.WebHome]] which structure the type of data and/or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] being sought;
--* build a query, in terms of the selected [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], which specifies what data are required and submitting this to a service that can query an [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]] which will return a list of (URLs of) data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] files and databases which satisfy the query;
--* processing the query result set and retrieving data and/or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] from the supplied URLs.
++* optionally browsing a subject matter domain category scheme to find Dataflows (and hence Data Structure Definitions) and Metadataflows which structure the type of data and/or reference metadata being sought;
++* build a query, in terms of the selected Data Structure Definition or Metadata Structure Definition, which specifies what data are required and submitting this to a service that can query an SDMX registry which will return a list of (URLs of) data and reference metadata files and databases which satisfy the query;
++* processing the query result set and retrieving data and/or reference metadata from the supplied URLs.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1f4779f4.jpg||height="328" width="554"]]
  **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
--= 4 SDMX Registry/Repository Architecture =
++= {{id name="_Toc93839"/}}4 SDMX Registry/Repository Architecture =
--== 4.1 Architectural Schematic ==
++== {{id name="_Toc93840"/}}4.1 Architectural Schematic ==
--The architecture of the [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]]/repository is derived from the objectives stated above. It is a layered architecture that is founded by a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 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>>doc:Glossary.Structural metadata.WebHome]] required to drive these applications.
++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.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_99c4cc7e.jpg||height="325" width="553"]]
  **Figure 4: Schematic of the Registry Content and Services**
--== 4.2 Structural Metadata Repository ==
++== {{id name="_Toc93841"/}}4.2 Structural Metadata Repository ==
--The basic layer is that of a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:Glossary.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]], Processes etc. This layer is supported by the Structure Submission and Query Service.
++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.
--Note that the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API supports all of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:Glossary.Artefact.WebHome]]. The only structural [[artefacts>>doc:Glossary.Artefact.WebHome]] that are not yet supported are:
++Note that the SDMX REST API supports all of the SDMX structural artefacts. The only structural artefacts that are not yet supported are:
  * Registration of data and metadata sources
--* [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]]
++* Subscription and Notification
--As of the initial version of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:Glossary.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Registry Interface messages, instead.
++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="_Toc93842"/}}4.3 Provisioning Metadata Repository ==
--The function of this repository is to support the definition of the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:Glossary.Data source.WebHome]]. These links can be specified for a data/metadata provider, for a specific data or [[metadata flow>>doc:Glossary.Metadataflow.WebHome]]. In the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model this is called the Provision or Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
++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="_Toc93843"/}}5 Registry Interfaces and Services =
--== 5.1 Registry Interfaces ==
++== {{id name="_Toc93844"/}}5.1 Registry Interfaces ==
  The Registry Interfaces are:
  * Notify Registry Event
--* Submit [[Subscription>>doc:Glossary.Subscription.WebHome]] Request
--* Submit [[Subscription>>doc:Glossary.Subscription.WebHome]] Response
++* Submit Subscription Request
++* Submit Subscription Response
  * Submit Registration Request
  * Submit Registration Response
  * Query Registration Request
  * Query Registration Response
--* Query [[Subscription>>doc:Glossary.Subscription.WebHome]] Request
--* Query [[Subscription>>doc:Glossary.Subscription.WebHome]] Response
++* Query Subscription Request
++* Query Subscription Response
  The registry interfaces are invoked in one of two ways:
--1. The interface is the name of the root node of the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] 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>>doc:Glossary.SDMX-ML.WebHome]] 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>>doc:Glossary.Structural metadata.WebHome]]. This is detailed in sections 5.2.2 and 5.2.3.
++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.
--All these interactions with the Registry – with the exception of NotifyRegistryEvent – are designed in pairs. The first document, the one which invokes the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR interface, is a “Request” document. The message returned by the interface is a “Response” document.
++All these interactions with the Registry – with the exception of NotifyRegistryEvent – are designed in pairs. The first document, the one which invokes the SDMX-RR interface, is a “Request” document. The message returned by the interface is a “Response” document.
--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>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-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.
++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="_Toc93845"/}}5.2 Registry Services ==
--=== 5.2.1 Introduction ===
++=== {{id name="_Toc93846"/}}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="_Toc93847"/}}5.2.2 Structure Submission Service ===
--The registry must support a mechanism for submitting [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://github.com/sdmx-twg/sdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], where changes at an Item [[level>>doc:Glossary.Level.WebHome]] is also possible (see next section on the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]]).
++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).
--=== 5.2.3 Structure Query Service ===
++=== {{id name="_Toc93848"/}}5.2.3 Structure Query Service ===
--The registry must support a mechanism for querying for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://github.com/sdmx-twg/sdmx-rest]]). The registry response to this query mechanism is the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 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-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:
  * Structure
--The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:Glossary.Artefact.WebHome]] that may be queried are:
++The SDMX structural artefacts that may be queried are:
--* [[data flows>>doc:Glossary.Dataflow.WebHome]] and [[metadata flows>>doc:Glossary.Metadataflow.WebHome]]
--* [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:Glossary.Metadata structure definition.WebHome]]
--* [[code lists>>doc:sdmx:Glossary.Code list.WebHome]]
++* data flows and metadata flows
++* data structure definitions and metadata structure definitions
++* code lists
  * value lists
--* [[concept schemes>>doc:Glossary.Concept scheme.WebHome]]
++* concept schemes
  * reporting taxonomies
--* [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] and metadata [[provision agreements>>doc:Glossary.Provision agreement.WebHome]]
++* provision agreements and metadata provision agreements
  * structure maps
--* [[representation>>doc:Glossary.Representation.WebHome]] map
++* representation map
  * organisation scheme map
--* [[concept scheme>>doc:Glossary.Concept scheme.WebHome]] map
--* [[category>>doc:Glossary.Category.WebHome]] scheme map
++* concept scheme map
++* category scheme map
  * reporting taxonomy map
  * processes
  * hierarchies
--* [[constraints>>doc:Glossary.Constraint.WebHome]]
--* [[category>>doc:Glossary.Category.WebHome]] schemes
--* categorisations and categorised objects (examples are categorised [[data flows>>doc:Glossary.Dataflow.WebHome]] and [[metadata flows>>doc:Glossary.Metadataflow.WebHome]], [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], [[metadata structure definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] registered [[data sources>>doc:Glossary.Data source.WebHome]] and metadata sources)
--* organisation schemes ([[agency scheme>>doc:Glossary.Agency scheme.WebHome]], [[data provider scheme>>doc:Glossary.Data provider scheme.WebHome]], [[data consumer scheme>>doc:Glossary.Data consumer scheme.WebHome]], organisation unit scheme)
++* constraints
++* category schemes
++* categorisations and categorised objects (examples are categorised data flows and metadata flows, data structure definitions, metadata structure definitions, provision agreements registered data sources and metadata sources)
++* organisation schemes (agency scheme, data provider scheme, data consumer scheme, organisation unit scheme)
--Due to the [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] implementation the other [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] that may be queried are:
++Due to the VTL implementation the other structural metadata artefacts that may be queried are:
  * Transformation schemes
  * Custom type schemes
  * Name personalisation schemes
--* [[VTL>>doc:Glossary.Validation and transformation language.WebHome]] mapping schemes
++* VTL mapping schemes
  * Ruleset schemes
  * User defined operator schemes
--=== 5.2.4 Data and Reference Metadata Registration Service ===
++=== {{id name="_Toc93849"/}}5.2.4 Data and Reference Metadata Registration Service ===
  This service must implement the following Registry Interfaces:
@@ -232,17 +232,17 @@
  * QueryRegistrationRequest
  * QueryRegistrationResponse
--The Data and Metadata Registration Service allows [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant files and webaccessible databases containing published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:Glossary.Data set.WebHome]] or metadatasets, and MAY extract a concise [[representation>>doc:Glossary.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) values (e.g., values of the data [[attribute>>doc:Glossary.Attribute.WebHome]], [[dimension>>doc:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:Glossary.Data set.WebHome]] or metadata-set. These are called [[Constraints>>doc:Glossary.Constraint.WebHome]] in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-IM.
++The Data and Metadata Registration Service allows SDMX conformant files and webaccessible databases containing published data and reference metadata to be registered in the SDMX Registry. The registration process MAY validate the content of the datasets or metadatasets, and MAY extract a concise representation of the contents in terms of concept values (e.g., values of the data attribute, dimension, metadata attribute), or entire keys, and storing this as a record in the registry to enable discovery of the original dataset or metadata-set. These are called Constraints in the SDMX-IM.
  The Data and Metadata Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry:
--* that the data/metadata provider is allowed to register the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset;
--* that the content of the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset meets the validation [[constraints>>doc:Glossary.Constraint.WebHome]]. This is dependent upon such [[constraints>>doc:Glossary.Constraint.WebHome]] being defined in the structural repository and which reference the relevant [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:Glossary.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]];
--* that a queryable [[data source>>doc:Glossary.Data source.WebHome]] exists – this would necessitate the registration service querying the service to determine its existence;
--* that a simple [[data source>>doc:Glossary.Data source.WebHome]] exists (i.e., a file accessible at a URL);
--* that the correct [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] is used by the registered data;
--* that the [[components>>doc:Glossary.Component.WebHome]] ([[Dimensions>>doc:Glossary.Dimension.WebHome]], [[Attributes>>doc:Glossary.Attribute.WebHome]], [[Measures>>doc:Glossary.Measure.WebHome]], Metadata [[Attributes>>doc:Glossary.Attribute.WebHome]], etc.) are consistent with the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]];
--* that the valid [[representations>>doc:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) to which these [[components>>doc:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]. The Registration has an action [[attribute>>doc:Glossary.Attribute.WebHome]] which takes one of the following values:
++* that the data/metadata provider is allowed to register the dataset or metadataset;
++* that the content of the dataset or metadataset meets the validation constraints. This is dependent upon such constraints being defined in the structural repository and which reference the relevant Dataflow, Metadataflow, Data Provider, Metadata Provider, Data Structure Definition, Metadata Structure Definition, Provision Agreement, Metadata Provision Agreement;
++* that a queryable data source exists – this would necessitate the registration service querying the service to determine its existence;
++* that a simple data source exists (i.e., a file accessible at a URL);
++* that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data;
++* that the components (Dimensions, Attributes, Measures, 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**
@@ -250,18 +250,18 @@
  |(% 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
--The Registration has three Boolean [[attributes>>doc:Glossary.Attribute.WebHome]] which may be present to determine how an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] compliant [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset indexing application must index the [[datasets>>doc:Glossary.Data set.WebHome]] or metadatasets upon registration. The indexing application behaviour is as follows:
++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>>doc:Glossary.Series key.WebHome]] (for a [[Dataset>>doc:Glossary.Data set.WebHome]] registration) or metadata target values (for a Metadataset registration)
++|(% 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>>doc:Glossary.Dimension.WebHome]] of the [[Dataset>>doc:Glossary.Data set.WebHome]] (for a [[Dataset>>doc:Glossary.Data set.WebHome]] registration) or the range of actual (present) values for each Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] 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>>doc:Glossary.Dimension.WebHome]] values (the Key) is actually present in the [[Dataset>>doc:Glossary.Data set.WebHome]]
++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>>doc:Glossary.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:Glossary.Data set.WebHome]]. The validity period of the Metadatasets may also be indexed.
++|(% 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.
--=== 5.2.5 Data and Reference Metadata Discovery ===
++=== {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
  The Data and Metadata Discovery Service implements the following Registry Interfaces:
@@ -268,63 +268,66 @@
  * QueryRegistrationRequest
  * QueryRegistrationResponse
--=== 5.2.6 Subscription and Notification ===
++=== {{id name="_Toc93851"/}}5.2.6 Subscription and Notification ===
--The [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces:
++The Subscription and Notification Service implements the following Registry Interfaces:
  * SubmitSubscriptionRequest
  * SubmitSubscriptionResponse
  * NotifyRegistryEvent
--The data sharing paradigm relies upon the consumers of data and metadata being able to pull information from [[data providers>>doc:Glossary.Data provider.WebHome]]’ dissemination systems. For this to work efficiently, a [[data consumer>>doc:Glossary.Data consumer.WebHome]] needs to know when to pull data, i.e., when something has changed in the registry (e.g., a [[dataset>>doc:Glossary.Data set.WebHome]] has been updated and re-registered). Additionally, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] systems may also want to know if a new [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Code List>>doc:Glossary.Code list.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] has been added. The [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]] Service comprises two parts: [[subscription>>doc:Glossary.Subscription.WebHome]] management, and [[notification>>doc:Glossary.Notification.WebHome]].
++The data sharing paradigm relies upon the consumers of data and metadata being able to pull information from data providers’ dissemination systems. For this to work efficiently, a data consumer needs to know when to pull data, i.e., when something has changed in the registry (e.g., a dataset has been updated and re-registered). Additionally, SDMX systems may also want to know if a new Data Structure Definition, Code List or Metadata Structure Definition has been added. The Subscription and Notification Service comprises two parts: subscription management, and notification.
--[[Subscription>>doc:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:Glossary.Subscription.WebHome]] request which contains:
++Subscription management involves a user submitting a subscription request which contains:
--* a query or [[constraint>>doc:Glossary.Constraint.WebHome]] expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific [[dataflow>>doc:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:Glossary.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]).
--* a list of URIs or endpoints to which an XML [[notification>>doc:Glossary.Notification.WebHome]] message can be sent. Supported endpoint types will be email (mailto~: ) and HTTP POST (a normal http:~/~/ address);
++* 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);
  * request for a list of submitted subscriptions;
--* deletion of a [[subscription>>doc:Glossary.Subscription.WebHome]];
++* deletion of a subscription;
--[[Notification>>doc:Glossary.Notification.WebHome]] requires that the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:Glossary.Subscription.WebHome]] request query), and to issue an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[notification>>doc:Glossary.Notification.WebHome]] document to the endpoints specified in the relevant subscriptions.
++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="_Toc93852"/}}5.2.7 Registry Behaviour ===
--The following table defines the behaviour of the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]]. 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>>doc:Glossary.Version.WebHome]] of a Maintainable, unless semantic versioning is used.
++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>>doc:Glossary.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:Glossary.Artefact.WebHome]] 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>>doc:Glossary.Artefact.WebHome]] that follows semantic versioning, unless a newer [[version>>doc:Glossary.Version.WebHome]] is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft [[versions>>doc:Glossary.Version.WebHome]]. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:Glossary.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:Glossary.Artefact.WebHome]]. This means that any system may internally perform any change within a [[version>>doc:Glossary.Version.WebHome]] of an [[Artefact>>doc:Glossary.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then (as also explained in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”) the [[Artefacts>>doc:Glossary.Artefact.WebHome]] must adhere to the Semantic Versioning rules.
++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" %)(((
--1) If the action is set to “replace” (or a [[maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
--2) Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
--3) If the action is set to “delete” (or a [[maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] 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>>doc:Glossary.Version.WebHome]].
--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.
++1. 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.
++1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
++1. If the action is set to “delete” (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:
--4) The semantic versioning rules in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] documentation MUST be obeyed.
++a) Be a draft version.
  )))
--|(% style="width:188px" %)Structure submission|(% style="width:542px" %)Structures are submitted at the [[level>>doc:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the [[level>>doc:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]].
--|(% 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>>doc:Glossary.Attribute.WebHome]] set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] data query.
++|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
++|(% 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.
++4) 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.
--= 6 Identification of SDMX Objects =
++= {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
--== 6.1 Identification, Versioning, and Maintenance ==
++== {{id name="_Toc93854"/}}6.1 Identification, Versioning, and Maintenance ==
--All major classes of the [[SDMX Information model>>doc:Glossary.SDMX Information Model.WebHome]] inherit from one of:
++All major classes of the SDMX Information model inherit from one of:
  * //**IdentifiableArtefact**// – this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations.
  * //**NameableArtefact**// – this has all of the features of //IdentifiableArtefact// plus the ability to have a multi-lingual name and description.
--* //**VersionableArtefact**// – this has all of the above features plus a [[version>>doc:Glossary.Version.WebHome]] number, according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
++* //**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="_Toc93855"/}}6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1683f36a.jpg||height="688" width="587"]]
  **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
--The table below shows the identification and related data [[attributes>>doc:Glossary.Attribute.WebHome]] to be stored in a registry for objects that are one of:
++The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
  * //nnotable//
  * //Identifiable//
@@ -338,7 +338,7 @@
  |(% 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 language specific variants
++|(% 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" %)
@@ -347,11 +347,11 @@
  |(% 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>>doc:Glossary.Version.WebHome]]|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the [[version>>doc:Glossary.Version.WebHome]] number according to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules.
++|(% 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>>doc:Glossary.SDMX-ML.WebHome]] file.
++| |(% 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.
@@ -359,30 +359,30 @@
  **Table 1: Common Attributes of Object Types**
--== 6.2 Unique identification of SDMX objects ==
++== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
--=== 6.2.1 Agencies and Metadata Providers ===
++=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
--The [[Maintenance Agency>>doc:Glossary.Maintenance agency.WebHome]] in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
++The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_c71516c5.jpg||height="313" width="554"]]
  **Figure 6: Agency Scheme Model**
--The Agency in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top level of this structure is maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] has a fixed id and [[version>>doc:Glossary.Version.WebHome]] ([[version>>doc:Glossary.Version.WebHome]]‘1.0’) and is never declared explicitly in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
++The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an nlevel structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version (version ‘1.0’) and is never declared explicitly in the SDMX object identification mechanism.
--In order to achieve this [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules:
++In order to achieve this SDMX adopts the following rules:
--* Agencies are maintained in an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme).
--* The agency of the [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
--* The “top-level” agency is [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-level” [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
--* Agencies registered in the top-level scheme can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] and so on.
--* The AgencyScheme has a fixed [[version>>doc:Glossary.Version.WebHome]], i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:Glossary.Artefact.WebHome]] follow.
++* Agencies are maintained in an Agency Scheme (which is a sub class of Organisation Scheme).
++* The agency of the Agency Scheme must also be declared in a (different) Agency Scheme.
++* The “top-level” agency is SDMX and maintains the “top-level” Agency Scheme.
++* Agencies registered in the top-level scheme can themselves maintain a single Agency Scheme. Agencies in these second-tier schemes can themselves maintain a single Agency Scheme and so on.
++* The AgencyScheme has a fixed version, i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other Artefacts follow.
  * There can be only one AgencyScheme maintained by any one Agency. It has a fixed id of AGENCIES.
--* The /hierarchy of Organisation is not inherited by [[Maintenance Agency>>doc:Glossary.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] is a flat list of Maintenance Agencies.
--* The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:Glossary.Agency scheme.WebHome]].
++* The /hierarchy of Organisation is not inherited by Maintenance Agency – thus each Agency Scheme is a flat list of Maintenance Agencies.
++* The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the SDMX agency scheme.
--In other words, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] and is contained in the top-level [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
++In other words, SDMX is not a part of the hierarchical ID structure for agencies. However, SDMX is, itself, a maintenance agency and is contained in the top-level Agency Scheme.
  This supports a hierarchical structure of agencyID.
@@ -390,16 +390,14 @@
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_eaceb05e.jpg||height="251" width="432"]]
--**Figure 7: Example of Hierarchic Structure of Agencies **
++**Figure 7: Example of Hierarchic Structure of Agencies **The following organizations maintain an Agency Scheme.
--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
--Each agency is identified by its full [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] excluding SDMX.
++Each agency is identified by its full hierarchy excluding SDMX.
  e.g., the id of EE as an agencyID is AA.DD.EE
@@ -409,20 +409,19 @@
  **Figure 8: Example Showing Use of Agency Identifiers**
--Each of these [[maintenance agencies>>doc:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:Glossary.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
++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.
--Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]], i.e., the Metadatasets; the latter are the containers of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] combined with a target that those metadata refer to.
++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="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
  ==== 6.2.2.1 Introduction ====
--To provide interoperability between [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]/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>>doc:Glossary.SDMX Information Model.WebHome]] objects. Most of these unique identifiers are composite (containing [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]], 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>>doc:Glossary.Component.WebHome]] in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR APIs. In other words, the URN for any [[Identifiable Artefact>>doc:Glossary.Identifiable artefact.WebHome]] is constructed from its [[component>>doc:Glossary.Component.WebHome]] identifiers (agency, id, (% style="color:#e74c3c" %)version(%%) etc.).
++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 ====
--(% class="wikigeneratedid" id="HCaseRulesforURN" %)
--**//__Case Rules for URN__//**
++===== **//__Case Rules for URN__//** =====
  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
@@ -430,9 +430,9 @@
  ~* this can repeat and may not be present (see explanation below)
--Note that in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. For this reason, the only [[version>>doc:Glossary.Version.WebHome]] information that is allowed is for the maintainable object.
++Note that in the SDMX Information Model there are no concrete Versionable Artefacts that are not a Maintainable Artefact. For this reason, the only version information that is allowed is for the maintainable object.
--The [[Maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The [[version>>doc:Glossary.Version.WebHome]] information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning.
++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 ====
@@ -445,84 +445,91 @@
  The packages are:
  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-version** is the [[version>>doc:Glossary.Version.WebHome]], according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present.
++**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>>doc:Glossary.Code.WebHome]] 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>>doc:Glossary.Level.WebHome]] in its [[hierarchy>>doc:Glossary.Hierarchy.WebHome]]. 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.
++**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>>doc:Glossary.Code.WebHome]] can have a parent [[Code>>doc:Glossary.Code.WebHome]] and a (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have a parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) these are maintained in a flat structure and therefore do not have a containerobject-id.
++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.
  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.
--(% class="wikigeneratedid" id="HGenericExamplesoftheURNStructure" %)
--//__**Generic Examples of the URN Structure**__//
++===== //__**Generic Examples of the URN Structure**__// =====
  __Actual object is a maintainable__
--SDMXPrefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid(version)
++SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version)
  __Actual object is contained in a maintained object with no intermediate containing object__
--SDMXPrefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid(version).object-id
++SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).object-id
  __Actual object is contained in a maintained object with an intermediate containing object__
--SDMXPrefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
++SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
  __Actual object is contained in a maintained object with no intermediate containing__ __object but__ __the object type itself is hierarchical__
--In this case the object id may not be unique in itself but only within the context of the [[hierarchy>>doc:Glossary.Hierarchy.WebHome]]. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a [[Category>>doc:Glossary.Category.WebHome]] in a CategoryScheme. The [[Category>>doc:Glossary.Category.WebHome]] is hierarchical, and all intermediate [[Categories>>doc:Glossary.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for CategoryScheme/ [[Category>>doc:Glossary.Category.WebHome]]/ [[Category>>doc:Glossary.Category.WebHome]].
++In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a CategoryScheme. The Category is hierarchical, and all intermediate Categories are shown as a contained object. The example below shows the generic structure for CategoryScheme/ Category/ Category.
--SDMXPrefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
++SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
  Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
--In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a MetadataAttribute where the contained objects are MetadataAttributeDescriptor (first contained object id) and MetadataAttribute (subsequent contained object ids). The example below shows the generic structure for [[MSD>>doc:Glossary.Metadata structure definition.WebHome]]/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute
++In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a MetadataAttribute where the contained objects are MetadataAttributeDescriptor (first contained object id) and MetadataAttribute (subsequent contained object ids). The example below shows the generic structure for MSD/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute
--SDMXPrefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
++SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
--(% class="wikigeneratedid" id="HConcreteExamplesoftheURNStructure" %)
--//__**Concrete Examples of the URN Structure**__//
++===== //__**Concrete Examples of the URN Structure**__// =====
--The [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT of legacy (% style="color:#e74c3c" %)version(%%) 2.1 maintained by the toplevel Agency TFFS would have the URN:
++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>>doc:Glossary.Code.WebHome]] for Argentina maintained by ISO in the [[code list>>doc:Glossary.Code list.WebHome]] CL_3166A2 of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be:
++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>>doc:Glossary.Category.WebHome]] (id of 1) which has parent [[category>>doc:Glossary.Category.WebHome]] (id of 2) maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] in the [[category scheme>>doc:Glossary.Category scheme.WebHome]] SUBJECT_MATTER_DOMAINS of the semantic extended (% style="color:#e74c3c" %)version(%%) 1.0.0draft would be:
++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>>doc:Glossary.Attribute.WebHome]] maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] in the [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] CONTACT_METADATA of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 where the [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] of the Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] is CONTACT_DETAILS/CONTACT_NAME would be:
++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>>doc:Glossary.Dataflow.WebHome]] maintained by ABC and identified as EXTERNAL_DEBT of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be:
++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>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to create the URN from the individual identification [[attributes>>doc:Glossary.Attribute.WebHome]] submitted and to transform the URN to these identification [[attributes>>doc:Glossary.Attribute.WebHome]]. The identification [[attributes>>doc:Glossary.Attribute.WebHome]] are:
++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:
--* **Identifiable and [[Nameable Artefacts>>doc:Glossary.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic)
--* **[[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]]**: id, (% style="color:#e74c3c" %)version(%%), agencyId
++* **Identifiable and Nameable Artefacts**: id (in some cases this id may be hierarchic)
++* **Maintainable Artefacts**: id, version, agencyId
--The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to resolve the unique identifier of an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:Glossary.Artefact.WebHome]] and to produce an [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] rendering of that [[artefact>>doc:Glossary.Artefact.WebHome]] if it is located in the Registry.
++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 ===
@@ -609,114 +609,124 @@
  === {{id name="_Toc93860"/}}6.2.4 URN Identification components of SDMX objects ===
--The table below describes the identification [[components>>doc:Glossary.Component.WebHome]] for all [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object types that have identification. Note the actual [[attributes>>doc:Glossary.Attribute.WebHome]] 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>>doc:Glossary.Attribute.WebHome]] of the Agency class that is associated to the ConceptScheme.
++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.
  Note that for brevity the URN examples omit the prefix (classnames in italics indicate maintainable objects, keywords in bold indicate fixed value) All URNs have the prefix:
  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--(% style="width:1419.29px" %)
--|(% style="width:227px" %)**Classname**|(% style="width:645px" %)**Ending URN pattern**|(% style="width:543px" %)**Example**
--|(% style="width:227px" %)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:645px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:543px" %)ECB:**AGENCIES**(**1.0**).AA
--|(% style="width:227px" %)//AgencyScheme//|(% style="width:645px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:543px" %)ECB:**AGENCIES**(**1.0**)
--|(% style="width:227px" %)//Categorisation//|(% style="width:645px" %)categorisationAgencyId:categorisationId(version)|(% style="width:543px" %)IMF:cat001(1.0.0)
--|(% style="width:227px" %)Category|(% style="width:645px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:543px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
--|(% style="width:227px" %)//CategoryScheme//|(% style="width:645px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:543px" %)IMF:SDDS(1.0.0)
--|(% style="width:227px" %)//CategorySchemeMap//|(% style="width:645px" %)(((
++(% 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" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:1049px" %)**Example**
++|(% style="width:250px" %)//CategorySchemeMap//|(% style="width:639px" %)(((
  catSchemeMapAgencyId:catSchemeMapId(version)
--)))|(% style="width:543px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
--|(% style="width:227px" %)Code|(% style="width:645px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:543px" %)SDMX:CL_FREQ(1.0.0).Q
--|(% style="width:227px" %)//Codelist//|(% style="width:645px" %)codeListAgencyId:codeListId(version)|(% style="width:543px" %)SDMX:CL_FREQ(1.0.0)
--|(% style="width:227px" %)ComponentMap|(% style="width:645px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:543px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
--|(% style="width:227px" %)Concept|(% style="width:645px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:543px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
--|(% style="width:227px" %)//ConceptScheme//|(% style="width:645px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:543px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
--|(% style="width:227px" %)//ConceptSchemeMap//|(% style="width:645px" %)(((
++)))|(% 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" %)(((
  conceptSchemeMapAgencyId:conceptSchemeMap
  Id(version)
--)))|(% style="width:543px" %)SDMX:CONCEPT_MAP(1.0.0)
--|(% style="width:227px" %)CustomType|(% style="width:645px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:543px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
--|(% style="width:227px" %)//CustomTypeScheme//|(% style="width:645px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:543px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
--|(% style="width:227px" %)DataAttrribute|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:543px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
--|(% style="width:227px" %)//DataConstraint//|(% style="width:645px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:543px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0)
--|(% style="width:229px" %)DataConsumer|(% style="width:645px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:543px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
--|(% style="width:229px" %)//DataConsumerScheme//|(% style="width:645px" %)(((
++)))|(% 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)
++
++|(% 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:543px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
--|(% style="width:229px" %)//Dataflow//|(% style="width:645px" %)dataflowAgencyId:dataflowId(version)|(% style="width:543px" %)TFFS:CRED_EXT_DEBT(1.0.0)
--|(% style="width:229px" %)DataProvider|(% style="width:645px" %)(((
++)))|(% 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:543px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
--|(% style="width:229px" %)//DataProviderScheme//|(% style="width:645px" %)(((
++)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
++|(% style="width:248px" %)//DataProviderScheme//|(% style="width:643px" %)(((
  dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
--)))|(% style="width:543px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
--|(% style="width:229px" %)//DataStructure//|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:543px" %)TFFS:EXT_DEBT(1.0.0)
--|(% style="width:229px" %)Dimension|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:543px" %)TFFS:EXT_DEBT(1.0.0).FREQ
--|(% style="width:229px" %)(((
++)))|(% 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" %)(((
  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:543px" %)(((
++)))|(% 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" %)(((
  TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
  TFFS:EXT_DEBT(1.0.0).MeasureDescriptor
  TFFS:EXT_DEBT(1.0.0).AttributeDescriptor
  )))
--|(% style="width:229px" %)GroupDimensionDescriptor|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:543px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
--|(% style="width:229px" %)HierarchicalCode|(% style="width:645px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:543px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
--|(% style="width:206px" %)//Hierarchy//|(% style="width:645px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:543px" %)UNESCO:H-C-GOV(1.0.0)
--|(% style="width:206px" %)//HierarchyAssociation//|(% style="width:645px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:543px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
--|(% style="width:206px" %)Level|(% style="width:645px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:543px" %)UNESCO:H-C-GOV(1.0.0).LVL1
--|(% style="width:206px" %)Measure|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:543px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
--|(% style="width:206px" %)MetadataAttribute|(% style="width:645px" %)(((
++|(% 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
++
++|(% 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" %)(((
  msdAgencyId:msdId(version).metadataAttributeId.
  metadataAttributeId
--)))|(% style="width:543px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
--|(% style="width:206px" %)MetadataAttributeDescriptor|(% style="width:645px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:543px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
--|(% style="width:206px" %)//MetadataConstraint//|(% style="width:645px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:543px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
--|(% style="width:206px" %)//Metadataflow//|(% style="width:645px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:543px" %)IMF:SDDS_MDF(1.0.0)
--|(% style="width:206px" %)MetadataProvider|(% style="width:645px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:543px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
--|(% style="width:206px" %)//MetadataProviderScheme//|(% style="width:645px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:543px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
--|(% style="width:206px" %)//MetadataProvisionAgreement//|(% style="width:645px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:543px" %)IMF:SDDS_MDF_AB(1.0.0)
--|(% style="width:206px" %)//MetadataSet//|(% style="width:645px" %)metadataProviderId:metadataSetId(version)|(% style="width:543px" %)MD_PROVIDER:METADATASET(1.0.0)
--|(% style="width:206px" %)//MetadataStructure//|(% style="width:645px" %)msdAgencyId:msdId(version)|(% style="width:543px" %)IMF:SDDS_MSD(1.0.0)
--|(% style="width:227px" %)NamePersonalisation|(% style="width:527px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:545px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
--|(% style="width:227px" %)//NamePersonalisationScheme//|(% style="width:527px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:545px" %)ECB:PSN_SCHEME(1.0.0)
--|(% style="width:227px" %)//OrganisationSchemeMap//|(% style="width:527px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:545px" %)SDMX:AGENCIES_PROVIDERS(1.0.0)
--|(% style="width:227px" %)OrganisationUnit|(% style="width:527px" %)organisationUnitSchemeAgencyId:organisationUnitSchemeId(version).organisationUnitId|(% style="width:545px" %)ECB:ORGANISATIONS(1.0.0).1F
--|(% style="width:227px" %)//OrganisationUnitScheme//|(% style="width:527px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:545px" %)ECB:ORGANISATIONS(1.0.0)
--|(% style="width:227px" %)//Process//|(% style="width:527px" %)processAgencyId:processId{version)|(% style="width:545px" %)BIS:PROCESS1(1.0.0)
--|(% style="width:227px" %)ProcessStep|(% style="width:527px" %)(((
++)))|(% 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)
++
++|(% 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" %)(((
  processAgencyId:processId(version).processStepId.
  processStepId
--)))|(% style="width:545px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1
--|(% style="width:227px" %)//ProvisionAgreement//|(% style="width:527px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:545px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0)
--|(% style="width:227px" %)ReportingCategory|(% style="width:527px" %)(((
++)))|(% 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" %)(((
  reportingTaxonomyAgencyId:
  reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId
--)))|(% style="width:545px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
--|(% style="width:227px" %)//ReportingTaxonomy//|(% style="width:527px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:545px" %)IMF:REP_1(1.0.0)
--|(% style="width:227px" %)//ReportingTaxonomyMap//|(% style="width:527px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:545px" %)SDMX:RT_MAP(1.0.0)
--|(% style="width:229px" %)//RepresentationMap//|(% style="width:645px" %)repMapAgencyId:repMapId(version)|(% style="width:215px" %)SDMX:REF_AREA_MAPPING(1.0.0)
--|(% style="width:229px" %)Ruleset|(% style="width:645px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:215px" %)ECB:RULESET_23(1.0.0).SET111
--|(% style="width:229px" %)//RulesetScheme//|(% style="width:645px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:215px" %)ECB:RULESET_23(1.0.0)
--|(% style="width:229px" %)//StructureMap//|(% style="width:645px" %)structureMapAgencyId:structureMap(version)|(% style="width:215px" %)SDMX:BOP_STRUCTURES(1.0.0)
--|(% style="width:229px" %)Subscription|(% style="width:645px" %)(((
++)))|(% 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)
++
++|(% 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" %)(((
  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:1015px" %)This cannot be generated by a common mechanism as [[subscriptions>>doc:Glossary.Subscription.WebHome]], although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the [[Subscription>>doc:Glossary.Subscription.WebHome]], and for the application creating the [[subscription>>doc:Glossary.Subscription.WebHome]] to store the registry URN that is returned from the registry in the [[subscription>>doc:Glossary.Subscription.WebHome]] response message.
--|(% style="width:229px" %)TimeDimension|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:1015px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
--|(% style="width:229px" %)Transformation|(% style="width:645px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:1015px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
--|(% style="width:229px" %)//TransformationScheme//|(% style="width:645px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:1015px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
--|(% style="width:229px" %)Transition|(% style="width:645px" %)(((
++)))|(% 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" %)(((
  processAgencyId:processId(version).processStepId.
  transitionId
--)))|(% style="width:1015px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
--|(% style="width:229px" %)UserDefinedOperator|(% style="width:645px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:1015px" %)ECB:OS_CALC(1.2.0).OS267
--|(% style="width:229px" %)//UserDefinedOperatorScheme//|(% style="width:645px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:1015px" %)ECB:OS_CALC(1.2.0)
--|(% style="width:229px" %)//ValueList//|(% style="width:645px" %)valuelistAgencyId:valuelistId(version)|(% style="width:1015px" %)SDMX:VLIST(1.0.0)
--|(% style="width:229px" %)VtlCodelistMapping|(% style="width:645px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:1015px" %)ECB:CLIST_MP(2.0.0).ABZ
--|(% style="width:229px" %)VtlConceptMapping|(% style="width:645px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:1015px" %)ECB:CLIST_MP(1.0.0).XYA
--|(% style="width:229px" %)VtlDataflowMapping|(% style="width:645px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:1015px" %)ECB:CLIST_MP(1.0.0).MOQ
--|(% style="width:229px" %)//VtlMappingScheme//|(% style="width:645px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:1015px" %)ECB:CLIST_MP(2.0.0)
++)))|(% 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)
  **Table 3: Table of identification components for SDMX Identifiable Artefacts**
@@ -726,85 +726,85 @@
  === {{id name="_Toc93863"/}}7.1.1 Introduction ===
--The [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] must have the ability to support agencies in their role of defining and disseminating [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]]. These [[artefacts>>doc:Glossary.Artefact.WebHome]] include [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], [[code lists>>doc:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) etc. and are fully defined in the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]. An authenticated agency may submit valid [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] definitions which must be stored in the registry. Note that the term “[[structural metadata>>doc:Glossary.Structural metadata.WebHome]]” refers as a general term to all structural [[components>>doc:Glossary.Component.WebHome]] ([[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[Code Lists>>doc:Glossary.Code list.WebHome]], [[Concept Schemes>>doc:Glossary.Concept scheme.WebHome]], etc.)
++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.)
--At a minimum, [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] definitions may be submitted to and queried from the registry via an HTTP/HTTPS POST in the form of one of the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] messages for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] and the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] RESTful API for structure queries. The message may contain all [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items for the whole registry, [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items for one [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]], or individual [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items.
++At a minimum, structural metadata definitions may be submitted to and queried from the registry via an HTTP/HTTPS POST in the form of one of the SDMX-ML messages for structural metadata and the SDMX RESTful API for structure queries. The message may contain all structural metadata items for the whole registry, structural metadata items for one maintenance agency, or individual structural metadata items.
--[[Structural metadata>>doc:Glossary.Structural metadata.WebHome]] items
++Structural metadata items
--* may only be modified by the [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] which created them;
++* may only be modified by the maintenance agency which created them;
  * may only be deleted by the agency which created them;
  * may not be deleted if they are referenced from other constructs in the Registry.
--The (% style="color:#e74c3c" %)level(%%) of granularity for the maintenance of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[Structural Metadata>>doc:Glossary.Structural metadata.WebHome]] objects in the registry is the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. Especially for [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], though, partial maintenance may be performed, i.e., at the (% style="color:#e74c3c" %)level(%%) of the Item, by submitting an [[Item Scheme>>doc:Glossary.Item scheme.WebHome]] with the 'isPartial' flag set and a reduced set of Items.
++The level of granularity for the maintenance of SDMX Structural Metadata objects in the registry is the Maintainable Artefact. Especially for Item Schemes, though, partial maintenance may be performed, i.e., at the level of the Item, by submitting an Item Scheme with the 'isPartial' flag set and a reduced set of Items.
--The following table lists the [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]].
++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>>doc:Glossary.Item scheme.WebHome]]|(% style="width:324px" %)Codelist|(% style="width:490px" %)[[Code>>doc:Glossary.Code.WebHome]]
--|(% style="width:198px" %) |(% style="width:324px" %)[[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]]|(% style="width:490px" %)(% style="color:#e74c3c" %)Concept
--|(% style="width:198px" %) |(% style="width:324px" %)[[Category Scheme>>doc:Glossary.Category scheme.WebHome]]|(% style="width:490px" %)[[Category>>doc:Glossary.Category.WebHome]]
--|(% style="width:198px" %) |(% style="width:324px" %)[[Organisation Unit Scheme>>doc:Glossary.Organisation unit scheme.WebHome]]|(% style="width:490px" %)Organisation Unit
--|(% style="width:198px" %) |(% style="width:324px" %)[[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]|(% style="width:490px" %)Agency
--|(% style="width:198px" %) |(% style="width:324px" %)[[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]]|(% style="width:490px" %)[[Data Provider>>doc:Glossary.Data provider.WebHome]]
++|(% 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>>doc:Glossary.Data consumer scheme.WebHome]]|(% style="width:490px" %)[[Data Consumer>>doc:Glossary.Data consumer.WebHome]]
--|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy|(% style="width:490px" %)Reporting [[Category>>doc:Glossary.Category.WebHome]]
++|(% 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>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme|(% style="width:490px" %)[[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] Codelist Mapping [[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)Concept(%%) Mapping
++|(% 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>>doc:Glossary.Data structure definition.WebHome]]|(% style="width:490px" %)(((
--[[Dimension>>doc:Glossary.Dimension.WebHome]] Descriptor
--Group [[Dimension>>doc:Glossary.Dimension.WebHome]] Descriptor
--[[Dimension>>doc:Glossary.Dimension.WebHome]]
--Time [[Dimension>>doc:Glossary.Dimension.WebHome]]
--[[Attribute>>doc:Glossary.Attribute.WebHome]] Descriptor
--Data [[Attribute>>doc:Glossary.Attribute.WebHome]]
++|(% style="width:198px" %)Structure|(% style="width:324px" %)Data Structure Definition|(% style="width:490px" %)(((
++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>>doc:Glossary.Attribute.WebHome]] Descriptor Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]]
--|(% style="width:198px" %)Structure Usage|(% style="width:324px" %)[[Dataflow>>doc:Glossary.Dataflow.WebHome]]|(% style="width:490px" %)
--|(% style="width:198px" %) |(% style="width:324px" %)[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]|(% style="width:490px" %)
++|(% 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 (% style="color:#e74c3c" %)Map|(% style="width:490px" %)(((
--[[Component>>doc:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)Map(%%)
--Epoch (% style="color:#e74c3c" %)Map(%%)
--Date Pattern (% style="color:#e74c3c" %)Map
++|(% style="width:198px" %)None|(% style="width:324px" %)Structure Map|(% style="width:490px" %)(((
++Component Map
++Epoch Map
++Date Pattern Map
  )))
--|(% style="width:198px" %)None|(% style="width:324px" %)[[Representation>>doc:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:490px" %)[[Representation>>doc:Glossary.Representation.WebHome]] Mapping
--|(% style="width:198px" %)[[Item Scheme>>doc:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:324px" %)Organisation Scheme (% style="color:#e74c3c" %)Map|(% style="width:490px" %)Item (% style="color:#e74c3c" %)Map
--|(% style="width:198px" %) |(% style="width:324px" %)[[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:490px" %)Item (% style="color:#e74c3c" %)Map
--|(% style="width:198px" %) |(% style="width:324px" %)[[Category Scheme>>doc:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:490px" %)Item (% style="color:#e74c3c" %)Map
--|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy (% style="color:#e74c3c" %)Map|(% style="width:490px" %)Item (% style="color:#e74c3c" %)Map
--|(% style="width:198px" %)None|(% style="width:324px" %)[[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]|(% style="width:490px" %)
--|(% style="width:198px" %)None|(% style="width:324px" %)[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]]|(% style="width:490px" %)Hierarchical [[Code>>doc:Glossary.Code.WebHome]]
--|(% style="width:198px" %)None|(% style="width:324px" %)[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association|(% style="width:490px" %)
++|(% 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" %)
--**Table 4: Table of [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]] for Structural Definition Metadata**
++**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
  === {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
--The [[artefacts>>doc:Glossary.Artefact.WebHome]] included in the structural definitions are:
++The artefacts included in the structural definitions are:
--* All types of [[Item Scheme>>doc:Glossary.Item scheme.WebHome]] (Codelist, [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]], [[Category Scheme>>doc:Glossary.Category scheme.WebHome]], Organisation Scheme, [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]], [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]], Metadata Provider Scheme, [[Data Consumer Scheme>>doc:Glossary.Data consumer scheme.WebHome]], [[Organisation Unit Scheme>>doc:Glossary.Organisation unit scheme.WebHome]], Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, [[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
++* 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>>doc:Glossary.Data structure definition.WebHome]], Metadata Structure Definition)
--* All types of Structure Usage ([[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]])
++* 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>>doc:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], 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>>doc:Glossary.Category.WebHome]] in one or more [[Category Scheme>>doc:Glossary.Category scheme.WebHome]] using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the [[Category Schemes>>doc:Glossary.Category scheme.WebHome]].
++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 ====
@@ -818,29 +818,29 @@
  **Figure 10: SDMX-IM of links from Structure Usage to Category**
--In addition to the maintenance of the [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and the [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], the following links must be maintained in the registry:
++In addition to the maintenance of the Dataflow and the Metadataflow, the following links must be maintained in the registry:
--* [[Dataflow>>doc:Glossary.Dataflow.WebHome]] to Data Structure Definition
--* [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] to Metadata Structure Definition
++* Dataflow to Data Structure Definition
++* Metadataflow to Metadata Structure Definition
  The following links may be created by means of a Categorisation
--* Categorisation to [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and Category
--* Categorisation to [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] and Category
++* Categorisation to Dataflow and Category
++* Categorisation to Metadataflow and Category
  == {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ==
  === {{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>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-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 (% style="color:#e74c3c" %)level(%%) agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and [[timeliness>>doc:Glossary.Timeliness.WebHome]] metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
++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.
  Note that the term “data provisioning” here includes both the provisioning of data and metadata.
--Although the [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] 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.
++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 ===
--An organisation which publishes statistical data or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and wishes to make it available to an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] enabled community is called a [[Data Provider>>doc:Glossary.Data provider.WebHome]]. In terms of the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]], the [[Data Provider>>doc:Glossary.Data provider.WebHome]] is maintained in a [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]].
++An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_ec727775.jpg||height="455" width="551"]]
@@ -852,29 +852,29 @@
  **Figure 12: Schematic of the Provision Agreement**
--The diagram below is a logical [[representation>>doc:Glossary.Representation.WebHome]] of the data required in order to maintain [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]].
++The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_7b3d291a.jpg||height="246" width="579"]]
  **Figure 13: Logical class diagram of the information contained in the Provision Agreement**
--A [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] is [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. Each [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] must reference a [[Data Provider>>doc:Glossary.Data provider.WebHome]] or Metadata Provider and a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] Definition. The Data/Metadata Provider and the [[Dataflow>>doc:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] must exist already in order to set up a Metadata Provision or [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
++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="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===
--(% style="color:#e74c3c" %)Constraints(%%) are, effectively, lists of the valid or actual content of data and metadata. (% style="color:#e74c3c" %)Constraints(%%) can be used to specify a subset of the theoretical content of [[data set>>doc:Glossary.Data set.WebHome]] or [[metadata set>>doc:Glossary.Metadata set.WebHome]] which can be derived from the specification of the [[DSD>>doc:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:Glossary.Metadata structure definition.WebHome]]. A (% style="color:#e74c3c" %)Constraint(%%) can comprise a list of keys or a list of content (usually [[code>>doc:Glossary.Code.WebHome]] values) of a specific [[component>>doc:Glossary.Component.WebHome]] such as a [[dimension>>doc:Glossary.Dimension.WebHome]] or [[attribute>>doc:Glossary.Attribute.WebHome]].
++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.
--(% style="color:#e74c3c" %)Constraints(%%) comprise the specification of subsets of key or [[attribute>>doc:Glossary.Attribute.WebHome]] values that are contained in a [[data source>>doc:Glossary.Data source.WebHome]], or is to be provided for a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], or directly attached to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]. This is important metadata because, for example, the full range of possibilities which is implied by the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] (e.g., the complete set of valid keys is the Cartesian product of all the values in the [[code lists>>doc:Glossary.Code list.WebHome]] for each of the [[Dimensions>>doc:Glossary.Dimension.WebHome]]) is often more than is actually present in any specific [[data source>>doc:Glossary.Data source.WebHome]], or more than is intended to be supplied according to a specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]].
++Constraints comprise the specification of subsets of key or attribute values that are contained in a data source, or is to be provided for a Dataflow or Metadataflow, or directly attached to a Data Structure Definition or Metadata Structure Definition. This is important metadata because, for example, the full range of possibilities which is implied by the Data Structure Definition (e.g., the complete set of valid keys is the Cartesian product of all the values in the code lists for each of the Dimensions) is often more than is actually present in any specific data source, or more than is intended to be supplied according to a specific Dataflow.
--Often a [[Data Provider>>doc:Glossary.Data provider.WebHome]] will not be able to provide data for all key combinations, either because the combination itself is not meaningful, or simply because the provider does not have the data for that combination. In this case the [[Data Provider>>doc:Glossary.Data provider.WebHome]] could constrain the [[data source>>doc:Glossary.Data source.WebHome]] (at the (% style="color:#e74c3c" %)level(%%) of the [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] or the [[Data Provider>>doc:Glossary.Data provider.WebHome]]) by supplying metadata that defines the key combinations or cube regions that are available. This is done by means of a (% style="color:#e74c3c" %)Constraint(%%). The (% style="color:#e74c3c" %)Constraint(%%) is also used to define a [[code list>>doc:Glossary.Code list.WebHome]] subset which is used to populate a partial [[code list>>doc:Glossary.Code list.WebHome]].
++Often a Data Provider will not be able to provide data for all key combinations, either because the combination itself is not meaningful, or simply because the provider does not have the data for that combination. In this case the Data Provider could constrain the data source (at the level of the Provision Agreement or the Data Provider) by supplying metadata that defines the key combinations or cube regions that are available. This is done by means of a Constraint. The Constraint is also used to define a code list subset which is used to populate a partial code list.
--Furthermore, it is often useful to define subsets or views of the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] which restrict values in some [[code lists>>doc:Glossary.Code list.WebHome]], especially where many such subsets restrict the same [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]. Such a view is called a [[Dataflow>>doc:Glossary.Dataflow.WebHome]], and there can be one or more defined for any [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
++Furthermore, it is often useful to define subsets or views of the Data Structure Definition which restrict values in some code lists, especially where many such subsets restrict the same Data Structure Definition. Such a view is called a Dataflow, and there can be one or more defined for any Data Structure Definition.
--Whenever data is published or made available by a [[Data Provider>>doc:Glossary.Data provider.WebHome]], it must conform to a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] (and hence to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]). The [[Dataflow>>doc:Glossary.Dataflow.WebHome]] is thus a means of enabling content based processing.
++Whenever data is published or made available by a Data Provider, it must conform to a Dataflow (and hence to a Data Structure Definition). The Dataflow is thus a means of enabling content based processing.
--In addition, (% style="color:#e74c3c" %)Constraints(%%) 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>>doc:Glossary.Dimension.WebHome]] [[codes>>doc:Glossary.Code.WebHome]] that actually exist in a [[data source>>doc:Glossary.Data source.WebHome]] (these can be used to build relevant selection tables), and the Key Set can be used to specify the keys that exist in a [[data source>>doc:Glossary.Data source.WebHome]] (these can be used to guide the user to select only those [[Dimension>>doc:Glossary.Dimension.WebHome]] [[code>>doc:Glossary.Code.WebHome]] values that will return data based on the [[Dimension>>doc:Glossary.Dimension.WebHome]] values already selected).
++In addition, Constraints 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), and the Key Set can be used to specify the keys that exist in a data source (these can be used to guide the user to select only those Dimension code values that will return data based on the Dimension values already selected).
  === {{id name="_Toc93871"/}}7.3.2 Data and Metadata Constraints: Schematic ===
@@ -890,21 +890,21 @@
  Logical class diagram showing inheritance between and reference to constrainable artefacts
--The class diagram above shows that [[Data Provider>>doc:Glossary.Data provider.WebHome]], Metadata Provider, [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], Simple Datasource and REST Datasource (via the abstract Query Datasource) are all concrete sub-classes of Constrainable [[Artefact>>doc:Glossary.Artefact.WebHome]] and can therefore have (% style="color:#e74c3c" %)Constraints(%%) specified. Note that the actual (% style="color:#e74c3c" %)Constraint(%%) as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the (% style="color:#e74c3c" %)Constraint(%%) applies.
++The class diagram above shows that Data Provider, Metadata Provider, Dataflow, Metadataflow, Provision Agreement, Metadata Provision Agreement, Data Structure Definition, Metadata Structure Definition, Simple Datasource and REST Datasource (via the abstract Query Datasource) are all concrete sub-classes of Constrainable Artefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
--The content of the (% style="color:#e74c3c" %)Constraint(%%) can be found in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] document.
++The content of the Constraint can be found in the SDMX Information Model document.
  == {{id name="_Toc93873"/}}7.4 Data and Metadata Registration ==
  === {{id name="_Toc93874"/}}7.4.1 Basic Concepts ===
--A [[Data Provider>>doc:Glossary.Data provider.WebHome]] has published a new [[dataset>>doc:Glossary.Data set.WebHome]] conforming to an existing [[Dataflow>>doc:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]). 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>>doc:Glossary.Statistical data and metadata exchange.WebHome]] RESTful query with an [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] data stream.
++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.
--The [[Data Provider>>doc:Glossary.Data provider.WebHome]] wishes to make this new data available to one or more data collectors in a “pull” scenario, or to make the data available to [[data consumers>>doc:Glossary.Data consumer.WebHome]]. To do this, the [[Data Provider>>doc:Glossary.Data provider.WebHome]] registers the new [[dataset>>doc:Glossary.Data set.WebHome]] with one or more [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant registries that have been configured with structural and provisioning metadata. In other words, the registry “knows” the [[Data Provider>>doc:Glossary.Data provider.WebHome]] and “knows” what [[data flows>>doc:Glossary.Dataflow.WebHome]] the [[data provider>>doc:Glossary.Data provider.WebHome]] has agreed to make available.
++The Data Provider wishes to make this new data available to one or more data collectors in a “pull” scenario, or to make the data available to data consumers. To do this, the Data Provider registers the new dataset with one or more SDMX conformant registries that have been configured with structural and provisioning metadata. In other words, the registry “knows” the Data Provider and “knows” what data flows the data provider has agreed to make available.
--The same mechanism can be used to report or make available a [[metadata set>>doc:Glossary.Metadata set.WebHome]].
++The same mechanism can be used to report or make available a metadata set.
--[[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:Glossary.Data set.WebHome]] and [[metadata set>>doc:Glossary.Metadata set.WebHome]] registration via the Registration Request, which can be created by the Data/Metadata Provider (giving the [[Data Provider>>doc:Glossary.Data provider.WebHome]] 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.
++SDMX-RR supports dataset and metadata set registration via the Registration Request, which can be created by the Data/Metadata 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.
  === {{id name="_Toc93875"/}}7.4.2 The Registration Request ===
@@ -916,7 +916,7 @@
  ==== 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>>doc:Glossary.Data set.WebHome]] or [[metadata set>>doc:Glossary.Metadata set.WebHome]] to be registered. The Registration can optionally have information, which has been extracted from the Registration:
++The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per dataset or metadata set to be registered. The Registration can optionally have information, which has been extracted from the Registration:
  * validFrom
  * validTo
@@ -924,7 +924,7 @@
  The last updated date is useful during the discovery process to make sure the client knows which data is freshest.
--The Registration has an action [[attribute>>doc:Glossary.Attribute.WebHome]] which takes one of the following values:
++The Registration has an action attribute which takes one of the following values:
  (((
  (% style="width:761.294px" %)
@@ -940,35 +940,35 @@
  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
--The //QueryDatasource// is an abstract class that represents a [[data source>>doc:Glossary.Data source.WebHome]], which can understand an API query (i.e., a RESTful query – RESTDatasource) and respond appropriately. Each [[data source>>doc:Glossary.Data source.WebHome]] inherits the dataURL from //Datasource//, and the //QueryDatasource// has an additional URL to locate the specification of the service (specURL) to describe how to access it. All other supported protocols are assumed to use the SimpleDatasource URL.
++The //QueryDatasource// is an abstract class that represents a data source, which can understand an API query (i.e., a RESTful query – RESTDatasource) and respond appropriately. Each data source inherits the dataURL from //Datasource//, and the //QueryDatasource// has an additional URL to locate the specification of the service (specURL) to describe how to access it. All other supported protocols are assumed to use the SimpleDatasource URL.
--A SimpleDatasource is used to reference a physical [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] file that is available at a URL.
++A SimpleDatasource is used to reference a physical SDMX-ML file that is available at a URL.
--The RegistrationRequest has an action [[attribute>>doc:Glossary.Attribute.WebHome]] which defines whether this is a new (append) or updated (replace) Registration, or that the Registration is to be deleted (delete). The id is only provided for the replace and delete actions, as the Registry will allocate the unique id of the (new) Registration.
++The RegistrationRequest has an action attribute which defines whether this is a new (append) or updated (replace) Registration, or that the Registration is to be deleted (delete). The id is only provided for the replace and delete actions, as the Registry will allocate the unique id of the (new) Registration.
--The Registration includes [[attributes>>doc:Glossary.Attribute.WebHome]] that state how a SimpleDatasource is to be indexed when registered. The Registry registration process must act as follows:
++The Registration includes attributes that state how a SimpleDatasource is to be indexed when registered. The Registry registration process must act as follows:
--Information in the data or [[metadata set>>doc:Glossary.Metadata set.WebHome]] is extracted and placed in one or more (% style="color:#e74c3c" %)//Constraint//(%%)s (see the (% style="color:#e74c3c" %)//Constraint//(%%) model in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] – Section 2 of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards). The information to be extracted is indicated by the Boolean values set on the ProvisionAgreement or MetadataProvisionAgreement as shown in the table below.
++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>>doc:Glossary.Series key.WebHome]] and create a KeySet(s) (% style="color:#e74c3c" %)Constraint(%%).
--|indexDataSet|(% style="width:504px" %)Extract all the [[codes>>doc:Glossary.Code.WebHome]] and other content of the Key value of the [[Series Key>>doc:Glossary.Series key.WebHome]] in a [[Data Set>>doc:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of [[Dimension>>doc:Glossary.Dimension.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]], and the associated Selection Value.
++|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" %)(((
--This applies only to a registered __[[dataset>>doc:Glossary.Data set.WebHome]]__.
--Extract the Reporting Begin and Reporting End from the Header of the Message containing the [[data set>>doc:Glossary.Data set.WebHome]], and create a [[Reference Period>>doc:Glossary.Reference period.WebHome]] (% style="color:#e74c3c" %)constraint(%%).
++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" %)(((
--**[[Data Set>>doc:Glossary.Data set.WebHome]]**
--Extract the content of the [[Attribute>>doc:Glossary.Attribute.WebHome]] Values in a [[Data Set>>doc:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of Data [[Attribute>>doc:Glossary.Attribute.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the SDMXIM, and the associated Selection Value
--**[[Metadata Set>>doc:Glossary.Metadata set.WebHome]]**
--Indicate the presence of a Reported [[Attribute>>doc:Glossary.Attribute.WebHome]] by creating one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value.
++**Data Set**
++Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
++**Metadata Set**
++Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value.
  )))
  )))
--(% style="color:#e74c3c" %)Constraints(%%) that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
++Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
  The Registration must reference the ProvisionAgreement or MetadataProvisionAgreement to which it relates.
@@ -976,9 +976,9 @@
  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”.
--If the registration has succeeded, a Registration will be returned – this holds the Registry-allocated Id of the newly registered //Datasource// plus a //Datasource// holding the URL to access the [[dataset>>doc:Glossary.Data set.WebHome]], metadataset, or query service.
++If the registration has succeeded, a Registration will be returned – this holds the Registry-allocated Id of the newly registered //Datasource// plus a //Datasource// holding the URL to access the dataset, metadataset, or query service.
--The RegistrationResponse returns set of registration status (one for each registration submitted) in terms of a StatusMessage (this is common to all Registry responses) that indicates success or failure. In the event of registration failure, a set of MessageText are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of [[datasets>>doc:Glossary.Data set.WebHome]], that the response will contain some successful and some failed statuses. The logical model for the RegistrationResponse is shown below:
++The RegistrationResponse returns set of registration status (one for each registration submitted) in terms of a StatusMessage (this is common to all Registry responses) that indicates success or failure. In the event of registration failure, a set of MessageText are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the RegistrationResponse is shown below:
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_6c58dd9b.jpg||height="371" width="579"]]
@@ -1000,86 +1000,94 @@
  === {{id name="_Toc93879"/}}7.5.2 Subscription Information ===
--Regardless of the type of registry/repository events being observed, a [[subscription>>doc:Glossary.Subscription.WebHome]] always contains:
++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>>doc:Glossary.Notification.WebHome]] must be sent if the [[subscription>>doc:Glossary.Subscription.WebHome]] is activated. The URIs can be either mailto~: or http: protocol. In the former case an email [[notification>>doc:Glossary.Notification.WebHome]] is sent; in the latter an HTTP POST [[notification>>doc:Glossary.Notification.WebHome]] is sent.
--1. A user-defined identifier, which is returned in the response to the [[subscription>>doc:Glossary.Subscription.WebHome]] request. This helps with asynchronous processing and is NOT stored in the Registry.
--1. A validity period which defines both when the [[subscription>>doc:Glossary.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:Glossary.Notification.WebHome]] on expiration of the [[subscription>>doc:Glossary.Subscription.WebHome]].
++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 user-defined identifier, which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
++1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
 . 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>>doc:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository.
--|(% style="width:320px" %)DATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published [[dataset>>doc:Glossary.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 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>>doc:Glossary.Reference metadata.WebHome]] file or an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant database.
++|(% 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
  )))
  === {{id name="_Toc93880"/}}7.5.3 Wildcard Facility ===
--[[Subscription>>doc:Glossary.Subscription.WebHome]] [[notification>>doc:Glossary.Notification.WebHome]] supports wildcarded identifier [[components>>doc:Glossary.Component.WebHome]] URNs, which are identifiers which have some or all of their [[component>>doc:Glossary.Component.WebHome]] parts replaced by the wildcard character `*`. Identifier [[components>>doc:Glossary.Component.WebHome]] comprise:
++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:
  * agencyID
  * id
  * version
--Examples of wildcarded identifier [[components>>doc:Glossary.Component.WebHome]] for an identified object type of Codelist are shown below:
++Examples of wildcarded identifier components for an identified object type of Codelist are shown below:
  AgencyID = *
++
  Id = *
++
  Version = *
--This subscribes to all Codelists of all (% style="color:#e74c3c" %)versions(%%) for all agencies.
++This subscribes to all Codelists of all versions for all agencies.
  AgencyID = AGENCY1
++
  Id = CODELIST1
++
  Version = *
--This subscribes to all (% style="color:#e74c3c" %)versions(%%) of Codelist CODELIST1 maintained by the agency AGENCY1.
++This subscribes to all versions of Codelist CODELIST1 maintained by the agency AGENCY1.
  AgencyID = AGENCY1
++
  Id = *
++
  Version = *
--This subscribes to all (% style="color:#e74c3c" %)versions(%%) of all Codelist objects maintained by the agency AGENCY1.
++This subscribes to all versions of all Codelist objects maintained by the agency AGENCY1.
  AgencyID = *
++
  Id = CODELIST1
++
  Version = *
--This subscribes to all (% style="color:#e74c3c" %)versions(%%) of Codelist CODELIST1 maintained by any agency.
++This subscribes to all versions of Codelist CODELIST1 maintained by any agency.
--Note that if the [[subscription>>doc:Glossary.Subscription.WebHome]] is to the latest stable (% style="color:#e74c3c" %)version(%%) then this can be achieved by the + character, i.e.:
++Note that if the subscription is to the latest stable version then this can be achieved by the + character, i.e.:
  Version = +
--A [[subscription>>doc:Glossary.Subscription.WebHome]] to the latest (% style="color:#e74c3c" %)version(%%) (whether stable, draft or non-versioned) can be achieved by the character, i.e.:
++A subscription to the latest version (whether stable, draft or non-versioned) can be achieved by the ~~ character, i.e.:
  Version = ~~
--A [[subscription>>doc:Glossary.Subscription.WebHome]] to the latest stable (% style="color:#e74c3c" %)version(%%) within major (% style="color:#e74c3c" %)version(%%) 2 starting with (% style="color:#e74c3c" %)version(%%) 2.3.1 can be achieved by adding the + character after the minor (% style="color:#e74c3c" %)version(%%) number, i.e.:
++A subscription to the latest stable version within major version 2 starting with version 2.3.1 can be achieved by adding the + character after the minor version number, i.e.:
  Version = 2.3+.1
--The complete [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning syntax can be found in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
++The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
  === {{id name="_Toc93881"/}}7.5.4 Structural Repository Events ===
--Whenever a [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] ([[data structure definition>>doc:Glossary.Data structure definition.WebHome]], [[concept scheme>>doc:Glossary.Concept scheme.WebHome]], codelist, [[metadata structure definition>>doc:Glossary.Metadata structure definition.WebHome]], [[category scheme>>doc:Glossary.Category scheme.WebHome]], etc.) is added to, deleted from, or modified in the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository, a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] event is triggered. [[Subscriptions>>doc:Glossary.Subscription.WebHome]] may be set up to monitor all such events, or focus on specific [[artefacts>>doc:Glossary.Artefact.WebHome]] such as a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
++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.
  === {{id name="_Toc93882"/}}7.5.5 Registration Events ===
--Whenever a [[dataset>>doc:Glossary.Data set.WebHome]] or metadata-set is registered a registration event is created. A [[subscription>>doc:Glossary.Subscription.WebHome]] may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
++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>>doc:Glossary.Data set.WebHome]] or [[metadata sets>>doc:Glossary.Metadata set.WebHome]] registered by the specified data or metadata provider will activate the notification.
--|(% style="width:382px" %)ProvisionAgreement & MetadataProvisionAgreement|(% style="width:740px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] or [[metadata sets>>doc:Glossary.Metadata set.WebHome]] registered for the agreement will activate the notification.
--|(% style="width:382px" %)[[Dataflow>>doc:Glossary.Dataflow.WebHome]] & [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]|(% style="width:740px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] or [[metadata sets>>doc:Glossary.Metadata set.WebHome]] registered for the specified [[dataflow>>doc:Glossary.Dataflow.WebHome]] (or [[metadataflow>>doc:Glossary.Metadataflow.WebHome]]) will activate the notification.
--|(% style="width:382px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:740px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] or [[metadata sets>>doc:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:Glossary.Dataflow.WebHome]] (or [[metadataflows>>doc:Glossary.Metadataflow.WebHome]]) that are based on the specified [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] will activate the notification
--|(% style="width:382px" %)[[Category>>doc:Glossary.Category.WebHome]]|(% style="width:740px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] or [[metadata sets>>doc:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:Glossary.Dataflow.WebHome]], [[metadataflows>>doc:Glossary.Metadataflow.WebHome]], [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] that are categorised by the [[category>>doc:Glossary.Category.WebHome]].
++|(% 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.
  )))
  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
@@ -1092,24 +1092,24 @@
  **Figure 20: Logical Class Diagram of the Notification**
--A [[notification>>doc:Glossary.Notification.WebHome]] is an XML document that is sent to a user via email or http POST whenever a [[subscription>>doc:Glossary.Subscription.WebHome]] is activated. It is an asynchronous one-way message.
++A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
--Regardless of the registry [[component>>doc:Glossary.Component.WebHome]] that caused the event to be triggered, the following common information is in the message:
++Regardless of the registry component that caused the event to be triggered, the following common information is in the message:
  * Date and time that the event occurred
--* The URN of the [[artefact>>doc:Glossary.Artefact.WebHome]] that caused the event
--* The URN of the [[Subscription>>doc:Glossary.Subscription.WebHome]] that produced the [[notification>>doc:Glossary.Notification.WebHome]]
++* The URN of the artefact that caused the event
++* The URN of the Subscription that produced the notification
  * Event Action: Add, Replace, or Delete.
--Additionally, supplementary information may be contained in the [[notification>>doc:Glossary.Notification.WebHome]] as detailed below.
++Additionally, supplementary information may be contained in the notification as detailed below.
  === {{id name="_Toc93885"/}}7.6.2 Structural Event Component ===
--The [[notification>>doc:Glossary.Notification.WebHome]] will contain the MaintainableArtefact that triggered the event in a form similar to the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] structural message (using elements from that namespace).
++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).
  === {{id name="_Toc93886"/}}7.6.3 Registration Event Component ===
--The [[notification>>doc:Glossary.Notification.WebHome]] will contain the Registration.
++The notification will contain the Registration.
  ----