Data model: Difference between revisions

Revision as of 00:36, 10 August 2023

Revision as of 00:39, 10 August 2023

Line 7:

The term '''''data model''''' can refer to two distinct but closely related concepts. Sometimes it refers to an abstract formalization of the [[Object (philosophy)|objects]] and relationships found in a particular application ___domain: for example the customers, products, and orders found in a manufacturing organization. At other times it refers to the set of concepts used in defining such formalizations: for example concepts such as entities, attributes, relations, or tables. So the "data model" of a banking application may be defined using the entity–relationship "data model". This article uses the term in both senses.

A data model explicitly determines the structure of data. Data models are typically specified by a data specialist, data librarian, or a digital humanities scholar in a [[data modeling]] notation. These notations are often represented in graphical form.<ref name="MRM99">

Michael R. McCaleb (1999). [http://nvl.nist.gov/pub/nistpubs/jres/104/4/html/j44mac.htm#apa "A Conceptual Data Model of Datum Systems"] {{Webarchive

|url= https://web.archive.org/web/20080921063005/http://nvl.nist.gov/pub/nistpubs/jres/104/4/html/j44mac.htm#apa |date= 2008-09-21

Line 14:

A data model can sometimes be referred to as a [[data structure]], especially in the context of [[programming language]]s. Data models are often complemented by [[function model]]s, especially in the context of [[enterprise model]]s.

A data model explicitly determines the ''structure of data''; conversely, '''structured data''' is data organized according to an explicit data model or data structure. Structured data is in contrast to ''[[unstructured data]]'' and ''[[semi-structured data]]''.

== Overview ==