Data Model [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 Model ======

[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Data Model is a [[public:99_annexes:annex-b-terms-and-definitions:m:model|Model]] of [[public:99_annexes:annex-b-terms-and-definitions:d:data|Data]]. It represents selected aspects of how Data is identified, organized, related, constrained, and used for a defined purpose.

A Data Model may describe:

  * Data elements and their identities
  * Data types and permitted values
  * [[public:99_annexes:annex-b-terms-and-definitions:s:structure|Structures]] and compositions
  * Relationships among Data elements
  * [[public:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraints]] governing valid Data
  * Identifiers, keys, and references
  * Rules for representing, storing, or exchanging Data
  * Associations with governed [[public:99_annexes:annex-b-terms-and-definitions:s:semantic|semantic]] meaning

A Data Model can be expressed at different levels of abstraction. A conceptual Data Model identifies the principal kinds of Data and their relationships without prescribing an implementation. A logical Data Model provides additional Structure, types, Constraints, and relationships. A physical Data Model describes how the Data is realized using a particular storage, exchange, or processing technology.

In the SIP-RA context, a Data Model does not silently combine Data, Structure, semantics, [[public:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], and [[public:99_annexes:annex-b-terms-and-definitions:g:governance|Governance]]. It identifies its represented concerns and the relationships among them so that each concern can evolve under appropriate control.

===== Definition =====

//a Model that represents selected Data elements, Structures, relationships, Constraints, and associated meaning for a defined purpose//

===== Source =====

Derived from the Dido Solutions definitions of [[public:99_annexes:annex-b-terms-and-definitions:d:data|Data]] and [[public:99_annexes:annex-b-terms-and-definitions:m:model|Model]], informed by [[public:99_annexes:annex-b-terms-and-definitions:m:mda|Model Driven Architecture (MDA)]] and ISO/IEC 11179 metadata-registry concepts.

===== Note =====

A Data Model is distinct from the Data that conforms to it. For example, a Data Model may define the Structure, type, relationships, and Constraints of a transaction record, while an individual transaction record contains the Data values.

A Data Model may reference semantic definitions and Interpretation rules, but those references do not make the Data Model the sole governing source for semantics or Interpretation.

===== Example =====

A logistics-readiness Data Model identifies units, personnel, equipment, supplies, locations, readiness observations, and reporting periods. It specifies the relationships and Constraints among those elements without requiring a particular database product, message format, or implementation platform.

----

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