Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 22.1
edited by Helena
on 2025/05/15 14:33
Change comment: There is no comment for this version
To version 27.1
edited by Helena
on 2025/05/15 14:39
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>>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).
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).
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>>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:
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:
191 191  
192 192  * Structure
193 193  
... ... @@ -280,7 +280,7 @@
280 280  Subscription management involves a user submitting a subscription request which contains:
281 281  
282 282  * a query or constraint expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific dataflow, or for a domain category, or changes to a Data Structure Definition).
283 -* a list of URIs or endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address);
283 +* a list of URIs or endpoints to which an XML notification message can be sent. Supported endpoint types will be email (mailto~: ) and HTTP POST (a normal http:~/~/ address);
284 284  * request for a list of submitted subscriptions;
285 285  * deletion of a subscription;
286 286  
... ... @@ -329,14 +329,12 @@
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 -* //Annotable//
332 +* //nnotable//
333 333  * //Identifiable//
334 334  * //Nameable//
335 335  * //Versionable//
336 336  * //Maintainable//
337 337  
338 -:
339 -
340 340  (((
341 341  (% style="width:1052.29px" %)
342 342  |**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
... ... @@ -364,9 +364,9 @@
364 364  
365 365  **Table 1: Common Attributes of Object Types**
366 366  
367 -=== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ===
365 +== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
368 368  
369 -===== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers =====
367 +=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
370 370  
371 371  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.
372 372  
... ... @@ -743,7 +743,7 @@
743 743  
744 744  === {{id name="_Toc93862"/}}7.1 Structural Definition Metadata ===
745 745  
746 -===== {{id name="_Toc93863"/}}7.1.1 Introduction =====
744 +=== {{id name="_Toc93863"/}}7.1.1 Introduction ===
747 747  
748 748  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.)
749 749  
... ... @@ -810,7 +810,7 @@
810 810  
811 811  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
812 812  
813 -===== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure =====
811 +=== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
814 814  
815 815  The artefacts included in the structural definitions are:
816 816  
... ... @@ -819,19 +819,19 @@
819 819  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
820 820  * All types of Structure Usage (Dataflow, Metadataflow)
821 821  
822 -===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
820 +=== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===
823 823  
824 -**7.1.3.1 Structure Usage: Basic Concepts**
822 +==== 7.1.3.1 Structure Usage: Basic Concepts ====
825 825  
826 826  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.
827 827  
828 -**7.1.3.2 Structure Usage Schematic**
826 +==== 7.1.3.2 Structure Usage Schematic ====
829 829  
830 830  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_52097ab5.jpg||height="246" width="438"]]
831 831  
832 832  **Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
833 833  
834 -**7.1.3.3 Structure Usage Model**
832 +==== 7.1.3.3 Structure Usage Model ====
835 835  
836 836  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_302cc1a2.jpg||height="548" width="578"]]
837 837