dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_collaboration

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_collaboration [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_collaboration [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Node Collaboration ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +Logical Node Collaboration describes how two or more Logical Nodes work together through explicit logical Communication Endpoints and logical interaction patterns.
 +
 +Logical Node Collaboration supports distributed operation. Examples of collaboration include publishing information, subscribing to information, issuing commands, acknowledging commands, requesting decisions, responding to requests, recording provenance, and producing evidence-related records.
 +
 +The Logical Architecture explicitly represents collaboration, enabling reviewers to identify participating Nodes, Node Roles, endpoints, information structures, Runtime Planes, governance constraints, and traceability relationships.
 +
 +===== Definition =====
 +
 +//Explicit logical cooperation among Logical Nodes through Communication Endpoints and interaction patterns.//
 +
 +===== Source =====
 +
 +Specialization of Node, Communication Endpoint, Runtime Plane, and Traceability from Part 1, Sections 7.2, 7.6, 7.5, and 7.10; generalises interaction material from the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +Logical Node Collaboration does not require one communication style. Implementation profiles realize collaboration through publish/subscribe, request/response, RPC, REST, message queues, event streams, file exchange, shared services, or other mechanisms.
 +
 +===== Example =====
 +
 +A transaction intake Node publishes a transaction event that a validation Node consumes. The validation Node then publishes a validation result that an audit and provenance Node records.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]