====== 5.2 FX Demo Classification Path ====== [[fxdemo:03-part:05-fx-demo-logical-profile-overview:start | Go To FX Demo Logical Profile Overview ]] The FX Demo Logical Profile inherits the classification path defined in Part 1. [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:f:finance_ecosphere|Finance Ecosphere]] └── [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:m:monetary_ecosystem|Monetary Ecosystem]] └── [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]] **Figure 5-2:** Classification path for the FX Demo Logical Profile. The classification path establishes the business and semantic scope of the FX Demo. It identifies the FX Demo as a [[dido:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]] profile within the [[dido:99_annexes:annex-b-terms-and-definitions:m:monetary_ecosystem|Monetary Ecosystem]] and the [[dido:99_annexes:annex-b-terms-and-definitions:f:finance_ecosphere|Finance Ecosphere]]. The classification path does not identify any of the following: a runtime domain, deployment namespace, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Domain ID, topic namespace, repository path, container name, pod name, process identifier, or implementation profile. Later implementation and deployment profiles use the classification path for documentation, metadata, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], governance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] context, without making it a runtime identifier. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.