Terminology-oriented database: Difference between revisions

Revision as of 18:32, 9 March 2012

Revision as of 18:33, 4 January 2013

Line 6:

| publisher = Morgan Kaufmann Publishers

| year = 2000

| isbn = 1-55860-647-5}}</ref>. It implements [[conceptsconcept]]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 approach of a terminology-oriented database is conceptual rather than technical. 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