Abox
 | This article relies largely or entirely on a single source. (April 2024) |
In
ABox statements must be TBox-compliant: they are assertions that use the vocabulary defined by the TBox.
TBox statements are sometimes associated with object-oriented classes and ABox statements associated with instances of those classes.
Examples of ABox and TBox statements
ABox statements typically deal with concrete entities. They specify what category an entity belongs to, or what relation one entity has to another entity.
- Item A is-an-instance-of Category C
- Item A has-this-relation-to Item B
Examples:
- Niger is-a country.
- Chad is-a country
- Niger is-next-to Chad.
- Agadez is-a city.
- Agadez is-located-in Niger.
TBox statements typically (or definitions of domain categories and implied relations) such as:
- An entity X can be a country or a city
- So Dagamanet is-a neighbourhood is not a fact you can specify, though it is a fact in real life.
- A is-next-to B if B is-next-to A
- So Niger is-next-to Chad implies Chad is-next-to Niger.
- X is a place if X is-a city or X is-a country.
- So Niger is-a country implies Niger is-a place.
- place A contains place B if place B is-located-in A.
- So Agadez is-located-in Niger implies Niger contains Agadez.
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
References
 | This computer science article is a stub. You can help Wikipedia by expanding it. |