The reverse reading is named, not improvised
Answers Derivation · Nomenclature
A relationship is stored once, and its reverse is read, never asserted. But a reading needs a name: the reverse of 'includes surface' is not 'is includes surface by'. Each relationship therefore declares its inverse verb, so that the same one assertion reads as a sentence from either end. OWL 2 states the discipline: declare one property the inverse of another and the reverse follows by inference. The inverse inherits the claim, differs from the forward verb, and is never the forward verb wrapped in 'is ... by'.
What goes wrong without it
A relationship stored once still has to be readable from both ends, and a mechanically generated reverse produces phrases no one would write. Declaring one property the inverse of another lets the reverse follow by inference and still read as language. It is what keeps a structure traversable in both directions without asserting anything twice.
What proves it — 1
Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.
- registry integritynamed inverse
Every relationship names the verb its reverse reading uses; it differs from the forward verb and is never the forward verb wrapped in 'is ... by'.
Derived from — 2
Where this model stands
Every relationship names its inverse, and the reader uses it wherever a relationship is read from its target.
An inverse must exist, must differ from the forward verb, and is never the mechanical 'is <verb> by' form.
What it does not claim
No relationship is symmetric, so no inverse equals its verb; if one ever does it must declare symmetry rather than pass silently.
RUL-018