Difference between revisions of "Subscription and Notification Pattern"
Jump to navigation
Jump to search
(Started specification) |
|||
| Line 1: | Line 1: | ||
Two distinct business requirements for Subscription and Notification Pattern: Updating of previously shared Evidence or being informed about an Event | Two distinct business requirements for Subscription and Notification Pattern: Updating of previously shared Evidence or being informed about an Event | ||
| − | Technically also two different approaches to Notification: Sending updated Data or Event Notifications that contain only the identification data and the event type. | + | Technically also two different approaches to Notification: Sending updated Data of a defined Evidence type or Event Notifications that contain only the identification data and the event type. Technical approach and business requirement do not relate one two one, giving rise to potential hybrid approaches. |
| + | |||
| + | The reference Architecture for the DE4A projects focusses the Subscription and Notification Pattern on Event Notification, which can be combines with the [[Lookup Pattern]] to cover the updating previously shared evidence use case. | ||
| + | |||
Revision as of 09:00, 23 April 2021
Two distinct business requirements for Subscription and Notification Pattern: Updating of previously shared Evidence or being informed about an Event
Technically also two different approaches to Notification: Sending updated Data of a defined Evidence type or Event Notifications that contain only the identification data and the event type. Technical approach and business requirement do not relate one two one, giving rise to potential hybrid approaches.
The reference Architecture for the DE4A projects focusses the Subscription and Notification Pattern on Event Notification, which can be combines with the Lookup Pattern to cover the updating previously shared evidence use case.
Used by the following use cases
Application collaborations
TBD