Abox: Difference between revisions
link to the general knowledge graph concept and not Google's implementation of it, as the general concept is what is meant here |
Merged content from Tbox to here. See Talk:Abox#Merge_Abox_into_Tbox. Tag: Disambiguation links added |
||
| Line 1: | Line 1: | ||
{{other uses|TBOX (disambiguation)}} |
|||
{{Unreferenced|date=April 2009}} |
|||
In [[computer science]], an '''ABox''' is an "assertion component"—a fact associated with a conceptual model or [[Ontology (computer science)|ontologies]] within a [[knowledge base]]. |
|||
In [[computer science]], an '''ABox''' is an "assertion component"—a fact associated with a conceptual model or [[Ontology (computer science)|ontologies]] within a [[knowledge base]].<ref name="TRG93">{{cite journal |first=Thomas R. |last=Gruber |authorlink=Tom Gruber |date=June 1993 |url=http://tomgruber.org/writing/ontolingua-kaj-1993.pdf |title=A translation approach to portable ontology specifications |journal=[[Knowledge Acquisition]] |volume=5 |issue=2 |pages=199–220 |doi=10.1006/knac.1993.1008|citeseerx=10.1.1.101.7493 }}</ref> |
|||
The terms "ABox" and "[[TBox]]" are used to describe two different types of statements in knowledge bases. TBox statements describe a domain of interest by defining classes and properties as a domain vocabulary. ABox are TBox-compliant statements that use the vocabulary. |
The terms "ABox" and "[[TBox]]" are used to describe two different types of statements in knowledge bases. TBox statements describe a domain of interest by defining classes and properties as a domain vocabulary. ABox are TBox-compliant statements that use the vocabulary. |
||
| Line 24: | Line 25: | ||
==See also== |
==See also== |
||
* [[Tbox|TBox]] |
|||
* [[Description logic#Modeling]] |
* [[Description logic#Modeling]] |
||
* [[Metadata]] |
* [[Metadata]] |
||
Revision as of 13:28, 30 August 2021
In computer science, an ABox is an "assertion component"—a fact associated with a conceptual model or ontologies within a knowledge base.[1]
The terms "ABox" and "TBox" are used to describe two different types of statements in knowledge bases. TBox statements describe a domain of interest by defining classes and properties as a domain vocabulary. ABox are TBox-compliant statements that use the vocabulary.
TBox statements are sometimes associated with object-oriented classes and ABox statements associated with instances of those classes.
Together ABox and TBox statements make up a knowledge base or a Knowledge graph.
Examples of ABox and TBox statements
ABox statements typically have the form:
A is an instance of B
or
John is a Person
This should be contrasted with TBox statements (or definitions of domain resources) such as:
All Students are Persons
or
There are two types of Persons: Students and Teachers
TBox statements tend to be more permanent within a knowledge base and are used and stored as a schema or a data model. In contrast, ABox statements are much more dynamic in nature and tend to be stored as instance data within transactional systems within databases. With the newer, NoSQL databases and especially with RDF databases (see Triplestore) the storage distinction may no longer apply. Data and models can be stored using the same approach. However, models continue to be more permanent, have a different lifecycle and are typically stored as separate graphs within such database.
See also
 | This computer science article is a stub. You can help Wikipedia by expanding it. |
- ^ Gruber, Thomas R. (June 1993). "A translation approach to portable ontology specifications" (PDF). Knowledge Acquisition. 5 (2): 199–220. CiteSeerX 10.1.1.101.7493. doi:10.1006/knac.1993.1008.