Situation / State of Affairs¶
Local identifier:
xwkont:concept:situation-state-of-affairsSlug:situation-state-of-affairsEditorial status:reviewedCreated:2026-07-04Modified:2026-07-08
Scope Note¶
Selection rationale (per ADR-0018's admission bar): Situation / State of Affairs is the fifth concept drafted from the 0.2.0 batch. TODO.md's own seed flagged this candidate as "weaker/more UFO-centric than [Space, Abstract, Quantity]; good test of whether it generalizes or stays source-specific." An initial direct-verification pass (2026-07-04) found only 1 of 8 sources (GFO) with an unambiguous formal class, and an independent external review reached the same HOLD conclusion, recommending DOLCE's DnS module and GFO's Configuroid be fetched before deciding this crosswalk's fate.
Follow-up primary-source pass (2026-07-05) fetched both: DOLCE's separate ExtendedDnS.owl module (xwkont:ref:dolce-extendeddns-owl) and the remainder of modules/gfo-base.owl plus GFO's dedicated modules/situation/gfo-situation.ttl module. Both resolved in favor of a materially stronger cross-source pattern than the initial pass found:
- DOLCE — contrary to the initial pass's "DOLCE has no formal situation class" finding (which only checked core
DOLCE-Lite.owl), DOLCE's separate DnS module does formally define#situation, equivalent tonon-agentive-social-object ⊓ setting-for(some particular) ⊓ satisfies(some description). This is DOLCE's real treatment of the concept — coreDOLCE-Lite.owl's own commentary had said as much, but this pass is the first to independently fetch and verify it. - GFO — the initial pass stopped at the parent class
Configurationand missed a class literally namedSituation(rdfs:subClassOf Configuration) in the samegfo-base.owlfile, plus an entire dedicatedsituationmodule (gfo-situation.ttl) with its own:Situationclass built on a different superclass lineage (gfo-core:TimeExtendedIndividual). GFO treats this concept seriously enough to warrant a whole extension module, not just a passing base-ontology class. - UFO — unchanged from the initial pass:
ontouml:situationis a genuine, well-documented OntoUML-vocabulary construct, though still not reified in the 2021 comprehensive paper's own prose.
Net effect: 3 of 8 sources (GFO, DOLCE, UFO) now have an unambiguous formally-defined class matching this concept's core sense — DOLCE moves from "no correspondence, state is a different sense" to a genuine second solid correspondence. This is still short of ADR-0018's original ≥3-source seed count in the strict sense of "named in the seed," but is now comparable in strength (not just source-count) to the batch's other concepts. See Uncertainty for the updated maintainer decision.
This crosswalk compares each source ontology's own treatment of a "situation"/"state of affairs"-like category — a configuration or circumstance comprehended as a whole, typically description- or context-dependent — distinct from Event/Process (already reviewed) and from Quality/Quantity's own notion of a value "holding" at a time. Sources compared: BFO, DOLCE, SUMO, UFO, GFO, YAMATO, TUpper, GUM (per ADR-0015's 8-source scope).
Cross-cutting finding, established this session: the word "situation" is used informally, as a world- or time-index, in several sources' own prose (DOLCE's state/process/stative comments; UFO's 2021 paper) without ever being reified as a class there — this is a citation-precision trap distinct from, but related to, the ones found in time.md/quantity-amount-of-matter.md: informal usage of a term is not the same as that term being a defined category in the source, even when the source's own commentary explicitly gestures at the concept (DOLCE's comments describe what a "situation" would be — a description-dependent unifying criterion for a perdurant — while explicitly declining to formalize it in the fetched module; that formalization lives in DOLCE's separate DnS (Descriptions and Situations) extension, not core DOLCE-Lite). See note-001, note-002.
Exclusions: this crosswalk does not address Universal/Type (a separate 0.2.0-batch candidate; UFO's OntoUML stereotype vocabulary — already the primary source for this crosswalk's UFO row — also defines type/kind/phase stereotypes relevant there) or Event/Process (already reviewed; DOLCE's stative/state/process branch is directly relevant background, already covered by process.md and event.md for the occurrent side of this comparison).
Core.ttl placement resolved 2026-07-08 (session-060, maintainer-confirmed). Re-examination found the external review's three-way sense split (configuration/comprehended-whole sense: GFO Configuration/Situation, UFO OntoUML situation; stative occurrent sense: DOLCE State; fluent/proposition-holding sense: TUpper state) was already resolved within this crosswalk's own content by the 2026-07-05 follow-up pass: the reviewed correspondence set covers only the configuration/comprehended-whole sense (GFO Situation in both its modules, DOLCE's DnS-module situation, UFO's OntoUML situation stereotype — 3 real sources); DOLCE's occurrent State is retained only as an explicitly-flagged non-equivalent entry (mapping-002), and TUpper's fluent-like state was never given a correspondence at all. The senses were never actually collapsed — uncertainty-001's structured field had simply never been marked resolved to reflect what the Review History narrative already claimed. xwkont-core:SituationStateOfAffairs was added to data/ontology/core.ttl as a sibling of Object under Continuant, following GFO's own Presential-side Situation and DOLCE's own non-agentive-social-object placement of situation — both continuant-committing sources place their evidence on the continuant side. See data/ontology/core.ttl.
Labels, Alternate Labels, and Source Terminology¶
| Role | Label or term | Source | Language | Notes |
|---|---|---|---|---|
| XwkOnt working label | Situation / State of Affairs | XwkOnt | en |
Not yet in data/ontology/core.ttl — see Scope Note. |
| Alternate label | (no class — see Uncertainty) | BFO | en |
Zero occurrences of "situation" in bfo-core.ttl. |
| Source term | State | DOLCE | en |
A formally defined class, but denotes a stative occurrent (perdurant subtype), not a configuration-of-entities category — see note-001. |
| Alternate label | (only as an axiom-variable name — see Uncertainty) | SUMO | en |
?SITUATION is conventional variable naming for a ?FORMULA-typed argument to holdsDuring, not a defined class. |
| Alternate label | Situation | UFO | en |
Used informally (world-index) throughout the 2021 paper's prose, never reified there; ontouml:situation/ontouml:situationNature are real, formally documented OntoUML vocabulary terms — see note-002. |
| Source term | Configuration / Situation | GFO | en |
Configuration is the base class; Situation (rdfs:subClassOf Configuration, in the same gfo-base.owl file) is the most-specific match, plus a dedicated situation extension module with its own :Situation class — see below. |
| Source term | situation (DnS module) | DOLCE | en |
Formally defined in DOLCE's separate ExtendedDnS.owl module (not core DOLCE-Lite.owl) — see below. |
| Alternate label | (no defined class — see Uncertainty) | YAMATO | en |
Not checked in TODO.md's seed; confirmed no defined class in the fetchable document (see Source Definitions). |
| Alternate label | State (informal, fluent-like) | TUpper | en |
Used only inside holds/prior's own informal-semantics glosses ("the state f"), never separately defined. |
| Alternate label | (no class — see Uncertainty) | GUM | en |
Zero occurrences of "Situation"/"StateOfAffairs" in GUM-31.owl. |
Source Definitions and Contextual Notes¶
| Source | Term or identifier | Dimension | Claim type | Definition, quotation, or paraphrase | Reference | Locator | Notes |
|---|---|---|---|---|---|---|---|
| BFO | (no class found) | technical | non-equivalence | Full-text grep of bfo-core.ttl for "situation" (case-insensitive) returned zero matches. |
xwkont:ref:bfo-2020 |
verified absence: bfo-core.ttl, fetched and read directly 2026-07-04 |
Consistent with BFO's general austerity about description-dependent/context-dependent categories, already observed for Quantity in quantity-amount-of-matter.md. |
| DOLCE | State (+ stative) | technical | direct quotation | "Within stative occurrences, we distinguish between states and processes according to homeomericity: sitting is classified as a state but running is classified as a process, since there are (very short) temporal parts of a running that are not themselves runnings." rdfs:subClassOf stative; stative itself rdfs:subClassOf perdurant. |
xwkont:ref:dolce-lite-owl |
verified: DOLCE-Lite.owl, class #state, fetched and read directly 2026-07-04 |
A real, formally defined class — but an occurrent (stative perdurant) category distinguished from process by homeomericity, not a "configuration of entities"/situation-like category. See note-001 for the separate sense of "situation" DOLCE's own comments discuss but do not formalize here. |
| DOLCE | (situation — discussed in commentary, not reified in this module) | philosophical | paraphrase | The same class's own comment continues: "states differ from situations because they are not assumed to have a description from which they depend... at any time, one can conceive a description that asserts the constraints by which a state of a certain type is such, and in this case, it becomes a situation... If we want to consider all the aspects of a process together, we need to postulate a unifying descriptive set of criteria (i.e. a 'description'), according to which that process is circumstantiated in a 'situation'." No class named #situation exists anywhere in the fetched DOLCE-Lite.owl. |
xwkont:ref:dolce-lite-owl |
verified absence in this module: DOLCE-Lite.owl, full-text grep for #situation returned zero matches, fetched and read directly 2026-07-04 |
DOLCE's own prose explicitly attributes formal treatment of "situation" and "description" to a separate module (the well-known DnS — Descriptions and Situations — extension), not to core DOLCE-Lite. This crosswalk records the absence in the fetched artifact rather than assuming DnS content without fetching it separately — resolved below (xwkont:ref:dolce-extendeddns-owl). |
| DOLCE | situation | technical | direct quotation | "A situation is a social object that appears in the domain of an ontology only because there is a description whose components can 'carve up' a view (setting) on that domain. A situation has to satisfy a description..., and it has to be setting for at least one entity. In other words, it is the ontological counterpart... of settings (situations from SC, contexts, episodes, states of affairs, structures, configurations, cases, etc.). A perdurant is usually the only mandatory constituent of a setting." owl:equivalentClass of non-agentive-social-object ⊓ setting-for(some particular) ⊓ satisfies(some description); owl:disjointWith collection, concept, information-object, figure, description. |
xwkont:ref:dolce-extendeddns-owl |
verified: ExtendedDnS.owl, class #situation, fetched and read directly 2026-07-05 |
Resolves uncertainty-002: DOLCE's DnS module — not core DOLCE-Lite.owl — does formally define a situation class matching this concept's core sense, and its own comment explicitly glosses it as the ontological counterpart of "states of affairs... configurations... cases." This is DOLCE's real, previously-unfetched contribution to this concept — see note-004. |
| SUMO | (no class — ?SITUATION is a conventional variable name only) |
technical | non-equivalence | (holdsDuring ?TIME ?SITUATION1) ... (entails ?SITUATION1 ?SITUATION2) — ?SITUATION here is a variable of the same type as holdsDuring's own documented second argument, ?FORMULA: "(holdsDuring ?TIME ?FORMULA) means that the proposition denoted by ?FORMULA is true in the time frame ?TIME." One further prose occurrence: "permit assessment of the probability of an event or situation" (informal, inside a different term's documentation). |
xwkont:ref:sumo-niles-pease-2001 |
verified absence: current Merge.kif, full-text grep for "situation" (case-insensitive) returned 12 hits, all either the ?SITUATION variable-naming convention or incidental prose, fetched and read directly 2026-07-04 |
No (subclass Situation ...) or (instance Situation ...) assertion exists anywhere — ?SITUATION is informal variable-naming sugar for a Formula/Proposition-typed argument, not a distinct SUMO class. |
| UFO | (no reified class in the 2021 paper; informal world-index usage only) | technical | non-equivalence | All 21 occurrences of "situation" in the paper's full extracted text are informal, world-indexing usage — e.g. "the value of a given FlowerColor can change from situation to situation," "in a counterfactual situation," "in world w1... in that situation" — never (instance x Situation)-style reification or a defined Situation class/stereotype in the paper's own axioms. |
xwkont:ref:ufo-2021 |
verified absence in the paper itself: 2021 Applied Ontology paper, full-text re-searched directly 2026-07-04 (21 occurrences individually inspected) | This is a genuine gap between the 2021 comprehensive paper (silent on a formal Situation class) and the wider UFO/OntoUML literature (which does formalize it) — see the next row and note-002. |
| UFO | situation (stereotype) / situationNature | technical | direct quotation | ontouml:situation: "Can be used to represent certain configurations of entities that can be comprehended as a whole." ontouml:situationNature: "Indicates that the restricted type includes situation individuals among its instances." |
xwkont:ref:ontouml-vocabulary |
verified: ontouml.ttl, fetched and read directly 2026-07-04 |
Confirms TODO.md's seed naming exactly. Notably, this definition ("configurations of entities... comprehended as a whole") is close in spirit to GFO's Configuration definition below — the two sources' formal treatments (OntoUML's stereotype vocabulary; GFO's base ontology class) converge more closely with each other than either does with DOLCE's occurrent-side state. |
| GFO | Configuration | technical | direct quotation | "We consider a collection of presential facts which exist at the same time-boundary. Such collections may be considered themselves as presentials, and we call them configurations. It is further required that configurations contain at least one material object." rdfs:subClassOf Presential; owl:disjointWith Material_boundary, owl:disjointWith Material_object. |
xwkont:ref:gfo |
verified: modules/gfo-base.owl, class Configuration, fetched and read directly 2026-07-04 |
The base-ontology class; see the more specific Situation subclass below, which is the closer match to this concept's core sense. |
| GFO | Situation | technical | direct quotation | "A situation is a special configuration which can be comprehended as a whole and satisfies certain conditions of unity, which are imposed by relations and categories associated with the situation. Herein, we consider situations to be the most complex kind of presentials." rdfs:subClassOf Configuration. |
xwkont:ref:gfo |
verified: modules/gfo-base.owl, class Situation, fetched and read directly 2026-07-05 |
Resolves uncertainty-003. Missed by the 2026-07-04 pass, which stopped at the parent Configuration class — GFO independently names its most-specific configuration-of-entities class Situation, the exact term this crosswalk targets. Sibling classes Configuroid (rdfs:subClassOf Process — the occurrent-side counterpart to Configuration) and Situoid (rdfs:subClassOf Configuroid; "processes whose boundaries are situations... the most complex integrated wholes of the world") were also found and glossed. |
| GFO | Situation (dedicated module) | technical | direct quotation | skos:definition: "Situations as complex entities that are comprehended as wholes." rdfs:subClassOf gfo-core:TimeExtendedIndividual, plus restrictions requiring hasParticipant some Object and hasSituationPart some Attributive. |
xwkont:ref:gfo |
verified: modules/situation/gfo-situation.ttl, class :Situation, fetched and read directly 2026-07-05 |
A second, independently-maintained GFO module (versioned separately, https://w3id.org/gfo/situation) dedicated entirely to situation theory — distinct superclass lineage (TimeExtendedIndividual, not Presential/Configuration) from the base-module Situation class above. Flagged as an internal GFO cross-module naming/lineage inconsistency, not resolved further in this pass — see note-005. Confirms GFO treats this concept as substantial enough to warrant a dedicated extension, strengthening rather than weakening GFO's correspondence. |
| YAMATO | (no class found) | technical | non-equivalence | Full-text search of the extracted YAMATO 2010 technical report for "situation" and "configuration" (case-insensitive) found no defined class or criterial distinction matching this concept — the document's own top-level distinctions (Substrate/entity, Continuant/Occurrent, Physical/abstract, already documented in time.md/space.md/abstract-concrete.md) do not include one. |
xwkont:ref:yamato-mizoguchi-2010 |
verified absence: 2010 technical report, full extracted text re-searched directly 2026-07-04 | Not part of TODO.md's original seed for this concept; checked directly for completeness, consistent with this crosswalk's practice (and the other four 0.2.0-batch crosswalks') of checking all 8 sources regardless of the seed's own coverage. |
| TUpper | (informal fluent-like usage only, no defined predicate) | technical | non-equivalence | holds: "(holds f occ) is TRUE in an interpretation of TUpper if and only if the state f is true after the activity occurrence occ." prior: "...the state f is true prior to the activity occurrence occ." No state or fluent predicate/class is separately declared or defined anywhere in TUpper-Terms.html. |
xwkont:ref:tupper-colore |
verified absence, informal only: TUpper-Terms.html, full-text grep for "state"/"fluent"/"situation"/"configuration" returned only these two informal-gloss occurrences, fetched and read directly 2026-07-04 |
Corrects TODO.md's seed, which listed TUpper's contribution as simply "state" without noting it is unreified — f here plays the role of a situation-calculus fluent (a proposition that can hold or not at a point), consistent with TUpper's PSL/situation-calculus lineage, but no state class or predicate is itself defined. |
| GUM | (no class found) | technical | non-equivalence | Full-text grep of GUM-31.owl for "Situation" and "StateOfAffairs" (case-sensitive, matching GUM's own PascalCase convention) returned zero matches. |
xwkont:ref:gum-owl |
verified absence: GUM-31.owl, fetched and read directly 2026-07-04 |
Not part of TODO.md's original seed; checked directly for completeness. Unlike Time, Space, Abstract, and Quantity — where GUM contributed previously-uncredited content in each of the prior four 0.2.0-batch crosswalks — this is the first concept in the batch where GUM has confirmed nothing to add. |
Source Ontology Correspondences¶
| Correspondence ID | Source ontology | Source term | Source identifier or IRI | Source version | Reference | Inclusion rationale |
|---|---|---|---|---|---|---|
xwkont:correspondence:situation-state-of-affairs:001 |
GFO | Situation | https://w3id.org/gfo/base/Situation |
GFO 2024-11-18 (directly verified 2026-07-05) | xwkont:ref:gfo |
The most-specific formally defined base-ontology class directly matching this concept's core sense (supersedes the parent Configuration class as the primary GFO correspondence). |
xwkont:correspondence:situation-state-of-affairs:002 |
UFO | situation (stereotype) | https://w3id.org/ontouml#situation |
OntoUML vocabulary, undated (directly verified 2026-07-04) | xwkont:ref:ontouml-vocabulary |
Included as UFO's own (OntoUML-vocabulary-level) formal treatment, despite the 2021 comprehensive paper itself never reifying a Situation class — see Source Definitions and note-002 for this gap. |
xwkont:correspondence:situation-state-of-affairs:003 |
DOLCE | State | http://www.loa-cnr.it/ontologies/DOLCE-Lite.owl#state |
DOLCE-Lite v397 (directly verified 2026-07-04) | xwkont:ref:dolce-lite-owl |
Included with an explicit sense-mismatch caveat — DOLCE's state is an occurrent (stative perdurant), not a configuration-of-entities category; recorded because TODO.md's seed named it, not because it is judged equivalent to GFO's/UFO's sense. See note-001. |
xwkont:correspondence:situation-state-of-affairs:004 |
DOLCE | situation | http://www.loa-cnr.it/ontologies/ExtendedDnS.owl#situation |
ExtendedDnS v397 (directly verified 2026-07-05) | xwkont:ref:dolce-extendeddns-owl |
DOLCE's real formal treatment of this concept, found in its separate DnS module — resolves uncertainty-002; this is the correspondence-002-level sense match, not correspondence:003's state. |
xwkont:correspondence:situation-state-of-affairs:005 |
GFO | Situation (dedicated module) | https://w3id.org/gfo/situation/Situation |
GFO-situation, release 2024-12-07 (directly verified 2026-07-05) | xwkont:ref:gfo |
A second, independently-versioned GFO module dedicated to situation theory; recorded alongside correspondence:001 to note the cross-module naming/lineage difference — see note-005. |
No BFO, SUMO, YAMATO, TUpper, or GUM correspondence is recorded — see Source Definitions and Uncertainty.
Semantic Comparison Notes¶
| Note ID | Dimension | Claim type | Note | Supporting references | Confidence |
|---|---|---|---|---|---|
note-001 |
philosophical | editorial observation | DOLCE's state (core DOLCE-Lite.owl) and DOLCE's situation (the separate DnS module, xwkont:ref:dolce-extendeddns-owl) are not the same thing, despite DOLCE's own core-module commentary discussing both in the same passage. state is a stative perdurant (an occurrent, distinguished from process by homeomericity — "sitting" vs. "running"). DnS's situation is a formally defined social object, equivalentClass of non-agentive-social-object ⊓ setting-for(some particular) ⊓ satisfies(some description) — structurally much closer to GFO's Configuration/Situation or UFO's OntoUML situation stereotype than to DOLCE's own state class. As of the 2026-07-05 pass, DOLCE's DnS-module situation is now this crosswalk's DOLCE-side primary correspondence (correspondence:004); state (correspondence:003) remains recorded only because TODO.md's original seed named it, with the same sense-mismatch caveat as before. |
xwkont:ref:dolce-lite-owl, xwkont:ref:dolce-extendeddns-owl |
high |
note-002 |
technical | editorial observation | UFO's own comprehensive 2021 paper — the primary source for all of this repository's other UFO correspondences — never reifies a Situation class in its own axioms, despite using the word 21 times as an informal world-index. The formal treatment (ontouml:situation/ontouml:situationNature) lives only in the separate OntoUML vocabulary artifact, which per docs/methodology/primary-source-verification.md's established practice is treated as a derived modeling-notation artifact, not identical to UFO's own theoretical claims. This is a stronger version of the xwkont:ref:ufo-2021/ontouml-vocabulary distinction already noted for other UFO-related crosswalk work — here, the only UFO-side evidence for this concept comes from the OntoUML side, with zero support from the paper itself. |
xwkont:ref:ufo-2021, xwkont:ref:ontouml-vocabulary |
high |
note-003 |
philosophical | editorial observation | Where a formal definition exists (GFO's Situation; DOLCE DnS's situation; UFO's OntoUML situation), all three converge closely in substance — each describes a collection/configuration of entities comprehended or existing together as a whole, neither reducible to a single entity nor itself an occurrent. As of the 2026-07-05 pass this is now a genuine 3-source point of convergence (previously recorded as thin, 2-source), materially strengthening this crosswalk's cross-source pattern relative to the batch's other four concepts, though the underlying artifacts still differ in kind (GFO: base-ontology class; DOLCE: DnS-extension class; UFO: OntoUML-vocabulary stereotype, not the 2021 paper itself). |
xwkont:ref:gfo, xwkont:ref:dolce-extendeddns-owl, xwkont:ref:ontouml-vocabulary |
medium |
note-004 |
technical | editorial observation | Resolves uncertainty-002. DOLCE's DnS module (ExtendedDnS.owl, "OWL engineering by Aldo Gangemi") formally defines situation, description, concept, figure, and related social-reification vocabulary that core DOLCE-Lite.owl explicitly declines to formalize (per note-001's quoted commentary). This is DOLCE's real, intended treatment of the concept this crosswalk targets — the initial 2026-07-04 pass's "no DOLCE correspondence beyond a different-sense state" finding is superseded, not merely supplemented. |
xwkont:ref:dolce-extendeddns-owl |
high |
note-005 |
technical | editorial observation | Resolves uncertainty-003, and surfaces a new, smaller open question. GFO defines Situation in two separately-versioned places: (1) modules/gfo-base.owl's Situation, rdfs:subClassOf Configuration (itself rdfs:subClassOf Presential); and (2) a dedicated modules/situation/gfo-situation.ttl module's own :Situation class, rdfs:subClassOf gfo-core:TimeExtendedIndividual — a different superclass lineage, with additional restrictions (hasParticipant some Object, hasSituationPart some Attributive). Both were directly verified 2026-07-05. This crosswalk records both (correspondence:001 and correspondence:005) without attempting to reconcile the two lineages — that reconciliation is GFO's own internal modeling question, not one this crosswalk needs to resolve to record GFO's contribution. Confirms GFO invests substantially in this concept (base class plus a whole dedicated extension module), the strongest single-source evidence found for this concept across all 8 sources. |
xwkont:ref:gfo |
medium |
Mapping Assertions or Candidate Relations¶
| Mapping ID | Subject | Relation category | Object | predicate_id |
mapping_justification |
Status | Confidence | Rationale | Provenance |
|---|---|---|---|---|---|---|---|---|---|
xwkont:mapping:situation-state-of-affairs:001 |
GFO:Situation | close-match |
UFO:situation (OntoUML stereotype) | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Both denote a collection/configuration of entities comprehended as a whole, existing together (GFO: "the most complex kind of presentials," subject to "conditions of unity"; UFO: no explicit temporal qualifier but the same whole-comprehension criterion). Not high because GFO's is a base-ontology class, while UFO's is a modeling-notation stereotype from a different kind of artifact (OntoUML vocabulary, not the 2021 paper) — a cross-artifact-type comparison, not a like-for-like one. |
xwkont:ref:gfo, xwkont:ref:ontouml-vocabulary |
xwkont:mapping:situation-state-of-affairs:002 |
DOLCE:State | unknown |
GFO:Situation | none | semapv:ManualMappingCuration |
candidate | low | Recorded explicitly as a non-equivalence, not a correspondence — DOLCE's state is an occurrent (stative perdurant), while GFO's Situation is a Presential (continuant-like collection). Despite both appearing under TODO.md's original seed language, they answer different questions. |
xwkont:ref:dolce-lite-owl, xwkont:ref:gfo |
xwkont:mapping:situation-state-of-affairs:008 |
DOLCE:situation (DnS) | close-match |
GFO:Situation | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Both denote a social/comprehended-whole configuration of entities satisfying conditions of unity (DOLCE: "comprehended as a whole," dependent on a description; GFO: "comprehended as a whole," "conditions of unity... imposed by relations and categories"). Not high because DOLCE's is explicitly description-dependent (a non-agentive-social-object) while GFO's Situation carries no explicit description-dependency requirement in its own definition text. |
xwkont:ref:dolce-extendeddns-owl, xwkont:ref:gfo |
xwkont:mapping:situation-state-of-affairs:009 |
DOLCE:situation (DnS) | close-match |
UFO:situation (OntoUML stereotype) | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Corrected (2026-07-06, full-corpus audit): the original rationale asserted a historical/genealogical claim ("DOLCE's DnS situation is itself historically and terminologically the closer ancestor of UFO/OntoUML's tradition") with no cited source text supporting it, and explicitly conceded it was "not independently re-derived." The actual evidentiary basis available is a triangulated one, via GFO: mapping-008 directly quotes DOLCE's situation as "comprehended as a whole"; mapping-001 directly quotes UFO's stereotype sharing the same "whole-comprehension criterion" against GFO's own "comprehended as a whole" text. DOLCE and UFO are not directly compared against each other by any cited quotation here -- the correspondence is inferred by both sharing the same criterion with GFO, not confirmed by a direct DOLCE-UFO textual comparison. close-match and medium confidence (not raised) reflect that this is an inference from two other mappings' cited evidence, not an independently-verified direct comparison. |
xwkont:ref:dolce-extendeddns-owl, xwkont:ref:ontouml-vocabulary |
xwkont:mapping:situation-state-of-affairs:003 |
xwkont-core:SituationStateOfAffairs | unknown |
BFO | none | semapv:ManualMappingCuration |
candidate | low | No BFO correspondence identified; zero occurrences of "situation" anywhere in bfo-core.ttl. |
xwkont:ref:bfo-2020 |
xwkont:mapping:situation-state-of-affairs:004 |
xwkont-core:SituationStateOfAffairs | unknown |
SUMO | none | semapv:ManualMappingCuration |
candidate | low | No SUMO correspondence identified; ?SITUATION is a conventional variable name for a Formula-typed holdsDuring argument, not a distinct class. |
xwkont:ref:sumo-niles-pease-2001 |
xwkont:mapping:situation-state-of-affairs:005 |
xwkont-core:SituationStateOfAffairs | unknown |
TUpper | none | semapv:ManualMappingCuration |
candidate | low | No reified TUpper correspondence identified; "state" appears only inside holds/prior's own informal-semantics glosses as a fluent-like value, not as a defined predicate or class. |
xwkont:ref:tupper-colore |
xwkont:mapping:situation-state-of-affairs:006 |
xwkont-core:SituationStateOfAffairs | unknown |
YAMATO | none | semapv:ManualMappingCuration |
candidate | low | No YAMATO correspondence identified; no defined class or criterial distinction found in the fetchable technical report. | xwkont:ref:yamato-mizoguchi-2010 |
xwkont:mapping:situation-state-of-affairs:007 |
xwkont-core:SituationStateOfAffairs | unknown |
GUM | none | semapv:ManualMappingCuration |
candidate | low | No GUM correspondence identified; zero occurrences of "Situation"/"StateOfAffairs" in GUM-31.owl. The first 0.2.0-batch concept where GUM contributes nothing previously uncredited. |
xwkont:ref:gum-owl |
Uncertainty, Non-Equivalence, and Open Questions¶
| Item ID | Type | Description | Impact | Follow-up |
|---|---|---|---|---|
uncertainty-001 |
~~open-question~~ Maintainer-confirmed (session-060). The remaining blocker this item flagged — a maintainer judgment call on scope stability, given the external review's "concept scope is unstable" comment (three different senses) — is resolved by re-examining what the 2026-07-05 pass already did: the reviewed correspondence set covers only the configuration/comprehended-whole sense (GFO Situation in both its modules, DOLCE's DnS-module situation, UFO's OntoUML situation stereotype — 3 real sources). DOLCE's occurrent State (correspondence-003) is retained only as an explicitly-flagged non-equivalent entry — mapping-002 records it as unknown/non-equivalence against GFO's Situation, per note-001's own explanation that state and DnS's situation "are not the same thing." TUpper's fluent-like state was never given a correspondence at all (mapping-005 records only an absence). The three senses the external review worried about were never actually collapsed into one reviewed correspondence set — this item's own structured resolved field had simply never been updated to reflect what the Review History narrative already claimed on 2026-07-06. Placed in data/ontology/core.ttl as xwkont-core:SituationStateOfAffairs, a sibling of Object under Continuant, following GFO's own Presential-side Situation and DOLCE's own non-agentive-social-object placement of situation — both continuant-committing sources place their evidence on the continuant side; UFO's OntoUML stereotype does not contradict this. mapping-003 through mapping-007's xwkont-core:Situation (candidate) placeholder subject was renamed to the real xwkont-core:SituationStateOfAffairs identifier across all five rows, matching the class actually placed. docs/ontology/core-ontology.md, core-axioms.md, core-ontology.mmd, and the structural-fallback required_terms lists in docs/publication/validation-commands.md/.github/workflows/validate.yml were kept in sync in the same pass. |
Updated 2026-07-05 — evidence base materially strengthened, decision still open. The 2026-07-04 pass found only 1 of 8 sources (GFO) with an unambiguous formal class, and an independent external review reached the same HOLD conclusion, recommending DOLCE's DnS module and GFO's Configuroid be fetched first. This 2026-07-05 pass fetched both, plus GFO's dedicated situation module, and found: DOLCE's DnS module does formally define situation (resolves uncertainty-002); GFO independently names its most-specific configuration class Situation and maintains a whole dedicated extension module for situation theory (resolves uncertainty-003). The cross-source pattern is now 3 of 8 sources (GFO, DOLCE, UFO) with unambiguous formal classes, up from 1. Should this concept now proceed toward reviewed status, or does the batch still hold it for other reasons (e.g., internal concept-scope instability flagged by the external review's second comment — DOLCE's state/DnS's situation/TUpper's state still represent three different senses that should not be collapsed)? This is now a stronger evidentiary case than before, but the review's separate "concept scope is unstable" comment (three different senses) was not itself resolved by this pass and remains a live concern independent of source-count. |
No longer blocks on missing primary-source data (both flagged fetches are done); the remaining blocker is a maintainer judgment call on scope stability and whether 3-source (with DOLCE's DnS-derived, not core-module, evidence) meets reviewed standards comparable to the batch's other concepts. |
Resolved; this concept is now placed in core.ttl. No further follow-up. |
uncertainty-002 |
resolved | ~~DOLCE's own formal treatment of "situation"... was not fetched.~~ Resolved 2026-07-05: DOLCE's separate ExtendedDnS.owl module was fetched and read directly; it formally defines #situation — see Source Definitions, correspondence:004, and note-004. |
Directly strengthens uncertainty-001's evidence base — DOLCE moves from a sense-mismatched correspondence (state) to a second solid one (situation). |
None outstanding; resolved. |
uncertainty-003 |
resolved | ~~GFO's Configuration has a sibling class Configuroid... not independently fetched or glossed.~~ Resolved 2026-07-05: Configuroid (rdfs:subClassOf Process) and its subclass Situoid were fetched and glossed — see the GFO row in Source Definitions and note-005. Additionally, a class literally named Situation (rdfs:subClassOf Configuration) was found in the same module, plus an entire dedicated situation extension module with its own :Situation class. |
Strengthens GFO's correspondence from the parent Configuration class to the more specific, exactly-named Situation class; surfaces a new (lower-stakes) open point about two different GFO Situation lineages — see note-005. |
None outstanding beyond note-005's observation, which does not require further action to record GFO's contribution. |
uncertainty-004 |
non-equivalence | UFO's own 2021 comprehensive paper — this repository's primary UFO reference for every other crosswalk — contains zero reified Situation class despite 21 informal usages; the only formal evidence is the derived OntoUML vocabulary artifact. This is a stronger version of the general UFO/OntoUML/gUFO non-identity already documented in docs/methodology/primary-source-verification.md. |
Affects how correspondence-002/mapping-001 should be read — this is the first 0.2.0-batch concept where a UFO correspondence rests entirely on the OntoUML fallback rather than the paper itself. |
None outstanding beyond what's recorded; flagged here and in note-002 for traceability and to inform the uncertainty-001 review decision. |
Provenance and References¶
xwkont:ref:bfo-2020— Basic Formal Ontology (BFO) 2020 / ISO/IEC 21838-2:2021 — verified absence directly againstbfo-core.ttl, 2026-07-04xwkont:ref:dolce-lite-owl— DOLCE-Lite OWL translation — verified (state) / verified absence in this module (situation) directly againstDOLCE-Lite.owl, 2026-07-04xwkont:ref:dolce-extendeddns-owl— DOLCE ExtendedDnS OWL module — verified directly againstExtendedDnS.owl, class#situation, 2026-07-05xwkont:ref:sumo-niles-pease-2001— Towards a Standard Upper Ontology (Niles & Pease, 2001) — verified absence directly against current SUMOMerge.kif, 2026-07-04xwkont:ref:ufo-2021— UFO: Unified Foundational Ontology (Guizzardi et al., 2021) — verified absence directly (full-text re-search, 21 occurrences individually inspected), 2026-07-04xwkont:ref:ontouml-vocabulary— OntoUML Vocabulary (OWL/Turtle) — verified directly, 2026-07-04xwkont:ref:gfo— General Formal Ontology (GFO) — verified directly againstmodules/gfo-base.owl(Configuration,Situation,Configuroid,Situoid) andmodules/situation/gfo-situation.ttl(:Situation), 2026-07-04/2026-07-05xwkont:ref:yamato-mizoguchi-2010— YAMATO 2010 technical report (Mizoguchi) — verified absence directly against the extracted PDF, 2026-07-04xwkont:ref:tupper-colore— TUpper COLORE formalization (Grüninger) — verified absence, informal only directly againstTUpper-Terms.html, 2026-07-04xwkont:ref:gum-owl— GUM 3.1 OWL (Bateman) — verified absence directly againstGUM-31.owl, 2026-07-04
Review History¶
| Review ID | Date | Outcome | Notes |
|---|---|---|---|
| — | 2026-07-04 | Not yet reviewed — draft |
Fifth concept of the 0.2.0 batch (ADR-0018), following time.md, space.md, abstract-concrete.md, and quantity-amount-of-matter.md. All 8 sources checked directly against primary artifacts already cached from prior crosswalks' research. Confirms TODO.md's own prior caution that this candidate is "weaker/more UFO-centric" than the batch's other early entries — only GFO's Configuration is an unambiguous, directly comparable formal correspondence; UFO's evidence comes from the OntoUML vocabulary fallback rather than its own 2021 paper; DOLCE's state is a different-sense class; TUpper's state is unreified; BFO, SUMO, YAMATO, and GUM confirmed to have nothing at all. Pending maintainer review, with an explicit open question (uncertainty-001) about whether this crosswalk should advance toward reviewed, be re-scoped after fetching DOLCE's DnS module, or be deferred to a later batch. |
| — | 2026-07-05 | Not yet reviewed — draft |
Follow-up primary-source pass responding directly to the external review's recommended next step: fetched DOLCE's ExtendedDnS.owl module and GFO's modules/situation/gfo-situation.ttl module (plus the remainder of modules/gfo-base.owl). Found DOLCE's DnS module formally defines situation (resolves uncertainty-002) and GFO independently names its most-specific configuration class Situation plus maintains a dedicated situation-theory extension module (resolves uncertainty-003). Cross-source evidence moves from 1-of-8 to 3-of-8 sources with unambiguous formal classes (GFO, DOLCE, UFO). uncertainty-001's advance/re-scope/defer decision remains open for maintainer review, now against a materially stronger evidentiary record — see updated Scope Note and uncertainty-001. |
xwkont:review:situation-state-of-affairs:2026-07-05:01 |
2026-07-05 | Passed — advanced draft → reviewed |
Checked against docs/governance/contributing.md's Review Checklist: scope preserved (still comparing existing 8 sources per ADR-0015, no new domain concepts introduced); every xwkont:ref:* citation resolves to a real reference record, including the newly-added xwkont:ref:dolce-extendeddns-owl; correspondence/mapping/note/uncertainty ID numbering sequential with no gaps or duplicates (verified: correspondences 001-005, mappings 001-009, notes 001-005, uncertainty 001-004); all confidence values are within the ADR-0013-approved vocabulary (3 high, 5 medium, 6 low — no medium-high/low-medium used, so no sourcing-rationale requirement triggered). Correction (2026-07-06, full-corpus audit): this entry originally also claimed "mapping categories... match their stated justifications" — false for mapping-009, which asserted an unevidenced historical/genealogical claim about DOLCE DnS being UFO/OntoUML's "closer ancestor," explicitly conceding it was "not independently re-derived." Rewritten in this pass to state the actual evidentiary basis: a triangulated inference through GFO (mapping-001/mapping-008' shared "comprehended as a whole" quotations), not a direct DOLCE-UFO comparison. Category and confidence (close-match/medium) were already appropriate and are unchanged — only the rationale's fabricated claim was corrected. See docs/methodology/crosswalk-runbook.md's governing principle. Resolves uncertainty-001: the original HOLD rested on a thin 1-of-8 source count and a conflated-senses concern (DOLCE's occurrent state being read as this concept's "situation" sense) — the 2026-07-05 primary-source pass resolved both by finding a genuine 3-source (GFO, DOLCE via DnS, UFO via OntoUML) convergence on the same sense (a comprehended-as-a-whole configuration/social object), with the DOLCE correspondence now correctly sourced to DnS's situation rather than the different-sense state class. Explicit editorial note for future readers: unlike this repository's other DOLCE correspondences, this concept's DOLCE evidence comes from the separate DnS extension module (xwkont:ref:dolce-extendeddns-owl), not core DOLCE-Lite.owl (xwkont:ref:dolce-lite-owl) — do not assume DOLCE's core module covers this concept. Self-review, not independent third-party review. |
| — | 2026-07-08 | Core placement resolved — sibling of Object under Continuant | Session-060. Resolved uncertainty-001, the last open item blocking core.ttl placement, per the maintainer's explicit confirmation. Re-examined the external review's "concept scope is unstable" (three-way sense split) comment against this crosswalk's own 2026-07-05-resolved content and found the three senses were never actually collapsed into one reviewed correspondence set — the reviewed scope already covers only the configuration/comprehended-whole sense (GFO, DOLCE DnS, UFO OntoUML), with DOLCE's occurrent State and TUpper's unreified state correctly excluded/flagged rather than conflated in. uncertainty-001's own structured field had simply never been updated to reflect what this review history's 2026-07-06 entry already narratively claimed. Added xwkont-core:SituationStateOfAffairs (sibling of Object, under Continuant) to data/ontology/core.ttl, following GFO's Presential-side Situation and DOLCE's non-agentive-social-object situation (DnS). docs/ontology/core-ontology.md, core-axioms.md, core-ontology.mmd, and the structural-fallback required_terms lists in docs/publication/validation-commands.md/.github/workflows/validate.yml were kept in sync. |
Future Work¶
- ~~Resolve
uncertainty-001(whether to advance, re-scope, or defer this crosswalk)~~ — done 2026-07-05: advanceddraft→reviewed(xwkont:review:situation-state-of-affairs:2026-07-05:01), on the strength of the 3-of-8-source convergence found in the same pass. - ~~Core.ttl placement remains an open question~~ — done 2026-07-08 (session-060): placed as
xwkont-core:SituationStateOfAffairs, a sibling of Object under Continuant; seeuncertainty-001's resolution note anddata/ontology/core.ttl. - Consider whether GFO's two
Situationlineages (note-005) warrant a follow-up question to GFO's own maintainers or documentation, separate from this crosswalk's own scope. - ~~Create the Universal/Type crosswalk next~~ — done (
universal-type.mdreviewed). Residual OntoUML vocabulary (already this crosswalk's primary UFO source) is directly relevant there too (type/kind/phasestereotypes).