DSUBm_007: Should also the DSUBm profile include a Pull Notification

[scontento]

(See the complete example DSUBm_007 in DSUBm issues)

The DSUBm profile propose notifications in a push mechanism. The Extensions to the Document Metadata Subscription (DSUB)
profile also include a pull modality for the notification. Should also the DSUBm profile include a Pull Notification mechanism or is it sufficient to search (e.g using Find Document Lists [ITI-66] or Find Document References [ITI-67] transactions) on the resources combining query parameters and proper interval of time? At the moment no specific request have been already submitted for this implementation. If the pull notification is needed and a real use case is provided, it is possible to send change proposal during the public comment period. We propose here a possible way to utilize a pure Pull Notification modality using the $events operation of the Resource Subscription Search [ITI-113] transaction.

[GinoCanessa]

The Subscriptions Backport IG STU 1.2 (currently in ballot) adds support for including queries with notifications, which can be used to perform "notified pull". Information is available here.

[scontento]

We are still looking for a compelling use case in order to insert in DSUBm