Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:e:event_consumer_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:e:event_consumer_role [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Event Consumer Role ======
+[[dido:99_annexes:annex-b-terms-and-definitions:e:start|Return to E Terms]]
+===== Discussion =====
+An Event Consumer Role identifies a Logical Node's responsibility for receiving and using an event.
+The Event Consumer Role supports downstream processing, validation, interpretation, audit, provenance, monitoring, policy evaluation, or evidence expectations. The Logical Architecture identifies the event endpoint, the expected event structure, the consuming Logical Node, the Runtime Plane, and the traceability expectations.
+A Logical Node performing an Event Consumer Role uses the received event in accordance with its assigned logical responsibility.
+===== Definition =====
+//Communication Role responsible for receiving and using an event from a Logical Communication Endpoint.//
+===== Source =====
+Specialization of Communication Endpoint, Node Role, Data Structure Instance, and Runtime Plane from Part 1, Sections 7.6, 7.4, 7.8, and 7.5; generalised from domain-event and data-plane subscription material in the original FX Demo Reference Architecture.
+===== Note =====
+An Event Consumer Role does not require event-streaming technology. Implementation profiles realize events through the selected communication mechanism.
+===== Example =====
+A logical Audit and Provenance Node performs an Event Consumer Role when it receives a validation-result event and records provenance for that result.
+----
+[[dido:99_annexes:annex-b-terms-and-definitions:e:start|Return to Top]]