fxdemo:01-part:11-conceptual-rules-and-constraints:11-6-implementation-mappings-do-not-redefine-concepts

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
fxdemo:01-part:11-conceptual-rules-and-constraints:11-6-implementation-mappings-do-not-redefine-concepts [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1fxdemo: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 1: Line 1:
 +====== 11.6 Implementation Mappings Do Not Redefine Concepts ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +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:
 +  Communication Endpoint → DDS Topic
 +  Data Structure Definition → IDL structure
 +  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 [[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>
 +