Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:c:communication_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:c:communication_role [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Communication Role ======
+[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to C Terms]]
+===== Discussion =====
+A Communication Role identifies how a Logical Node participates in a Logical Communication Endpoint.
+Communication Roles describe logical participation in an exchange. They do not prescribe communication technology, protocol, deployment topology, or runtime packaging.
+A Logical Node performs one or more Communication Roles for a given endpoint. The same Logical Node also performs different Communication Roles across different endpoints. For example, a Logical Node publishes health status, subscribes to configuration updates, consumes commands, and produces acknowledgements.
+===== Definition =====
+//Logical participation responsibility performed by a Logical Node at a Logical Communication Endpoint.//
+===== Source =====
+Specialization of Node Role and Communication Endpoint from Part 1, Sections 7.4 and 7.6; generalised from publisher, subscriber, command, control-plane, and topic-participation material in the original FX Demo Reference Architecture.
+===== Note =====
+A Communication Role belongs to the logical interaction model. It does not identify a deployed process, network connection, protocol binding, or middleware participant.
+===== Example =====
+A Logical Node performs a Publisher Role when it produces health-status information for a logical health-status endpoint.
+----
+[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to Top]]