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

Summary

Details

Page properties
Content
... ... @@ -875,9 +875,9 @@
875 875  
876 876  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.
877 877  
878 -=== {{id name="_Toc90818"/}}7.3 Data and Metadata Constraints ===
878 +== 7.3 Data and Metadata Constraints ==
879 879  
880 -===== {{id name="_Toc90819"/}}7.3.1 Data and Metadata Constraints: Basic Concepts =====
880 +=== 7.3.1 Data and Metadata Constraints: Basic Concepts ===
881 881  
882 882  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.
883 883  
... ... @@ -891,13 +891,13 @@
891 891  
892 892  In addition, DataAvailabilityConstraints can be extremely useful in a data visualisation system, such as dissemination of statistics on a website. In such a system a Cube Region can be used to specify the Dimension codes that actually exist in a data source (these can be used to build relevant selection tables).
893 893  
894 -===== {{id name="_Toc90820"/}}7.3.2 Data and Metadata Constraints: Schematic =====
894 +=== 7.3.2 Data and Metadata Constraints: Schematic ===
895 895  
896 896  [[image:SDMX 3.1 Section 5_en_28d0cadc.jpg||height="326" width="580"]]
897 897  
898 898  **Figure 14: Schematic of the Constraint and the Artefacts that can be constrained**
899 899  
900 -===== {{id name="_Toc90821"/}}7.3.3 Data and Metadata Constraints: Model =====
900 +=== 7.3.3 Data and Metadata Constraints: Model ===
901 901  
902 902  [[image:SDMX 3.1 Section 5_en_a3184f6a.jpg||height="298" width="579"]]
903 903  
... ... @@ -913,9 +913,9 @@
913 913  
914 914  The content of the Constraint can be found in the SDMX Information Model document.
915 915  
916 -=== {{id name="_Toc90822"/}}7.4 Data Registration ===
916 +== 7.4 Data Registration ==
917 917  
918 -===== {{id name="_Toc90823"/}}7.4.1 Basic Concepts =====
918 +=== 7.4.1 Basic Concepts ===
919 919  
920 920  A Data Provider has published a new dataset conforming to an existing Dataflow (and hence Data Structure Definition). This is implemented as either a web-accessible SDMXML file, or in a database which has a web-services interface capable of responding to an SDMX RESTful query with an SDMX-ML data stream.
921 921  
... ... @@ -925,15 +925,15 @@
925 925  
926 926  SDMX-RR supports dataset registration via the Registration Request, which can be created by the Data Provider (giving the Data Provider maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response.
927 927  
928 -===== {{id name="_Toc90824"/}}7.4.2 The Registration Request =====
928 +=== 7.4.2 The Registration Request ===
929 929  
930 -**7.4.2.1 Registration Request Schematic**
930 +==== 7.4.2.1 Registration Request Schematic ====
931 931  
932 932  [[image:SDMX 3.1 Section 5_en_293a2ea6.jpg||height="337" width="554"]]
933 933  
934 934  **Figure 16: Schematic of the Objects Concerned with Registration**
935 935  
936 -**7.4.2.2 Registration Request Model**
936 +==== 7.4.2.2 Registration Request Model ====
937 937  
938 938  The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per dataset to be registered. The Registration can optionally have information, which has been extracted from the Registration:
939 939  
... ... @@ -945,13 +945,11 @@
945 945  
946 946  The Registration has an action attribute which takes one of the following values:
947 947  
948 -:
949 -
950 950  (((
951 -|**Action Attribute Value**|**Behaviour**
952 -|Append|Add this Registration to the registry
953 -|Replace|Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
954 -|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
949 +|(% style="width:224px" %)**Action Attribute Value**|(% style="width:1457px" %)**Behaviour**
950 +|(% style="width:224px" %)Append|(% style="width:1457px" %)Add this Registration to the registry
951 +|(% style="width:224px" %)Replace|(% style="width:1457px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
952 +|(% style="width:224px" %)Delete|(% style="width:1457px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
955 955  )))
956 956  
957 957  [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]]
... ... @@ -970,30 +970,24 @@
970 970  
971 971  https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
972 972  
973 -:
974 -
975 975  (((
976 -|**Indexing Required**|**Registration Process Activity**
977 -|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
978 -|indexDataSet|Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
979 -|indexReportingPeriod|(((
972 +(% style="width:918.835px" %)
973 +|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
974 +|indexTimeSeries|(% style="width:745px" %)Extract all the series keys and create a KeySet(s) Constraint.
975 +|indexDataSet|(% style="width:745px" %)Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
976 +|indexReportingPeriod|(% style="width:745px" %)(((
980 980  This applies only to a registered __dataset__.
981 -
982 982  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
983 983  )))
984 -|indexAttributes|(((
980 +|indexAttributes|(% style="width:745px" %)(((
985 985  **Data Set**
986 -
987 987  Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
988 988  
989 989  **Metadata Set**
990 -
991 -Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute
992 -
993 -Components of the Constraints model in the
985 +Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the
994 994  )))
995 -|**Indexing Required**|**Registration Process Activity**
996 -| |SDMX-IM. Note that the content is not stored in the Selection Value.
987 +|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
988 +| |(% style="width:745px" %)SDMX-IM. Note that the content is not stored in the Selection Value.
997 997  )))
998 998  
999 999  Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).