Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -340,13 +340,12 @@ 340 340 341 341 The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages. 342 342 343 -|**Interface**|**Behaviour** 344 -|All|((( 343 +|(% style="width:143px" %)**Interface**|(% style="width:1729px" %)**Behaviour** 344 +|(% style="width:143px" %)All|(% style="width:1729px" %)((( 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. 349 - 350 350 * Annotation - this applies to the Maintainable object and its contained elements, such a Code in a Code list. 351 351 * validTo 352 352 * validFrom ... ... @@ -355,19 +355,20 @@ 355 355 * uri 356 356 * isExternalReference 357 357 358 -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. 359 -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. 360 360 361 -1. Not have the final attribute set to “true” 362 -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: 363 363 364 -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. 365 365 366 -* 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. 367 367 ))) 368 -|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. 369 -|SubmitProvisioningRequest|No additional behaviour. 370 -|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" %)((( 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.