A.6.REL:11 - SoTA-Echoing
A.6.REL:11.1 - Ontological SoTA and constructional sources
This pattern uses these sources to constrain its account of occurrence existence and identity. They provide ontological comparisons, not notation selection.
| Ontological source | What it contributes | FPF adoption, mutation, and practical effect |
|---|---|---|
| Florio and Linnebo, Introduction to Constructional Ontology, 2024 | Separates constructors, constructor inputs, the source account’s construction process, and output identity. | Adopt the construction test and adapt the source process to FPF method and work distinctions. Section 4.3 asks which system acts as constructor, which method it enacts, which entities are inputs, which work it performs, and how that work occurrence contributes to output or relation identity. Row creation and assertion remain non-constructive unless the direct rule declares the corresponding work constitutive. |
| Borgo and Righetti, Towards Applied Constructional Ontology, 2025 | Tests how constructional analysis could reconstruct existing foundational ontologies and exposes conceptual, structural, completeness, and consistency questions; it is an early applied step, not a finished recipe. | Adapt with that maturity boundary. Checklist 9 and the physical case require a recoverable construction choice instead of accepting an inherited relation representation or taxonomy. |
| Partridge, BORO Ontology, C-FORS 2025 presentation | Presents a 4D extensional, categorical, and constructional ontology with an ontology-evolution method. | Adapt as a current ontological comparison under a boundary. Sections 4.3 and 5.1 use temporal extent and constituting occurrences when the direct identity rule needs them. FPF rejects universal 4D identity, unrestricted composition, and BORO’s category architecture for this pattern. |
| Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint | Provides a current foundational-ontology implementation with differentiated relational-aspect and reification patterns. | Adapt its ontological distinctions as a current comparison; reject its OWL implementation as proof of FPF occurrence existence or identity. Section 4.4 separates direct relation, assertion, reifier, and optional relator without importing the complete category hierarchy. |
| OntoUML Relator, specification lineage | Models a relator as a dependent truth-maker for a material relation. | Reject as current competitive SoTA; retain and adapt as a lineage comparison for material relators. Section 4.4 permits a relator only when the direct material ontology identifies the relator, its dependence relations to the participants, and its occurrence-identity rule. |
A.6.REL:11.2 - Representation and implementation stress tests
This pattern uses these sources to test whether the selected ontological distinctions can be represented and used. They do not determine what relation occurrences exist or how they are identified.
| Representation or implementation line | Distinction tested | Bounded use in A.6.REL |
|---|---|---|
TypeDB 3.x links statement and current relation model | A query can expose a relation variable with named source-language role players, while shorthand remains available when the represented relation instance need not be referenced. That source term denotes neither an FPF system-role kind nor a system-role assignment. | Adapt as a representation stress test; reject as an ontology source. Sections 4.2, 4.5, and 4.6 preserve a readable direct relation before explicit individuation. TypeDB demonstrates one implementable representation; it does not establish the FPF relation kind, obtaining condition, or identity rule. |
| RDF 1.2 Concepts, Candidate Recommendation Snapshot, 7 April 2026 | Distinguishes a proposition expressed by a triple term, assertion of a triple, and reifiers used for further statements. | Adapt as a representation stress test; reject graph syntax and reifier identity as world-side identity sources. Sections 4.4 and 5.3 apply that distinction to proposition, assertion, and reifier separation. |
The worked cases expose both boundaries outside information-system projects.