Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -502,7 +502,7 @@ 502 502 503 503 In the explanation below the actual object that is the target of the URN is called the **//actual object//**. 504 504 505 -**SDMXPrefix:** urn:sdmx:org. 505 +**SDMXPrefix:** urn:sdmx:org. 506 506 507 507 **SDMX-IM package name:** sdmx.infomodel.package= 508 508 ... ... @@ -1250,7 +1250,7 @@ 1250 1250 1251 1251 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 1252 1253 -=== 1253 +=== 7.5.1Subscription Logical Class Diagram === 1254 1254 1255 1255 [[image:1747829554603-150.png]] 1256 1256 ... ... @@ -1281,47 +1281,37 @@ 1281 1281 1282 1282 Examples of wildcarded identifier components for an identified object type of Codelist are shown below. 1283 1283 1284 -AgencyID = % 1285 - 1284 +//AgencyID = % 1286 1286 Id = % 1286 +Version = %// 1287 1287 1288 -Version = % 1289 - 1290 1290 This subscribes to all Codelists of all versions for all agencies. 1291 1291 1292 -AgencyID = AGENCY1 1293 - 1290 +//AgencyID = AGENCY1 1294 1294 Id = CODELIST1 1292 +Version = %// 1295 1295 1296 -Version = % 1297 - 1298 1298 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1299 1299 1300 -AGENCY1 1301 - 1296 +//AGENCY1 1302 1302 AgencyID = AGENCY1 1303 - 1304 1304 Id = % 1299 +Version = %// 1305 1305 1306 -Version = % 1307 - 1308 1308 This subscribes to all versions of all Codelist objects maintained by the agency 1309 1309 1310 -AGENCY1 1311 - 1303 +//AGENCY1 1312 1312 AgencyID = % 1313 - 1314 1314 Id = CODELIST1 1306 +Version = %// 1315 1315 1316 -Version = % 1317 - 1318 1318 This subscribes to all versions of Codelist CODELIST1 maintained by the agency 1319 1319 1320 -AGENCY1 1310 +//AGENCY1// 1321 1321 1322 1322 Note that if the subscription is to the latest version then this can be achieved by the * character 1323 1323 1324 -i.e. Version = * 1314 +//i.e. Version = *// 1325 1325 1326 1326 Note that a subscription using the URN mechanism cannot use wildcard characters. 1327 1327 ... ... @@ -1333,16 +1333,15 @@ 1333 1333 1334 1334 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: 1335 1335 1326 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1327 +|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification. 1328 +|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification. 1329 +|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1330 +|(% 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 1331 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1332 +|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification. 1333 +|(% 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. 1336 1336 1337 -|**Selector**|**Comment** 1338 -|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification. 1339 -|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification. 1340 -|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1341 -|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will 1342 -|**Selector**|**Comment** 1343 -| |activate the notification. 1344 -|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1345 - 1346 1346 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. 1347 1347 1348 1348 == 7.6 Notification == ... ... @@ -1349,8 +1349,10 @@ 1349 1349 1350 1350 === 7.6.1 Logical Class Diagram === 1351 1351 1341 +[[image:1747829675568-610.png]] 1352 1352 1353 -==== Figure 20: Logical Class Diagram of the Notification ==== 1343 +(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %) 1344 +**Figure 20: Logical Class Diagram of the Notification** 1354 1354 1355 1355 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. 1356 1356 ... ... @@ -1370,5 +1370,3 @@ 1370 1370 === 7.6.3 Registration Event Component === 1371 1371 1372 1372 The notification will contain the Registration. 1373 - 1374 -
- 1747829675568-610.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content