FPF Reference

    Aspect branch application

    Preface node heading:aspect-branch-application:24525

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    For AspectOf, the BORO and CCO rows above supply the constructor-sensitive question: which bearer, facet rule, dependent aspect, and identity conditions make this structural part? Fine's composition-first pressure blocks a bare aspect label from deciding parthood. A.14 adapts that line in A.14:5.3, the decision procedure, and CC-ASP-1 through CC-ASP-4; C.13 slice remains an optional report, not the constructor of the aspect. The serious alternatives are routed rather than renamed: measured Characteristic (C.16/A.19), viewpoint or view (E.17), representation or projection (C.29 or its direct pattern), selected partition, and temporal restriction (PhaseOf/C.27.TA). This route is no worse for correctness and cheaper for a cold reader than a universal aspect kind; its cost is that the author must identify the actual relation before reusing the word.

    The resulting collection alternatives are deliberately distinct:

    • Selected: an ordinary subject-specific belongs-to sentence plus the collection's own rule.
    • Rejected: one generic MemberOf, because it collapses formal inclusion, classification, participation, collection belonging, and constructive parthood.
    • Rejected for present public use: one qualified generic collection-belonging predicate, because its qualifiers must recreate every subject rule and make the first move harder.
    • Retained as a separate possible claim: constructive parthood, but only when its direct relation obtains and all six A.1 matters pass.

    At comparable correctness and temporal adequacy, the selected answer is no worse than the qualified or separately named alternatives and is cheaper for a cold reader and maintainer. A generic predicate looks cheaper only because it omits decisive conditions. The real cost is that A.14 supplies no immediate cross-domain query key for all belongs-to relations; use F.18 to name a narrower relation when repeated query, comparison, or declaration use justifies that extra vocabulary.

    The rest of the catalogue retains its own governing source lines:

    • Metrical mereology advances motivate PortionOf with explicit μ and Σ-laws, preventing the classic “stuff as components” fallacy.
    • Temporal parts and identity through change motivate PhaseOf as transitive proper temporal parthood, with nesting and overlap allowed, partition-specific coverage and non-overlap, and escalation when identity criteria fail.
    • Engineering product models, including the ISO 15926 family, pressure authors to keep functional classification, physical product breakdown, and stocks or consumables distinct; A.14 routes those claims to their direct relations instead of one part tree.
    • Knowledge-episteme edition histories in contemporary MBSE and open-science practice motivate explicit endpoint identities and provenance-preserving composition. FPF uses the C.2.1 identity triple and independently obtaining EpistemeEditionRelation for distinct editions; A.14 retains PhaseOf only for a proper temporal restriction of one unchanged episteme.

    The net effect is a minimal-sufficient catalogue: direct component, constituent, portion, bearer-dependent aspect, phase, and collection-belonging claims stay distinct, while a separately grounded constructive part claim remains possible without another universal relation vocabulary.

    Treat this source account as current for this edition. Reopen only the affected A.14 rule if a cited constructional source changes a distinction used here, a newer relation architecture provides the same claim correctness and history at lower reader or maintenance cost, or a direct consumer needs a meaning that the current rule cannot express. Recheck A.14:5.3 and CC-ASP-1 through CC-ASP-4 for an AspectOf change; recheck Solution item 5 and CC-MEM-1 through CC-MEM-3 for a collection-belonging or separately grounded parthood change. An ordinary change to a bearer, facet rule, aspect occurrence, collection rule, belonging occurrence, or optional trace reopens only that claim and its support, not this source decision.

    Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)