Terminology-oriented database
 |
A terminology-oriented database or terminology-oriented database management system is a conceptual extension of an object-oriented database.[1] It implements concepts defined in a terminology model. Compared with object-oriented databases, 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 databases and in relational databases, is identical,[2] 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
- ^ Cattell, R.J.J. (2000). The Object Data Standard: ODMG 3.0. Morgan Kaufmann Publishers. ISBN 1-55860-647-5.
{{cite book}}: Unknown parameter|coauthor=ignored (|author=suggested) (help) - ^ Karge, R. (2003). Unified Database Theory (PDF document). The 7th World Multi-Conference on SYSTEMICS, CYBERNETICS AND INFORMATICS - SCI 2003. Orlando, Florida (USA).
{{cite conference}}: External link in|conferenceurl=|conferenceurl=ignored (|conference-url=suggested) (help); Unknown parameter|month=ignored (help)