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

Summary

Details

Page properties
Content
... ... @@ -933,7 +933,7 @@
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).
... ... @@ -1000,7 +1000,7 @@
1000 1000  
1001 1001  The Registration must reference the ProvisionAgreement to which it relates.
1002 1002  
1003 -===== {{id name="_Toc90825"/}}7.4.3 Registration Response =====
995 +=== 7.4.3 Registration Response ===
1004 1004  
1005 1005  After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”.
1006 1006  
... ... @@ -1012,7 +1012,7 @@
1012 1012  
1013 1013  **Figure 18: Logical class diagram showing the registration response**
1014 1014  
1015 -=== {{id name="_Toc90826"/}}7.5 Subscription and Notification Service ===
1007 +== 7.5 Subscription and Notification Service ==
1016 1016  
1017 1017  The contents of the SDMX Registry/Repository will change regularly: new code lists and key families will be published and new datasets and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
1018 1018  
... ... @@ -1020,7 +1020,7 @@
1020 1020  
1021 1021  When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
1022 1022  
1023 -===== {{id name="_Toc90827"/}}7.5.1 Subscription Logical Class Diagram =====
1015 +=== 7.5.1 Subscription Logical Class Diagram ===
1024 1024  
1025 1025  [[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]]
1026 1026