Terminology-oriented database: Difference between revisions

Content deleted Content added
m disambiguated concepts
BG19bot (talk | contribs)
m WP:CHECKWIKI error fix for #61. Punctuation goes before References. Do general fixes if a problem exists. - using AWB (8853)
Line 1:
A '''terminology-oriented database''' [management system] is a conceptual extension of an [[object-oriented database]].<ref>{{Cite book
| last = Cattell
| first = R.J.J.
Line 6:
| publisher = Morgan Kaufmann Publishers
| year = 2000
| 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 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
| url = http://www.odaba.com/content/downloads/documentation/P1_UnifiedDatabaseTheory.pdf
| title = Unified Database Theory
Line 19:
| ___location = Orlando, Florida (USA)
| format = PDF document
}}</ref>, data for a terminology-oriented database can be stored theoretically in any type of database as well as in an XML file. Thus, terminology-oriented databases may support several database systems for storing application data.
 
== References ==