Core ontology¶
A deliberately small ontology containing the minimal high-level concepts and relations needed to interpret or connect more specialized domain concepts.
Core Idea¶
A core ontology supplies a stable conceptual nucleus on which richer or domain-specific ontologies depend. Designers identify concepts required across intended extensions, define them with minimal commitments and let specialized vocabularies refine rather than duplicate them. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
The load-bearing residual is not the broad topic of knowledge representation. It is minimal shared semantic foundation for ontology extension and alignment. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test.
Scope of Application¶
Core ontology belongs to knowledge representation and is useful where the analyst can specify a community or information system, competence questions, minimal concept set, relations and axioms, natural-language glossary, extension ontologies, mappings and governance, then evaluate every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail. The scope is broad within that domain but bounded by the need for every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.
Clarity¶
The abstraction clarifies a crowded vocabulary by making every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Core ontology can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Core ontology. Core ontology compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: a community or information system, competence questions, minimal concept set, relations and axioms, natural-language glossary, extension ontologies, mappings and governance. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of knowledge representation because they reuse a community or information system, competence questions, minimal concept set, relations and axioms, natural-language glossary, extension ontologies, mappings and governance, Designers identify concepts required across intended extensions, define them with minimal commitments and let specialized vocabularies refine rather than duplicate them., and type the carrier, state every parameter and convention in the definition, test that every retained concept is necessary for the declared shared scope and extensions can map to it without importing unrelated domain detail, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Core ontology Domain-specific
Parents (1) — more general patterns this builds on
-
Core ontology is a kind of Abstraction Prime
The proposed strict upward parent is
prime:abstraction.
Hierarchy path (1) — routes to 1 parentless root
- Core ontology → Abstraction
Neighborhood in Abstraction Space¶
Core ontology sits in a crowded region of the domain-specific corpus (33rd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Semantic Knowledge Representation (29 abstractions)
Nearest neighbors
- Semantic integration — 0.91
- Minimal mappings — 0.91
- MultiNet — 0.90
- Terminology server — 0.90
- Information model — 0.90
Computed from structural-signature embeddings · 2026-09-08