Skip to Content
Last modified by Artur on 2025/09/30 13:28
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.5
edited by Helena
on 2025/06/08 16:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -89,7 +89,7 @@
89 89  
90 90  In that context, the term “Metadata” refers to reference metadata.
91 91  
92 -=== {{id name="_Toc90785"/}}3.3 Registration ===
92 +== 3.3 Registration ==
93 93  
94 94  Publishing the data and reference metadata involves the following steps for a Data/Metadata Provider:
95 95  
... ... @@ -100,13 +100,13 @@
100 100  
101 101  **Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
102 102  
103 -=== {{id name="_Toc90786"/}}3.4 Notification ===
103 +== 3.4 Notification ==
104 104  
105 105  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
106 106  
107 107  • 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.
108 108  
109 -=== {{id name="_Toc90787"/}}3.5 Discovery ===
109 +== 3.5 Discovery ==
110 110  
111 111  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:
112 112  
... ... @@ -118,9 +118,9 @@
118 118  
119 119  **Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
120 120  
121 -= {{id name="_Toc90788"/}}4 SDMX Registry/Repository Architecture =
121 += 4 SDMX Registry/Repository Architecture =
122 122  
123 -=== {{id name="_Toc90789"/}}4.1 Architectural Schematic ===
123 +== 4.1 Architectural Schematic ==
124 124  
125 125  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.
126 126  
... ... @@ -128,7 +128,7 @@
128 128  
129 129  **Figure 4: Schematic of the Registry Content and Services**
130 130  
131 -=== {{id name="_Toc90790"/}}4.2 Structural Metadata Repository ===
131 +== 4.2 Structural Metadata Repository ==
132 132  
133 133  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.
134 134  
... ... @@ -139,15 +139,15 @@
139 139  
140 140  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.
141 141  
142 -=== {{id name="_Toc90791"/}}4.3 Provisioning Metadata Repository ===
142 +== 4.3 Provisioning Metadata Repository ==
143 143  
144 144  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.
145 145  
146 146  This layer is supported by the Data and Metadata Registration Service.
147 147  
148 -= {{id name="_Toc90792"/}}5 Registry Interfaces and Services =
148 += 5 Registry Interfaces and Services =
149 149  
150 -=== {{id name="_Toc90793"/}}5.1 Registry Interfaces ===
150 +== 5.1 Registry Interfaces ==
151 151  
152 152  The Registry Interfaces are:
153 153  
... ... @@ -173,17 +173,17 @@
173 173  
174 174  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.
175 175  
176 -=== {{id name="_Toc90794"/}}5.2 Registry Services ===
176 +== 5.2 Registry Services ==
177 177  
178 -===== {{id name="_Toc90795"/}}5.2.1 Introduction =====
178 +=== 5.2.1 Introduction ===
179 179  
180 180  The services described in this section do not imply that each is implemented as a discrete web service.
181 181  
182 -===== {{id name="_Toc90796"/}}5.2.2 Structure Submission Service =====
182 +=== 5.2.2 Structure Submission Service ===
183 183  
184 184  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).
185 185  
186 -===== {{id name="_Toc90797"/}}5.2.3 Structure Query Service =====
186 +=== 5.2.3 Structure Query Service ===
187 187  
188 188  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:
189 189