Data Structure Definition [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.
====== Data Structure Definition ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

A Data Structure Definition describes the expected structure, meaning, and constraints of a class of information. It defines the reusable model that governs one or more Data Structure Instances.

A Data Structure Definition may identify required fields, optional fields, field meanings, permitted data types, constraints, identifiers, timestamps, provenance references, lifecycle values, or other structural and semantic expectations.

A Data Structure Definition exists at the conceptual level. Later parts may realize it as an IDL structure, a JSON Schema definition, an XML Schema definition, a UML class, a SysML block, a database schema, a message schema, an ontology class, or another formal structure.

===== Definition =====

//description of the structure, meaning, and constraints of a class of information//

===== Source =====

Adapted from FX Demo Reference Architecture, Section 2.1.3, Data Structure Definition; aligned with SIP-RA separation of data, structure, semantics, and interpretation.

===== Note =====

A Data Structure Definition is not a Data Structure Instance, Communication Endpoint, DDS Topic, database table, file, or message.

===== Example =====

A later FX profile may define a CashFlowObligation structure that identifies the fields, meanings, and constraints for cash-flow obligation records.

----

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