| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:l:logical_node [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:l:logical_node [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| A Logical Node identifies a platform-independent participant in the distributed logical architecture. It provides a logical point of responsibility for communication, role assignment, governance, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], observability, auditability, and expectations for [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. | A Logical Node identifies a platform-independent participant in the distributed logical architecture. It provides a logical point of responsibility for communication, role assignment, governance, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], observability, auditability, and expectations for [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. |
| |
| A Logical Node builds on the Part 1 concept of [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]. It adds logical structure by identifying the roles, responsibilities, endpoints, plane participation, and interaction patterns associated with a participant. | A Logical Node builds on the Part 1 concept of [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]]. It adds logical structure by identifying the roles, responsibilities, endpoints, plane participation, and interaction patterns associated with a participant. |
| |
| A Logical Node represents a logical participant such as an internal participant, external participant, gateway, adapter, analytical component, validation participant, policy participant, registry participant, monitoring participant, audit participant, or provenance participant. The Logical Architecture identifies the participant and its responsibilities without prescribing how later parts execute or deploy it. | A Logical Node represents a logical participant such as an internal participant, external participant, gateway, adapter, analytical component, validation participant, policy participant, registry participant, monitoring participant, audit participant, or provenance participant. The Logical Architecture identifies the participant and its responsibilities without prescribing how later parts execute or deploy it. |
| **Source:** | **Source:** |
| |
| Specialises [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] from Part 1, Section 7.2; generalises logical node material from the original FX Demo Reference Architecture for use in the distributed, node-based Logical Architecture / PIM. | Specializes [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] from Part 1, Section 7.2; generalises logical node material from the original FX Demo Reference Architecture for use in the distributed, node-based Logical Architecture / PIM. |
| |
| **Note:** | **Note:** |
| |
| A Logical Node is not a process, container, pod, virtual machine, server, library, thread, task, RPC method, REST resource, DDS participant, or deployment artefact. Later parts use those mechanisms as possible realisations of Logical Nodes; they do not redefine the concept of Logical Nodes. | A Logical Node is not a process, container, pod, virtual machine, server, library, thread, task, RPC method, REST resource, DDS participant, or deployment artifact. Later parts use those mechanisms as possible realisations of Logical Nodes; they do not redefine the concept of Logical Nodes. |
| |
| **Example:** | **Example:** |