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

Summary

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 -=== 7.5.1Subscription Logical Class Diagram ===
1253 +=== 7.5.1Subscription Logical Class Diagram ===
1254 1254  
1255 1255  [[image:1747829554603-150.png]]
1256 1256  
... ... @@ -1281,37 +1281,47 @@
1281 1281  
1282 1282  Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1283 1283  
1284 -//AgencyID = %
1284 +AgencyID = %
1285 +
1285 1285  Id = %
1286 -Version = %//
1287 1287  
1288 +Version = %
1289 +
1288 1288  This subscribes to all Codelists of all versions for all agencies.
1289 1289  
1290 -//AgencyID = AGENCY1
1292 +AgencyID = AGENCY1
1293 +
1291 1291  Id = CODELIST1
1292 -Version = %//
1293 1293  
1296 +Version = %
1297 +
1294 1294  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1295 1295  
1296 -//AGENCY1
1300 +AGENCY1
1301 +
1297 1297  AgencyID = AGENCY1
1303 +
1298 1298  Id = %
1299 -Version = %//
1300 1300  
1306 +Version = %
1307 +
1301 1301  This subscribes to all versions of all Codelist objects maintained by the agency
1302 1302  
1303 -//AGENCY1
1310 +AGENCY1
1311 +
1304 1304  AgencyID = %
1313 +
1305 1305  Id = CODELIST1
1306 -Version = %//
1307 1307  
1316 +Version = %
1317 +
1308 1308  This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1309 1309  
1310 -//AGENCY1//
1320 +AGENCY1
1311 1311  
1312 1312  Note that if the subscription is to the latest version then this can be achieved by the * character
1313 1313  
1314 -//i.e. Version = *//
1324 +i.e. Version = *
1315 1315  
1316 1316  Note that a subscription using the URN mechanism cannot use wildcard characters.
1317 1317  
... ... @@ -1323,15 +1323,16 @@
1323 1323  
1324 1324  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:
1325 1325  
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.
1334 1334  
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 +
1335 1335  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1336 1336  
1337 1337  == 7.6 Notification ==
... ... @@ -1338,10 +1338,8 @@
1338 1338  
1339 1339  === 7.6.1 Logical Class Diagram ===
1340 1340  
1341 -[[image:1747829675568-610.png]]
1342 1342  
1343 -(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
1344 -**Figure 20: Logical Class Diagram of the Notification**
1353 +==== Figure 20: Logical Class Diagram of the Notification ====
1345 1345  
1346 1346  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.
1347 1347  
... ... @@ -1361,3 +1361,5 @@
1361 1361  === 7.6.3 Registration Event Component ===
1362 1362  
1363 1363  The notification will contain the Registration.
1373 +
1374 +
1747829675568-610.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content