Terminology-oriented database: Difference between revisions

Revision as of 02:39, 11 May 2011

Latest revision as of 16:24, 18 June 2025

(16 intermediate revisions by 13 users not shown)

Line 1:

A '''terminology-oriented database''' [or '''terminology-oriented database management system]''' is a conceptual extension of an [[object-oriented database]].<ref>{{Cite book

| last = Cattell

| first = R.J.J.

| coauthorauthor2 = 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 [[concepts]] 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 [[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 approachdata model of a terminology-oriented database is ahigh-level; conceptual rather than a technical. Thethe 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]]sdatabases 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

| first = R.

| last = Karge

| year date=July 2003

| month = July

| year = 2003

| conference = The 7th World Multi-Conference on SYSTEMICS, CYBERNETICS AND INFORMATICS - SCI 2003

| conferenceurlconference-url = https://lists.cs.columbia.edu/pipermail/tccc/2002-October/000467.html

| ___location = Orlando, Florida (USAUS)

| 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.

Terminology databases, when these contain terms and vocabularies, these become valuable for ontologies and in turn ontologies can help process associated triples or complex predicates thus going deeper than hierarchies or keys in RDBMS. [[Semantic mapper|Semantic mapping]] can also enhance performance.

== References ==