Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -292,15 +292,13 @@ 292 292 293 293 3The Registration has an action attribute which takes one of the following values: 294 294 295 -|((( 296 -**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 297 297 298 -**Attribute Value** 299 -)))|**Behaviour** 300 -|Append|Add this registration to the registry 301 -|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 302 -|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 303 - 304 304 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: 305 305 306 306 |**Boolean Attribute**|**Behaviour if Value is “true”** ... ... @@ -316,10 +316,9 @@ 316 316 317 317 The Data and Metadata Discovery Service implements the following Registry Interfaces: 318 318 319 - QueryRegistrationRequest 317 +* QueryRegistrationRequest 318 +* QueryRegistrationResponse 320 320 321 - QueryRegistrationResponse 322 - 323 323 === 5.2.6 Subscription and Notification === 324 324 325 325 The Subscription and Notification Service implements the following Registry Interfaces: ... ... @@ -343,13 +343,12 @@ 343 343 344 344 The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. 345 345 346 -|**Interface**|**Behaviour** 347 -|All|((( 343 +|(% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour** 344 +|(% style="width:143px" %)All|(% style="width:1729px" %)((( 348 348 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: 349 349 350 350 * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list. 351 351 * Description - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 352 - 353 353 * Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 354 354 * validTo 355 355 * validFrom ... ... @@ -358,26 +358,25 @@ 358 358 * uri 359 359 * isExternalReference 360 360 361 -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. 362 -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. 363 363 364 -1. Not have the final attribute set to “true” 365 -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: 366 366 367 -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. 368 368 369 -* 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. 370 370 ))) 371 -|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. 372 -|SubmitProvisioningRequest|No additional behaviour. 373 -|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" %)((( 374 374 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. 375 375 376 376 For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query. 377 377 ))) 378 378 379 - 380 - 381 381 = 6 Identification of SDMX Objects = 382 382 383 383 == 6.1 Identification, Versioning, and Maintenance == ... ... @@ -384,7 +384,6 @@ 384 384 385 385 All major classes of the SDMX Information model inherit from one of: 386 386 387 - 388 388 * **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. 389 389 * **NamableArtefact **- this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description, 390 390 * **VersionableArtefact **– this has all of the above features plus a version number and a validity period.