Terminology-oriented database: Difference between revisions

Content deleted Content added
m databas→database - typos.toolforge.org
 
Line 11:
}}</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 databasdatabase 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 databases and in [[relational database]]s, is identical,<ref>{{cite conference
| url = http://www.odaba.com/content/downloads/documentation/P1_UnifiedDatabaseTheory.pdf
| title = Unified Database Theory