Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:l:logical_event [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:l:logical_event [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Logical Event ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Logical Event represents a Logical Data Structure Instance that reports an occurrence, observation, | ||
| + | |||
| + | A Logical Event reports that something occurred or that a Logical Node observed, produced, derived, decided, or changed something. It does not instruct another Node to act. Commands express intended action; events report occurrence or result. | ||
| + | |||
| + | Logical Events support distributed processing by allowing Logical Nodes to communicate changes, observations, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //Logical Data Structure Instance reporting an occurrence, observation, | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Specialization of Data Structure Instance from Part 1, Section 7.8; generalised from domain-event and data-plane material in the original FX Demo Reference Architecture. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Logical Event is not an event-streaming technology or event-bus implementation. Implementation profiles realize events through selected communication mechanisms. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A transaction-received event reports that a Transaction Intake Node received a candidate transaction record. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | [[dido: | ||