An ontology log (“olog”, spoken like “o log”) is a labeled graph with an attitude: vertices are labeled with ontological types and edges are labeled with aspects of ontological relationships. The path category of an ontology log is a diagram with an attitude, representing an ontology which can be interpreted in a chosen setting. Non-trivial ontological facts can be added as path equivalences.
Ontology logs provide a basis for database construction. In particular, an ontology log can serve as the schema for structured data.
As originally introduced in (Spivak & Kent 2012), ologs are diagrams into Set or another topos. However, as they anticipated, and as later realized by (Patterson 2017), ologs can be generalized to diagrams into Rel or another bicategory of relations.
An ontology log is a commuting diagram into a topos or a bicategory of relations. In the former case, they are known as functional ologs, and in the latter case, they are known as relational ologs. The labels of the diagram are expected to adhere to language-specific good practices. Labeled objects, arrows, and equivalences are called types, aspects, and facts respectively.
Target categories are called data categories and functors from ontology logs to data categories are called instance data. (Patterson 2017, p. 26)
These rules are enumerated in (Spivak & Kent 2012) as “good practices” which should be followed but may be distorted or ignored as part of authorial intent.
Type labels should:
Aspect labels should:
Facts do not need to be labeled, but the author should indicate as many of them as they know about, even facts which seem simple or trivial.
(…)
(…)
Last revised on September 18, 2024 at 19:19:29. See the history of this page for a list of all contributions to it.