16.3 FX Logical Endpoints Remain Distinct from Communication Technologies [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 16.3 FX Logical Endpoints Remain Distinct from Communication Technologies ======
[[fxdemo:03-part:16-fx-demo-logical-rules-and-constraints:start | Go To FX Demo Logical Rules and Constraints ]]

An FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoint]] represents a platform-independent point of information exchange among FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]]. It does not represent a [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] resource, [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] method, Protocol Buffers service, message queue, event stream, file, database handoff, shared-memory location, or network route.

Implementation profiles select communication mechanisms that realise FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]]. The selected mechanism supports the FX logical exchange, but it does not redefine the endpoint's logical purpose, participating [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], Communication Roles, information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classification, governance constraints, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>