Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 21.5
edited by Helena
on 2025/06/08 16:29
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

Summary

Details

Page properties
Content
... ... @@ -191,7 +191,7 @@
191 191  
192 192  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]]
193 193  
194 -===== {{id name="_Toc90798"/}}5.2.4 Data and Reference Metadata Registration Service =====
194 +=== 5.2.4 Data and Reference Metadata Registration Service ===
195 195  
196 196  This service must implement the following Registry Interfaces:
197 197  
... ... @@ -214,23 +214,24 @@
214 214  
215 215  The Registration has an action attribute which takes one of the following values:
216 216  
217 -|**Action Attribute Value**|**Behaviour**
218 -|Append|Add this registration to the registry
219 -|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
220 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
217 +(% style="width:893.835px" %)
218 +|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour**
219 +|(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry
220 +|(% 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
221 +|(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
221 221  
222 222  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:
223 223  
224 -|**Boolean Attribute**|**Behaviour if Value is “true”**
225 -|indexTimeSeries|A compliant indexing application must index all the time series keys
226 -|indexDataSet|(((
225 +(% style="width:896.835px" %)
226 +|**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”**
227 +|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys
228 +|indexDataSet|(% style="width:712px" %)(((
227 227  A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset.
228 -
229 229  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
230 230  )))
231 -|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
232 +|indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset.
232 232  
233 -===== {{id name="_Toc90799"/}}5.2.5 Data Discovery =====
234 +=== 5.2.5 Data Discovery ===
234 234  
235 235  The Data Discovery Service implements the following Registry Interfaces:
236 236  
... ... @@ -237,7 +237,7 @@
237 237  * QueryRegistrationRequest
238 238  * QueryRegistrationResponse
239 239  
240 -===== {{id name="_Toc90800"/}}5.2.6 Subscription and Notification =====
241 +=== 5.2.6 Subscription and Notification ===
241 241  
242 242  The Subscription and Notification Service implements the following Registry Interfaces:
243 243  
... ... @@ -256,7 +256,7 @@
256 256  
257 257  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.
258 258  
259 -===== {{id name="_Toc90801"/}}5.2.7 Registry Behaviour =====
260 +=== 5.2.7 Registry Behaviour ===
260 260  
261 261  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.
262 262