View source for Semantic data model

{{short description|Database model}}
{{Infobox technology|name=Semantic data model|type=semantics-based database description|companies=U.S. Air Force as [[Integrated Computer-Aided Manufacturing]] program|year=mid-1970s|product=[[Gellish]] (2005), [[ISO 15926]]-2 (2002)|facility=Planning of Data Resources, Building of Shareable Databases, Evaluation of Vendor Software, Integration of Existing Databases}}
[[File:A2 4 Semantic Data Models.svg|thumb|320px|The relationship of "Semantic data models" with "physical data stores" and "real world".<ref name="FIPS184">[http://www.itl.nist.gov/fipspubs/idef1x.doc FIPS Publication 184] {{webarchive|url=https://web.archive.org/web/20131203223034/http://www.itl.nist.gov/fipspubs/idef1x.doc |date=2013-12-03 }} released of IDEF1X by the Computer Systems Laboratory of the National Institute of Standards and Technology (NIST). 21 December 1993.</ref>|alt=]]

A '''semantic data model''' ('''SDM''') is a [[:wiktionary:high-level|high-level]] semantics-based database description and structuring formalism ([[database model]]) for databases. This database model is designed to capture more of the meaning of an application environment than is possible with contemporary database models. An SDM specification describes a database in terms of the kinds of entities that exist in the application environment, the classifications and groupings of those entities, and the structural interconnections among them. SDM provides a collection of high-level modeling primitives to capture the semantics of an application environment. By accommodating derived information in a database structural specification, SDM allows the same information to be viewed in several ways; this makes it possible to directly accommodate the variety of needs and processing requirements typically present in database applications. The design of the present SDM is based on our experience in using a preliminary version of it. SDM is designed to enhance the effectiveness and usability of database systems. An SDM database description can serve as a formal specification and documentation tool for a database; it can provide a basis for supporting a variety of powerful user interface facilities, it can serve as a conceptual database model in the database design process; and, it can be used as the database model for a new kind of database management system.

== In software engineering ==
A '''semantic data model''' in [[software engineering]] has various meanings: 
# It is a [[conceptual data model]] in which semantic information is included. This means that the model describes the meaning of its instances. Such a semantic [[data model]] is an abstraction that defines how the stored [[symbol]]s (the instance data) relate to the real world.<ref name ="FIPS184"/>
# It is a [[conceptual data model]] that includes the capability to express and exchange information which enables parties to interpret meaning (semantics) from the instances, without the need to know the meta-model. Such semantic models are fact-oriented (as opposed to object-oriented). Facts are typically expressed by [[binary relations]] between [[data]] elements, whereas higher order relations are expressed as collections of binary relations. Typically binary relations have the form of triples: Object-RelationType-Object. For example: the Eiffel Tower <is located in> Paris.

Typically the instance data of semantic data models explicitly include the kinds of relationships between the various data elements, such as <is located in>. To interpret the meaning of the facts from the instances, it is required that the meaning of the kinds of relations (relation types) be known. Therefore, semantic data models typically standardize such relation types. This means that the second kind of semantic data models enables that the instances express facts that include their own meanings. 
The second kind of semantic data models are usually meant to create semantic databases. The ability to include meaning in semantic databases facilitates building [[distributed database]]s that enable applications to interpret the meaning from the content. This implies that semantic databases can be integrated when they use the same (standard) relation types. This also implies that in general they have a wider applicability than relational or [[object-oriented database]]s.

== Overview ==
The logical data structure of a [[database management system]] (DBMS), whether [[Hierarchical model|hierarchical]], [[Network model|network]], or [[Relational model|relational]], cannot totally satisfy the [[Requirements analysis|requirements]] for a conceptual definition of data, because it is limited in scope and biased toward the implementation strategy employed by the DBMS. Therefore, the need to define data from a [[Three schema approach|conceptual view]] has led to the development of semantic data modeling techniques. That is, techniques to define the meaning of data within the context of its interrelationships with other data, as illustrated in the figure. The real world, in terms of resources, ideas, events, etc., are symbolically defined within physical data stores. A semantic data model is an abstraction which defines how the stored symbols relate to the real world. Thus, the model must be a true representation of the real world.<ref name ="FIPS184"/>

According to Klas and Schrefl (1995), the "overall goal of semantic data models is to capture more meaning of data by integrating relational concepts with more powerful abstraction concepts known from the [[Artificial Intelligence]] field. The idea is to provide high level modeling primitives as an integral part of a data model in order to facilitate the representation of real world situations".<ref>Wolfgang Klas, Michael Schrefl (1995). "Semantic data modeling" In: ''Metaclasses and Their Application''. Book Series Lecture Notes in Computer Science. Publisher Springer Berlin / Heidelberg. Volume Volume 943/1995.</ref>

== History ==
The need for semantic data models was first recognized by the U.S. Air Force in the mid-1970s as a result of the [[Integrated Computer-Aided Manufacturing]] (ICAM) Program. The objective of this program was to increase manufacturing productivity through the systematic application of computer technology. The ICAM Program identified a need for better analysis and communication techniques for people involved in improving manufacturing productivity. As a result, the ICAM Program developed a series of techniques known as the IDEF (ICAM Definition) Methods which included the following:<ref name ="FIPS184"/>
* [[IDEF0]] used to produce a “function model” which is a structured representation of the activities or processes within the environment or system.
* [[IDEF1]] used to produce an “information model” which represents the structure and semantics of information within the environment or system.
** [[IDEF1X]] a semantic data modeling technique used to produce a graphical information model which represents the structure and semantics of information within an environment or system. Use of this standard permits the construction of semantic data models which may serve to support the management of data as a resource, the integration of information systems, and the building of computer databases.
* [[IDEF2]] used to produce a “dynamics model” which represents the time varying behavioral characteristics of the environment or system.

During the 1990s, the application of semantic modelling techniques resulted in the semantic data models of the second kind. An example of such is the semantic data model that is standardised as [[ISO 15926]]-2 (2002), which is further developed into the semantic modelling language [[Gellish]] (2005). The definition of the Gellish language is documented in the form of a semantic data model. Gellish itself is a semantic modelling language, that can be used to create other semantic models. Those semantic models can be stored in Gellish Databases, being semantic databases.

== Applications ==
A semantic data model can be used to serve many purposes. Some key objectives include:<ref name ="FIPS184"/>
* Planning of data resources: A preliminary data model can be used to provide an overall view of the data required to run an enterprise. The model can then be analyzed to identify and scope projects to build shared data resources.
* Building of shareable databases: A fully developed model can be used to define an application independent view of data which can be validated by users and then transformed into a physical database design for any of the various DBMS technologies. In addition to generating databases which are consistent and shareable, development costs can be drastically reduced through data modeling.
* Evaluation of vendor software: Since a data model actually represents the infrastructure of an organization, vendor software can be evaluated against a company’s data model in order to identify possible inconsistencies between the infrastructure implied by the software and the way the company actually does business.
* Integration of existing databases: By defining the contents of existing databases with semantic data models, an integrated data definition can be derived. With the proper technology, the resulting conceptual schema can be used to control transaction processing in a distributed database environment. The U.S. Air Force Integrated Information Support System (I2S2) is an experimental development and demonstration of this kind of technology, applied to a heterogeneous type of DBMS environments.

== See also ==

* [[Computational mathematics]]
* [[Conceptual schema]]
* [[Entity-relationship model]]
* [[Information model]]
* [[Object-role modeling]]
* [[Ontology (information science)]]
* [[Relational Model/Tasmania]]
* [[Semantic technology]]
* [[Three-schema approach]]

== References ==
{{NIST-PD}}
{{reflist}}

== Further reading ==
* Naphtali D. Rishe (1992). [https://users.cs.fiu.edu/~sdbtools/hpdrc/library/books/datades-book/ Database Design: The Semantic Modeling Approach]. McGraw-Hill.
* Johan ter Bekke (1992). ''Semantic Data Modeling''. Prentice Hall.
* Alfonso F. Cardenas and Dennis McLeod (1990). ''Research Foundations in Object-Oriented and Semantic Database Systems''. Prentice Hall.
* Peter Gray, Krishnarao G. Kulkarni and, Norman W. Paton (1992). ''Object-Oriented Databases: A Semantic Data Model Approach''. Prentice-Hall International Series in Computer Science.
* Michael Hammer and Dennis McLeod (1978). "The Semantic Data Model: a Modeling Mechanism for Data Base Applications." In: ''Proc. ACM SIGMOD Int’l. Conf. on Management of Data''. Austin, Texas, May 31 - June 2, 1978, pp.&nbsp;26–36.
* Hammer, Michael, and Dennis McLeod. "Database Description with SDM: A Semantic Database Model." ACM Transactions on Database Systems (TODS) 6.3 (1981): 351-86. Web.

== External links ==
* {{Wikidata-inline}}
* [http://www.jhterbekke.net/SemanticDataModeling.html Semantic Data Modeling] Johan ter Bekke tribute site.
* [https://www.holistics.io/blog/the-ideal-semantic-layer Technical analysis of semantic data modeling layer in BI tools] 

{{Data model}}

{{DEFAULTSORT:Semantic Data Model}}
[[Category:Data modeling]]
[[Category:Systems analysis]]
[[Category:Knowledge representation]]