A.6.P:4.4 - Keep world-side, declaration, assertion, designation, and representation objects distinct
| Object | Engineering question | Defining or constraining rule |
|---|---|---|
| direct relation kind | Which obtaining occurrences fall under this classificatory distinction? | direct relation pattern, with A.6.RCD and E.24 when admission is current |
| relation-participant meaning | How does one actual participant contribute to the obtaining predicate while retaining its own kind? | direct relation pattern |
| actual participant | Which exact independently governed entity participates under that meaning? | participant’s direct pattern and the direct relation pattern |
| semantic predicate and applicability | Under which condition and qualifications does the direct relation obtain for those participants? | direct relation pattern |
RelationSignature declaration | Which relation semantics and typed participant declarations are reusable? | A.6.0 |
declaration-local SlotSpec | Which participant meaning, participant ValueKind, and receiving-episteme designation mode are declared for typed reuse? | A.6.5 |
| relation-participant designation | Which value or governed reference in a receiving episteme denotes one actual participant? | C.2.1, with A.6.5 only when a compatible SlotSpec is current |
| relational assertion | Which episteme affirms or denies the direct predicate, or carries another exact claim-family modality? | C.2.1 plus the direct claim pattern |
| relation-occurrence description episteme | Which episteme describes one already individuated occurrence? | C.2.1 |
| individuated relation occurrence | Which obtaining occurrence does a later claim or direct relation compare, qualify, nest, or reference? | direct relation pattern with A.6.REL |
| designator and reference use | Which governed name denotes an already recoverable object, and which receiving episteme uses that reference? | F.18 and the receiving claim pattern |
| publication relation | Which episteme edition is made available, to whom, and for which use? | E.17 and E.24.PUB |
| representation element | Which table field, row, tuple component, graph edge, formula position, functional expression, or arrow corresponds to an independently governed object or claim content? | C.29 for the explicit correspondence; the representation object’s own pattern for its identity and change |
A representation can correspond to a direct relation, assertion content, declaration, participant designation, or already recoverable occurrence. State the exact source element, represented FPF object or claim content, and explicit C.29 correspondence. Representation form neither makes the relation obtain nor supplies participant or occurrence identity.
Functional and arrow forms are assertion or representation notation. The following installed-part example is hypothetical: a relied use first needs the missing direct relation and occurrence rules identified in §5.1.
installedPartOf(Bearing_B, Pump_P, during=Interval_T)
Bearing_B --installedPartOf{during=Interval_T}--> Pump_P
The first can represent the content of a relational assertion; the second is a binary projection in a selected representation. After those rules exist, a use that relies on either notation declares how its argument or endpoint elements correspond to the actual participants, direct predicate, qualifications, and any designated occurrence. The ordinary readable sentence remains sufficient when no representation-dependent use is current.