Difference between revisions of "Subscription and Notification Pattern"
Jump to navigation
Jump to search
(Started specification) |
|||
| Line 1: | Line 1: | ||
| − | Subscription and Notification Pattern | + | 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. Techncial approach and business requirement do not relate one two one, giving rise to potential hybrid approaches. | ||
| + | |||
Revision as of 08:31, 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 or Event Notifications that contain only the identification data and the event type. Techncial approach and business requirement do not relate one two one, giving rise to potential hybrid approaches.
Used by the following use cases
Application collaborations
TBD