Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.3
edited by Helena
on 2025/05/21 15:27
Change comment: There is no comment for this version
To version 2.11
edited by Helena
on 2025/05/21 15:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -288,25 +288,27 @@
288 288  * that a queryable data source exists - this would necessitate the registration service querying the service to determine its existence
289 289  * that a simple data source exists (i.e. a file accessible at a URL)
290 290  * that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data that the components (Dimensions, Attributes, Measures, Identifier Components etc.) are consistent with the Data Structure Definition or Metadata Structure Definition
291 -* that the valid representations of the concepts to which these components correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
291 +* that the valid representations of the concepts to which these components 382 correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
292 292  
293 293  3The Registration has an action attribute which takes one of the following values:
294 294  
295 -(% style="margin-left:auto; margin-right:auto" %)
296 -|(% style="width:200px" %)(((
295 +|(% style="width:249px" %)(((
297 297  **Action Attribute Value**
298 -)))|(% style="width:1672px" %)**Behaviour**
299 -|(% style="width:200px" %)Append|(% style="width:1672px" %)Add this registration to the registry
300 -|(% style="width:200px" %)Replace|(% style="width:1672px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
301 -|(% style="width:200px" %)Delete|(% style="width:1672px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
297 +)))|(% style="width:1622px" %)**Behaviour**
298 +|(% style="width:249px" %)Append|(% style="width:1622px" %)Add this registration to the registry
299 +|(% style="width:249px" %)Replace|(% style="width:1622px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
300 +|(% style="width:249px" %)Delete|(% style="width:1622px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
301 +
302 302  The Registration has three Boolean attributes which may be present to determine how an SDMX compliant Dataset or Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows:
303 -|(% style="width:200px" %)**Boolean Attribute**|(% style="width:1672px" %)**Behaviour if Value is “true”**
304 -|(% style="width:200px" %)indexTimeSeries|(% style="width:1672px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
305 -|(% style="width:200px" %)indexDataSet|(% style="width:1672px" %)(((
303 +
304 +|**Boolean Attribute**|**Behaviour if Value is “true”**
305 +|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
306 +|indexDataSet|(((
306 306  A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
308 +
307 307  Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
308 308  )))
309 -|(% style="width:200px" %)indexReportingPeriod|(% style="width:1672px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
311 +|indexReportingPeriod|A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
310 310  
311 311  === 5.2.5 Data and Reference Metadata Discovery ===
312 312  
... ... @@ -338,8 +338,8 @@
338 338  
339 339  The following table defines the behaviour of the SDMX Registry for the various Registry Interface messages.
340 340  
341 -|(% style="width:227px" %)**Interface**|(% style="width:1644px" %)**Behaviour**
342 -|(% style="width:227px" %)All|(% style="width:1644px" %)(((
343 +|(% style="width:244px" %)**Interface**|**Behaviour**
344 +|(% style="width:244px" %)All|(((
343 343  1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final attribute is set to “true” in which case the only changes that are allowed are to the following constructs:
344 344  
345 345  * Name – this applies to the Maintainable object and its contained elements, such a Code in a Code list.
... ... @@ -353,6 +353,7 @@
353 353  * isExternalReference
354 354  
355 355  2) Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted.
358 +
356 356  3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
357 357  
358 358  а) Not have the final attribute set to “true”
... ... @@ -359,11 +359,12 @@
359 359  b) Not be referenced from any other object in the Registry.
360 360  
361 361  4) The version rules in the SDMX Schema documentation MUST be obeyed.
365 +
362 362  5) The specific rules for the elements and attributes documented in the SDMX Schema MUST be obeyed.
363 363  )))
364 -|(% style="width:227px" %)SubmitStructureRequest|(% style="width:1644px" %)Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
365 -|(% style="width:227px" %)SubmitProvisioningRequest|(% style="width:1644px" %)No additional behaviour.
366 -|(% style="width:227px" %)Submit Registration Request|(% style="width:1644px" %)(((
368 +|(% style="width:244px" %)SubmitStructureRequest|Structures are submitted at the level of the Maintainable Artefact and the behaviour in “All” above is therefore at the level of the Maintainable Artefact.
369 +|(% style="width:244px" %)SubmitProvisioningRequest|No additional behaviour.
370 +|(% style="width:244px" %)Submit Registration Request|(((
367 367  If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean attributes set in the Registration.
368 368  For a queryable datasource the Registry MAY validate that the source exists and can accept an SDMX-ML data query.
369 369  )))
... ... @@ -486,7 +486,7 @@
486 486  
487 487  The generic structure of the URN is as follows:
488 488  
489 ->SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
493 +SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
490 490  
491 491  ~* this can repeat and may not be present (see explanation below)
492 492  
... ... @@ -498,7 +498,7 @@
498 498  
499 499  In the explanation below the actual object that is the target of the URN is called the **//actual object//**.
500 500  
501 -**SDMXPrefix:** urn:sdmx:org.
505 +**SDMXPrefix:** urn:sdmx:org.                                     
502 502  
503 503  **SDMX-IM package name:** sdmx.infomodel.package=
504 504  
... ... @@ -1073,8 +1073,6 @@
1073 1073  
1074 1074  ==== 7.1.3.3 Structure Usage Model ====
1075 1075  
1076 -[[image:1747829078194-749.png]]
1077 -
1078 1078  **Figure 10: SDMX-IM of links from Structure Usage to Category**
1079 1079  
1080 1080  In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
... ... @@ -1101,10 +1101,10 @@
1101 1101  
1102 1102  An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
1103 1103  
1104 -[[image:1747829109466-595.png]]
1105 1105  
1106 1106  **Figure 11: SDMX-IM of the Data Provider**
1107 1107  
1109 +
1108 1108  Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
1109 1109  
1110 1110  [[image:1747824123019-181.jpeg]]
... ... @@ -1113,10 +1113,8 @@
1113 1113  
1114 1114  The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1115 1115  
1116 -[[image:1747829139951-378.png]]
1117 1117  
1118 -(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
1119 -**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1119 +==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
1120 1120  
1121 1121  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
1122 1122  
... ... @@ -1144,12 +1144,13 @@
1144 1144  
1145 1145  === 7.3.3 Data and Metadata Constraints: Model ===
1146 1146  
1147 -[[image:1747829204737-370.png]]
1148 1148  
1149 -**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1150 1150  
1151 -The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1149 +==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
1152 1152  
1151 +The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1152 +
1153 +
1153 1153  The content of the Constraint can be found in the SDMX Information Model document.
1154 1154  
1155 1155  == 7.4 Data and Metadata Registration ==
... ... @@ -1170,7 +1170,7 @@
1170 1170  
1171 1171  [[image:1747824123025-411.jpeg]]
1172 1172  
1173 -**Figure 16: Schematic of the Objects Concerned with Registration**
1174 + **Figure 16: Schematic of the Objects Concerned with Registration**
1174 1174  
1175 1175  ==== 7.4.2.2 Registration Request Model ====
1176 1176  
... ... @@ -1184,14 +1184,11 @@
1184 1184  
1185 1185  The Registration has an action attribute which takes one of the following values:
1186 1186  
1187 -(% style="width:970.294px" %)
1188 -|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
1189 -|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
1190 -|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1191 -|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1188 +|**Action Attribute Value**|**Behaviour**
1189 +|Append|Add this Registration to the registry
1190 +|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1191 +|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1192 1192  
1193 -[[image:1747829290890-122.png]]
1194 -
1195 1195  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1196 1196  
1197 1197  The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
... ... @@ -1206,19 +1206,25 @@
1206 1206  
1207 1207  Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below.
1208 1208  
1209 -|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
1210 -|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
1211 -|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
1212 -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.
1207 +|**Indexing Required**|**Registration Process Activity**
1208 +|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1209 +|indexDataSet|(((
1210 +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
1211 +
1212 +Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
1213 1213  )))
1214 -|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1214 +|indexReportingPeriod|(((
1215 1215  This applies only to a registered dataset.
1216 +
1216 1216  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1217 1217  )))
1218 -|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1219 +|indexAttributes|(((
1219 1219  **Data Set**
1221 +
1220 1220  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
1223 +
1221 1221  **Metadata Set**
1225 +
1222 1222  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 SDMX-IM. Note that the content is not stored in the Selection Value.
1223 1223  )))
1224 1224  
... ... @@ -1228,13 +1228,14 @@
1228 1228  
1229 1229  === 7.4.3 Registration Response ===
1230 1230  
1231 -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 Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
1235 +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 Submit Registration class has a status field which is either set to
1232 1232  
1237 +“Success”, “Warning” or “Failure”.
1238 +
1233 1233  If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service.
1234 1234  
1235 1235  The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
1236 1236  
1237 -[[image:1747829477882-750.png]]
1238 1238  
1239 1239  **Figure 18: Logical class diagram showing the registration response**
1240 1240  
... ... @@ -1244,12 +1244,15 @@
1244 1244  
1245 1245  A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
1246 1246  
1247 -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”.
1252 +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
1248 1248  
1249 -=== 7.5.1Subscription Logical Class Diagram ===
1254 +“notification”.
1250 1250  
1251 -[[image:1747829554603-150.png]]
1256 + 7.5.1Subscription Logical Class Diagram
1252 1252  
1258 +
1259 +[[image:1747824123028-257.png]]
1260 +
1253 1253  **Figure 19: Logical Class Diagram of the Subscription**
1254 1254  
1255 1255  === 7.5.2 Subscription Information ===
... ... @@ -1256,58 +1256,73 @@
1256 1256  
1257 1257  Regardless of the type of registry/repository events being observed, a subscription always contains:
1258 1258  
1259 -1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
1260 -1. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
1261 -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.
1262 -1. A selector which specifies which type of events are of interest. The set of event types is:
1267 +~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
1263 1263  
1264 -|(% style="width:327px" %)**Event Type**|(% style="width:1545px" %)**Comment**
1265 -|(% style="width:327px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1545px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1266 -|(% style="width:327px" %)DATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1267 -|(% style="width:327px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1268 -|(% style="width:327px" %)ALL_EVENTS|(% style="width:1545px" %)All events of the specified EventType
1269 +2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
1269 1269  
1271 +3. 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.
1272 +
1273 +4. A selector which specifies which type of events are of interest. The set of event types is:
1274 +
1275 +|**Event Type**|**Comment**
1276 +|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1277 +|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1278 +|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1279 +|ALL_EVENTS|All events of the specified EventType
1280 +
1270 1270  === 7.5.3 Wildcard Facility ===
1271 1271  
1272 1272  Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
1273 1273  
1274 -* agencyID
1275 -* id
1276 -* version
1285 + agencyID
1277 1277  
1287 + id
1288 +
1289 + version
1290 +
1278 1278  Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1279 1279  
1280 -//AgencyID = %
1293 +AgencyID = %
1294 +
1281 1281  Id = %
1282 -Version = %//
1283 1283  
1297 +Version = %
1298 +
1284 1284  This subscribes to all Codelists of all versions for all agencies.
1285 1285  
1286 -//AgencyID = AGENCY1
1301 +AgencyID = AGENCY1
1302 +
1287 1287  Id = CODELIST1
1288 -Version = %//
1289 1289  
1305 +Version = %
1306 +
1290 1290  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1291 1291  
1292 -//AGENCY1
1309 +AGENCY1
1310 +
1293 1293  AgencyID = AGENCY1
1312 +
1294 1294  Id = %
1295 -Version = %//
1296 1296  
1315 +Version = %
1316 +
1297 1297  This subscribes to all versions of all Codelist objects maintained by the agency
1298 1298  
1299 -//AGENCY1
1319 +AGENCY1
1320 +
1300 1300  AgencyID = %
1322 +
1301 1301  Id = CODELIST1
1302 -Version = %//
1303 1303  
1325 +Version = %
1326 +
1304 1304  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1305 1305  
1306 -//AGENCY1//
1329 +AGENCY1
1307 1307  
1308 1308  Note that if the subscription is to the latest version then this can be achieved by the * character
1309 1309  
1310 -//i.e. Version = *//
1333 +i.e. Version = *
1311 1311  
1312 1312  Note that a subscription using the URN mechanism cannot use wildcard characters.
1313 1313  
... ... @@ -1319,15 +1319,16 @@
1319 1319  
1320 1320  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:
1321 1321  
1322 -|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
1323 -|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
1324 -|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
1325 -|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1326 -|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1327 -|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
1328 -|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification.
1329 -|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1330 1330  
1346 +|**Selector**|**Comment**
1347 +|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
1348 +|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
1349 +|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1350 +|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1351 +|**Selector**|**Comment**
1352 +| |activate the notification.
1353 +|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1354 +
1331 1331  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1332 1332  
1333 1333  == 7.6 Notification ==
... ... @@ -1334,10 +1334,8 @@
1334 1334  
1335 1335  === 7.6.1 Logical Class Diagram ===
1336 1336  
1337 -[[image:1747829675568-610.png]]
1338 1338  
1339 -(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
1340 -**Figure 20: Logical Class Diagram of the Notification**
1362 +==== Figure 20: Logical Class Diagram of the Notification ====
1341 1341  
1342 1342  A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
1343 1343  
... ... @@ -1357,3 +1357,5 @@
1357 1357  === 7.6.3 Registration Event Component ===
1358 1358  
1359 1359  The notification will contain the Registration.
1382 +
1383 +
1747829078194-749.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
1747829109466-595.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -30.4 KB
Content
1747829139951-378.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
1747829204737-370.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
1747829290890-122.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -41.4 KB
Content
1747829477882-750.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -24.6 KB
Content
1747829554603-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -99.1 KB
Content
1747829675568-610.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content