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

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

From 21.3 to 21.4 From 21.7 to 21.8

From version 21.4

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

Change comment: There is no comment for this version

To version 21.7

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -89,7 +89,7 @@
  In that context, the term “Metadata” refers to reference metadata.
--=== {{id name="_Toc90785"/}}3.3 Registration ===
++== 3.3 Registration ==
  Publishing the data and reference metadata involves the following steps for a Data/Metadata Provider:
@@ -100,13 +100,13 @@
  **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
--=== {{id name="_Toc90786"/}}3.4 Notification ===
++== 3.4 Notification ==
  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
  • registry support of a subscription-based notification service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the subscription request.
--=== {{id name="_Toc90787"/}}3.5 Discovery ===
++== 3.5 Discovery ==
  Discovering published data and reference metadata involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an SDMX-enabled data or reference metadata resource:
@@ -118,9 +118,9 @@
  **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
--= {{id name="_Toc90788"/}}4 SDMX Registry/Repository Architecture =
++= 4 SDMX Registry/Repository Architecture =
--=== {{id name="_Toc90789"/}}4.1 Architectural Schematic ===
++== 4.1 Architectural Schematic ==
  The architecture of the SDMX registry/repository is derived from the objectives stated above. It is a layered architecture that is founded by a structural metadata repository which supports a provisioning metadata repository which supports the registry services. These are all supported by the SDMX-ML schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the structural metadata required to drive these applications.
@@ -128,7 +128,7 @@
  **Figure 4: Schematic of the Registry Content and Services**
--=== {{id name="_Toc90790"/}}4.2 Structural Metadata Repository ===
++== 4.2 Structural Metadata Repository ==
  The basic layer is that of a structural metadata service which supports the lifecycle of SDMX structural metadata artefacts such as Maintenance Agencies, Data Structure Definitions, Metadata Structure Definitions, Provision Agreements, Processes etc. This layer is supported by the Structure Submission and Query Service.
@@ -139,15 +139,15 @@
  As of the initial version of SDMX 3.0 no messages are defined to support these artefacts; hence, users may need to use SDMX 2.1 Registry Interface messages, instead.
--=== {{id name="_Toc90791"/}}4.3 Provisioning Metadata Repository ===
++== 4.3 Provisioning Metadata Repository ==
  The function of this repository is to support the definition of the structural metadata that describes the various types of data-store which model SDMX-conformant databases or files, and to link to these data sources. These links can be specified for a data/metadata provider, for a specific data or metadata flow. In the SDMX model this is called the Provision or Metadata Provision Agreement.
  This layer is supported by the Data and Metadata Registration Service.
--= {{id name="_Toc90792"/}}5 Registry Interfaces and Services =
++= 5 Registry Interfaces and Services =
--=== {{id name="_Toc90793"/}}5.1 Registry Interfaces ===
++== 5.1 Registry Interfaces ==
  The Registry Interfaces are:
@@ -173,17 +173,17 @@
  It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the SDMX-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous.
--=== {{id name="_Toc90794"/}}5.2 Registry Services ===
++== 5.2 Registry Services ==
--===== {{id name="_Toc90795"/}}5.2.1 Introduction =====
++=== 5.2.1 Introduction ===
  The services described in this section do not imply that each is implemented as a discrete web service.
--===== {{id name="_Toc90796"/}}5.2.2 Structure Submission Service =====
++=== 5.2.2 Structure Submission Service ===
  The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
--===== {{id name="_Toc90797"/}}5.2.3 Structure Query Service =====
++=== 5.2.3 Structure Query Service ===
  The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
@@ -191,7 +191,7 @@
  The SDMX structural artefacts that may be queried are defined in the SDMX structure web service specification which is compatible with this release of the standard __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[->>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]][[rest/blob/master/doc/structures.md>>url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]]__[[url:https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]]
--===== {{id name="_Toc90798"/}}5.2.4 Data and Reference Metadata Registration Service =====
++=== 5.2.4 Data and Reference Metadata Registration Service ===
  This service must implement the following Registry Interfaces:
@@ -214,23 +214,24 @@
  The Registration has an action attribute which takes one of the following values:
--|**Action Attribute Value**|**Behaviour**
--|Append|Add this registration to the registry
--|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
--|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
++(% style="width:893.835px" %)
++|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour**
++|(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry
++|(% style="width:241px" %)Replace|(% style="width:650px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
++|(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
  The Registration has three Boolean attributes which may be present to determine how an SDMX compliant dataset or metadataset indexing application must index the datasets or metadatasets upon registration. The indexing application behaviour is as follows:
--|**Boolean Attribute**|**Behaviour if Value is “true”**
--|indexTimeSeries|A compliant indexing application must index all the time series keys
--|indexDataSet|(((
++(% style="width:896.835px" %)
++|**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”**
++|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys
++|indexDataSet|(% style="width:712px" %)(((
  A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset.
--
  Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
  )))
--|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
++|indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
--===== {{id name="_Toc90799"/}}5.2.5 Data Discovery =====
++=== 5.2.5 Data Discovery ===
  The Data Discovery Service implements the following Registry Interfaces:
@@ -237,7 +237,7 @@
  * QueryRegistrationRequest
  * QueryRegistrationResponse
--===== {{id name="_Toc90800"/}}5.2.6 Subscription and Notification =====
++=== 5.2.6 Subscription and Notification ===
  The Subscription and Notification Service implements the following Registry Interfaces:
@@ -256,7 +256,7 @@
  Notification requires that the structural metadata repository and the provisioning metadata repository monitor any event which is of interest to a user (the object of a subscription request query), and to issue an SDMX notification document to the endpoints specified in the relevant subscriptions.
--===== {{id name="_Toc90801"/}}5.2.7 Registry Behaviour =====
++=== 5.2.7 Registry Behaviour ===
  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. It should be noted, though, that as of SDMX 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all Maintainable Artefacts. Moreover, while the old versioning scheme is allowed, given there is no more a "final" flag, there is no way guaranteeing the consistency across version of a Maintainable, unless semantic versioning is used.