15.4 Logical Data Structures Remain Distinct from Serialisation Formats [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.

====== 15.4 Logical Data Structures Remain Distinct from Serialisation Formats ======
[[fxdemo:02-part:start | Go To Top ]]

A [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definition]] describes the structure, meaning, and constraints of an information class at the platform-independent logical level. It does not represent an IDL structure, a Protocol Buffers message, a JSON Schema definition, an XML Schema definition, an Avro schema, an OpenAPI schema, a database table, an ontology class, a generated type, a file, or a wire-format payload.

Implementation profiles select data representation mechanisms that realize [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definitions]] and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instances]]. The selected representation supports implementation, exchange, storage, validation, or processing. It does not redefine the logical information structure.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>