Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 21.8
edited by Helena
on 2025/06/08 16:32
Change comment: There is no comment for this version
To version 21.7
edited by Helena
on 2025/06/08 16:30
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,26 +263,28 @@
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 -(% style="width:982.835px" %)
267 -|(% style="width:217px" %)**Interface**|(% style="width:763px" %)**Behaviour**
268 -|(% style="width:217px" %)All|(% style="width:763px" %)(((
266 +|**Interface**|**Behaviour**
267 +|All|(((
269 269  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.
270 270  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.
271 271  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:
272 272  
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.
272 +1. Be a draft version.
275 275  
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 -|(% 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.
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.
280 280  )))
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.
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.
282 282  
283 -= 6 Identification of SDMX Objects =
285 += {{id name="_Toc90802"/}}6 Identification of SDMX Objects =
284 284  
285 -== 6.1 Identification, Versioning, and Maintenance ==
287 +=== {{id name="_Toc90803"/}}6.1 Identification, Versioning, and Maintenance ===
286 286  
287 287  All major classes of the SDMX Information model inherit from one of:
288 288  
... ... @@ -291,7 +291,7 @@
291 291  * //**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.
292 292  * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object.
293 293  
294 -=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
296 +===== {{id name="_Toc90804"/}}6.1.1 Identification, Naming, Versioning, and Maintenance Model =====
295 295  
296 296  [[image:SDMX 3.1 Section 5_en_4a9b2cfc.jpg||height="688" width="587"]]
297 297  
... ... @@ -300,11 +300,13 @@
300 300  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
301 301  
302 302  * //Annotable//
303 -* //Identifiable//
304 -* //Nameable//
305 -* //Versionable//
306 -* //Maintainable//
307 307  
306 +//Identifiable// • //Nameable//
307 +
308 +• //Versionable//
309 +
310 +• //Maintainable//
311 +
308 308  | |(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
309 309  | |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
310 310  | |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
... ... @@ -349,9 +349,9 @@
349 349  
350 350  **Table 1: Common Attributes of Object Types**
351 351  
352 -== 6.2 Unique identification of SDMX objects ==
356 +=== {{id name="_Toc90805"/}}6.2 Unique identification of SDMX objects ===
353 353  
354 -=== 6.2.1 Agencies and Metadata Providers ===
358 +===== {{id name="_Toc90806"/}}6.2.1 Agencies and Metadata Providers =====
355 355  
356 356  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.
357 357  
... ... @@ -606,7 +606,7 @@
606 606  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
607 607  
608 608  |**Classname**|**Ending URN pattern**|**Example**
609 -|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
613 +|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
610 610  |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
611 611  |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
612 612  |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
... ... @@ -831,7 +831,7 @@
831 831  The artefacts included in the structural definitions are:
832 832  
833 833  * 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)
834 -* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
838 +* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
835 835  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
836 836  * All types of Structure Usage (Dataflow, Metadataflow)
837 837  
... ... @@ -855,13 +855,13 @@
855 855  
856 856  In addition to the maintenance of the Dataflow and the Metadataflow, the following links must be maintained in the registry:
857 857  
858 -1.
862 +1.
859 859  1*. Dataflow to Data Structure Definition
860 860  1*. Metadataflow to Metadata Structure Definition
861 861  
862 862  The following links may be created by means of a Categorisation
863 863  
864 -1.
868 +1.
865 865  1*. Categorisation to Dataflow and Category
866 866  1*. Categorisation to Metadataflow and Category
867 867  
... ... @@ -1057,7 +1057,7 @@
1057 1057  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.
1058 1058  1. A selector which specifies which type of events are of interest. The set of event types is:
1059 1059  
1060 -:
1064 +:
1061 1061  ::
1062 1062  
1063 1063  (((