Differences

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

--- fxdemo:01-part:11-conceptual-rules-and-constraints:11-6-implementation-mappings-do-not-redefine-concepts [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:11-6-implementation-mappings-do-not-redefine-concepts to fxdemo:01-part:11-conceptual-rules-and-constraints:11-6-implementation-mappings-do-not-redefine-concepts owen
+++ fxdemo:01-part:11-conceptual-rules-and-constraints:11-6-implementation-mappings-do-not-redefine-concepts [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-Implementation mappings realise conceptual and logical elements for a specific technology stack. They do not redefine the concepts they realise.
+Implementation mappings realize conceptual and logical elements for a specific technology stack. They do not redefine the concepts they realize.
 For example, a Phase 0 implementation profile may map:
@@ Line 9: / Line 9: @@
   Node → Python process packaged as an OCI-compatible container image
   Runtime Plane → DDS topic namespace or partition
-Those mappings support implementation. They do not change the conceptual meaning of Communication Endpoint, Data Structure Definition, Node, or Runtime Plane.
+Those mappings support implementation. They do not change the conceptual meaning of [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], or [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>