Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 21.7
edited by Helena
on 2025/06/08 16:30
Change comment: There is no comment for this version
To version 21.8
edited by Helena
on 2025/06/08 16:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -163,7 +163,7 @@
163 163  
164 164  The registry interfaces are invoked in one of two ways:
165 165  
166 -*
166 +*
167 167  *1. The interface is the name of the root node of the SDMX-ML document
168 168  *1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the SDMX-ML document.
169 169  
... ... @@ -263,28 +263,26 @@
263 263  
264 264  Given the above, the behaviour described in the following table concerns either draft Artefacts using semantic versioning or any Artefacts using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft Artefact that follows semantic versioning, unless a newer version is introduced according to the semantic versioning rules. Furthermore, even when draft Artefacts are submitted, the registry has to verify semantic versioning is respected against the previous non-draft versions. It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned Artefacts applies to externally shared Artefacts. This means that any system may internally perform any change within a version of an Artefact, until the latter is shared outside of that system or becomes public. Then (as also explained in the SDMX Standards Section 6 “Technical Notes”) the Artefacts must adhere to the Semantic Versioning rules.
265 265  
266 -|**Interface**|**Behaviour**
267 -|All|(((
266 +(% style="width:982.835px" %)
267 +|(% style="width:217px" %)**Interface**|(% style="width:763px" %)**Behaviour**
268 +|(% style="width:217px" %)All|(% style="width:763px" %)(((
268 268  1. If the action is set to “replace” (or a maintainable Artefact is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted.
269 269  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.
270 270  1. If the action is set to “delete” (or a maintainable Artefact is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must:
271 271  
272 -1. Be a draft version.
273 +a) Be a draft version.
274 +b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
273 273  
274 -b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
275 -
276 276  4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
277 277  )))
278 -|Structure submission|(((
279 -Structures are submitted at the level of the
280 -
281 -Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
278 +|(% style="width:217px" %)Structure submission|(% style="width:763px" %)(((
279 +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.
282 282  )))
283 -|SubmitRegistrationRequest|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. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
281 +|(% style="width:217px" %)SubmitRegistrationRequest|(% style="width:763px" %)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. For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX data query.
284 284  
285 -= {{id name="_Toc90802"/}}6 Identification of SDMX Objects =
283 += 6 Identification of SDMX Objects =
286 286  
287 -=== {{id name="_Toc90803"/}}6.1 Identification, Versioning, and Maintenance ===
285 +== 6.1 Identification, Versioning, and Maintenance ==
288 288  
289 289  All major classes of the SDMX Information model inherit from one of:
290 290  
... ... @@ -293,7 +293,7 @@
293 293  * //**VersionableArtefact**// – this has all of the above features plus a version number, according to the SDMX versioning rules in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
294 294  * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object.
295 295  
296 -===== {{id name="_Toc90804"/}}6.1.1 Identification, Naming, Versioning, and Maintenance Model =====
294 +=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
297 297  
298 298  [[image:SDMX 3.1 Section 5_en_4a9b2cfc.jpg||height="688" width="587"]]
299 299  
... ... @@ -302,13 +302,11 @@
302 302  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
303 303  
304 304  * //Annotable//
303 +* //Identifiable//
304 +* //Nameable//
305 +* //Versionable//
306 +* //Maintainable//
305 305  
306 -//Identifiable// • //Nameable//
307 -
308 -• //Versionable//
309 -
310 -• //Maintainable//
311 -
312 312  | |(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
313 313  | |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
314 314  | |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
... ... @@ -353,9 +353,9 @@
353 353  
354 354  **Table 1: Common Attributes of Object Types**
355 355  
356 -=== {{id name="_Toc90805"/}}6.2 Unique identification of SDMX objects ===
352 +== 6.2 Unique identification of SDMX objects ==
357 357  
358 -===== {{id name="_Toc90806"/}}6.2.1 Agencies and Metadata Providers =====
354 +=== 6.2.1 Agencies and Metadata Providers ===
359 359  
360 360  The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
361 361  
... ... @@ -610,7 +610,7 @@
610 610  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
611 611  
612 612  |**Classname**|**Ending URN pattern**|**Example**
613 -|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
609 +|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
614 614  |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
615 615  |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
616 616  |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
... ... @@ -835,7 +835,7 @@
835 835  The artefacts included in the structural definitions are:
836 836  
837 837  * All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme, Agency Scheme, Data Provider Scheme, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
838 -* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
834 +* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
839 839  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
840 840  * All types of Structure Usage (Dataflow, Metadataflow)
841 841  
... ... @@ -859,13 +859,13 @@
859 859  
860 860  In addition to the maintenance of the Dataflow and the Metadataflow, the following links must be maintained in the registry:
861 861  
862 -1.
858 +1.
863 863  1*. Dataflow to Data Structure Definition
864 864  1*. Metadataflow to Metadata Structure Definition
865 865  
866 866  The following links may be created by means of a Categorisation
867 867  
868 -1.
864 +1.
869 869  1*. Categorisation to Dataflow and Category
870 870  1*. Categorisation to Metadataflow and Category
871 871  
... ... @@ -1061,7 +1061,7 @@
1061 1061  1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
1062 1062  1. A selector which specifies which type of events are of interest. The set of event types is:
1063 1063  
1064 -:
1060 +:
1065 1065  ::
1066 1066  
1067 1067  (((