====== 16.8 FX Demo Logical Profile Does Not Prescribe Communication Pattern Implementation ======
[[fxdemo:03-part:16-fx-demo-logical-rules-and-constraints:start | Go To FX Demo Logical Rules and Constraints ]]

The FX Demo Logical Profile defines FX communication roles and FX interaction patterns without prescribing how a selected technology implements them.

An FX logical publication does not require [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] or an event stream. An FX logical subscription does not require topic-based middleware. An FX logical request does not require [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] or [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]]. An FX logical command does not require an orchestration command or control API. An FX logical acknowledgement does not require synchronous communication.

Implementation profiles select communication patterns and technologies that realise the FX logical interaction while preserving FX logical meaning, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classification, governance constraints, policy constraints, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.

----

<WRAP centeralign>

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

</WRAP>