P3-REQ-17-6-006
Statement
The FX Demo Logical Profile SHALL distinguish FX logical information structures from IDL structures, Protocol Buffers messages, JSON Schema definitions, XML Schema definitions, Avro schemas, OpenAPI schemas, ontology classes, database tables, generated language types, files, wire formats, runtime payloads, and implementation records.
Source
Part 3, Section 17.6: FX Logical Information Requirements.
Rationale
FX logical information structures are platform-independent architectural concepts that define the meaning of information exchanged and processed within the Foreign Exchange Domain. Technologies such as IDL structures, Protocol Buffers messages, JSON Schema definitions, XML Schema definitions, Avro schemas, OpenAPI schemas, database tables, generated language types, and wire formats are implementation mechanisms that may realize a logical information structure but do not define its architectural meaning.
Maintaining this distinction preserves the separation between logical architecture and implementation, allowing multiple Implementation Profiles to realize the same logical information structures using different technologies while maintaining architectural consistency and interoperability.
Applies To
This requirement applies to every FX logical information structure defined within the FX Demo Logical Profile.
It applies specifically to:
-
logical information architecture;
-
platform-independent modeling;
-
Implementation Profile development;
-
architectural conformance reviews; and
-
architectural governance.
Verification
Verification SHALL confirm that logical information structures are defined independently of implementation-specific representations.
Verification activities should include review checks confirming that:
-
logical information structures are not represented as implementation artefacts;
-
implementation representations are treated as realizations rather than architectural definitions;
-
platform independence is preserved; and
-
architectural concepts remain clearly separated from implementation technologies.
Traceability
This requirement preserves the separation between conceptual information architecture, logical information architecture, and implementation-specific information representations established throughout Parts 1, 2, and 3.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.