Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -192,8 +192,10 @@ 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 “Response” document.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 196 196 197 +“Response” document. 198 + 197 197 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. 198 198 199 199 == 5.2 Registry Services == ... ... @@ -292,13 +292,15 @@ 292 292 293 293 3The Registration has an action attribute which takes one of the following values: 294 294 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 297 +|((( 298 +**Action** 301 301 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 + 302 302 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: 303 303 304 304 |**Boolean Attribute**|**Behaviour if Value is “true”** ... ... @@ -314,9 +314,10 @@ 314 314 315 315 The Data and Metadata Discovery Service implements the following Registry Interfaces: 316 316 317 -* QueryRegistrationRequest 318 -* QueryRegistrationResponse 321 + QueryRegistrationRequest 319 319 323 + QueryRegistrationResponse 324 + 320 320 === 5.2.6 Subscription and Notification === 321 321 322 322 The Subscription and Notification Service implements the following Registry Interfaces: ... ... @@ -340,12 +340,13 @@ 340 340 341 341 The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. 342 342 343 -| (% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour**344 -| (% style="width:143px" %)All|(% style="width:1729px" %)(((348 +|**Interface**|**Behaviour** 349 +|All|((( 345 345 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: 346 346 347 347 * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list. 348 348 * Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 354 + 349 349 * Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 350 350 * validTo 351 351 * validFrom ... ... @@ -354,25 +354,26 @@ 354 354 * uri 355 355 * isExternalReference 356 356 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. 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: 358 358 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: 366 +1. Not have the final attribute set to “true” 367 +1. Not be referenced from any other object in the Registry. 360 360 361 -а) Not have the final attribute set to “true” 362 -b) Not be referenced from any other object in the Registry. 369 +1. The version rules in the SDMX Schema documentation MUST be obeyed. 363 363 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. 371 +* The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed. 367 367 ))) 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" %)(((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|((( 371 371 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. 372 372 373 373 For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query. 374 374 ))) 375 375 381 + 382 + 376 376 = 6 Identification of SDMX Objects = 377 377 378 378 == 6.1 Identification, Versioning, and Maintenance == ... ... @@ -379,6 +379,7 @@ 379 379 380 380 All major classes of the SDMX Information model inherit from one of: 381 381 389 + 382 382 * **IdentifiableArtefact** - this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations. 383 383 * **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description, 384 384 * **VersionableArtefact **– this has all of the above features plus a version number and a validity period.