SIE.3:11 - SoTA-Echoing
The practice question is how to settle an available model’s adequacy for the receiving questions when that adequacy is still unknown. For the inspection question in §5.2, the selected starting line is requirements-led model qualification: recover the distinction between requirement, plan, and observation, try the available meanings, and develop only the gap that survives that trial. This adapts LOT and its maintained resources.
A serious alternative for that same unsettled question is to develop the model together with a small knowledge-graph prototype, adapting the ontology-and-graph work described by LOT4KG. The prototype can reveal a missing relation when the receiving query is executed. Compare a bounded prototype with bounded model qualification, rather than charging it for a complete production platform:
| Answer to the same inspection-model question | Comparable work and useful evidence | Choice and accepted trade-off |
|---|---|---|
| Qualify or extend the model before selecting its realization | Examine the required definitions with domain participants and replay the requirement/plan/observation, configuration, unit, and time cases. Keep the model and cases sufficient for that query. | Adapt LOT in §4.1.1–5 and §5.2. This settles the semantic distinction without choosing graph encoding or query machinery. It supplies no evidence that an executable mapping or query is correct; SIE.7 and SIE.10 still need that evidence for their own claims. |
| Qualify the model through a small graph and executable query | Examine the same definitions and cases, then encode representative instances and the query. This adds encoding and execution work but can expose errors that a prose-only model trial misses. | Adapt the LOT4KG route when execution can settle an uncertainty material to model adequacy, especially when graph realization is already selected. In §5.2, the first unresolved issue is what counts as an observation; executing a query over a class that also includes plans cannot settle that domain meaning. The model-first route is selected for that issue, accepting deferred execution evidence. |
The comparison is qualitative and scoped to the same questions and counterexamples; it is not a claim that one route is always cheaper or more effective. A prototype’s additional effort earns its place when it can change the qualification. Neither route can replace domain meaning with successful execution.
The remaining contributions constrain that choice:
| Source and comparison role | Operative move and limit |
|---|---|
| LOT supplies the selected requirements, development, publication, and maintenance line. | Adopt domain questions and participant validation; adapt §4.1.3 and §4.1.7 so sufficient reuse can finish and the receiver can rely on a maintained model. The source does not decide local meanings or establish this model’s adequacy. |
| LOT4KG supplies the coupled ontology/graph alternative. | Adapt its separation of ontology work and graph construction to the comparison above; reject treating graph construction as the only way to qualify a model. Its described activities support this alternative, not a measured superiority claim. |
| OWL 2 Overview supplies language and profile choices when formal semantics matter. | Adapt §4.1.6: check the properties actually claimed for the chosen language as well as the domain cases. Encoding validity cannot replace the model-adequacy question. |
| The public ISO/IEC 21838-1 scope supplies a possible top-level basis. | Adapt §4.1.2/6 only when that basis contributes needed coherence. It establishes neither a universal upper-ontology requirement nor local maintenance and versioning rules. |
Reopen the comparison if one required answer depends on a selected query or inference behavior that the model-only trial cannot settle, if a bounded prototype exposes a missed distinction, or if an available model can now answer the same cases with less qualification work. Return only to the affected question and §4.1.2–6. An already qualified model for an unchanged use remains the sufficient direct result in §4.1.3.