Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -814,11 +814,14 @@ 814 814 815 815 The artefacts included in the structural definitions are: 816 816 817 -* 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) 818 -* All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}} 819 -* All types of Structure (Data Structure Definition, Metadata Structure Definition) 820 -* All types of Structure Usage (Dataflow, Metadataflow) 817 +• 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) 821 821 819 +• All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}} 820 + 821 +• All types of Structure (Data Structure Definition, Metadata Structure Definition) 822 + 823 +• All types of Structure Usage (Dataflow, Metadataflow) 824 + 822 822 ===== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===== 823 823 824 824 **7.1.3.1 Structure Usage: Basic Concepts** ... ... @@ -847,9 +847,9 @@ 847 847 * Categorisation to Dataflow and Category 848 848 * Categorisation to Metadataflow and Category 849 849 850 -== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning == 853 +=== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning === 851 851 852 -=== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts === 855 +===== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts ===== 853 853 854 854 Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the SDMX-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service level agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and timeliness metadata can be supported by this framework which makes it practical to implement information supply chain monitoring. 855 855 ... ... @@ -857,7 +857,7 @@ 857 857 858 858 Although the Provision Agreement directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of structural metadata. 859 859 860 -=== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case === 863 +===== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case ===== 861 861 862 862 An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme. 863 863 ... ... @@ -879,9 +879,9 @@ 879 879 880 880 A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider or Metadata Provider and a Dataflow or Metadataflow Definition. The Data/Metadata Provider and the Dataflow/Metadataflow must exist already in order to set up a Metadata Provision or Provision Agreement. 881 881 882 -== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints == 885 +=== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints === 883 883 884 -=== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts === 887 +===== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===== 885 885 886 886 Constraints are, effectively, lists of the valid or actual content of data and metadata. Constraints can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD. A Constraint can comprise a list of keys or a list of content (usually code values) of a specific component such as a dimension or attribute. 887 887 ... ... @@ -945,14 +945,17 @@ 945 945 946 946 The Registration has an action attribute which takes one of the following values: 947 947 951 +: 952 + 948 948 ((( 949 -(% style="width:679.294px" %) 950 -|(% style="width:196px" %)**Action Attribute Value**|(% style="width:480px" %)**Behaviour** 951 -|(% style="width:196px" %)Append|(% style="width:480px" %)Add this Registration to the registry 952 -|(% style="width:196px" %)Replace|(% style="width:480px" %)((( 953 -Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest 954 +|**Action Attribute Value**|**Behaviour** 955 +|Append|Add this Registration to the registry 956 +|Replace|((( 957 +Replace the existing Registration with identified by the id in the 958 + 959 +Registration of the SubmitRegistrationRequest 954 954 ))) 955 -| (% style="width:196px" %)Delete|(% style="width:480px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest961 +|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest 956 956 ))) 957 957 958 958 [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_bc1dcdec.jpg||height="575" width="579"]]