Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 21.15
edited by Helena
on 2025/06/08 16:43
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
... ... @@ -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,13 +1012,13 @@
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  
1019 1019  **Figure 19: Logical Class Diagram of the Subscription**
1020 1020  
1021 -=== 7.5.2 Subscription Information ===
1021 +===== {{id name="_Toc90828"/}}7.5.2 Subscription Information =====
1022 1022  
1023 1023  Regardless of the type of registry/repository events being observed, a subscription always contains:
1024 1024  
... ... @@ -1027,16 +1027,18 @@
1027 1027  1. A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
1028 1028  1. A selector which specifies which type of events are of interest. The set of event types is:
1029 1029  
1030 +:
1031 +::
1032 +
1030 1030  (((
1031 -(% style="width:1061.83px" %)
1032 -|**Event Type**|(% style="width:660px" %)**Comment**
1033 -|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1034 -|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1035 -|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1036 -|ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType
1034 +|**Event Type**|**Comment**
1035 +|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1036 +|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1037 +|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1038 +|ALL_EVENTS|All events of the specified EventType
1037 1037  )))
1038 1038  
1039 -=== 7.5.3 Wildcard Facility ===
1041 +===== {{id name="_Toc90829"/}}7.5.3 Wildcard Facility =====
1040 1040  
1041 1041  Subscription notification supports wildcarded identifier components URNs, which are identifiers which have some or all of their component parts replaced by the wildcard character `*`. Identifier components comprise:
1042 1042