Skip to content

Quality inherence

Refuse to let a property exist on its own — bind every attribute to a bearer, a context, and the inherence relation that ties them, so a value with no namable owner is a category error, not a discovery.

Version
v4 · 2026-09-28 · History · 2 corrections
Domain-specific #
118
Domain group
Humanities
Origin domain
Philosophy
Subdomain
Upper Ontology → Philosophy

Core Idea

Quality inherence is the ontological commitment, foundational to upper-ontology frameworks like the Basic Formal Ontology (BFO), that a property — a mass, a color, a credit score — cannot exist as a free-standing particular. It exists only as a feature of some bearer, tied to that bearer's identity through an inherence relation (BFO's inheres_in). A property without a bearer is not undiscovered; it is a category error.

How would you explain it like I'm…

No Color Without a Thing

A color can't just float around by itself — there is always something that is red, like a red ball. Quality inherence is the idea that every quality, like a color, a weight, or a temperature, has to belong to some thing. If you find a quality with no thing it belongs to, something has gone wrong.

Every Property Needs an Owner

Quality inherence is a rule used by people who build careful lists of what kinds of things exist, called ontologies. It says that a property — like a mass, a color, or a temperature — cannot exist on its own; it only exists as a property of some thing, called its bearer. So whenever you write down a property, you must say what it belongs to, and usually when and where. A temperature that belongs to no object, or a credit score with no borrower, is a mistake. The fix is always the same: name the bearer.

Properties Depend on Bearers

Quality inherence is the ontological commitment that a property, such as a mass, color, charge or temperature, cannot exist as a free-standing thing; it exists only as a feature of a bearer, and its identity is tied to that bearer. Frameworks like the Basic Formal Ontology (BFO) build this in with an 'inheres in' relation linking each quality to the entity that has it. Every property claim therefore binds a bearer, the quality, and a context such as a time, place, or comparison class. Two things with the same value — two apples of the same red — may be seen as having distinct individual qualities, or as sharing one quality type, but either way each quality instance belongs to its own bearer and cannot be moved to another. The rule does not say which properties are essential or whether properties can change; it only says properties are the kind of thing that depends on a bearer to exist.

 

Quality inherence is the commitment, foundational to upper ontologies such as Basic Formal Ontology (BFO), that a property is existentially dependent on a bearer: it exists only as a feature of some entity, and its identity conditions are tied to that entity's. A property with no bearer is treated as a category error rather than as something undiscovered. Every property claim has the same structure: a bearer with independent identity conditions, an inherence relation (BFO's inheres_in), the quality, and a context such as time, place, or comparison class. On a trope reading, two bearers with the same value have numerically distinct qualities; on a universals reading, the quality type may be shared, but each quality token is still borne and non-transferable. The commitment blocks errors such as a color with no colored thing or a credit score with no borrower, and its remedy is always to name the bearer. It appears as BFO's Quality class and inheres_in relation, as the rule that attributes belong to entities in conceptual data modeling, and as fields bound to instances in software type systems. It makes no claim about essential versus accidental properties, causal origin, mind-dependence, or persistence through change.

Scope of Application

Quality inherence lives within upper ontology and formal modeling, where the bearer–quality–context grammar is explicit machinery that refuses to instantiate a free-standing property.

  • Basic Formal Ontology (BFO) — the home: bfo:Quality and bfo:inheres_in enforce existential dependence on a bearer.
  • Foundational ontologies (DOLCE, UFO) — qualities and modes encoding the same dependent-property commitment.
  • Conceptual data modeling (UML, entity-relation) — the rule that attributes are always attributes-of-an-entity.
  • Software type systems — records and objects whose fields lose identity when detached from their instance.

Clarity

Naming quality inherence stops the silent slide from a value to a thing that has that value, as though "38.7°C" or "AA-rated" were a particular one could store or transfer. It separates the bearer, the existentially dependent quality, and the manifestation (the measured value). The modeler stops asking "what is the temperature?" and asks the sharper "whose temperature, when, under what comparison class?"

Manages Complexity

An upper ontology must accommodate endlessly varied properties, each with its own measurement and baggage. Quality inherence collapses that catalog into one fixed grammar: every property resolves into the same slots — a bearer, a quality that inheres in it, a context, a manifestation. The modeler stops reasoning case by case and instead fills one inherence schema, with mis-modeling reduced to a single diagnostic: an unbound quality is a category error.

Abstract Reasoning

Holding the inherence grammar turns it into working moves: a diagnostic detecting unbound qualities (no namable bearer signals a malformed class upstream), an interventionist repair (name the bearer, reattach through the relation), reading change as a bearer losing one quality and gaining another, and boundary-drawing that separates inherence from causal dependence, essential-versus-accidental status, and persistence.

Knowledge Transfer

Within formal modeling the commitment transfers as mechanism, its grammar and diagnostics intact across BFO, DOLCE, UML, and type systems — co-instances of one discipline, not analogies. Beyond formal frameworks the reach thins to the bare metaphysical claim that properties belong to things, which is substrate-neutral and already carried by the parent primes Relation and Essentialism; the BFO class apparatus is the domain-specific formalization and need not travel.

Relationships to Other Abstractions

Local relationship map for Quality inherenceParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Quality inherenceDOMAINPrime abstraction: Relation — includesRelationPRIMEPrime abstraction: Dependency — is a decomposition ofDependencyPRIME

Current abstraction Quality inherence Domain-specific

Parents (2) — outgoing typed relations

  • Quality inherence includes Relation Prime

    Quality inherence contains the bearer-to-quality inherence relation that binds every property-token to the particular on which it existentially depends.

  • Quality inherence is a decomposition of Dependency Prime

    Quality inherence is the upper-ontology form of existential dependency in which a property-token cannot exist without its bearer.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Quality inherence sits in a moderately populated region (55th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Property Ontology & Code Smells (18 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25