Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 26.1
edited by Helena
on 2025/05/15 14:38
Change comment: There is no comment for this version
To version 22.1
edited by Helena
on 2025/05/15 14:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -183,11 +183,11 @@
183 183  
184 184  === {{id name="_Toc93847"/}}5.2.2 Structure Submission Service ===
185 185  
186 -The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
186 +The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
187 187  
188 188  === {{id name="_Toc93848"/}}5.2.3 Structure Query Service ===
189 189  
190 -The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
190 +The registry must support a mechanism for querying for structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__ [[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. The registry response to this query mechanism is the SDMX Structure message, which has as its root node:
191 191  
192 192  * Structure
193 193  
... ... @@ -329,12 +329,14 @@
329 329  
330 330  The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
331 331  
332 -* //nnotable//
332 +* //Annotable//
333 333  * //Identifiable//
334 334  * //Nameable//
335 335  * //Versionable//
336 336  * //Maintainable//
337 337  
338 +:
339 +
338 338  (((
339 339  (% style="width:1052.29px" %)
340 340  |**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
... ... @@ -362,9 +362,9 @@
362 362  
363 363  **Table 1: Common Attributes of Object Types**
364 364  
365 -== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
367 +=== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ===
366 366  
367 -=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
369 +===== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers =====
368 368  
369 369  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.
370 370  
... ... @@ -741,7 +741,7 @@
741 741  
742 742  === {{id name="_Toc93862"/}}7.1 Structural Definition Metadata ===
743 743  
744 -=== {{id name="_Toc93863"/}}7.1.1 Introduction ===
746 +===== {{id name="_Toc93863"/}}7.1.1 Introduction =====
745 745  
746 746  The SDMX Registry must have the ability to support agencies in their role of defining and disseminating structural metadata artefacts. These artefacts include data structure definitions, code lists, concepts etc. and are fully defined in the SDMX-IM. An authenticated agency may submit valid structural metadata definitions which must be stored in the registry. Note that the term “structural metadata” refers as a general term to all structural components (Data Structure Definitions, Metadata Structure Definitions, Code Lists, Concept Schemes, etc.)
747 747  
... ... @@ -808,7 +808,7 @@
808 808  
809 809  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
810 810  
811 -=== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
813 +===== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure =====
812 812  
813 813  The artefacts included in the structural definitions are:
814 814  
... ... @@ -817,19 +817,19 @@
817 817  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
818 818  * All types of Structure Usage (Dataflow, Metadataflow)
819 819  
820 -=== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===
822 +===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
821 821  
822 -==== 7.1.3.1 Structure Usage: Basic Concepts ====
824 +**7.1.3.1 Structure Usage: Basic Concepts**
823 823  
824 824  The Structure Usage defines, in its concrete classes of Dataflow and Metadataflow, which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more Category in one or more Category Scheme using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the Category Schemes.
825 825  
826 -==== 7.1.3.2 Structure Usage Schematic ====
828 +**7.1.3.2 Structure Usage Schematic**
827 827  
828 828  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_52097ab5.jpg||height="246" width="438"]]
829 829  
830 830  **Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
831 831  
832 -==== 7.1.3.3 Structure Usage Model ====
834 +**7.1.3.3 Structure Usage Model**
833 833  
834 834  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_302cc1a2.jpg||height="548" width="578"]]
835 835