Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -992,7 +992,7 @@ 992 992 993 993 The Registration must reference the ProvisionAgreement to which it relates. 994 994 995 -=== 7.4.3 Registration Response === 995 +===== {{id name="_Toc90825"/}}7.4.3 Registration Response ===== 996 996 997 997 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”. 998 998 ... ... @@ -1004,7 +1004,7 @@ 1004 1004 1005 1005 **Figure 18: Logical class diagram showing the registration response** 1006 1006 1007 -== 7.5 Subscription and Notification Service == 1007 +=== {{id name="_Toc90826"/}}7.5 Subscription and Notification Service === 1008 1008 1009 1009 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. 1010 1010 ... ... @@ -1012,7 +1012,7 @@ 1012 1012 1013 1013 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”. 1014 1014 1015 -=== 7.5.1 Subscription Logical Class Diagram === 1015 +===== {{id name="_Toc90827"/}}7.5.1 Subscription Logical Class Diagram ===== 1016 1016 1017 1017 [[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]] 1018 1018