Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:25:10 UTC

A.6.RSIR:11 - SoTA-Echoing

The comparisons below inform this bounded recovery: distinguish the engineering objects before selecting their direct rule. They do not supply the obtaining or identity rule for the recovered object.

Practice or source lineWhy it matters for RSIRFPF adoption in this pattern
Modular ontology design-pattern work, including MODL, MOMo, and commonsense ontology micropatterns such as Shimizu and Hitzler 2024 and Eells, Dave, Hitzler, and Shimizu 2024.Ontology-engineering contribution: use small reusable ontology structures without copying local slot doctrine across patterns.Adopt and narrow: RSIR does not become an ontic registry. It recovers the current governed object, leaves participant meaning and actual participation with the direct relation pattern, uses A.6.5 only for a current RelationSignature SlotSpec, uses the chosen representation’s conventions for positions and their correspondence, and uses E.24 only for durable ontic decisions.
Ontology-interoperability lifecycle work such as Qiang 2025 and 2026.A caution that overlapping labels and conflicting local concepts become expensive if not settled before reuse, matching, and validation.Treat interface, slot, function, Method, concern, and bare role as recovery cues until the current EntityOfConcern, direct relation and participants, declaration, any representation position and correspondence, and direct pattern are named by use; bare role starts at E.10.ROLE.
Process-representation ODP work such as Norouzi, Hertling, Waitelonis, and Sack 2025.A warning that process and workflow ontologies often hide implicit patterns from domain users.Adapt for RSIR source labels: “process”, “workflow”, “method”, “function”, “parameter”, and “interface” may remain useful source labels, but they do not carry FPF-governed content until the direct method, work, transformation-flow, role, slot, publication, or evidence pattern is selected.
gUFO, UFO, and OntoUML role, relator, situation, and high-order type practice, including Almeida, Guizzardi, Sales, and Fonseca 2026.A foundational-ontology warning against flattening system classifications, assignment occurrences, participant meanings, declaration-local slots, representation positions, status classifications, and evidence uses into one taxonomy.Use only as a bounded comparator. FPF recovers local system-role kinds and direct U.SystemRoleAssignment species separately; direct patterns retain participant meanings, A.6.5 retains declaration-local SlotSpecs, the chosen representation and its conventions supply positions and their correspondence, and episteme uses retain their direct relations.
Engineering architecture practice around functions, ports, modules, interfaces, signatures, and views.A.6.M, A.6.F, A.6.0, E.18, C.30, C.30.ASV, C.30.AD and C.30.TFS-REL define the different objects named by these related terms.Adapt as a positive recovery map: preserve interface and function language as recognition cues, then recover module-interface, signature, functional port, transformation-flow, architecture-of, structural-view, architecture-description, API publication, protocol, or plain source-label use by current claim.