Terminology-oriented database: Difference between revisions

Content deleted Content added
m Disambiguating links to Semantic mapping (link changed to Semantic mapper) using DisamAssist.
Bluelinking 1 books for verifiability.) #IABot (v2.1alpha3
Line 2:
| last = Cattell
| first = R.J.J.
| author2 = D.K. Barry
| title = The Object Data Standard: ODMG 3.0
| publisher = Morgan Kaufmann Publishers
| year = 2000
| isbn = 1-55860-647-5
| isbn = 1-55860-647-5}}</ref> It implements [[concept]]s defined in a [[terminology model]]. Compared with [[object-oriented database]]s, the terminology-oriented database requires some minor conceptual extensions on the schema level as supporting set relations (super-set, subset, intersection etc.), weak-typed collections or shared inheritance.
| url-access = registration
| url = https://archive.org/details/isbn_9781558606470_0
| isbn = 1-55860-647-5}}</ref> It implements [[concept]]s defined in a [[terminology model]]. Compared with [[object-oriented database]]s, the terminology-oriented database requires some minor conceptual extensions on the schema level as supporting set relations (super-set, subset, intersection etc.), weak-typed collections or shared inheritance.
 
The data model of a terminology-oriented database is high-level; the terminology-oriented database provides facilities for transforming a [[terminology model]] provided by subject area experts completely into a [[database schema]]. The target schema might be the [[database schema]] for an [[object-oriented database]] as well as a [[relational database]] schema, or even an [[XML]] schema. Typically, terminology-oriented databases are not bound on a specific database type. Since the information content, which can be stored in [[object-oriented database]]s and in [[relational database]]s, is identical,<ref>{{cite conference