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

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

From 1.1 to 1.2 From 15.1 to 16.1

From version 1.2

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

Change comment: There is no comment for this version

To version 15.1

edited by Helena
on 2025/07/14 11:34

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 11 added, 0 removed)
Objects (0 modified, 1 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]
- SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

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

Content

@@ -4,10 +4,11 @@
  **Revision History**
--|**Revision**|**Date**|**Contents**
--| |April 2011|Initial release
--|1.0|July 2011|Rectification of problems of the specifications dated April 2011
--|2.0|July 2020|Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
++(% style="width:833.294px" %)
++|(% style="width:122px" %)**Revision**|(% style="width:126px" %)**Date**|(% style="width:581px" %)**Contents**
++|(% style="width:122px" %) |(% style="width:126px" %)April 2011|(% style="width:581px" %)Initial release
++|(% style="width:122px" %)1.0|(% style="width:126px" %)July 2011|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011
++|(% style="width:122px" %)2.0|(% style="width:126px" %)July 2020|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
  **Corrigendum**
@@ -15,19 +15,19 @@
 . **Problem**
--Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Provision Agreement as it was identified in version 2.0, and not as it is identified in version 2.1.
++Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] as it was identified in [[version>>doc:sdmx:Glossary.Version.WebHome]] 2.0, and not as it is identified in [[version>>doc:sdmx:Glossary.Version.WebHome]] 2.1.
  **Rectification**
--Provision Agreement is a Maintainable Artefact at version 2.1 and so the relationship is shown directly to the Provision Agreement class and not indirectly to the Provision Agreement via a ProvisionAgreementRef class.
++[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] is a [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] at [[version>>doc:sdmx:Glossary.Version.WebHome]] 2.1 and so the relationship is shown directly to the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] class and not indirectly to the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] via a ProvisionAgreementRef class.
  **~1. Problem**
--Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Registration class without the indexAttributes attribute.
++Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Registration class without the indexAttributes [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
  **Rectification**
--The attribute indexAttribute attribute is added to the Registration class and a description is of its purpose is given in the table at line 916.
++The [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] indexAttribute [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is added to the Registration class and a description is of its purpose is given in the table at line 916.
  **2. Problem**
@@ -35,77 +35,77 @@
  The reference to AGENCY_SCHEME is changed to AGENCIES.
--**Adoption of the Validation and Transformation Language in 2020**
++**Adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] in 2020**
--The SDMX specifications dated July 2011 envisaged the adoption of a language aimed at defining algorithms for the derivation of the data and presented a basic framework requiring however further elaboration for its actual use.
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specifications dated July 2011 envisaged the adoption of a language aimed at defining algorithms for the derivation of the data and presented a basic framework requiring however further elaboration for its actual use.
--Following the adoption of the Validation and Transformation Language (VTL) version 2.0 and its application to SDMX 2.1, this section of the SDMX specifications has been integrated by introducing the VTL package, maintainable artefacts, nameable artefacts to the sections 5.2.3, 6.2.2, 6.2.3, 6.2.4 and 7.1.1.
++Following the adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]) [[version>>doc:sdmx:Glossary.Version.WebHome]] 2.0 and its application to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1, this section of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specifications has been integrated by introducing the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] package, [[maintainable artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]], [[nameable artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]] to the sections 5.2.3, 6.2.2, 6.2.3, 6.2.4 and 7.1.1.
  = 1 Introduction =
--The business vision for SDMX envisages the promotion of a “data sharing” model to facilitate low-cost, high-quality statistical data and metadata exchange. Data sharing reduces the reporting burden of organisations by allowing them to publish data once, and let their counterparties “pull” data and related metadata as required. The scenario is based on:
++The business vision for [[SDMX>>doc:sdmx: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:sdmx: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 availability of an abstract information model capable of supporting timeseries and cross-sectional data, structural metadata, and reference metadata (SDMX-IM)
--* standardised XML schemas derived from the model (SDMX-ML)
++* the availability of an abstract information model capable of supporting timeseries and cross-sectional data, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-IM)
++* standardised XML schemas derived from the model ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-ML)
  * the use of web-services technology (XML, XSD, WSDL, WADL)
--Such an architecture needs to be well organised, and the SDMX Registry/Repository (SDMX-RR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the SDMX components required to support the datasharing vision.
++Such an architecture needs to be well organised, and the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repository ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:sdmx:Glossary.Component.WebHome]] required to support the datasharing vision.
--However, it is important to emphasis 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.
++However, it is important to emphasis that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR provides support for the submission and retrieval of all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx: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.
--Standard formats for the exchange of aggregated statistical data and metadata as prescribed in SDMX v2.1 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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] v2.1 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 enabled systems, many XML (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 and metadata structure definitions, XSLT style-sheets 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.
++As organisations migrate to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML (and conventional) [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] will be produced (e.g. Data Structure, Metadata Structure, [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] and [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] definitions (often collectively called [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]), XML schemas generated from data and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], XSLT style-sheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] between parties in a controlled and organized way.
  This is the role of the registry.
--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.
++With the fundamental [[SDMX>>doc:sdmx: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:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], with an emphasis on maintenance, retrieval and sharing of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. 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 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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to achieve their mission. The architectural standards address registry services which initially comprise:
--* structural metadata repository
++* [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository
  * data and metadata registration
  * query
--The registry services outlined in this specification are designed to help the SDMX community manage the proliferation of SDMX assets and to support data sharing for reporting and dissemination.
++The registry services outlined in this specification are designed to help the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] assets and to support data sharing for reporting and dissemination.
  = 2 Scope and Normative Status =
--The scope of this document is to specify the logical interfaces for the SDMX registry in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry.
++The scope of this document is to specify the logical interfaces for the [[SDMX registry>>doc:sdmx: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.
  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 (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 diagram are clearly marked as “Logical Class Diagram ...”)
++* with UML diagrams excerpted from the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]])
++* with UML diagrams that are not a part of the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] but are included here for clarity and to aid implementations (these diagram 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 sections 5 and 6 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 (Part 03 of the SDMX Standard). All other sections of this document are informative.
++Note that sections 5 and 6 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:sdmx:Glossary.Notification.WebHome]] mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] specification (Part 03 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standard). All other sections of this document are informative.
--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.
++Note that although the term “authorised user” is used in this document, the [[SDMX>>doc:sdmx: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.
  = 3 Scope of the SDMX Registry/Repository =
  == 3.1 Objective ==
--The objective of the SDMX registry/repository is, in broad terms, to allow organisations to publish statistical data and reference metadata in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold:
++The objective of the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc:sdmx: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:
--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.
++1. To maintain and publish [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that describes the structure and valid content of data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources such as databases, [[metadata repositories>>doc:sdmx:Glossary.Metadata repository.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. This [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] enables software applications to understand and to interpret the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] in these sources.
++1. To enable applications, organisations, and individuals to share and to discover data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. This facilitates data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] dissemination by implementing the data sharing vision of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
  == 3.2 Structural Metadata ==
--Setting up structural metadata and the exchange context (referred to as “data provisioning”) involves the following steps for maintenance agencies:
++Setting up [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and the exchange context (referred to as “data provisioning”) involves the following steps for [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]]:
--* 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 attributes and presentational arrangement of a Metadataset and their valid values and content
--* if required, defining a subset or view of a MSD which allows some restriction of content called a “metadataflow definition”
--* defining which subject matter domains (specified as a Category Scheme) are related to the Dataflow and Metadataflow Definitions to enable browsing
--* defining one or more lists of Data Providers (which includes metadata providers)
--* defining which Data Providers have agreed to publish a given Dataflow and/or Metadataflow Definition - this is called a Provision Agreement
++* agreeing and creating a specification of the structure of the data (called a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] in this document but also known as “key family”) which defines the [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], [[measures>>doc:sdmx:Glossary.Measure.WebHome]] and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] of a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] and their valid value set
++* if required, defining a subset or view of a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] which allows some restriction of content called a “[[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition”
++* agreeing and creating a specification of the structure of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] ([[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]) which defines the [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] and presentational arrangement of a Metadataset and their valid values and content
++* if required, defining a subset or view of a [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] definition”
++* defining which subject matter domains (specified as a [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]) are related to the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definitions to enable browsing
++* defining one or more lists of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] (which includes metadata providers)
++* defining which [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] have agreed to publish a given [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and/or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition - this is called a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
  [[image:1747824122996-812.jpeg]]
@@ -113,10 +113,10 @@
  == 3.3 Registration ==
--Publishing the data and reference metadata involves the following steps for a Data Provider:
++Publishing the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] involves the following steps for a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]:
--* making the reference metadata and data available in SDMX-ML conformant data files or databases (which respond to an SDMX-ML query with SDMX-ML data). The data and reference metadata files or databases must be webaccessible, and must conform to an agreed Dataflow or Metadataflow Definition (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
++* making the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] conformant data files or databases (which respond to an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] query with [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data). The data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] files or databases must be webaccessible, and must conform to an agreed [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] subset)
++* registering the existence of published [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX registries>>doc:sdmx:Glossary.SDMX Registry.WebHome]]
  [[image:1747824123003-199.jpeg]]
@@ -124,17 +124,17 @@
  == 3.4 Notification ==
--Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
++Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] involves:
--* registry support of a subscription-based notification service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the subscription request
++* registry support of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]-based [[notification>>doc:sdmx: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:sdmx:Glossary.Subscription.WebHome]] request
  == 3.5 Discovery ==
--Discovering published data and reference metadata involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an SDMX-enabled data or reference metadata resource:
++Discovering published data and [[reference metadata>>doc:sdmx: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:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] resource:
--* optionally browsing a subject matter domain category scheme to find Dataflow Definitions (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
++* optionally browsing a subject matter domain [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] to find [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definitions (and hence [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]) and [[Metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]] which structure the type of data and/or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] being sought
++* build a query, in terms of the selected [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], which specifies what data are required and submitting this to a service that can query an [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] which will return a list of (URLs of) data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] files and databases which satisfy the query
++* processing the query result set and retrieving data and/or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] from the supplied URLs
  [[image:1747824123006-476.jpeg]]
@@ -144,7 +144,7 @@
  == 4.1 Architectural Schematic ==
--The architecture of the SDMX registry/repository is derived from the objectives stated above. It is a layered architecture that is founded by a structural metadata repository which supports a provisioning metadata repository which supports the registry services. These are all supported by the SDMX-ML schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the structural metadata required to drive these applications.
++The architecture of the [[SDMX registry>>doc:sdmx: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:sdmx:Glossary.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc:sdmx: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:sdmx:Glossary.Structural metadata.WebHome]] required to drive these applications.
  [[image:1747824123008-995.jpeg]]
@@ -152,18 +152,18 @@
  == 4.2 Structural Metadata Repository ==
--The basic layer is that of a structural metadata service which supports the lifecycle of SDMX structural metadata artefacts such as Maintenance Agencies, Data Structure Definitions, Metadata Structure Definitions, Provision Agreements, Processes etc. This layer is supported by the Structure Submission and Query Service.
++The basic layer is that of a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], Processes etc. This layer is supported by the Structure Submission and Query Service.
--Note that the SDMX-ML Submit Structure Request message supports all of the SDMX structural artefacts. The only structural artefacts that are not supported by the SDMX-ML Submit Structure Request are::
++Note that the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Submit Structure Request message supports all of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. The only structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that are not supported by the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Submit Structure Request are::
  * Registration of data and metadata sources
  * Subscription and Notification
--Separate registry-based messages are defined to support these artefacts.
++Separate registry-based messages are defined to support these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].
  == 4.3 Provisioning Metadata Repository ==
--The function of this repository is to support the definition of the structural metadata that describes the various types of data-store which model SDMX-conformant databases or files, and to link to these data sources. These links can be specified for a data provider, for a specific data or metadata flow. In the SDMX model this is called the Provision Agreement.
++The function of this repository is to support the definition of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:sdmx:Glossary.Data source.WebHome]]. These links can be specified for a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]], for a specific data or [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]]. In the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model this is called the Provision Agreement.
  This layer is supported by the Data and Metadata Registration Service.
@@ -174,27 +174,27 @@
  The Registry Interfaces are:
  * Notify Registry Event
--* Submit Subscription Request
--* Submit Subscription Response
++* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request
++* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response
  * Submit Registration Request
  * Submit Registration Response
  * Query Registration Request
  * Query Registration Response
--* Query Subscription Request
--* Query Subscription Response
++* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request
++* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response
  * Submit Structure Request
  * Submit Structure 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 document
--1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
++1. The interface is the name of the root node of the [[SDMX-ML>>doc:sdmx: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:sdmx:Glossary.SDMX-ML.WebHome]] document.
--In addition to these interfaces the registry must support a mechanism for querying for structural metadata. This is detailed in 5.2.2.
++In addition to these interfaces the registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This is detailed in 5.2.2.
--All these interactions with the Registry – with the exception of Notify Registry Event – 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.
++All these interactions with the Registry – with the exception of Notify Registry Event – are designed in pairs. The first document – the one which invokes the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-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-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the request-response 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>>doc:sdmx: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 request-response pattern, because it is inherently asynchronous.
  == 5.2 Registry Services ==
@@ -204,45 +204,45 @@
  === 5.2.2 Structure Submission and Query Service ===
--This service must implement the following SDMX-ML Interfaces:
++This service must implement the following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Interfaces:
  * SubmitStructureRequest
  * SubmitStructureResponse
--These interfaces allow structural definitions to be created, modified, and removed in a controlled fashion. It also allows the structural metadata artefacts to be queried and retrieved either in part or as a whole. 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 (see next section on the SDMX Information Model).
++These interfaces allow structural definitions to be created, modified, and removed in a controlled fashion. It also allows the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] to be queried and retrieved either in part or as a whole. In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact (see next section on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Information Model).
  === 5.2.3 Structure Query Service ===
--The registry must support a mechanism for querying for structural metadata. This mechanism can be one or both of the SDMX-ML Query message and the SDMX REST interface for structural metadata (this is defined in Part 7 of the SDMX standards). The registry response to both of these query mechanisms is the SDMX Structure message which has as its root node
++The registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This mechanism can be one or both of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message and the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] (this is defined in Part 7 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards). The registry response to both of these query mechanisms is the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Structure message which has as its root node
  * Structure
--The SDMX structural artefacts that may be queried are:
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that may be queried are:
--* dataflows and metadataflows
--* data structure definitions and metadata structure definitions
++* [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and metadataflows
++* [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
  * codelists
--* concept schemes
++* [[concept>>doc:sdmx:Glossary.Concept.WebHome]] schemes
  * reporting taxonomies
--* provision agreements
++* [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]
  * structure sets
  * processes
  * hierarchical code lists
--* constraints
++* [[constraints>>doc:sdmx:Glossary.Constraint.WebHome]]
  * category schemes
--* categorisations and categorised objects (examples are categorised dataflows and metadatflows, 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)
++* categorisations and categorised objects (examples are categorised [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and metadatflows, [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] registered [[data sources>>doc:sdmx:Glossary.Data source.WebHome]] and metadata sources)
++* organisation schemes ([[agency scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]], [[data provider scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]], [[data consumer scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]], organisation unit scheme)
--Due to the VTL implementation the other structural artefact that may be queried are:
++Due to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] implementation the other structural [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that may be queried are:
  * transformation schemes
  * custom type schemes
  * name personalisation schemes
--* vtl mapping schemes
++* [[vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes
  * ruleset schemes
  * user defined operator schemes
--The SDMX query messages that are a part of the SDMX-ML Query message are:
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] query messages that are a part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message are:
  * StructuresQuery
  * DataflowQuery
@@ -261,7 +261,7 @@
  * ProvisionAgreementQuery
  * ConstraintQuery
--Due to the VTL implementation the other query messages that became a part of the SDMX-ML Query message are:
++Due to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] implementation the other query messages that became a part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message are:
  * TransformationSchemeQuery
  * CustomTypeSchemeQuery
@@ -272,7 +272,7 @@
  === 5.2.4 Data and Reference Metadata Registration Service ===
--This service must implement the following SDMX-ML Interfaces:
++This service must implement the following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Interfaces:
  * SubmitRegistrationRequest
  * SubmitRegistrationResponse
@@ -279,78 +279,69 @@
  * QueryRegistrationRequest
  * QueryRegistrationResponse
--The Data and Metadata Registration Service allows SDMX conformant XML files and web-accessible databases containing published data and reference metadata to be registered in the SDMX Registry. The registration process MAY validate the content of the data-sets or metadata-sets, 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 data-set or metadata-set. These are called Constraints in the SDMX-IM.
++The Data and Metadata Registration Service allows [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant XML files and web-accessible databases containing published data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the data-sets or metadata-sets, and MAY extract a concise [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the contents in terms of [[concept>>doc:sdmx:Glossary.Concept.WebHome]] values (e.g. values of the data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]], [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original data-set or metadata-set. These are called [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-IM.
  The Data and Metadata Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry:
--* that the data provider is allowed to register the data-set or metadata-set
--* that the content of the data set or metadata set 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, Data Structure Definition, Metadata Structure Definition, 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, Identifier Components etc.) are consistent with the Data Structure Definition or   Metadata Structure Definition
--*  that the valid representations of the concepts to which these components 382 correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
++* that the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] is allowed to register the data-set or metadata-set
++* that the content of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] meets the validation [[constraints>>doc:sdmx:Glossary.Constraint.WebHome]]. This is dependent upon such [[constraints>>doc:sdmx:Glossary.Constraint.WebHome]] being defined in the structural repository and which reference the relevant [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], Provision Agreement
++* that a queryable [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists - this would necessitate the registration service querying the service to determine its existence
++* that a simple [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists (i.e. a file accessible at a URL)
++* that the correct [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] is used by the registered data that the [[components>>doc:sdmx:Glossary.Component.WebHome]] ([[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]], [[Measures>>doc:sdmx:Glossary.Measure.WebHome]], Identifier [[Components>>doc:sdmx:Glossary.Component.WebHome]] etc.) are consistent with the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or   [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
++* that the valid [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] to which these [[components>>doc:sdmx:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
--3The Registration has an action attribute which takes one of the following values:
++The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
--|(((
--**Action**
++|(% style="width:219px" %)**Action [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Value**|(% style="width:1652px" %)**Behaviour**
++|(% style="width:219px" %)Append|(% style="width:1652px" %)Add this registration to the registry
++|(% style="width:219px" %)Replace|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
++|(% style="width:219px" %)Delete|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
--**Attribute Value**
--)))|**Behaviour**
--|Append|Add this registration to the registry
--|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
--|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++The Registration has three Boolean [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] which may be present to determine how an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] or [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] indexing application must index the [[Datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] 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 Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows:
++|(% style="width:228px" %)**Boolean [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]**|(% style="width:1644px" %)**Behaviour if Value is “true”**
++|(% style="width:228px" %)indexTimeSeries|(% style="width:1644px" %)A compliant indexing application must index all the time [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] (for a [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] registration) or metadata target values (for a [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] registration)
++|(% style="width:228px" %)indexDataSet|(% style="width:1644px" %)A compliant indexing application must index the range of actual (present) values for each [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] of the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] (for a [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] registration) or the range of actual (present) values for each Metadata [[Attribute>>doc:sdmx: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:sdmx:Glossary.Dimension.WebHome]] values (the Key) is actually present in the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]]
++|(% style="width:228px" %)indexReportingPeriod|(% style="width:1644px" %)A compliant indexing application must index the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] or [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]
--|**Boolean Attribute**|**Behaviour if Value is “true”**
--|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
--|indexDataSet|(((
--A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
--
--Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
--)))
--|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
--
  === 5.2.5 Data and Reference Metadata Discovery ===
  The Data and Metadata Discovery Service implements the following Registry Interfaces:
--         QueryRegistrationRequest
++* QueryRegistrationRequest
++* QueryRegistrationResponse
--         QueryRegistrationResponse
--
  === 5.2.6 Subscription and Notification ===
--The Subscription and Notification Service implements the following Registry Interfaces:
++The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] 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’ 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.
++The data sharing paradigm relies upon the consumers of data and metadata being able to pull information from [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]]’ dissemination systems. For this to work efficiently, a [[data consumer>>doc:sdmx: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:sdmx:Glossary.Data set.WebHome]] has been updated and re-registered). Additionally, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] systems may also want to know if a new [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] has been added. The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] Service comprises two parts: [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management, and [[notification>>doc:sdmx:Glossary.Notification.WebHome]].
--Subscription management involves a user submitting a subscription request which contains:
++[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request which contains:
--* a query or constraint expression in terms of a filter which defines the events for which the user is interested (e.g. new data for a specific dataflow, or for a domain category, or changes to a Data Structure Definition).
--* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address)
++* a query or [[constraint>>doc:sdmx: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:sdmx:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:sdmx:Glossary.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]).
++* a list of URIs or end-points to which an XML [[notification>>doc:sdmx:Glossary.Notification.WebHome]] message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
  * request for a list of submitted subscriptions
--* deletion of a subscription
++* deletion of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]
--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-ML notification document to the end-points specified in the relevant subscriptions.
++[[Notification>>doc:sdmx:Glossary.Notification.WebHome]] requires that the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request query), and to issue an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document to the end-points specified in the relevant subscriptions.
  === 5.2.7 Registry Behaviour ===
--The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
++The following table defines the behaviour of the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages.
--|**Interface**|**Behaviour**
--|All|(((
--1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final attribute is set to “true” in which case the only changes that are allowed are to the following constructs:
++|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour**
++|(% style="width:227px" %)All|(% style="width:1644px" %)(((
++1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is set to “true” in which case the only changes that are allowed are to the following constructs:
--* Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
--* Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
--
--* Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list.
++* Name – this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
++* Description - this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
++* Annotation - this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
  * validTo
  * validFrom
  * structureURL
@@ -358,43 +358,40 @@
  * uri
  * isExternalReference
--1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
--1. If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
++2) Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
++3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
--1. Not have the final attribute set to “true”
--1. Not be referenced from any other object in the Registry.
++а) Not have the final [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set to “true”
++b) Not be referenced from any other object in the Registry.
--1. The version rules in the SDMX Schema documentation MUST be obeyed.
--
--* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
++4) The [[version>>doc:sdmx:Glossary.Version.WebHome]] rules in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Schema documentation MUST be obeyed.
++5) The specific rules for the elements and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] documented in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Schema MUST be obeyed.
  )))
--|SubmitStructureRequest|Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
--|SubmitProvisioningRequest|No additional behaviour.
--|Submit Registration Request|(((
--If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration.
--
--For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
++|(% style="width:227px" %)SubmitStructureRequest|(% style="width:1644px" %)Structures are submitted at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
++|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour.
++|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)(((
++If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] set in the Registration.
++For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data query.
  )))
--
--
  = 6 Identification of SDMX Objects =
  == 6.1 Identification, Versioning, and Maintenance ==
--All major classes of the SDMX Information model inherit from one of:
++All major classes of the [[SDMX Information model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] inherit from one of:
--
  * **IdentifiableArtefact** - this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations.
  * **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description,
--* **VersionableArtefact **– this has all of the above features plus a version number and a validity period.
--* **MaintainableArtefact** – this has all of the above features, and indication as to whether the object is “final” and cannot be changed or deleted, registry and structure URIs, plus an association to the maintenance agency of the object.
++* **VersionableArtefact **– this has all of the above features plus a [[version>>doc:sdmx:Glossary.Version.WebHome]] number and a validity period.
++* **MaintainableArtefact** – this has all of the above features, and indication as to whether the object is “final” and cannot be changed or deleted, registry and structure URIs, plus an association to the [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] of the object.
  === 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
++[[image:1747824504225-229.png]]
++
  **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
--The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
++The table below shows the identification and related data [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to be stored in a registry for objects that are one of:
  * Annotable
  * Identifiable
@@ -402,60 +402,58 @@
  * Versionable
  * Maintainable
--|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
--|Annotable|AnnotationTitle|C|string|
--| |AnnotationType|C|string|
--| |AnnotationURN|C|string|
--| |(((
--AnnotationText in the form of
++(% style="width:935.294px" %)
++|**Object Type**|(% style="width:244px" %)**Data [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]**|(% style="width:99px" %)**Status**|**Data type**|(% style="width:389px" %)**Notes**
++|Annotable|(% style="width:244px" %)AnnotationTitle|(% style="width:99px" %)C|string|(% style="width:389px" %)
++| |(% style="width:244px" %)AnnotationType|(% style="width:99px" %)C|string|(% style="width:389px" %)
++| |(% style="width:244px" %)AnnotationURN|(% style="width:99px" %)C|string|(% style="width:389px" %)
++| |(% style="width:244px" %)(((
++AnnotationText in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]
++)))|(% style="width:99px" %)C| |(% style="width:389px" %)This can have languagespecific variants.
++|Identifiable|(% style="width:244px" %)all content as for Annotable plus|(% style="width:99px" %) | |(% style="width:389px" %)
++| |(% style="width:244px" %)id|(% style="width:99px" %)M|string|(% style="width:389px" %)
++| |(% style="width:244px" %)uri|(% style="width:99px" %)C|string|(% style="width:389px" %)
++| |(% style="width:244px" %)urn|(% style="width:99px" %)C|string|(% style="width:389px" %)Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
++|Nameable|(% style="width:244px" %)all content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
++| |(% style="width:244px" %)Name in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]|(% style="width:99px" %)M|string|(% style="width:389px" %)This can have languagespecific variants.
++| |(% style="width:244px" %)(((
++Description in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]
++)))|(% style="width:99px" %)C|string|(% style="width:389px" %)This can have languagespecific variants.
++|Versionable|(% style="width:244px" %)All content as for Identifiable plus|(% style="width:99px" %) | |(% style="width:389px" %)
++| |(% style="width:244px" %)[[version>>doc:sdmx:Glossary.Version.WebHome]]|(% style="width:99px" %)C|string|(% style="width:389px" %)This is the [[version>>doc:sdmx:Glossary.Version.WebHome]] number. If not present the default is 1.0
++| |(% style="width:244px" %)validFrom|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
++| |(% style="width:244px" %)validTo|(% style="width:99px" %)C|Date/time|(% style="width:389px" %)
++|Maintainable|(% style="width:244px" %)All content as for Versionable plus|(% style="width:99px" %) | |(% style="width:389px" %)
++| |(% style="width:244px" %)final|(% style="width:99px" %) |boolean|(% style="width:389px" %)Value of “true” indicates that this is a final specification and it cannot be changed except as a new [[version>>doc:sdmx:Glossary.Version.WebHome]]. Note that providing a “final’ object is not referenced from another object then it may be deleted.
++| |(% style="width:244px" %)isExternalReference|(% style="width:99px" %)C|boolean|(% style="width:389px" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURI, each of which must return a valid [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file.
++| |(% style="width:244px" %)serviceURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the service that can be queried for this resource
++| |(% style="width:244px" %)structureURL|(% style="width:99px" %)C|string|(% style="width:389px" %)The url of the resource.
++| |(% style="width:244px" %)(Maintenance) agencyId|(% style="width:99px" %)M|string|(% style="width:389px" %)The object must be linked to a [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]].
--International String
--)))|C| |This can have languagespecific variants.
--| | | | |
--|Identifiable|all content as for Annotable plus| | |
--| |id|M|string|
--| |uri|C|string|
--| |urn|C|string|Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
--|Nameable|all content as for Identifiable plus| | |
--| |Name in the form of International String|M|string|This can have languagespecific variants.
--| |(((
--Description in the form of International
++**Table 1: Common [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] of Object Types**
--String
--)))|C|string|This can have languagespecific variants.
--|Versionable|All content as for Identifiable plus| | |
--| |version|C|string|This is the version number. If not present the default is 1.0
--| |validFrom|C|Date/time|
--| |validTo|C|Date/time|
--|Maintainable|All content as for Versionable plus| | |
--| |final| |boolean|Value of “true” indicates that this is a final specification and it cannot be changed except as a new version. Note that providing a “final’ object is not referenced from another object then it may be deleted.
--| |isExternalReference|C|boolean|Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURI, each of which must return a valid SDMX-ML file.
--| |serviceURL|C|string|The url of the service that can be queried for this resource
--| |structureURL|C|string|The url of the resource.
--| |(Maintenance) agencyId|M|string|The object must be linked to a maintenance agency.
--
--**Table 1: Common Attributes of Object Types**
--
  == 6.2 Unique identification of SDMX objects ==
  === 6.2.1 Agencies ===
--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.
++The [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
--**Figure 6: Agency Scheme Model**
++[[image:1747994320263-112.png]]
--The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an n-level structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version and is never declared explicitly in the SDMX object identification mechanism.
++**Figure 6: [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] Model**
--In order to achieve this SDMX adopts the following rules:
++The Agency in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is an n-[[level>>doc:sdmx:Glossary.Level.WebHome]] structure. The top [[level>>doc:sdmx:Glossary.Level.WebHome]] of this structure is maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top [[level>>doc:sdmx:Glossary.Level.WebHome]] can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] has a fixed id and [[version>>doc:sdmx:Glossary.Version.WebHome]] and is never declared explicitly in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
--1. Agencies are maintained in an Agency Scheme (which is a sub class of Organisation Scheme)
--1. The agency of the Agency Scheme must also be declared in a (different) Agency Scheme.
--1. The “top-level” agency is SDMX and maintains the “top-level” Agency Scheme.
--1. 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.
--1. The AgencyScheme cannot be versioned and so take a default version number of 1.0 and cannot be made “final”.
++In order to achieve this [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules:
++
++1. Agencies are maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme)
++1. The agency of the [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
++1. The “top-[[level>>doc:sdmx:Glossary.Level.WebHome]]” agency is [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-[[level>>doc:sdmx:Glossary.Level.WebHome]]” [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
++1. Agencies registered in the top-[[level>>doc:sdmx:Glossary.Level.WebHome]] scheme can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] and so on.
++1. The AgencyScheme cannot be versioned and so take a default [[version>>doc:sdmx:Glossary.Version.WebHome]] number of 1.0 and cannot be made “final”.
 . There can be only one AgencyScheme maintained by any one Agency. It has a fixed Id of AGENCIES.
--1. The /hierarchy of Organisation is not inherited by Maintenance Agency – thus each Agency Scheme is a flat list of Maintenance Agencies.
--1. The format of the agency identifier is agencyID.agencyID etc. The toplevel agency in this identification mechanism is the agency registered in the SDMX agency scheme. 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.
++1. The /hierarchy of Organisation is not inherited by [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] is a flat list of Maintenance Agencies.
++1. The format of the agency identifier is agencyID.agencyID etc. The toplevel agency in this identification mechanism is the agency registered in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. In other words, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] and is contained in the top-[[level>>doc:sdmx:Glossary.Level.WebHome]] [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
  This supports a hierarchical structure of agencyID.
@@ -463,7 +463,7 @@
  [[image:1747824123012-527.jpeg]]
--==== Figure 7: Example of Hierarchic Structure of Agencies ====
++**Figure 7: Example of Hierarchic Structure of Agencies**
  The following organizations maintain an Agency Scheme.
@@ -472,46 +472,46 @@
  * BB – contains Agencies CC, DD
  * DD – Contains Agency EE
--Each agency is identified by its full hierarchy excluding SDMX.
++Each agency is identified by its full [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] excluding SDMX.
  e.g. the id of EE as an agencyID is AA.DD.EE
  An example of this is shown in the XML snippet below.
++[[image:1747832400104-286.png]]
--[[image:1747824123013-196.jpeg]]
++**Figure 8: Example Showing Use of Agency Identifiers**
--==== Figure 8: Example Showing Use of Agency Identifiers ====
++Each of these [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:sdmx: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.
--
  === 6.2.2 Universal Resource Name (URN) ===
  ==== 6.2.2.1 Introduction ====
--To provide interoperability between SDMX Registry/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) SDMX-IM objects. Most of these unique identifiers are composite (containing maintenance agency, or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification components in the SDMX-RR APIs. In other words, the URN for any Identifiable Artefact is constructed from its component identifiers (agency, Id, version etc.).
++To provide interoperability between [[SDMX Registry>>doc:sdmx: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:sdmx:Glossary.SDMX Information Model.WebHome]] objects. Most of these unique identifiers are composite (containing [[maintenance agency>>doc:sdmx: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:sdmx:Glossary.Component.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR APIs. In other words, the URN for any [[Identifiable Artefact>>doc:sdmx:Glossary.Identifiable artefact.WebHome]] is constructed from its [[component>>doc:sdmx:Glossary.Component.WebHome]] identifiers (agency, Id, [[version>>doc:sdmx:Glossary.Version.WebHome]] etc.).
  ==== 6.2.2.2 URN Structure ====
--===== //Case Rules for URN// =====
++(% class="wikigeneratedid" id="HCaseRulesforURN" %)
++//Case Rules for URN//
  For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
  The generic structure of the URN is as follows:
--SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
++>SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
  ~* this can repeat and may not be present (see explanation below)
--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.
++Note that in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:sdmx:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. For this reason the only [[version>>doc:sdmx:Glossary.Version.WebHome]] information that is allowed is for the maintainable object.
--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 [[Maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period(.).
  ==== 6.2.2.3 Explanation of the generic structure ====
  In the explanation below the actual object that is the target of the URN is called the **//actual object//**.
--**SDMXPrefix:** urn:sdmx:org.
++**SDMXPrefix:** urn:sdmx:org.
  **SDMX-IM package name:** sdmx.infomodel.package=
@@ -519,270 +519,223 @@
  **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 of the maintainable object and is enclosed in round brackets (). It will always be present.
++**(maintainable-object-version)** is the [[version>>doc:sdmx:Glossary.Version.WebHome]] of the maintainable object and is enclosed in round brackets (). It will always be present.
--**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a Code is in a maintained object (Code List) and has no intermediary container object, whereas a Metadata Attribute has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata Attribute. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower level in its hierarchy. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to Attribute Descriptor, Dimension Descriptor, and Measure Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a
++**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is in a maintained object ([[Code List>>doc:sdmx:Glossary.Code list.WebHome]]) and has no intermediary container object, whereas a Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower [[level>>doc:sdmx:Glossary.Level.WebHome]] in its [[hierarchy>>doc:sdmx: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 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor, [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor, and [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Descriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor, [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor, and [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Descriptor is not included when the actual object is a Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] or a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]/[[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]/ Time [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], or a [[Measure>>doc:sdmx:Glossary.Measure.WebHome]].
--URN, the id of the Attribute Descriptor, Dimension Descriptor, and Measure Descriptor is not included when the actual object is a Data Attribute or a Dimension/Measure Dimension/ Time Dimension, or a Measure.
++Note that although a [[Code>>doc:sdmx:Glossary.Code.WebHome]] can have a parent [[Code>>doc:sdmx:Glossary.Code.WebHome]] and a [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] can have a parent [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] these are maintained in a flat structure and therefore do not have a container-object-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 container-object-id.
++For example the sequence is agency:DSDid([[version>>doc:sdmx:Glossary.Version.WebHome]]).DimensionId and not agency:DSDid([[version>>doc:sdmx:Glossary.Version.WebHome]]).DimensionDescriptorId.DimensionId.
--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.
--===== //Generic Examples of the URN Structure// =====
++===== __**//Generic Examples of the URN Structure//**__ =====
++__Actual object is a maintainable__
--Actual object is a maintainable
++> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
--SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
++__Actual object is contained in a maintained object with no intermediate containing object__
--Actual object is contained in a maintained object with no intermediate containing object
++> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
--SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
++__Actual object is contained in a maintained object with an intermediate containing object__
--Actual object is contained in a maintained object with an intermediate containing object
++> SDMXPrefix.SDMX-IM package name.classname=agency
--SDMXPrefix.SDMX-IM package name.classname=agency
--
  id:maintained-object-id(version).contained-object-id.object-id
--Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical
++__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__
--In this case the object id may not be unique in itself but only within the context of the hierarchy. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a Category in a Category Scheme. The Category is hierarchical and all intermediate Categories are shown as a contained object. The example below shows the generic structure for Category Scheme/Category/Category
++In this case the object id may not be unique in itself but only within the context of the [[hierarchy>>doc:sdmx: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:sdmx:Glossary.Category.WebHome]] in a [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. The [[Category>>doc:sdmx:Glossary.Category.WebHome]] is hierarchical and all intermediate [[Categories>>doc:sdmx:Glossary.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]/[[Category>>doc:sdmx:Glossary.Category.WebHome]]/[[Category>>doc:sdmx:Glossary.Category.WebHome]]
--SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
++> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
--Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
++__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
--In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata Attribute where the contained objects are Report Structure (first contained object id) and Metadata Attribute (subsequent contained object Ids). The example below shows the generic structure for MSD/Report Structure/Metadata Attribute/Metadata Attribute
++In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] where the contained objects are Report Structure (first contained object id) and Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] (subsequent contained object Ids). The example below shows the generic structure for [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]/Report Structure/Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]/Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
--SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
++> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
--===== //Concrete Examples of the URN Structure// =====
++===== __**//Concrete Examples of the URN Structure//**__ =====
--The Data Structure Definition CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
++The [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
--urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
++> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
--The URN for a code for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
++The URN for a [[code>>doc:sdmx:Glossary.Code.WebHome]] for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
--urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
++> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
--The URN for a category (id of 1) which has parent category (id of 2) maintained by SDMX in the category scheme SUBJECT_MATTER_DOMAINS version 1.0 would be:
++The URN for a [[category>>doc:sdmx:Glossary.Category.WebHome]] (id of 1) which has parent [[category>>doc:sdmx:Glossary.Category.WebHome]] (id of 2) maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] in the [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] SUBJECT_MATTER_DOMAINS version 1.0 would be:
--urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
++> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
--The URN for a Metadata Attribute maintained by SDMX in the MSD CONTACT_METADATA version 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
++The URN for a Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] in the [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] CONTACT_METADATA [[version>>doc:sdmx:Glossary.Version.WebHome]] 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
  CONTACT_DETAILS/CONTACT_NAME would be:
--urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
++> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
--The TFFS defines ABC as a sub Agency of TFFS then the URN of a Dataflow maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be:
++The TFFS defines ABC as a sub Agency of TFFS then the URN of a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] maintained by ABC and identified as EXTERNAL_DEBT version 1.0 would be:
--urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
++> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
  TERNAL_DEBT(1.0)
--The SDMX-RR MUST support this globally unique identification scheme. The SDMXRR 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:
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The SDMXRR MUST be able to create the URN from the individual identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] submitted and to transform the URN to these identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. The identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are:
--* **Identifiable and Nameable Artefacts**: id (in some cases this id may be hierarchic)
--* **Maintainable Artefacts**: id, version, agencyId,
++* **Identifiable and [[Nameable Artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic)
++* **Maintainable [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]**: id, [[version>>doc:sdmx:Glossary.Version.WebHome]], agencyId,
--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.
++The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to resolve the unique identifier of an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] and to produce an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] rendering of that [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] if it is located in the Registry.
  === 6.2.3 Table of SDMX-IM Packages and Classes ===
--The table below lists all of the packages in the SDMX-IM together with the concrete classes that are in these packages and whose objects have a URN.
++The table below lists all of the packages in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] together with the concrete classes that are in these packages and whose objects have a URN.
--|**Package**|(((
--**URN Classname (model classname**
--
--**where this is different)**
++(% style="width:644.294px" %)
++|(% style="width:127px" %)**Package**|(% style="width:494px" %)(((
++**URN Classname (model classname where this is different)**
  )))
--|base|Agency
--| |OrganisationUnitScheme
--| |AgencyScheme
--| |DataProviderScheme
--| |DataConsumerScheme
--| |OrganisationUnit
--| |DataProvider
--| |DataConsumer
--| |
--|datastructure|DataStructure (DataStructureDefinition)
--| |AttributeDescriptor
--| |DataAttribute
--| |GroupDimensionDescriptor
--| |DimensionDescriptor
--| |Dimension
--| |MeasureDimension
--| |TimeDimension
--| |MeasureDescriptor
--| |PrimaryMeasure
--| |Dataflow (DataflowDefinition)
--| |
--|metadatastructure|MetadataTarget
--| |DimensionDescriptorValueTarget
--| |IdentifiableObjectTarget
--| |ReportPeriodTarget
--| |DataSetTarget
--| |ReportStructure
--| |MetadataAttribute
--| |(((
++|(% style="width:127px" %)base|(% style="width:494px" %)Agency
++|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnitScheme
++|(% style="width:127px" %) |(% style="width:494px" %)AgencyScheme
++|(% style="width:127px" %) |(% style="width:494px" %)DataProviderScheme
++|(% style="width:127px" %) |(% style="width:494px" %)DataConsumerScheme
++|(% style="width:127px" %) |(% style="width:494px" %)OrganisationUnit
++|(% style="width:127px" %) |(% style="width:494px" %)DataProvider
++|(% style="width:127px" %) |(% style="width:494px" %)DataConsumer
++|(% style="width:127px" %)datastructure|(% style="width:494px" %)DataStructure (DataStructureDefinition)
++|(% style="width:127px" %) |(% style="width:494px" %)AttributeDescriptor
++|(% style="width:127px" %) |(% style="width:494px" %)DataAttribute
++|(% style="width:127px" %) |(% style="width:494px" %)GroupDimensionDescriptor
++|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptor
++|(% style="width:127px" %) |(% style="width:494px" %)Dimension
++|(% style="width:127px" %) |(% style="width:494px" %)MeasureDimension
++|(% style="width:127px" %) |(% style="width:494px" %)TimeDimension
++|(% style="width:127px" %) |(% style="width:494px" %)MeasureDescriptor
++|(% style="width:127px" %) |(% style="width:494px" %)PrimaryMeasure
++|(% style="width:127px" %) |(% style="width:494px" %)Dataflow (DataflowDefinition)
++|(% style="width:127px" %)metadatastructure|(% style="width:494px" %)MetadataTarget
++|(% style="width:127px" %) |(% style="width:494px" %)DimensionDescriptorValueTarget
++|(% style="width:127px" %) |(% style="width:494px" %)IdentifiableObjectTarget
++|(% style="width:127px" %) |(% style="width:494px" %)ReportPeriodTarget
++|(% style="width:127px" %) |(% style="width:494px" %)DataSetTarget
++|(% style="width:127px" %) |(% style="width:494px" %)ReportStructure
++|(% style="width:127px" %) |(% style="width:494px" %)MetadataAttribute
++|(% style="width:127px" %) |(% style="width:494px" %)(((
  MetadataStructure
  (MetadataStructureDefinition)
  )))
--| |Metadataflow (MetadataflowDefinition)
--| |
--|process|Process
--| |ProcessStep
--| |Transition
--| |
--|registry|ProvisionAgreement
--| |AttachmentConstraint
--| |ContentConstraint
--| |Subscription
--| |
--|mapping|StructureMap
--| |StructureSet
--| |ComponentMap
--|**Package**|(((
--**URN Classname (model classname**
++|(% style="width:127px" %) |(% style="width:494px" %)Metadataflow (MetadataflowDefinition)
++|(% style="width:127px" %)process|(% style="width:494px" %)Process
++|(% style="width:127px" %) |(% style="width:494px" %)ProcessStep
++|(% style="width:127px" %) |(% style="width:494px" %)Transition
++|(% style="width:127px" %)registry|(% style="width:494px" %)ProvisionAgreement
++|(% style="width:127px" %) |(% style="width:494px" %)AttachmentConstraint
++|(% style="width:127px" %) |(% style="width:494px" %)ContentConstraint
++|(% style="width:127px" %) |(% style="width:494px" %)Subscription
++|(% style="width:127px" %)mapping|(% style="width:494px" %)StructureMap
++|(% style="width:127px" %) |(% style="width:494px" %)StructureSet
++|(% style="width:127px" %) |(% style="width:494px" %)ComponentMap
++|(% style="width:127px" %) |(% style="width:494px" %)ConceptSchemeMap
++|(% style="width:127px" %) |(% style="width:494px" %)OrganisationSchemeMap
++|(% style="width:127px" %) |(% style="width:494px" %)CodelistMap
++|(% style="width:127px" %) |(% style="width:494px" %)CategorySchemeMap
++|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomyMap
++|(% style="width:127px" %) |(% style="width:494px" %)ConceptMap
++|(% style="width:127px" %) |(% style="width:494px" %)OrganisationMap
++|(% style="width:127px" %) |(% style="width:494px" %)CodeMap
++|(% style="width:127px" %) |(% style="width:494px" %)HybridCodelistMap
++|(% style="width:127px" %) |(% style="width:494px" %)CategoryMap
++|(% style="width:127px" %) |(% style="width:494px" %)HybridCodeMap
++|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategoryMap
++|(% style="width:127px" %)codelist|(% style="width:494px" %)Codelist
++|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCodelist
++|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy
++|(% style="width:127px" %) |(% style="width:494px" %)Hierarchy
++|(% style="width:127px" %) |(% style="width:494px" %)Code
++|(% style="width:127px" %) |(% style="width:494px" %)HierarchicalCode
++|(% style="width:127px" %) |(% style="width:494px" %)Level
++|(% style="width:127px" %)categoryscheme|(% style="width:494px" %)CategoryScheme
++|(% style="width:127px" %) |(% style="width:494px" %)Category
++|(% style="width:127px" %) |(% style="width:494px" %)Categorisation
++|(% style="width:127px" %) |(% style="width:494px" %)ReportingTaxonomy
++|(% style="width:127px" %) |(% style="width:494px" %)ReportingCategory
++|(% style="width:127px" %)conceptscheme|(% style="width:494px" %)ConceptScheme
++|(% style="width:127px" %) |(% style="width:494px" %)Concept
++|(% style="width:127px" %)transformation|(% style="width:494px" %)TransformationScheme
++|(% style="width:127px" %) |(% style="width:494px" %)Transformation
++|(% style="width:127px" %) |(% style="width:494px" %)CustomTypeScheme
++|(% style="width:127px" %) |(% style="width:494px" %)CustomType
++|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisationScheme
++|(% style="width:127px" %) |(% style="width:494px" %)NamePersonalisation
++|(% style="width:127px" %) |(% style="width:494px" %)VtlCodelistMapping
++|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptMapping
++|(% style="width:127px" %) |(% style="width:494px" %)VtlDataflowMapping
++|(% style="width:127px" %) |(% style="width:494px" %)VtlConceptSchemeMapping
++|(% style="width:127px" %) |(% style="width:494px" %)RulesetScheme
++|(% style="width:127px" %) |(% style="width:494px" %)Ruleset
++|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperatorScheme
++|(% style="width:127px" %) |(% style="width:494px" %)UserDefinedOperator
--**where this is different)**
--)))
--| |ConceptSchemeMap
--| |OrganisationSchemeMap
--| |CodelistMap
--| |CategorySchemeMap
--| |ReportingTaxonomyMap
--| |ConceptMap
--| |OrganisationMap
--| |CodeMap
--| |HybridCodelistMap
--| |CategoryMap
--| |HybridCodeMap
--| |ReportingCategoryMap
--| |
--|codelist|Codelist
--| |HierarchicalCodelist
--| |Hierarchy
--| |Hierarchy
--| |Code
--| |HierarchicalCode
--| |Level
--| |
--|categoryscheme|CategoryScheme
--| |Category
--| |Categorisation
--| |ReportingTaxonomy
--| |ReportingCategory
--| |
--|conceptscheme|ConceptScheme
--| |Concept
--| |
--|transformation|TransformationScheme
--| |Transformation
--| |CustomTypeScheme
--| |CustomType
--| |NamePersonalisationScheme
--| |NamePersonalisation
--| |VtlCodelistMapping
--| |VtlConceptMapping
--| |VtlDataflowMapping
--| |VtlConceptSchemeMapping
--| |RulesetScheme
--| |Ruleset
--| |UserDefinedOperatorScheme
--| |UserDefinedOperator
--| |
++**Table 2: [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] Packages and Contained Classes**
--**Table 2: SDMX-IM Packages and Contained Classes**
--
--
  === 6.2.4 URN Identification components of SDMX objects ===
--The table below describes the identification components for all SDMX object types that have identification. Note the actual attributes are all Id, but have been prefixed by their class name or multiple class names to show navigation, e.g. conceptSchemeAgencyId is really the Id attribute of the Agency class that is associated to the ConceptScheme.
++The table below describes the identification [[components>>doc:sdmx:Glossary.Component.WebHome]] for all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object types that have identification. Note the actual [[attributes>>doc:sdmx: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:sdmx:Glossary.Attribute.WebHome]] of the Agency class that is associated to the ConceptScheme.
  ~* indicates that the object is maintainable.
  Note that for brevity the URN examples omit the prefix. All URNs have the prefix
--urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
++> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--
--|**SDMX Class**|**Key attribute(s)**|**Example of URN**
--|Agency|The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|(((
++(% style="width:1277.29px" %)
++|(% style="width:269px" %)**SDMX Class**|(% style="width:453px" %)**Key attribute(s)**|(% style="width:550px" %)**Example of URN**
++|(% style="width:269px" %)Agency|(% style="width:453px" %)The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.|(% style="width:550px" %)(((
  IMF
--
--
  Sub agency in the IMF AGENCIES
--
--
  IMF.SubAgency1
  )))
--|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
--|Concept|(((
--conceptSchemeAgencyId:
--
--conceptSchemeId(version).conceptId
--)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
--|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
--|Code|codeListAgencyId:codelistId(version).codeId|(((
--SDMX:CL_FREQ(1.0).Q
--
--
++|(% style="width:269px" %)*ConceptScheme|(% style="width:453px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
++|(% style="width:269px" %)Concept|(% style="width:453px" %)conceptSchemeAgencyId:
++conceptSchemeId(version).conceptId|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
++|(% style="width:269px" %)*Codelist|(% style="width:453px" %)codeListAgencyId:codeListId(version)|(% style="width:550px" %)SDMX:CL_FREQ(1.0)
++|(% style="width:269px" %)Code|(% style="width:453px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:550px" %)SDMX:CL_FREQ(1.0).Q
++|(% style="width:269px" %)(((
++*Hierarchical Codelist
++)))|(% style="width:453px" %)hierachicalCodelistAgencyId:
++hierarchicalCodelistId(version)|(% style="width:550px" %)(((
++UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
  )))
--
--
--
--|(((
--*Hierarchical
--
--Codelist
--)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
--UNESCO:CL_EXP_SOURCE(1.0)
--
--
--)))
--|Hierarchy|(((
++|(% style="width:269px" %)Hierarchy|(% style="width:453px" %)(((
  hierachicalcodeListAgencyId:
--
  hierarchicalcodelistId(version).Hierarchy
--)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
--|Level|(((
++)))|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0).
++H-C-GOV
++|(% style="width:269px" %)Level|(% style="width:453px" %)(((
  hierachicalcodeListAgencyId:
--
  hierarchicalcodelistId(version).Hierarchy.Level
--)))|(((
++)))|(% style="width:550px" %)(((
  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
--
--
  )))
--|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
--|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
--|(((
++|(% style="width:269px" %)HierarchicalCode|(% style="width:453px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
++|(% style="width:269px" %)*DataStructure|(% style="width:453px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:550px" %)TFFS:EXT_DEBT(1.0)
++|(% style="width:269px" %)(((
  Dimension
--
  Descriptor
--
  Measure
--
  Descriptor
--
  Attribute
--
  Descriptor
--)))|(((
++)))|(% style="width:453px" %)(((
  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
--
  componentListId
--
  where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
--)))|(((
++)))|(% style="width:550px" %)(((
  TFFS:EXT_DEBT(1.0).DimensionDescriptor
  TFFS:EXT_DEBT(1.0).MeasureDescriptor
@@ -789,289 +789,209 @@
  TFFS:EXT_DEBT(1.0).AttributeDescriptor
  )))
--|(((
++|(% style="width:269px" %)(((
  GroupDimension
--
  Descriptor
--)))|(((
++)))|(% style="width:453px" %)(((
  dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
--
  groupDimensionDescriptorId
--)))|TFFS:EXT_DEBT(1.0).SIBLING
--|Dimension|(((
++)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).SIBLING
++|(% style="width:269px" %)Dimension|(% style="width:453px" %)(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
--
  dimensionId
--)))|TFFS:EXT_DEBT(1.0).FREQ
--|TimeDimension|(((
++)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).FREQ
++|(% style="width:269px" %)TimeDimension|(% style="width:453px" %)(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
--
  timeDimensionId
--)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
--|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
--
--
--
--| |measureDimensionId|
--|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
--|PrimaryMeasure|(((
++)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
++|(% style="width:269px" %)Measure Dimension|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
++measureDimensionId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
++|(% style="width:269px" %)DataAttrribute|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
++|(% style="width:269px" %)PrimaryMeasure|(% style="width:453px" %)(((
  dataStructureDefinitionAgencyId: dataStructureDefinition (version).
--
  primaryMeasureId
--)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
--|(((
--*Category
--
--Scheme
--)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
--|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
++)))|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
++|(% style="width:269px" %)(((
++*Category Scheme
++)))|(% style="width:453px" %)categorySchemeAgencyId:
++categorySchemeId(version)|(% style="width:550px" %)IMF:SDDS(1.0)
++|(% style="width:269px" %)Category|(% style="width:453px" %)categorySchemeAgencyId:
++categorySchemeId(version).
++categoryId.categoryId categoryId.categoryId etc.|(% style="width:550px" %)(((
  IMF:SDDS(1.0):
--
  level_1_category.level_2_category …
  )))
--|(((
--*Reporting
--
--Taxonomy
--)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
--|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
++|(% style="width:269px" %)(((
++*Reporting Taxonomy
++)))|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:550px" %) IMF:REP_1(1.0)
++|(% style="width:269px" %)ReportingCategory|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:550px" %)(((
  IMF:REP_1(1.0):
--
  level_1_repcategory.level_2_repcategory …
  )))
--|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
--|(((
--*Organisation
++|(% style="width:269px" %)*Categorisation|(% style="width:453px" %)categorisationAgencyId: categorisationId(version)|(% style="width:550px" %)IMF:cat001(1.0)
++|(% style="width:269px" %)(((
++*Organisation Unit Scheme
++)))|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:550px" %)ECB:ORGANISATIONS(1.0)
++|(% style="width:269px" %)Organisation Unit|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:550px" %)ECB:ORGANISATIONS(1.0).1F
++|(% style="width:269px" %)*AgencyScheme|(% style="width:453px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:550px" %)ECB:AGENCIES(1.0)
--Unit Scheme
--)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
--|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
--|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
--
--
--
--|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
--|(((
--*DataProvider
--
--Scheme
--)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
--|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
--|(((
--*DataConsumer
--
--Scheme
--)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
--|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
--|(((
--*Metadata
--
--Structure
--)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
--|MetadataTarget|(((
++(% style="width:1274.29px" %)
++|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:535px" %)ECB:AGENCY(1.0).AA
++|(% style="width:262px" %)(((
++*DataProvider Scheme
++)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0)
++|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
++|(% style="width:262px" %)(((
++*DataConsumer Scheme
++)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0)
++|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
++|(% style="width:262px" %)(((
++*Metadata Structure
++)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:535px" %)IMF:SDDS_MSD(1.0)
++|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)(((
  MSDAgencyId:
--
  MSDId(version).metadataTargetId
--)))|IMF:SDDS_MSD(1.0).AGENCY
--|(((
++)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY
++|(% style="width:262px" %)(((
  Dimension
--
  DescriptorValues
--
  Target
--)))|(((
++)))|(% style="width:369px" %)(((
  MSDAgencyId: MSDId(version).
--
  metadataTargetId.keyDescriptorValueTargetId
--)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
--|Identifiable ObjectTarget|(((
++)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
++|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)(((
++MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
++)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
++|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)(((
  MSDAgencyId:
++MSDId(version).metadataTargetId.dataSetTargetId
++)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
++|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)(((
++MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
++)))|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
--MSDId(version).metadataTargetId.identifiable
--
--ObjectTargetId
--)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
--|DataSetTarget|(((
--MSDAgencyId:
--
--MSDId(version).metadataTargetId.dataSet
--
--TargetId
--)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
--|PeportPeriod Target|(((
--MSDAgencyId:
--
--MSDId(version).metadataTargetId.reportPeriod
--
--TargetId
--)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
--
--
--
--|(((
++(% style="width:1277.29px" %)
++|(% style="width:270px" %)(((
  ReportStructure
--
--
--)))|(((
--MSDAgencyId:
--
--MSDId(version).reportStructureId
--)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
--|(((
--Metadata
--
--Attribute
--)))|(((
--MSDAgencyId:
--
--MSDId(version).reportStructureId.metadataattri buteID
--)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
--|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
--|*Provision Agreement|(((
++)))|(% style="width:454px" %)(((
++MSDAgencyId: MSDId(version).reportStructureId
++)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
++|(% style="width:270px" %)(((
++Metadata Attribute
++)))|(% style="width:454px" %)(((
++MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
++)))|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
++|(% style="width:270px" %)*Dataflow|(% style="width:454px" %)dataflowAgencyId: dataflowId(version)|(% style="width:549px" %)TFFS:CRED_EXT_DEBT(1.0)
++|(% style="width:270px" %)*Provision Agreement|(% style="width:454px" %)(((
  provisionAgreementAgencyId:provisionAgreem entId(version)
--
--
--)))|(((
++)))|(% style="width:549px" %)(((
  TFFS:CRED_EXT_DEBT_AB(1.0)
--
--
--
  )))
--|(((
--*Content
--
--Constraint
--)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
--|(((
--*Attachment
--
--Constraint
--)))|(((
++|(% style="width:270px" %)(((
++*Content Constraint
++)))|(% style="width:454px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:549px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
++|(% style="width:270px" %)(((
++*Attachment Constraint
++)))|(% style="width:454px" %)(((
  constraintAgencyId:
  attachmentConstraintId(version)
--)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
--|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
--|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
--|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
--|Component Map|(((
++)))|(% style="width:549px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
++|(% style="width:270px" %)*Metadataflow|(% style="width:454px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:549px" %)IMF:SDDS_FLOW(1.0)
++|(% style="width:270px" %)*StructureSet|(% style="width:454px" %)structureSetAgencyId: structureSetId(version)|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0)
++|(% style="width:270px" %)StructureMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
++|(% style="width:270px" %)Component Map|(% style="width:454px" %)(((
  structureSetAgencyId: structureSetId(version).
  structureMapId. componentMapId
--)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
--|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
--|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
--
--
--
--| |(((
++)))|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
++|(% style="width:270px" %)CodelistMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
++|(% style="width:270px" %)CodeMap|(% style="width:454px" %)structureSetAgencyId: structureSetId(version).
  codeListMapId.
++codeMapId|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
--codeMapId
--)))|
--|(((
--Category
--
--SchemeMap
--)))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
--|CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
--|Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
--|Organisation Map|structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0
--|(((
++(% style="width:1279.29px" %)
++|(% style="width:271px" %)(((
++CategorySchemeMap
++)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
++|(% style="width:271px" %)CategoryMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_MAP
++|(% style="width:271px" %)Organisation SchemeMap|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
++|(% style="width:271px" %)Organisation Map|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0
++|(% style="width:271px" %)(((
  Concept
  SchemeMap
--)))|structureSetAgencyId: structureSetId(version). conceptSchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD
--|ConceptMap|(((
++)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). conceptSchemeMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD
++|(% style="width:271px" %)ConceptMap|(% style="width:453px" %)(((
  structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
--
  conceptMapId
--
--
--)))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
--|(((
--Reporting
--
--TaxonomyMap
--)))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
--|(((
--Reporting
--
--CategoryMap
--)))|(((
++)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
++|(% style="width:271px" %)(((
++ReportingTaxonomyMap
++)))|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP
++|(% style="width:271px" %)(((
++ReportingCategoryMap
++)))|(% style="width:453px" %)(((
  structureSetAgencyId: structureSetId(version).
--
  reportngCategoryId
--)))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
++)))|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
--
--
--|(((
--HybridCodelist
--
--Map
--)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
--|HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
--|*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
--|ProcessStep|(((
++(% style="width:1282.29px" %)
++|(% style="width:272px" %)(((
++HybridCodelistMap
++)))|(% style="width:450px" %)structureSetAgencyId: structureSetId(version).
++hybridCodelistMapId.|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
++|(% style="width:272px" %)HybridCodeMap|(% style="width:450px" %)structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
++|(% style="width:272px" %)*Process|(% style="width:450px" %)processAgencyId: processId{version]|(% style="width:557px" %)BIS:PROCESS1(1.0)
++|(% style="width:272px" %)ProcessStep|(% style="width:450px" %)(((
  processAgencyId: processId(version).
--
  processStepId
--)))|BIS:PROCESS1(1.0).STEP1
--|Transition|(((
++)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1
++|(% style="width:272px" %)Transition|(% style="width:450px" %)(((
  processAgencyId: processId(version).
--
  processStepId transitionId
--)))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
--|Subscription|The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message.
--|(((
--*Transformation
--
--Scheme
--)))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
--|Transformation|(((
++)))|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1.TRANSITION1
++|(% style="width:272px" %)Subscription|(% style="width:450px" %)The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is not itself an [[Identifiable Artefact>>doc:sdmx:Glossary.Identifiable artefact.WebHome]] 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:557px" %)This cannot be generated by a common mechanism as [[subscriptions>>doc:sdmx: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:sdmx: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:sdmx:Glossary.Subscription.WebHome]], and for the application creating the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] to store the registryURN that is returned from the registry in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response message.
++|(% style="width:272px" %)(((
++*Transformation Scheme
++)))|(% style="width:450px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:557px" %)ECB: TRANSFORMATION_SCHEME(1.0)
++|(% style="width:272px" %)Transformation|(% style="width:450px" %)(((
  transformationSchemeAgencyId transformationSchemeId(version)
--
  transformationId
--)))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
--|CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
++)))|(% style="width:557px" %)ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
++|(% style="width:272px" %)CustomType Scheme|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:557px" %)ECB:CUSTOM_TYPE_SCHEME(1.0)
--
--
--|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
--|(((
++(% style="width:1281.29px" %)
++|(% style="width:275px" %)CustomType|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:552px" %)ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
++|(% style="width:275px" %)(((
  Name
--
  Personalisation
--
  Scheme
--)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
--|(((
++)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:552px" %)ECB:PSN_SCHEME(1.0)
++|(% style="width:275px" %)(((
  Name
--
  Personalisation
--)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
--|VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
--|VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
--|VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
--|VtlDataflow Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0).MOQ
--|(((
++)))|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
++namePersonalisationId|(% style="width:552px" %)ECB:PSN_SCHEME(1.0).PSN1234
++|(% style="width:275px" %)VtlMapping Scheme|(% style="width:450px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:552px" %)ECB:CLIST_MP(2.0)
++|(% style="width:275px" %)VtlCodelist Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:552px" %)ECB:CLIST_MP(2.0).ABZ
++|(% style="width:275px" %)VtlConcept Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).XYA
++|(% style="width:275px" %)VtlDataflow Mapping|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:552px" %)ECB:CLIST_MP(1.0).MOQ
++|(% style="width:275px" %)(((
  VtlConcept
  SchemeMapping
--)))|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|ECB:CLIST_MP(1.0).Z11
--|RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
--|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
--|(((
--UserDefined
++)))|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId|(% style="width:552px" %)ECB:CLIST_MP(1.0).Z11
++|(% style="width:275px" %)RulesetScheme|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:552px" %)ECB:RULESET_23(1.0)
++|(% style="width:275px" %)Ruleset|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:552px" %)ECB:RULESET_23(1.0).SET111
++|(% style="width:275px" %)(((
++UserDefinedOperatorScheme
++)))|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:552px" %)ECB:OS_CALC(1.2)
++|(% style="width:275px" %)UserDefined Operator|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:552px" %)ECB:OS_CALC(1.2).OS267
--OperatorScheme
--)))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
--|UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
++**Table 3: Table of identification components for SDMX Identifiable Artefacts**
--7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
--
--
  = 7 Implementation Notes =
  == 7.1 Structural Definition Metadata ==
@@ -1078,142 +1078,102 @@
  === 7.1.1 Introduction ===
--The SDMX Registry must have the ability to support agencies in their role of defining and disseminating structural metadata artefacts. These artefacts include data structure definitions, code lists, concepts etc. and are fully defined in the SDMX-IM. An authenticated agency may submit valid structural metadata definitions which must be stored in the registry. Note that the term “structural metadata” refers as a general term to all structural components (Data structure Definitions, Metadata Structure Definitions, Code lists, Concept Schemes, etc.)
++The [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] must have the ability to support agencies in their role of defining and disseminating [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. These [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] include [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], [[concepts>>doc:sdmx:Glossary.Concept.WebHome]] etc. and are fully defined in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. An authenticated agency may submit valid [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] definitions which must be stored in the registry. Note that the term “[[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]” refers as a general term to all structural [[components>>doc:sdmx:Glossary.Component.WebHome]] ([[Data structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[Code lists>>doc:sdmx:Glossary.Code list.WebHome]], [[Concept Schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], etc.)
--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 registry messages for structural metadata and the SDMX Query message for structure queries. The use of SOAP is also recommended, as described in the SDMX Web Services Guidelines. The message may contain all structural metadata items for the whole registry, structural metadata items for one maintenance agency, or individual structural metadata items.
++At a minimum, [[structural metadata>>doc:sdmx: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:sdmx:Glossary.SDMX-ML.WebHome]] registry messages for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Query message for structure queries. The use of SOAP is also recommended, as described in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Web Services Guidelines. The message may contain all [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items for the whole registry, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items for one [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], or individual [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items.
--Structural metadata items
++[[Structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items
--* may only be modified by the maintenance agency which created them
++* may only be modified by the [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] 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 level of granularity for the maintenance of SDMX Structural Metadata objects in the registry is the Maintainable Artefact. In other words, any function such as add, modify, delete is at the level of the Maintainable Artefact. For instance, if a Code is added to a Code List, or the Name of a Code is changed, the Registry must replace the existing Code List with the submitted Code List of the same Maintenance Agency, Code List, Id and Version.
++The [[level>>doc:sdmx:Glossary.Level.WebHome]] of granularity for the maintenance of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Structural Metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] objects in the registry is the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. In other words, any function such as add, modify, delete is at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. For instance, if a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is added to a [[Code List>>doc:sdmx:Glossary.Code list.WebHome]], or the Name of a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is changed, the Registry must replace the existing [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] with the submitted [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] of the same [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], [[Code List>>doc:sdmx:Glossary.Code list.WebHome]], Id and Version.
--The following table lists the Maintainable Artefacts.
++The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
--|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
--|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
--|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
--|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
--|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
--|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
--|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
--|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
--|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
--|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
--|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
--|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
--| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
--| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
--| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
--| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
--| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
--| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
--| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
--Vtl       Concept       Scheme
--
--Mapping
--)))
--| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
--| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
--| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
--| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)(((
++(% style="width:640.294px" %)
++|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content**
++|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %)
++|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code
++|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept
++|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category
++|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit
++|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency
++|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider
++|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer
++|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category
++|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation
++|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type
++|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation
++|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping
++|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping
++|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping
++|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset
++|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator
++|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator
++|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)(((
  Dimension Descriptor
--
  Group Dimension
--
  Descriptor
--
  Dimension
--
  Measure Dimension
--
  Time Dimension
--
  Attribute Descriptor
--
  Data Attribute
--
  Measure Descriptor
--
  Primary Measure
  )))
--| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
--Metadata Target,
--
--Dimension Descriptor
--
++|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
++Metadata Target, Dimension Descriptor
  Values Target Identifiable
--
  Object Target
--
  Report Period Target
--
  Data SetTarget
--
  Report Structure
--
  Metadata Attribute
  )))
--| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
--| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
--| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
--| |(% colspan="2" %)None|(% colspan="2" %)Structure Set|(% colspan="2" %)(((
++|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %)
++|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %)
++|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step
++|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)(((
  Component Map
--
  Concept Scheme Map
--
  Codelist Map
--
  Category Scheme Map
--
  Reporting Taxonomy Map
--
  Organisation Scheme Map
--
  Concept Map
--
  Code Map
--
  Category Map
--
  Organisation Map
--
  Reporting Category Map
--
  Hybrid Codelist Map
--
  Hybrid Code Map
  )))
--| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
--| |(% colspan="2" %)None|(% colspan="2" %)Hierarchical Codelist|(% colspan="2" %)(((
++|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %)
++|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)(((
  Hierarchy
--
  Hierarchical Code
  )))
--| | | | | | |
  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
  === 7.1.2 Item Scheme, Structure ===
--The artefacts included in the structural definitions are:
++The [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] included in the structural definitions are:
--* All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
--* All types of Structure (Data Structure Definition, Metadata Structure
++* All types of [[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] ([[Codelist>>doc:sdmx:Glossary.Code list.WebHome]], [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]], Organisation Scheme - [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]], [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]], [[Data Consumer Scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]], Organisation Unit Scheme)
++* All types of Structure ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], Metadata Structure Definition)
++* All types of Structure Usage ([[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition, [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition)
--Definition)
--
--* All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
--
  === 7.1.3 Structure Usage ===
  ==== 7.1.3.1 Structure Usage: Basic Concepts ====
--The Structure Usage defines, in its concrete classes of Dataflow Definition and
++The Structure Usage defines, in its concrete classes of [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and
--Metadataflow Definition, 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.
++[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition, 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:sdmx:Glossary.Category.WebHome]] in one or more [[Category Scheme>>doc:sdmx: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:sdmx:Glossary.Category scheme.WebHome]].
  ==== 7.1.3.2 Structure Usage Schematic ====
@@ -1223,64 +1223,68 @@
  ==== 7.1.3.3 Structure Usage Model ====
++[[image:1747829078194-749.png]]
++
  **Figure 10: SDMX-IM of links from Structure Usage to Category**
--In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
++In addition to the maintenance of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and the [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition the following links must be maintained in the registry:
--* Dataflow Definition to Data Structure Definition
--* Metadataflow Definition to Metadata Structure Definition
++* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition to Data Structure Definition
++* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition to Metadata Structure Definition
  The following links may be created by means of a Categorisation
--* Categorisation to Dataflow Definition and Category
--* Categorisation to Metadataflow Definition and Category
++* Categorisation to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and Category
++* Categorisation to [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition and Category
  == 7.2 Data and Metadata Provisioning ==
  === 7.2.1 Provisioning Agreement: Basic concepts ===
--Data provisioning defines a framework in which the provision of different types of statistical data and metadata by various data 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.
++Data provisioning defines a framework in which the provision of different types of statistical data and metadata by various [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] can be specified and controlled. This framework is the basis on which the existence of data can be made known to the [[SDMX>>doc:sdmx: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 [[level>>doc:sdmx:Glossary.Level.WebHome]] agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
--Note that in the SDMX-IM the class “Data Provider” encompasses both data and metadata and the term “data provisioning” here includes both the provisioning of data and metadata.
++Note that in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] the class “[[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]” encompasses both data and metadata and the term “data provisioning” here includes both the provisioning of data and 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.
++Although the [[Provision Agreement>>doc:sdmx: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.
  === 7.2.2 Provisioning Agreement Model – pull use case ===
--An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
++An organisation which publishes statistical data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and wishes to make it available to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] enabled community is called a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]. In terms of the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]], the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] is maintained in a [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]].
++[[image:1747829109466-595.png]]
  **Figure 11: SDMX-IM of the Data Provider**
++Note that the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] does not inherit the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. The diagram below shows a logical schematic of the data model classes required to maintain [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]
--Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
--
  [[image:1747824123019-181.jpeg]]
  **Figure 12: Schematic of the Provision Agreement**
--The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
++The diagram below is a logical [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the data required in order to maintain [[Provision Agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]].
++[[image:1747829139951-378.png]]
--==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
++(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
++**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
--A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
++A [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] is [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. Each [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] must reference a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] and a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition. The [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] and the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition must exist already in order to set up a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].
  == 7.3 Data and Metadata Constraints ==
  === 7.3.1 Data and Metadata Constraints: Basic Concepts ===
--Constraints are, effectively, lists of the valid or actual content of data and metadata. Constraints can be used to specify a sub set 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.
++[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] are, effectively, lists of the valid or actual content of data and metadata. [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] can be used to specify a sub set of the theoretical content of [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] which can be derived from the specification of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. A [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] can comprise a list of keys or a list of content (usually [[code>>doc:sdmx:Glossary.Code.WebHome]] values) of a specific [[component>>doc:sdmx:Glossary.Component.WebHome]] such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] or [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
--Constraints comprise the specification of subsets of key or target values or attribute values that are contained in a Datasource, or is to be provided for a Dataflow or Metadataflow Definition, 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 Datasource, or more than is intended to be supplied according to a specific Dataflow Definition.
++[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] comprise the specification of subsets of key or target values or [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] values that are contained in a Datasource, or is to be provided for a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition, or directly attached to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx: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:sdmx: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:sdmx:Glossary.Code list.WebHome]] for each of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]) is often more than is actually present in any specific Datasource, or more than is intended to be supplied according to a specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition.
--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 Datasource (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 Content Constraint is also used to define a code list sub set which is used to populate a Partial Code List.
++Often a [[Data Provider>>doc:sdmx: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:sdmx:Glossary.Data provider.WebHome]] could constrain the Datasource (at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] or the [[Data Provider>>doc:sdmx: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 [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]. The Content [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] is also used to define a [[code list>>doc:sdmx:Glossary.Code list.WebHome]] sub set which is used to populate a Partial [[Code List>>doc:sdmx:Glossary.Code list.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 Definition, and there can be one or more defined for any Data Structure Definition.
++Furthermore, it is often useful to define subsets or views of the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] which restrict values in some [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], especially where many such subsets restrict the same [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Such a view is called a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition, and there can be one or more defined for any [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]].
--Whenever data is published or made available by a Data Provider, it must conform to a Dataflow Definition (and hence to a Data Structure Definition). The Dataflow Definition is thus a means of enabling content based processing.
++Whenever data is published or made available by a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], it must conform to a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition (and hence to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). The [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition is thus a means of enabling content based processing.
--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 datasource (these can be used to build relevant selection tables), and the Key Set can be used to specify the keys that exist in a datasource (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).
++In addition, [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] 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:sdmx:Glossary.Dimension.WebHome]] [[codes>>doc:sdmx:Glossary.Code.WebHome]] that actually exist in a datasource (these can be used to build relevant selection tables), and the Key Set can be used to specify the keys that exist in a datasource (these can be used to guide the user to select only those [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[code>>doc:sdmx:Glossary.Code.WebHome]] values that will return data based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] values already selected).
  === 7.3.2 Data and Metadata Constraints: Schematic ===
@@ -1290,26 +1290,25 @@
  === 7.3.3 Data and Metadata Constraints: Model ===
++[[image:1747829204737-370.png]]
++**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
--==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
++The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] specified. Note that the actual [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] applies.
--The     class    diagram          above shows that      DataProvider, DataflowDefinition, MetadataflowDefinition,         ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
++The content of the [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] can be found in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] document.
--
--The content of the Constraint can be found in the SDMX Information Model document.
--
  == 7.4 Data and Metadata Registration ==
  === 7.4.1 Basic Concepts ===
--A Data Provider has published a new dataset conforming to an existing Dataflow Definition (and hence Data Structure Definition). This is implemented as either a web-accessible SDMX-ML file, or in a database which has a web-services interface capable of responding to an SDMX-ML Query or RESTful query with an SDMX-ML data stream.
++A [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] has published a new [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] conforming to an existing [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition (and hence [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). This is implemented as either a web-accessible [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file, or in a database which has a web-services interface capable of responding to an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query or RESTful query with an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data stream.
--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 [[Data Provider>>doc:sdmx: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:sdmx:Glossary.Data consumer.WebHome]]. To do this, the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] registers the new [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] with one or more [[SDMX>>doc:sdmx: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:sdmx:Glossary.Data provider.WebHome]] and “knows” what [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] has agreed to make available.
--The same mechanism can be used to report or make available a metadata set.
++The same mechanism can be used to report or make available a [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]].
--SDMX-RR supports dataset and metadata set registration via the Registration Request, which can be created by the Data Provider (giving the Data Provider maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response.
++[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] registration via the Registration Request, which can be created by the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] (giving the [[Data Provider>>doc:sdmx: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.
  === 7.4.2 The Registration Request ===
@@ -1317,11 +1317,11 @@
  [[image:1747824123025-411.jpeg]]
--  **Figure 16: Schematic of the Objects Concerned with Registration**
++**Figure 16: Schematic of the Objects Concerned with Registration**
  ==== 7.4.2.2 Registration Request Model ====
--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:
++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:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] to be registered. The Registration can optionally have information which has been extracted from the Registration:
  * validFrom
  * validTo
@@ -1329,175 +1329,154 @@
  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 which takes one of the following values:
++The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
--|**Action Attribute Value**|**Behaviour**
--|Append|Add this Registration to the registry
--|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
--|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++(% style="width:798.294px" %)
++|(% style="width:212px" %)**Action Attribute Value**|(% style="width:582px" %)**Behaviour**
++|(% style="width:212px" %)Append|(% style="width:582px" %)Add this Registration to the registry
++|(% style="width:212px" %)Replace|(% style="width:582px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
++|(% style="width:212px" %)Delete|(% style="width:582px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++[[image:1747829290890-122.png]]
++
  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
--The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
++The Query Datasource is an abstract class that represents a [[data source>>doc:sdmx:Glossary.Data source.WebHome]] which can understand an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] query (SOAPDatasource) or RESTful query
  (RESTDatasource) and respond appropriately. Each of these different Datasources inherit the dataURL from Datasource, and the QueryDatasource has an additional URL to locate a WSDL or WADL document to describe how to access it. All other supported protocols are assumed to use the Simple Datasource URL.
--A Simple Datasource is used to reference a physical SDMX-ML file that is available at a URL.
++A Simple Datasource is used to reference a physical [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file that is available at a URL.
--The Registration Request 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 Request has an action [[attribute>>doc:sdmx: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 Registration includes attributes that state how a Simple Datasource is to be indexed when registered. The Registry registration process must act as follows.
++The Registration includes [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] that state how a Simple Datasource is to be indexed when registered. The Registry registration process must act as follows.
--Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below.
++Information in the data or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] is extracted and placed in one or more Content [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] (see the [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] – Section 2 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standards). The information to be extracted is indicated by the Boolean values set on the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] as shown in the table below.
--|**Indexing Required**|**Registration Process Activity**
--|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
--|indexDataSet|(((
--Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube
--
--Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
++(% style="width:860.294px" %)
++|(% style="width:185px" %)**Indexing Required**|(% style="width:672px" %)**Registration Process Activity**
++|(% style="width:185px" %)indexTimeSeries|(% style="width:672px" %)Extract all the [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] and create a KeySet(s) Constraint.
++|(% style="width:185px" %)indexDataSet|(% style="width:672px" %)(((
++Extract all the [[codes>>doc:sdmx:Glossary.Code.WebHome]] and other content of the Key value of the [[Series Key>>doc:sdmx:Glossary.Series key.WebHome]] in a [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]], and the associated Selection Value.
  )))
--|indexReportingPeriod|(((
--This applies only to a registered dataset.
--
--Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
++|(% style="width:185px" %)indexReportingPeriod|(% style="width:672px" %)(((
++This applies only to a registered [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
++Extract the Reporting Begin and Reporting End from the Header of the Message containing the [[data set>>doc:sdmx:Glossary.Data set.WebHome]], and create a [[Reference Period>>doc:sdmx:Glossary.Reference period.WebHome]] constraint.
  )))
--|indexAttributes|(((
--**Data Set**
--
--Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
--
--**Metadata Set**
--
--Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value.
++|(% style="width:185px" %)indexAttributes|(% style="width:672px" %)(((
++**[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]**
++Extract the content of the [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Values in a [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the SDMXIM, and the associated Selection Value
++**[[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]**
++Indicate the presence of a Reported [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] by creating one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value.
  )))
--Constraints that specify the contents of a Query Datasource are submitted to the Registry in a Submit Structure Request.
++[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] that specify the contents of a Query Datasource are submitted to the Registry in a Submit Structure Request.
--The Registration must reference the Provision Agreement to which it relates.
++The Registration must reference the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] to which it relates.
  === 7.4.3 Registration Response ===
--After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to
++After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
--“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:sdmx: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 Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of [[datasets>>doc:sdmx:Glossary.Data set.WebHome]], that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
--The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
++[[image:1747829477882-750.png]]
--
  **Figure 18: Logical class diagram showing the registration response**
  == 7.5 Subscription and Notification Service ==
--The contents of the SDMX Registry/Repository will change regularly: new code lists and key families will be published, new datasets and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
++The contents of the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repository will change regularly: new [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and key families will be published, new [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
--A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
++A user can submit a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] of qualifying events will be delivered. The [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] will be identified in the registry by a URN which is returned to the user when the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is created. If the user wants to delete the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] at a later point, the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] URN is used as identification. [[Subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]], and will notify the subscriber on expiry.
--When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a
++When a registry/repository [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is modified, any [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]. This is called a “[[notification>>doc:sdmx:Glossary.Notification.WebHome]]”.
--“notification”.
++=== 7.5.1Subscription Logical Class Diagram ===
-- 7.5.1Subscription Logical Class Diagram
++[[image:1747829554603-150.png]]
--
--[[image:1747824123028-257.png]]
--
  **Figure 19: Logical Class Diagram of the Subscription**
  === 7.5.2 Subscription Information ===
--Regardless of the type of registry/repository events being observed, a subscription always contains:
++Regardless of the type of registry/repository events being observed, a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] always contains:
--~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
++1. A set of URIs describing the end-points to which [[notifications>>doc:sdmx:Glossary.Notification.WebHome]] must be sent if the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is activated. The URIs can be either mailto~: or http: protocol. In the former case an email [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is sent; in the latter an HTTP POST [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is sent.
++1. A user-defined identifier which is returned in the response to the [[subscription>>doc:sdmx: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:sdmx:Glossary.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] on expiration of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]].
++1. A selector which specifies which type of events are of interest. The set of event types is:
--2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
++(% style="width:1031.29px" %)
++|(% style="width:319px" %)**Event Type**|(% style="width:678px" %)**Comment**
++|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:678px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository.
++|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database.
++|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published metadataset is registered. This can be either a SDMXML [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database.
++|(% style="width:319px" %)ALL_EVENTS|(% style="width:678px" %)All events of the specified EventType
--3. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
--
--4. A selector which specifies which type of events are of interest. The set of event types is:
--
--|**Event Type**|**Comment**
--|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
--|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
--|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
--|ALL_EVENTS|All events of the specified EventType
--
  === 7.5.3 Wildcard Facility ===
--Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
--         agencyID
++[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] [[notification>>doc:sdmx:Glossary.Notification.WebHome]] supports wildcarded identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] URNs, which are identiiers which have some or all of their [[component>>doc:sdmx:Glossary.Component.WebHome]] parts replaced by the wildcard character `%`. Identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] comprise:
--         id
++* agencyID
++* id
++* version
--         version
++Examples of wildcarded identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] for an identified object type of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] are shown below.
--Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
--
--AgencyID = %
--
++//AgencyID = %
  Id = %
++Version = %//
--Version = %
++This subscribes to all [[Codelists>>doc:sdmx:Glossary.Code list.WebHome]] of all [[versions>>doc:sdmx:Glossary.Version.WebHome]] for all agencies.
--This subscribes to all Codelists of all versions for all agencies.
--
--AgencyID = AGENCY1
--
++//AgencyID = AGENCY1
  Id = CODELIST1
++Version = %//
--Version = %
++This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] CODELIST1 maintained by the agency
--This subscribes to all versions of Codelist CODELIST1 maintained by the agency
--
--AGENCY1
--
++//AGENCY1
  AgencyID = AGENCY1
--
  Id = %
++Version = %//
--Version = %
++This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of all [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] objects maintained by the agency
--This subscribes to all versions of all Codelist objects maintained by the agency
--
--AGENCY1
--
++//AGENCY1
  AgencyID = %
--
  Id = CODELIST1
++Version = %//
--Version = %
++This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] CODELIST1 maintained by the agency
--This subscribes to all versions of Codelist CODELIST1 maintained by the agency
++//AGENCY1//
--AGENCY1
++Note that if the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is to the latest [[version>>doc:sdmx:Glossary.Version.WebHome]] then this can be achieved by the * character
--Note that if the subscription is to the latest version then this can be achieved by the * character
++//i.e. Version = *//
--i.e. Version = *
++Note that a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] using the URN mechanism cannot use wildcard characters.
--Note that a subscription using the URN mechanism cannot use wildcard characters.
--
  === 7.5.4 Structural Repository Events ===
--Whenever a maintainable artefact (data structure definition, concept scheme, codelist, metadata structure definition, category scheme, etc.) is added to, deleted from, or modified in the structural metadata repository, a structural metadata event is triggered. Subscriptions may be set up to monitor all such events, or focus on specific artefacts such as a Data Structure Definition.
++Whenever a [[maintainable artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] ([[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[codelist>>doc:sdmx:Glossary.Code list.WebHome]], [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]], etc.) is added to, deleted from, or modified in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository, a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] event is triggered. [[Subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] may be set up to monitor all such events, or focus on specific [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]].
  === 7.5.5 Registration Events ===
--Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
++Whenever a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadata-set is registered a registration event is created. A [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
++(% style="width:974.294px" %)
++|(% style="width:295px" %)**Selector**|(% style="width:677px" %)**Comment**
++|(% style="width:295px" %)DataProvider|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered by the specified [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] will activate the notification.
++|(% style="width:295px" %)ProvisionAgreement|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for the [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] will activate the notification.
++|(% style="width:295px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (&[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]])|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for the specified [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (or [[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]) will activate the notification.
++|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] (or [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]]) that are based on the specified [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] will activate the notification.
++|(% style="width:295px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] that are categorised by the [[category>>doc:sdmx:Glossary.Category.WebHome]].
--|**Selector**|**Comment**
--|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
--|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
--|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
--|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
--|**Selector**|**Comment**
--| |activate the notification.
--|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
--
  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
  == 7.6 Notification ==
@@ -1504,26 +1504,26 @@
  === 7.6.1 Logical Class Diagram ===
++[[image:1747829675568-610.png]]
--==== Figure 20: Logical Class Diagram of the Notification ====
++(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
++**Figure 20: Logical Class Diagram of the Notification**
--A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
++A [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is an XML document that is sent to a user via email or http POST whenever a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is activated. It is an asynchronous one-way message.
--Regardless of the registry component that caused the event to be triggered, the following common information is in the message:
++Regardless of the registry [[component>>doc:sdmx:Glossary.Component.WebHome]] 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 that caused the event
--* The URN of the Subscription that produced the notification
++* The URN of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that caused the event
++* The URN of the [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that produced the [[notification>>doc:sdmx:Glossary.Notification.WebHome]]
  * Event Action: Add, Replace, or Delete.
--Additionally, supplementary information may be contained in the notification as detailed below.
++Additionally, supplementary information may be contained in the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] as detailed below.
  === 7.6.2 Structural Event Component ===
--The notification will contain the MaintainableArtefact that triggered the event in a form similar to the SDMX-ML structural message (using elements from that namespace).
++The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the MaintainableArtefact that triggered the event in a form similar to the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] structural message (using elements from that namespace).
  === 7.6.3 Registration Event Component ===
--The notification will contain the Registration.
--
--
++The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the Registration.

1747824504225-229.png

Author

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

Size

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

Content

1747829078194-749.png

Author

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

Size

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

Content

1747829109466-595.png

Author

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

Size

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

Content

1747829139951-378.png

Author

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

Size

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

Content

1747829204737-370.png

Author

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

Size

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

Content

1747829290890-122.png

Author

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

Size

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

Content

1747829477882-750.png

Author

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

Size

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

Content

1747829554603-150.png

Author

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

Size

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

Content

1747829675568-610.png

Author

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

Size

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

Content

1747832400104-286.png

Author

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

Size

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

Content

1747994320263-112.png

Author

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

Size

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

Content

SUZ.Methodology.Code.MethodologyClass[0]

SKMS.Methodology.Code.MethodologyClass[0]