Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -231,7 +231,7 @@ 231 231 ))) 232 232 |indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset. 233 233 234 -=== =={{id name="_Toc90799"/}}5.2.5 Data Discovery =====234 +=== 5.2.5 Data Discovery === 235 235 236 236 The Data Discovery Service implements the following Registry Interfaces: 237 237 ... ... @@ -238,7 +238,7 @@ 238 238 * QueryRegistrationRequest 239 239 * QueryRegistrationResponse 240 240 241 -=== =={{id name="_Toc90800"/}}5.2.6 Subscription and Notification =====241 +=== 5.2.6 Subscription and Notification === 242 242 243 243 The Subscription and Notification Service implements the following Registry Interfaces: 244 244 ... ... @@ -257,7 +257,7 @@ 257 257 258 258 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. 259 259 260 -=== =={{id name="_Toc90801"/}}5.2.7 Registry Behaviour =====260 +=== 5.2.7 Registry Behaviour === 261 261 262 262 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. 263 263