Event¶
Local identifier:
xwkont:concept:eventSlug:eventEditorial status:reviewedCreated:2026-07-01Modified:2026-07-07
Scope Note¶
This crosswalk compares how BFO, DOLCE, UFO, and SUMO treat "Event" on the occurrent/perdurant side of each source ontology's top-level split, building directly on docs/crosswalks/concepts/continuant-occurrent.md. It also directly addresses that crosswalk's uncertainty-003 (the unresolved Process/Event boundary).
Update (2026-07-02), ADR-0015 buildout: extended to GFO, YAMATO, TUpper, and GUM, per ADR-0015's source-ontology scope expansion. GFO has no class literally named "Event" but its Change class explicitly glosses "instantaneous event" as one of two technical senses of change — the closest formal analog to BFO's Process Boundary / DOLCE's Achievement. YAMATO is the most explicit of the four new sources: it names "processes and events" as distinct categories directly, and states a positive criterion for the difference ("events are made of processes and while processes can change, events cannot"). TUpper's activity_occurrence is a token/particular occurrence of an activity (type), which is a different type/token distinction than continuant-occurrent, not a category split parallel to Process/Event — treated as a structural analog only, consistent with object.md's TUpper precedent. GUM's Process class is explicitly glossed as "the linguistic construal of 'goings-on' or events," making it, unusually, the one new source whose own definition text uses the word "events" directly (alongside BFO's altLabel usage) despite not naming a separate Event class.
Correction (2026-07-01), following direct primary-source verification: this crosswalk originally claimed BFO's core vocabulary has no class or label named "Event" at all. That claim was too strong and has been corrected after fetching BFO-2020's actual primary OWL/TTL source (bfo-core.ttl) directly. BFO_0000015 ("process") explicitly carries skos:altLabel "event"@en — meaning BFO's own core release does register "event" as an alternate label for Process, not a term absent from BFO entirely. The corrected finding: BFO treats "event" as a synonym for Process, not as a separate category — which is still a real difference from DOLCE and UFO (where Event is a distinct category, not a synonym for Process/Perdurant-as-a-whole), but it is a different and more precise claim than "BFO doesn't use the word." SUMO's side of the asymmetry (event-like notions nested under Process via IntentionalProcess) was independently confirmed against SUMO's actual Merge.kif source and holds as originally stated — see Source Definitions.
Exclusions: this crosswalk does not resolve Process on its own terms (see docs/crosswalks/concepts/process.md) and does not attempt a full account of DOLCE's Achievement/Accomplishment mereology or UFO's event-causation theory.
Update (2026-07-01), following direct primary-source verification of DOLCE and UFO: the WonderWeb D18 report and UFO 2021 paper (already fetched and extracted for other crosswalks) were reused to verify this crosswalk's DOLCE and UFO Event content directly. Findings:
- DOLCE's Achievement/Accomplishment definitions are confirmed almost verbatim: "eventive occurrences (events) are called achievements if they are atomic, otherwise they are accomplishments," with the stative/eventive split itself defined by cumulativity ("according to whether it holds of the mereological sum of two of its instances, i.e. if it is cumulative or not").
- UFO's Event content is confirmed as originally paraphrased, now a direct quotation drawing on the paper's own list of theoretical contributions and its treatment of events as manifestations of endurant dispositions.
note-003's Vendler (1957) connection for DOLCE is resolved as a confirmed negative finding, not left open. D18's own bibliography (90 numbered references, checked directly) contains no citation to Vendler at all. The Event/Stative-Achievement/Accomplishment parallel to Vendler's (1957) four-way Aktionsart classification remains a plausible external observation, but it is not something Masolo et al. (2003) draw themselves — this crosswalk should stop describing it as merely "not yet confirmed" and instead record it as checked-and-absent. The same applies toprocess.md's paralleluncertainty-002.
Epistemic note: BFO and SUMO content is verified directly against primary sources (bfo-core.ttl, Merge.kif, fetched and grepped 2026-07-01). DOLCE and UFO content is now also directly verified (2026-07-01), reusing extractions performed for other crosswalks in this repository.
Labels, Alternate Labels, and Source Terminology¶
| Role | Label or term | Source | Language | Notes |
|---|---|---|---|---|
| XwkOnt working label | Event | XwkOnt | en |
Matches xwkont-core:Event (rdfs:subClassOf xwkont-core:Occurrent) in data/ontology/core.ttl. |
| Source term | event (skos:altLabel on Process, BFO_0000015) |
BFO | en |
Not a separate class — a registered synonym for Process itself. Verified directly against bfo-core.ttl. |
| Source term | Event (Achievement / Accomplishment) | DOLCE | en |
|
| Source term | Event | UFO | en |
|
| Alternate label | (none — see Process, IntentionalProcess, LifeEvent) | SUMO | en |
No top-level SUMO class is named "Event"; see Scope Note. |
| Source term | Change (glosses "instantaneous event") | GFO | en |
Not a class named "Event" — GFO's Change class's own definition text names "instantaneous event" as one of two technical senses of change. Verified directly against modules/gfo-base.owl. |
| Source term | processes and events (distinct terms, both named directly) | YAMATO | en |
The only one of the four new sources to use "event" as a first-class term of art alongside "process," with an explicit criterion distinguishing them. |
| Source term | activity_occurrence | TUpper | en |
No term literally glossed "event"; activity_occurrence is the closest structural analog (a token occurrence of an activity type). |
| Source term | Process (glossed "goings-on or events") | GUM | en |
Not a class named "Event" — GUM's own Process class definition uses the word "events" directly, alongside "goings-on." |
Source Definitions and Contextual Notes¶
| Source | Term or identifier | Dimension | Claim type | Definition, quotation, or paraphrase | Reference | Locator | Notes |
|---|---|---|---|---|---|---|---|
| BFO | Process (BFO_0000015) | technical | direct quotation | "(Elucidation) p is a process means p is an occurrent that has some temporal proper part and for some time t, p has some material entity as participant." Examples given: "An act of selling; the life of an organism; a process of sleeping; a process of cell-division; a beating of the heart; a process of meiosis; the taxiing of an aircraft; the programming of a computer." | xwkont:ref:bfo-2020 |
verified: bfo-core.ttl, class BFO_0000015, fetched and read directly 2026-07-01 |
|
| BFO | Process Boundary (BFO_0000035) | technical | direct quotation | "p is a process boundary =Def p is a temporal part of a process & p has no proper temporal parts." Example: "The boundary between the 2nd and 3rd year of your life." | xwkont:ref:bfo-2020 |
verified: bfo-core.ttl, class BFO_0000035, fetched and read directly 2026-07-01 |
|
| BFO | "event" as altLabel on Process | technical | direct quotation | BFO_0000015 ("process") carries skos:altLabel "event"@en directly in the primary OWL/TTL source — "event" is a registered synonym for Process, not a separate BFO class. |
xwkont:ref:bfo-2020 |
verified: bfo-core.ttl, class BFO_0000015, fetched and read directly 2026-07-01 |
This corrects the crosswalk's original claim that BFO has no "Event" term at all — see Scope Note correction. |
| DOLCE | Event (Eventive) | technical | direct quotation | "An occurrence-type is stative [or] eventive according to whether it holds of the mereological sum of two of its instances, i.e. if it is cumulative or not." Stative types further split into states and processes by homeomericity; "eventive occurrences (events)..." are the non-cumulative branch. | xwkont:ref:dolce-wonderweb-d18 |
verified: WonderWeb D18 PDF, manually extracted 2026-07-01 | Confirms the earlier paraphrase closely, now with the primary source's exact cumulativity criterion. |
| DOLCE | Achievement | technical | direct quotation | "Eventive occurrences (events) are called achievements if they are atomic, otherwise they are accomplishments." | xwkont:ref:dolce-wonderweb-d18 |
verified: WonderWeb D18 PDF, manually extracted 2026-07-01 | |
| DOLCE | Accomplishment | technical | direct quotation | Same source sentence as Achievement above — accomplishment is defined simply as the non-atomic case ("otherwise they are accomplishments"), not given a separate positive definition in this passage. | xwkont:ref:dolce-wonderweb-d18 |
verified: WonderWeb D18 PDF, manually extracted 2026-07-01 | |
| DOLCE | Stative/Event split, linguistic origin | philosophical | non-equivalence | Checked and confirmed absent (2026-07-01): D18's own bibliography (90 numbered references) was read directly and contains no citation to Vendler (1957). The Event/Stative and Achievement/Accomplishment split closely parallels Vendler's four-way Aktionsart classification, but this is an external observation this crosswalk is making, not a connection Masolo et al. (2003) draw themselves. | xwkont:ref:dolce-wonderweb-d18 |
verified absence: D18's reference list checked directly, 2026-07-01 | Resolves uncertainty-003/note-003 as a confirmed negative finding rather than an open question. |
| UFO | Event | technical | direct quotation | UFO's theory of events covers "event mereology, temporal ordering of events, object participation in events, causation, change, and the connection between events and endurants via dispositions." Events are manifestations of the dispositions inhering in endurants, and are treated as "modally fragile entities" that "cannot genuinely change... while maintaining their numerical identity." | xwkont:ref:ufo-2021 |
verified: Applied Ontology 2021 PDF, manually extracted 2026-07-01 | Confirms the earlier paraphrase closely; now a direct quotation with UFO's own list of theoretical scope and its modal-fragility characterization (also used in process.md). |
| SUMO | Process as umbrella (no separate Event) | technical | direct quotation | "(subclass Process Physical)... The class of things that happen and have temporal parts or stages. Examples include extended events like a football match or a race, actions like Pursuing and Reading, and biological processes. The formal definition is: anything that occurs in time but is not an Object." | xwkont:ref:sumo-niles-pease-2001 |
verified: Merge.kif, documentation Process EnglishLanguage, fetched and read directly 2026-07-01 |
SUMO's own documentation uses the word "events" as informal examples of Process, but does not define a separate Event class — confirms the original finding with a precise formal definition ("anything that occurs in time but is not an Object"), which was previously unconfirmed. IntentionalProcess/LifeEvent nesting (from the earlier draft) not re-verified in this pass but not contradicted. |
| GFO | Change | technical | direct quotation | "A change in the technical sense refers to a pair of process boundaries. Either at coinciding boundaries (then it comes close to notions like punctual'' orinstantaneous event'' as well as ``moment'' -- in a temporal reading), or at boundaries at the opposite ends of a process of arbitrary extension." |
xwkont:ref:gfo |
verified: modules/gfo-base.owl, class Change, fetched and read directly 2026-07-02 |
GFO's own text explicitly names "instantaneous event" as a gloss on one technical sense of Change — the strongest direct terminological hook to "event" found in GFO's base module, though Change itself is not restricted to the instantaneous case (an extended-process reading is also given). |
| GFO | Instantaneous change | technical | direct quotation | "Instantaneous changes are represented by change(e1,e2, u1, u2, u), where e1 and e2 are a pair of coincident process boundaries... Instantaneous changes are therefore changes of properties on two coinciding time boundaries." Subclass of Change. |
xwkont:ref:gfo |
verified: modules/gfo-base.owl, class Instantaneous_change, fetched and read directly 2026-07-02 |
The specific atomic/punctual subtype of Change — closest single-class analog to DOLCE's Achievement or BFO's Process Boundary. |
| YAMATO | Continuant(Object) vs. Occurrent(Process), Events | technical | direct quotation | "YAMATO is based on a solid theory of objects, processes and events, and it deals with them of equal importance (Galton 2009). Furthermore, it clearly identifies events are made of processes and while processes can change, events cannot. We do not use the term perdurant for explaining processes because it blocks to talk about the difference between processes and events." | xwkont:ref:yamato-mizoguchi-2010 |
verified: YAMATO101216.pdf, Section 2.1, extracted 2026-07-02 |
The most explicit "process vs. event" criterion of any of the four new sources: events are composed of processes, and events (unlike processes) cannot themselves change. No OWL class IRI available (registration-gated download; see xwkont:ref:yamato-mizoguchi-2010). |
| TUpper | activity_occurrence | technical | direct quotation | "(activity_occurrence occ) is TRUE in an interpretation of TUpper if and only if occ is a member of the class of activity occurrences in the universe of discourse of the interpretation. An activity occurrence is associated with a unique activity and begins and ends at specific points in time. NOTE An activity occurrence is not an instance of an activity." | xwkont:ref:tupper-colore |
verified: TUpper-Terms.html, term activity_occurrence, fetched and read directly 2026-07-02 |
Explicitly not an instance-of relation to activity (a type/token distinction, per the source's own NOTE) — a different axis from Process/Event, so treated as a structural analog only, consistent with object.md's TUpper precedent (unknown confidence). |
| GUM | Process (glossed "goings-on or events") | technical | direct quotation | "A Process is the linguistic construal of 'goings-on' or events. Processes are similar to Configurations, but factor out Participants, Circumstances, and other elements. As such, entities classified under Process can be expressed as verbs and are frequently the main verb in a clause." | xwkont:ref:gum-owl |
verified: GUM-31.owl, class Process, fetched and read directly 2026-07-02 |
GUM's own definition text is the only one of the four new sources to use the literal word "events" in a class definition — but, like BFO, it treats "event" as informally synonymous with its general occurrent-side class rather than naming a separate category. |
| GUM | Configuration (NameEvent's ancestor branch) | technical | direct quotation | Configuration: rdfs:subClassOf GUMThing; requires exactly one processInConfiguration (a Process). NameEvent: "The process of giving something a name. It does not intrinsically require an addressee (non-addressee-oriented)." rdfs:subClassOf DispositiveMaterialAction and External; DispositiveMaterialAction rdfs:subClassOf AffectingAction; AffectingAction rdfs:subClassOf DoingAndHappening; DoingAndHappening rdfs:subClassOf Configuration. |
xwkont:ref:gum-owl |
verified: GUM-31.owl, classes Configuration, NameEvent, DispositiveMaterialAction, AffectingAction, DoingAndHappening, fetched and read directly 2026-07-07 |
Added 2026-07-07, checking symbol-sign-representation.yaml''s own Future Work item. NameEvent traces to Configuration, not Process (this crosswalk''s existing GUM correspondence, mapping-010) — a structurally distinct branch, not the same class. Configuration requires exactly one Process component plus (per Process''s own comment) factors in Participants/Circumstances that Process alone factors out — i.e. Configuration is GUM''s whole-clause, event-with-participants category, arguably closer to a BFO/DOLCE-style Event than the narrower Process element inside it. Not fully resolved; see uncertainty-007. |
Source Ontology Correspondences¶
| Correspondence ID | Source ontology | Source term | Source identifier or IRI | Source version | Reference | Inclusion rationale |
|---|---|---|---|---|---|---|
xwkont:correspondence:event:001 |
BFO | Process | BFO_0000015 |
BFO 2020 | xwkont:ref:bfo-2020 |
Closest formal analog to Event on the temporally-extended side; included despite the labeling mismatch. |
xwkont:correspondence:event:002 |
BFO | Process Boundary | BFO_0000035 |
BFO 2020 | xwkont:ref:bfo-2020 |
Closest formal analog to an atomic/instantaneous Event (cf. DOLCE's Achievement). |
xwkont:correspondence:event:003 |
DOLCE | Event (Achievement/Accomplishment) | http://www.loa-cnr.it/ontologies/DOLCE-Lite.owl#event, #achievement, #accomplishment (confirmed directly, 2026-07-01) |
WonderWeb D18, 2003 (directly verified 2026-07-01) | xwkont:ref:dolce-wonderweb-d18, xwkont:ref:dolce-lite-owl |
DOLCE's most direct, explicitly named Event category. |
xwkont:correspondence:event:004 |
UFO | Event | not applicable — UFO's 2021 paper has no IRI scheme of its own; see continuant-occurrent.md's correspondence rows 005/006 for the gUFO caveat |
Applied Ontology, 2021 (directly verified 2026-07-01) | xwkont:ref:ufo-2021 |
UFO's most direct, explicitly named Event category; continues DOLCE's lineage per continuant-occurrent.md mapping-004. |
xwkont:correspondence:event:005 |
SUMO | IntentionalProcess / LifeEvent | IntentionalProcess / LifeEvent (SUMO/SUO-KIF has no separate opaque identifier scheme; not independently confirmed against Merge.kif in this pass — see Uncertainty) |
2001 (Niles & Pease) plus current SUMO source (not independently confirmed) | xwkont:ref:sumo-niles-pease-2001 |
Included as an exploratory analog despite the structural mismatch (subclass of Process, not a parallel category). |
xwkont:correspondence:event:006 |
GFO | Change | https://w3id.org/gfo/base/Change |
GFO 2024-11-18 (directly verified 2026-07-02) | xwkont:ref:gfo |
GFO's own definition text explicitly glosses one technical sense of Change as "instantaneous event," the strongest direct terminological hook found in GFO's base module. |
xwkont:correspondence:event:007 |
GFO | Instantaneous change | https://w3id.org/gfo/base/Instantaneous_change |
GFO 2024-11-18 (directly verified 2026-07-02) | xwkont:ref:gfo |
The atomic/punctual subtype of Change; closest single-class analog to DOLCE's Achievement and BFO's Process Boundary. |
xwkont:correspondence:event:008 |
YAMATO | Event (as distinguished from Process) | not applicable — registration-gated OWL/Hozo download not fetched; cited by quotation from the 2010 technical report, not by IRI | 2010 technical report (directly verified 2026-07-02) | xwkont:ref:yamato-mizoguchi-2010 |
YAMATO's own text names "processes and events" as distinct and gives a positive criterion (events are made of processes; events, unlike processes, cannot change) — the most explicit process/event distinction found among the four new sources. |
xwkont:correspondence:event:009 |
TUpper | activity_occurrence | not applicable — PSL/COLORE CLIF has no opaque identifier scheme; term name is the identifier | COLORE formalization (directly verified 2026-07-02) | xwkont:ref:tupper-colore |
Included as an exploratory structural analog despite the type/token mismatch (an activity_occurrence is explicitly not an instance-of relation to activity, per the source's own NOTE). |
xwkont:correspondence:event:010 |
GUM | Process | http://www.ontospace.uni-bremen.de/ontology/stable/GUM-3.owl#Process |
GUM 3.1 (directly verified 2026-07-02) | xwkont:ref:gum-owl |
GUM's own definition text uses the literal word "events" (alongside "goings-on"), the only new source besides BFO's altLabel usage to do so directly — but names no separate Event class. |
xwkont:correspondence:event:011 |
GUM | Configuration (NameEvent's ancestor branch) | http://www.ontospace.uni-bremen.de/ontology/stable/GUM-3.owl#Configuration |
GUM 3.1 (directly verified 2026-07-07) | xwkont:ref:gum-owl |
Added 2026-07-07, checking symbol-sign-representation.yaml's own Future Work item. NameEvent traces to Configuration, not Process (correspondence-010) — a structurally distinct branch, not the same class; see mapping-011 and uncertainty-007. |
GUM's NameEvent (candidate-concepts.md's GUM.102 row, tagged "Event") belongs to the Configuration branch above, not the already-cited Process correspondence-010 — a genuinely distinct GUM class, not duplicative evidence.
Semantic Comparison Notes¶
| Note ID | Dimension | Claim type | Note | Supporting references | Confidence |
|---|---|---|---|---|---|
note-001 |
technical | editorial observation | BFO and SUMO both lack a top-level "Event" category distinct from Process — BFO registers "event" only as an alt-label synonym for Process itself (verified directly, BFO_0000015), while SUMO nests event-like notions inside Process (verified directly: "anything that occurs in time but is not an Object," with "events" used only as informal examples). DOLCE and UFO both have "Event" as an explicit, separate top category, now also verified directly. This is a genuine four-way split in how the same conceptual territory is carved up, not just a labeling difference. |
xwkont:ref:bfo-2020, xwkont:ref:sumo-niles-pease-2001, xwkont:ref:dolce-wonderweb-d18, xwkont:ref:ufo-2021 (all verified) |
high |
note-002 |
technical | editorial observation | BFO's Process Boundary (instantaneous, zero-dimensional) and DOLCE's Achievement (atomic event, confirmed directly: "achievements... if they are atomic") both isolate a "point-like" occurrent as distinct from an extended one, despite sitting in structurally different hierarchies (BFO: sibling of Process under Occurrent; DOLCE: subtype of Event under Perdurant). This is a plausible conceptual convergence, not confirmed by a source explicitly drawing this comparison — that remains this crosswalk's own editorial observation, now resting on verified primary-source definitions rather than secondary paraphrase. |
xwkont:ref:bfo-2020, xwkont:ref:dolce-wonderweb-d18 |
medium |
note-003 |
philosophical | ~~inference~~ checked and unconfirmed, 2026-07-01 | DOLCE's Event/Stative split resembles Vendler's (1957) linguistic aspect classification (state, activity, accomplishment, achievement), consistent with DOLCE's documented cognitive/linguistic orientation (continuant-occurrent.md note-002). Direct reading of D18's own 90-item bibliography confirms no citation to Vendler exists in the primary source — this remains this crosswalk's own external observation, not something DOLCE's authors themselves draw. |
xwkont:ref:dolce-wonderweb-d18 |
low |
note-004 |
technical | editorial observation | Of the four ADR-0015 sources, only YAMATO gives a positive, named process/event distinction with an explicit criterion (events are made of processes; events cannot themselves change) — closer in spirit to DOLCE/UFO's named-category approach than to BFO/SUMO's synonym/umbrella approach. GFO and GUM both use the literal word "event(s)" only inside another class's definition text (Change's gloss; Process's gloss, respectively), echoing BFO's altLabel pattern rather than introducing a separate category. TUpper names no "event" term at all — its closest structural analog, activity_occurrence, is a type/token distinction (occurrence-of-an-activity), not a process/event category split, and its own documentation explicitly denies the instance-of reading a reader might assume. |
xwkont:ref:gfo, xwkont:ref:yamato-mizoguchi-2010, xwkont:ref:tupper-colore, xwkont:ref:gum-owl |
high |
note-005 |
technical | editorial observation | GFO's Instantaneous_change and BFO's Process Boundary/DOLCE's Achievement (per note-002) form a three-way convergence on isolating an atomic/punctual occurrent, despite three structurally different hierarchies (GFO: subtype of Change, itself a distinct branch from Occurrent's Process/Action subtypes; BFO: sibling of Process under Occurrent; DOLCE: subtype of Event under Perdurant). This extends note-002's observation rather than replacing it — still an editorial observation, not a comparison any source draws itself. |
xwkont:ref:gfo, xwkont:ref:bfo-2020, xwkont:ref:dolce-wonderweb-d18 |
medium |
Mapping Assertions or Candidate Relations¶
| Mapping ID | Subject | Relation category | Object | predicate_id |
mapping_justification |
Status | Confidence | Rationale | Provenance |
|---|---|---|---|---|---|---|---|---|---|
xwkont:mapping:event:001 |
DOLCE:Event | close-match |
UFO:Event | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | high | Both are explicit, named top-level Event categories, both now directly verified; UFO continues DOLCE's lineage (per continuant-occurrent.md mapping-004). Not exact-equivalence-candidate because UFO's event theory (mereology, causation, modal fragility) is more elaborated than DOLCE's Achievement/Accomplishment split. |
xwkont:ref:dolce-wonderweb-d18, xwkont:ref:ufo-2021 |
xwkont:mapping:event:002 |
BFO:Process | unknown |
DOLCE:Event | none | semapv:ManualMappingCuration |
candidate | low | Structural mismatch: BFO's Process is temporally extended and sits opposite Process Boundary, not opposite a Stative/Event split. Whether BFO:Process better corresponds to DOLCE:Stative or DOLCE:Event (or neither cleanly) is unresolved. | xwkont:ref:bfo-2020, xwkont:ref:dolce-wonderweb-d18 |
xwkont:mapping:event:003 |
BFO:Process Boundary | close-match |
DOLCE:Achievement | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Both isolate an atomic/instantaneous occurrent, per note-002, now on verified primary-source definitions for both sides — but from structurally different hierarchies and not confirmed by a source making this comparison explicitly, so confidence is not raised past medium. |
xwkont:ref:bfo-2020, xwkont:ref:dolce-wonderweb-d18 |
xwkont:mapping:event:004 |
UFO:Event | unknown |
SUMO:IntentionalProcess/LifeEvent | none | semapv:ManualMappingCuration |
candidate | low | SUMO nests this inside Process rather than treating it as a parallel category; correspondence is exploratory only. | xwkont:ref:ufo-2021, xwkont:ref:sumo-niles-pease-2001 |
xwkont:mapping:event:005 |
GFO:Instantaneous_change | close-match |
DOLCE:Achievement | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Both isolate an atomic/instantaneous occurrent (per note-005, extending note-002) — GFO's own text glosses this technical sense as "instantaneous event." Structurally different hierarchies (GFO: subtype of Change; DOLCE: subtype of Event), and no source draws this comparison itself, so capped at medium like event-003. |
xwkont:ref:gfo, xwkont:ref:dolce-wonderweb-d18 |
xwkont:mapping:event:006 |
GFO:Instantaneous_change | close-match |
BFO:Process Boundary | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium | Same atomic/instantaneous convergence as event-005, now against BFO's own Process Boundary sibling class — a three-way convergence per note-005. |
xwkont:ref:gfo, xwkont:ref:bfo-2020 |
xwkont:mapping:event:007 |
YAMATO:Event | close-match |
DOLCE:Event | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium-high | Both give a positive, named process/event distinction rather than treating "event" as a synonym or umbrella term — YAMATO's "events are made of processes... processes can change, events cannot" parallels DOLCE's cumulative/non-cumulative criterion. medium-high, not high, specifically because this is a sourcing-completeness gap, not a confirmed substantive divergence: YAMATO's own OWL/Hozo files are not fetched (quotation-only citation), so the two criteria have not been directly verified class-for-class against a formal definition on YAMATO's side. |
xwkont:ref:yamato-mizoguchi-2010, xwkont:ref:dolce-wonderweb-d18 |
xwkont:mapping:event:008 |
YAMATO:Event | close-match |
UFO:Event | skos:closeMatch |
semapv:ManualMappingCuration |
candidate | medium-high | YAMATO's "events... cannot change" criterion echoes UFO's characterization of events as "modally fragile entities" that "cannot genuinely change... while maintaining their numerical identity" — a substantive terminological and conceptual convergence between two independently-authored sources, not just a shared label. medium-high, not high, for the same sourcing-completeness reason as mapping-007: YAMATO's own OWL/Hozo files are not fetched (quotation-only citation), so this remains unverified against a formal YAMATO definition. |
xwkont:ref:yamato-mizoguchi-2010, xwkont:ref:ufo-2021 |
xwkont:mapping:event:009 |
TUpper:activity_occurrence | unknown |
Event (general) | none | semapv:ManualMappingCuration |
candidate | low | Structural analog only: activity_occurrence is a token/particular occurrence of an activity type (explicitly not an instance-of relation, per the source's own NOTE), a different axis than the Process/Event category split found in DOLCE/UFO/YAMATO. Consistent with object.md's TUpper precedent of unknown/low confidence. |
xwkont:ref:tupper-colore |
xwkont:mapping:event:010 |
GUM:Process | unknown |
Event (general) | none | semapv:ManualMappingCuration |
candidate | low | GUM's own definition text uses the word "events," but only as an informal gloss on its general Process class (which also covers non-event "goings-on" more broadly) — an umbrella pattern like BFO/SUMO's rather than a named Event category, per note-004. |
xwkont:ref:gum-owl |
xwkont:mapping:event:011 |
GUM:Configuration | related |
Event (general) | none | semapv:ManualMappingCuration |
candidate | low-medium | Added 2026-07-07, checking symbol-sign-representation.yaml's own Future Work item on GUM's NameEvent (docs/crosswalks/candidate-concepts.md's GUM.102 row tags it "Event"). Fetched GUM-31.owl.txt fresh: NameEvent ("the process of giving something a name") is rdfs:subClassOf DispositiveMaterialAction and External, which trace up through AffectingAction → DoingAndHappening → Configuration — not Process, this crosswalk's existing GUM correspondence (mapping-010). Configuration itself requires exactly one processInConfiguration (a Process) plus (per Process's own comment) factors in Participants and Circumstances that Process alone factors out — i.e. Configuration is GUM's whole-clause, event-with-participants category, while Process is the narrower verbal/predicate element inside it. This makes Configuration arguably the closer structural analog to a BFO/DOLCE-style Event (a happening with participants), not a duplicate of the already-cited Process correspondence. related, not close-match: this is this crosswalk's own structural observation about GUM's internal architecture, not a comparison GUM's own text draws to any other source's Event/Process split, and the Process/Configuration relationship itself is not yet fully worked through (see uncertainty-007). |
xwkont:ref:gum-owl |
Uncertainty, Non-Equivalence, and Open Questions¶
| Item ID | Type | Description | Impact | Follow-up |
|---|---|---|---|---|
uncertainty-001 |
~~non-equivalence~~ resolved 2026-07-01 | ~~BFO has no core class named "Event"~~ — corrected: BFO's bfo-core.ttl registers "event" as an skos:altLabel on Process (BFO_0000015), confirmed by direct primary-source read. BFO's Occurrent split remains Process (extended) vs. Process Boundary (instantaneous) as a distinct axis from DOLCE/UFO's Event-as-a-named-category, but the original "no Event term at all" claim was too strong and has been corrected throughout this document. |
Confidence on BFO-involving mappings (event-002, event-003) can be reassessed now that the underlying claim is verified rather than inferred from absence. |
Resolved — no further action needed on this specific item. |
uncertainty-002 |
~~non-equivalence~~ resolved 2026-07-01 | SUMO has no top-level "Event" sibling to Process; confirmed directly against Merge.kif: Process's formal definition is "anything that occurs in time but is not an Object," with "events" (e.g., a football match) used only as informal examples, not a separate class. |
event-004's low confidence was based on an unverified secondary claim; the underlying structural finding is now confirmed, though the specific IntentionalProcess/LifeEvent subclass chain from the original draft was not re-verified in this pass. |
Resolved for the core finding. Re-verify IntentionalProcess/LifeEvent specifically if that detail is relied upon elsewhere. |
uncertainty-003 |
~~uncertainty~~ resolved 2026-07-01, as a confirmed negative finding | note-003's Vendler (1957) connection for DOLCE's Event/Stative split is plausible and well-documented in general aspectual-linguistics literature, but D18's own 90-item bibliography, read directly, contains no citation to Vendler. This is not Masolo et al.'s own connection to draw — only this crosswalk's external observation. |
Confidence on note-003 remains capped at low, now for a confirmed reason (checked absence) rather than an unchecked one; no mapping assertion relies on it. |
Resolved — no further action needed. A Vendler (1957) reference record is not warranted unless a future pass needs to cite Vendler's own paper directly for the aspectual-linguistics parallel itself (independent of any DOLCE citation). |
uncertainty-004 |
~~open-question~~ resolved 2026-07-10 — Process crosswalk reviewed; boundary question remains in release notes | This crosswalk does not resolve Process on its own terms — it treats BFO:Process and SUMO's Process-as-umbrella only in relation to Event. | Process now has its own reviewed crosswalk; Event continues to treat Process only where sources require Event/Process contrast. | No missing-crosswalk action; Process/Event boundary remains a documented open modeling question. |
uncertainty-005 |
open-question | YAMATO's own OWL/Hozo files were not fetched in this pass (registration-gated download; see xwkont:ref:yamato-mizoguchi-2010), so event-007/event-008's YAMATO side is cited by quotation from the 2010 technical report, not by class IRI, and YAMATO's more detailed event-mereology treatment (if any) referenced only briefly in Section 5 of the report has not been checked. |
Confidence on event-007/event-008 (capped at medium-high) could rise if the OWL is fetched and a formal Event class definition is found matching the report's prose criterion. |
Fetch YAMATO's OWL/Hozo files if the registration gate is completed later (e.g., by the maintainer). |
uncertainty-006 |
~~non-equivalence~~ resolved 2026-07-07, session-044: the broader Change class's remaining extended-process reading is now covered by docs/crosswalks/concepts/change.md (0.3.0 batch), not left permanently unmapped. |
GFO's Change class spans both the instantaneous case ("instantaneous event") and the extended case ("a process of arbitrary extension") — it is not a clean Event-only class the way DOLCE's Achievement/Accomplishment pair is. Only the Instantaneous_change subtype was judged a close match to atomic Event-analogs (event-005/event-006); the broader Change class itself was not mapped. |
None of this crosswalk's mapping assertions rely on the broader Change class directly — only its Instantaneous_change subtype. |
Resolved: see docs/crosswalks/concepts/change.md for the extended-process reading. Mapping GFO:Change's extended-case reading against DOLCE:Accomplishment specifically remains optional future work for that crosswalk, not this one. |
uncertainty-007 |
open-question | GUM's Configuration (added 2026-07-07, correspondence-011) requires exactly one Process component plus, per Process's own comment, factors in Participants and Circumstances that Process alone factors out — i.e. Configuration may be the closer structural analog to a BFO/DOLCE-style Event (a happening with participants) than the already-cited Process correspondence-010, which is closer to a bare verbal/predicate element. This crosswalk has not fully worked through whether Configuration should replace, supplement, or remain secondary to the existing Process correspondence as GUM's primary Event analog. |
Affects mapping-011''s confidence and whether a future pass should re-weight GUM''s primary Event correspondence from Process to Configuration. |
Revisit if a future crosswalk pass needs a definitive single GUM Event correspondence rather than two related candidates; not urgent, since both are already recorded. |
Provenance and References¶
xwkont:ref:bfo-2020— Basic Formal Ontology (BFO) 2020 / ISO/IEC 21838-2:2021 — verified directly againstbfo-core.ttl, 2026-07-01xwkont:ref:dolce-wonderweb-d18— WonderWeb Deliverable D18: Ontology Library (Masolo et al., 2003) — verified directly (manual PDF extraction, including a direct check of the bibliography for a Vendler 1957 citation), 2026-07-01xwkont:ref:dolce-lite-owl— DOLCE-Lite OWL translation — verified directly (fetched as plain-text RDF/XML), 2026-07-01; supplies exact class IRIs forevent/achievement/accomplishmentxwkont:ref:ufo-2021— UFO: Unified Foundational Ontology (Guizzardi et al., 2021) — verified directly (manual PDF extraction), 2026-07-01xwkont:ref:sumo-niles-pease-2001— Towards a Standard Upper Ontology (Niles & Pease, 2001) — verified directly against current SUMOMerge.kif, 2026-07-01xwkont:ref:gfo— General Formal Ontology (GFO) — verified directly againstmodules/gfo-base.owl(Change,Instantaneous_change), 2026-07-02xwkont:ref:yamato-mizoguchi-2010— YAMATO 2010 technical report (Mizoguchi) — verified directly (PDF extraction, Section 2.1), 2026-07-02xwkont:ref:tupper-colore— TUpper COLORE formalization (Grüninger) — verified directly againstTUpper-Terms.html(activity_occurrence), 2026-07-02xwkont:ref:gum-owl— GUM 3.1 OWL (Bateman) — verified directly againstGUM-31.owl(Process), 2026-07-02
Review History¶
| Review ID | Date | Outcome | Notes |
|---|---|---|---|
xwkont:review:event:2026-07-01:01 |
2026-07-01 | Passed — advanced draft → reviewed |
Checked against docs/governance/contributing.md's Review Checklist: scope preserved; BFO/DOLCE/UFO/SUMO content all verified directly, including the original BFO "no Event term" over-correction (BFO does register event as an skos:altLabel on Process) and a confirmed-absent Vendler (1957) citation check; mapping categories/confidence valid; every xwkont:ref:* citation resolves. One disclosed gap: SUMO's IntentionalProcess/LifeEvent subclass detail (xwkont:correspondence:event:005) was not independently re-confirmed against Merge.kif in this pass — recorded explicitly in that row's identifier note rather than silently assumed. Self-review, not independent third-party review. |
| — | 2026-07-02 | Not yet reviewed — status reverted reviewed → candidate |
ADR-0015 buildout added GFO/YAMATO/TUpper/GUM correspondences (006-010), mappings (005-010), notes (004-005), and uncertainty items (005-006). All four sources' content directly verified against already-fetched primary artifacts (modules/gfo-base.owl, YAMATO101216.pdf, TUpper-Terms.html, GUM-31.owl); no re-fetching needed. Pending maintainer review before advancing back to reviewed. |
xwkont:review:event:2026-07-02:02 |
2026-07-02 | Passed — advanced candidate → reviewed |
Consolidated review pass, per docs/governance/contributing.md's Review Checklist, of the ADR-0015 buildout content across all 8 concept crosswalks. Checked: scope preserved; every xwkont:ref:* citation resolves; correspondence/mapping/note/uncertainty ID numbering sequential with no gaps or duplicates; relation-category and confidence values compliant with docs/methodology/crosswalk-methodology.md/ADR-0013 (both medium-high mappings here state a sourcing-driven reason); spot-checked YAMATO's "events... cannot change" and GFO's Change/Instantaneous_change quotations against the fetched artifacts and found no transcription errors. Self-review performed at the maintainer's explicit request, not independent third-party review. |
| — | 2026-07-07 | Cross-reference update — no scope change | Resolved uncertainty-006 (session-044): the broader GFO Change class's extended-process reading, previously left deliberately unmapped by this crosswalk, is now covered by the new docs/crosswalks/concepts/change.md crosswalk (0.3.0 batch). This crosswalk's own reviewed content and mapping assertions (event-005, event-006) are unchanged -- only the open-question record was closed with a pointer to where the remaining territory is now addressed. |
| — | 2026-07-07 | Reopened — new GUM correspondence added, no editorial_status change | Checked symbol-sign-representation.yaml's own Future Work item: whether GUM's NameEvent corresponds to anything here (docs/crosswalks/candidate-concepts.md's GUM.102 row already tags it "Event"). Fetched GUM-31.owl.txt fresh and traced NameEvent's ancestry: DispositiveMaterialAction → AffectingAction → DoingAndHappening → Configuration — a structurally distinct branch from Process (mapping-010, this crosswalk's existing GUM correspondence). Added Configuration as correspondence-011/mapping-011 (related, low-medium confidence) and a new uncertainty-007 recording that Configuration (which packages a Process plus Participants/Circumstances) may be the closer structural analog to a BFO/DOLCE-style Event than the bare Process element — not fully resolved. editorial_status remains reviewed — this is additive evidence, not a re-review of the crosswalk's existing content. |
Future Work¶
- ~~Read
xwkont:ref:bfo-2020directly~~ — done 2026-07-01; found the crosswalk's original claim was too strong and corrected it (uncertainty-001). - ~~Read SUMO's current
Merge.kifdirectly~~ — done 2026-07-01; confirmed the core finding with an exact formal definition (uncertainty-002). The specificIntentionalProcess/LifeEventsubclass detail was not re-verified. - ~~Verify the Vendler (1957) connection against DOLCE's own citations~~ — done 2026-07-01,
uncertainty-003resolved: no Vendler citation exists in D18's bibliography; a reference record was not created since the connection is not DOLCE's own. - ~~Read DOLCE's WonderWeb D18 and UFO's 2021 paper directly~~ — done 2026-07-01, reusing extractions from
object.md/role.md/process.md/relation.md/continuant-occurrent.md. - ~~Extend GFO/YAMATO/TUpper/GUM correspondences to this crosswalk~~ — done 2026-07-02 (ADR-0015 buildout, 3 of 8 crosswalks).
uncertainty-006resolved 2026-07-07 (session-044, seechange.md);uncertainty-005remains open. - Process concept crosswalk exists at
docs/crosswalks/concepts/process.md. - Fetch YAMATO's OWL/Hozo files if the registration gate is completed, to move
event-007/event-008off quotation-only citation (uncertainty-005). - ~~Check whether GUM's
NameEventcorresponds to anything here~~ — done 2026-07-07: addedConfiguration(correspondence-011/mapping-011);uncertainty-007records the still-open Process-vs-Configuration weighting question.