Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -192,10 +192,8 @@ 192 192 193 193 In addition to these interfaces the registry must support a mechanism for querying for structural metadata. This is detailed in 5.2.2. 194 194 195 -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 195 +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. 196 196 197 -“Response” document. 198 - 199 199 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. 200 200 201 201 == 5.2 Registry Services == ... ... @@ -294,15 +294,13 @@ 294 294 295 295 3The Registration has an action attribute which takes one of the following values: 296 296 297 -|((( 298 -**Action** 295 +|(% style="width:249px" %)((( 296 +**Action Attribute Value** 297 +)))|(% style="width:1622px" %)**Behaviour** 298 +|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry 299 +|(% style="width:249px" %)Replace|(% style="width:1622px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 300 +|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 299 299 300 -**Attribute Value** 301 -)))|**Behaviour** 302 -|Append|Add this registration to the registry 303 -|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 304 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 305 - 306 306 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: 307 307 308 308 |**Boolean Attribute**|**Behaviour if Value is “true”** ... ... @@ -318,10 +318,9 @@ 318 318 319 319 The Data and Metadata Discovery Service implements the following Registry Interfaces: 320 320 321 - QueryRegistrationRequest 317 +* QueryRegistrationRequest 318 +* QueryRegistrationResponse 322 322 323 - QueryRegistrationResponse 324 - 325 325 === 5.2.6 Subscription and Notification === 326 326 327 327 The Subscription and Notification Service implements the following Registry Interfaces: ... ... @@ -345,13 +345,12 @@ 345 345 346 346 The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. 347 347 348 -|**Interface**|**Behaviour** 349 -|All|((( 343 +|(% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour** 344 +|(% style="width:143px" %)All|(% style="width:1729px" %)((( 350 350 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: 351 351 352 352 * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list. 353 353 * Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 354 - 355 355 * Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 356 356 * validTo 357 357 * validFrom ... ... @@ -360,19 +360,20 @@ 360 360 * uri 361 361 * isExternalReference 362 362 363 -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. 364 -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: 357 +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. 365 365 366 -1. Not have the final attribute set to “true” 367 -1. Not be referenced from any other object in the Registry. 359 +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: 368 368 369 -1. The version rules in the SDMX Schema documentation MUST be obeyed. 361 +а) Not have the final attribute set to “true” 362 +b) Not be referenced from any other object in the Registry. 370 370 371 -* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed. 364 +4) The version rules in the SDMX Schema documentation MUST be obeyed. 365 + 366 +5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed. 372 372 ))) 373 -|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. 374 -|SubmitProvisioningRequest|No additional behaviour. 375 -|Submit Registration Request|((( 368 +|(% style="width:143px" %)SubmitStructureRequest|(% style="width:1729px" %)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. 369 +|(% style="width:143px" %)SubmitProvisioningRequest|(% style="width:1729px" %)No additional behaviour. 370 +|(% style="width:143px" %)Submit Registration Request|(% style="width:1729px" %)((( 376 376 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. 377 377 378 378 For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.