Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1092,30 +1092,29 @@ 1092 1092 1093 1093 The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”. 1094 1094 1095 -=== =={{id name="_Toc90830"/}}7.5.4 Structural Repository Events =====1095 +=== 7.5.4 Structural Repository Events === 1096 1096 1097 1097 Whenever a maintainable artefact (data structure definition, concept scheme, codelist, metadata structure definition, category scheme, etc.) is added to, deleted from, or modified in the structural metadata repository, a structural metadata event is triggered. Subscriptions may be set up to monitor all such events, or focus on specific artefacts such as a Data Structure Definition. 1098 1098 1099 -=== =={{id name="_Toc90831"/}}7.5.5 Registration Events =====1099 +=== 7.5.5 Registration Events === 1100 1100 1101 1101 Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below: 1102 1102 1103 -: 1104 - 1105 1105 ((( 1106 -|**Selector**|**Comment** 1107 -|DataProvider|Any datasets registered by the specified dataprovider will activate the notification. 1108 -|ProvisionAgreement|Any datasets for the agreement will activate the notification. 1109 -|Dataflow|Any datasets for the specified dataflow will activate the notification. 1110 -|DataStructureDefinition|Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification 1111 -|Category|Any datasets registered for those dataflows, provision agreements that are categorised by the category. 1104 +(% style="width:1082.83px" %) 1105 +|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment** 1106 +|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any datasets registered by the specified dataprovider will activate the notification. 1107 +|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any datasets for the agreement will activate the notification. 1108 +|(% style="width:230px" %)Dataflow|(% style="width:850px" %)Any datasets for the specified dataflow will activate the notification. 1109 +|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification 1110 +|(% style="width:230px" %)Category|(% style="width:850px" %)Any datasets registered for those dataflows, provision agreements that are categorised by the category. 1112 1112 ))) 1113 1113 1114 1114 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. 1115 1115 1116 -== {{id name="_Toc90832"/}}7.6 Notification ==1115 +== 7.6 Notification == 1117 1117 1118 -=== ={{id name="_Toc90833"/}}7.6.1 Logical Class Diagram ====1117 +=== 7.6.1 Logical Class Diagram === 1119 1119 1120 1120 [[image:SDMX 3.1 Section 5_en_8bc1b889.jpg||height="379" width="579"]] 1121 1121 ... ... @@ -1132,11 +1132,11 @@ 1132 1132 1133 1133 Additionally, supplementary information may be contained in the notification as detailed below. 1134 1134 1135 -=== ={{id name="_Toc90834"/}}7.6.2 Structural Event Component ====1134 +=== 7.6.2 Structural Event Component === 1136 1136 1137 1137 The notification will contain the MaintainableArtefact that triggered the event in a form similar to the SDMX-ML structural message (using elements from that namespace). 1138 1138 1139 -=== ={{id name="_Toc90835"/}}7.6.3 Registration Event Component ====1138 +=== 7.6.3 Registration Event Component === 1140 1140 1141 1141 The notification will contain the Registration. 1142 1142