E.10.D1:11 - SoTA-Echoing
| Practice question | Current or lineage source | Use of source | FPF response | Adoption status |
|---|---|---|---|---|
| How should terminology distinguish the thing discussed, its concept, definition, and designation? | ISO 704:2022, Terminology work — Principles and methods. | Current terminology-work reference for this narrow distinction; it is not authority over FPF ontology. | C.2.1, F.17, and this pattern keep the claim-bearing episteme, reference scheme, local expression, local-sense claim, designation, and the value designated by that expression separate. | Adopt and specialize. Adopt the separation; use FPF claim and relation identity. |
| How should a model boundary remain explicit in domain-driven design? | Eric Evans, Domain-Driven Design Reference (2015 reference edition); DDD Crew, Context Mapping (maintained practice resource, checked 2026-08-10). | DDD lineage plus current practitioner material: bounded contexts and their relations answer explicit model and integration questions, and small question-specific maps are preferred to one all-purpose map. | A.1.1 defines direct model-applicability, actual-use, and fixed-content-coherence relations and gives the practitioner the condition for selecting BoundedModelUseStructure: their organization must change the engineering decision. | Adapt. Keep the Plain retrieval term and decision focus; reject use as a universal semantic, organizational, or project container. |
| What makes a model usable for one engineering decision rather than usable without qualification? | Erik Rosenlund et al., The Role of Standardization for Simulation in Model-Based Systems Engineering: A Survey Study Supplemented with Industrial Experiences (2025). | The survey and four industry accounts make intended use and known limitations necessary to model handoff and ask whether a model or its result can be used for that intended use. The evidence concerns modeling and simulation practice; it does not define every FPF model relation. | A.1.1 separates model applicability, actual assigned-Work use, and fixed-content coherence. The practitioner therefore starts with the direct relation that changes the decision and selects a wider structure only when its organization matters. | Adopt the use-specific boundary. Reject an unqualified model “context” and reject a metadata package as proof that the relation obtains. Do not import simulation-specific credibility machinery into every model use. |
| Which qualifications belong to a claim rather than to one generic context object? | Veronica dos Santos et al., CoaKG: A Contextualized Knowledge Graph Approach for Exploratory Search and Decision Making (2025). | CoaKG shows that temporal and provenance qualifiers and task constraints can change whether a claim answers a decision. Its contextualized-graph formalism is a comparison source, not an FPF data model. | A.2.6 keeps the claim, U.ClaimScope, admitted slices, qualification window, effective scheme, comparison scheme, and evidence relations distinct. Provenance does not become a member of one universal Context participant. | Adapt the separation. Reject the source’s generic context label as a new U-kind and stop the transfer before its graph representation and inference rules. |
| How should ambiguous wording be repaired when the missing detail changes downstream work? | Anmol Singhal et al., Generating Clarification Questions for Disambiguating Contracts (LREC-COLING 2024). | The study asks targeted clarification questions so non-legal readers can turn ambiguous clauses into actionable requirements. Its contract corpus and automated question generation do not establish a general ontology or an automatic FPF repair. | Step 1 asks what the reader would do differently; the selected recovery branch then returns one repaired statement or an honest unresolved result. A working situation, project use, or reader use is recovered only when naming it changes that action; otherwise the ordinary non-use boundary applies. | Adapt the action test. Keep human judgement and the truthful stop; reject contract-specific automation as the general method. |
| Should architecture, its description, and a viewpoint be recovered as one kind of context? | ISO/IEC/IEEE 42010:2022, Software, systems and enterprise — Architecture description. | This is a published architecture-description comparator, not SoTA authority for FPF architecture. It distinguishes an entity’s architecture from an architecture description and treats viewpoints as conventions used in that description; it explicitly does not define the entity’s architecture or environment. | C.30 distinguishes the described holon, obtaining ArchitectureRelation, selected structure, and ArchitectureClaim. E.17.0 separately tests a candidate episteme against a viewpoint edition. | Adapt only the separations. Do not import its heterogeneous Entity-of-Interest list as an FPF kind hierarchy or treat architecture, viewpoint, and environment as one recovery branch. |
| What does an operating boundary contribute to an environment or operating-condition claim? | Morayo Adedjouma et al., Defining Operational Design Domain for Autonomous Systems: A Domain-Agnostic and Risk-Based Approach (SoSE 2024). | The paper treats an operational design domain as a delimited operating domain that combines technological, environmental, regulatory, and user considerations for autonomous systems. It does not make an environment an architecture or viewpoint. | The environment branch returns to the subject claim and names the holon, relation, state, qualifier, constraint, or condition whose change affects the claim or action. | Adapt the explicit operating boundary. Reject automatic promotion to architecture and stop the transfer at claims about operating conditions; the paper does not supply a universal environment ontology. |
| How should lexical labels remain distinct from concepts, schemes, and ontology entities? | W3C SKOS Recommendation (2009) and OntoLex-Lemon Community Report (2016). | Older but still current reference models for this limited separation. Their classes and mapping properties are source vocabulary, not imported FPF relation semantics. | F.17 defines local expression and sense under a by-value scheme; F.9 independently tests each direct Bridge and each proposed bounded use. | Adapt. Keep label/sense/scheme separation; reject scheme membership or a mapping label as relation truth or use permission. |
These comparisons support the recovery branches for the wording uses named here. They do not show that the branch set is complete for every use of context or that this method dominates every alternative. The comparison changed the method in four places: it made intended model use explicit; kept claim scope, qualification, and provenance separate; split architecture, viewpoint, and environment; and made the wording repair depend on the reader’s next action. Reopen the method when a subject pattern defines a better distinction, a recurring use of context needs another productive branch, or a current practice source changes one of these action-bearing separations.