Differences

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

--- fxdemo:02-part:15-logical-rules-and-constraints:15-2-logical-nodes-remain-distinct-from-runtime-deployments:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:15-logical-rules-and-constraints:15-2-logical-nodes-remain-distinct-from-runtime-deployments:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:02-part:start | Go To Top ]]
-A [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] represents a platform-independent participant in the logical architecture. It does not represent a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, RPC endpoint, REST resource, DDS participant, or deployment artefact.
+A [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] represents a platform-independent participant in the logical architecture. It does not represent a process, service, container, pod, virtual machine, serverless function, thread, task, library, subroutine, RPC endpoint, REST resource, DDS participant, or deployment artifact.
-Implementation profiles select execution mechanisms that realise [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. Deployment profiles then describe how those implementation artefacts run in a concrete environment.
+Implementation profiles select execution mechanisms that realize [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. Deployment profiles then describe how those implementation artifacts run in a concrete environment.
-A single runtime artefact implements several [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] when the selected implementation approach combines responsibilities. Several runtime artefacts implement a single [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] when the selected implementation approach distributes responsibility. Neither choice redefines the [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]].
+A single runtime artifact implements several [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] when the selected implementation approach combines responsibilities. Several runtime artifacts implement a single [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] when the selected implementation approach distributes responsibility. Neither choice redefines the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]].
 ----