Differences

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

--- fxdemo:02-part:07-logical-communication-model:07-13-communication-pattern-independence:start [2026/07/11 11:11] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:07-logical-communication-model:07-13-communication-pattern-independence:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 4: / Line 4: @@
 The Logical Communication Model remains independent of the implementation of communication patterns.
-The Logical Architecture uses [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Roles]] to describe participation in information exchange. Implementation profiles select communication patterns and technologies according to the implementation context.
+The Logical Architecture uses [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Roles]] to describe participation in information exchange. Implementation profiles select communication patterns and technologies according to the implementation context.
 The same logical interaction can map to different implementation mechanisms. A logical publication can map to DDS, an event stream, a message queue, a file exchange, or another mechanism. A logical request can map to REST, RPC, a message exchange, a service call, or another mechanism. A logical command can map to a control topic, an API call, a queue message, an orchestration action, or another mechanism.