TR-0057 Data Collection Principles - Subscription and Notification
Subscription and Notification
-
Events generated by resources can be received using the <subscription> resource.
-
The <subscription> resource contains subscription information for its "subscribed-to" resource.
-
<subscription> resource is a child resource of the "subscribed-to" resource.
-
-
The originator (resource subscriber) has RETRIEVE privileges to the "subscribed-to" resource in order to create the <subscription> resource.
-
Notification policies specified in the attributes can be applied to the <subscription>.
-
Specify which, when, and how notifications are sent.
-
Example: batchNotify – receive batches of notification rather than one at a time.
-
Subcription and notification example