Pith. sign in

REVIEW 4 major objections 4 minor 39 references

F -- A Model of Events based on the Foundational Ontology DOLCE+DnS Ultralite

T0 review · 4 major / 4 minor · reviewed 2026-08-12 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read Event-Model-F represents events with six modular ontology patterns, covering time, space, participants, structural relations, documentation, and interpretations.

desk verdict Solid ontology-engineering paper whose real novelty is the six-pattern architecture, but the formal axioms are missing from the paper and the causality/correlation patterns are too thin as presented. read the letter →

arxiv 2411.16609 v1 pith:AY2T462R submitted 2024-11-25 cs.AI

Ansgar Scherp , Thomas Franz , Carsten Saathoff , Steffen Staab This is my paper · ORCID
classification cs.AI
keywords eventscoreontologyDOLCE+DnSUltraliteDescriptionsandSituationseventparticipationcompositioncausalityinterpretation
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

Distributed systems that process events need a shared, machine-readable way to describe what an event is, when and where it happened, who and what took part, and how events relate. This paper argues that existing event models cover participation, time, space, and documentation but fall short on structure and interpretation, and it presents Event-Model-F as a formal remedy. Event-Model-F is built on the DOLCE+DnS Ultralite foundational ontology and packs six functional requirements into six modular ontology patterns: participation, mereological composition, causality, correlation, documentation, and interpretation. If the model works as claimed, components in an emergency-response or similar distributed system can exchange event descriptions with unambiguous semantics, and the same occurrence can carry different, even conflicting, interpretations.

What carries the argument

The load-bearing machinery is DUL's Descriptions and Situations (DnS) pattern. In each of the six Event-Model-F patterns, a Situation includes the events and objects being described, and a Description it satisfies classifies them with EventTypes and Roles—for instance F:Cause and F:Effect for causality, F:Participant for participation, F:Composite and F:Component for mereology. Reifying these relations as situations makes them first-class individuals, which is what lets one event be described from several contextual points of view at once. The non-functional requirements—extensibility, axiomatization, modularity, reusability, and separation of concerns—are handled by a pattern-oriented design aligned with DUL.

What would settle it

Open the published OWL axiomatization and ask whether a consistent model can assert the same event as both F:Cause and F:Effect of itself under a single F:Justification; because no constraints on these roles are given, the pattern would accept such a self-cause, showing that it does not yet carry the causal semantics it claims to represent.

Watch

Extended reading notes

Core claim

The central claim is that Event-Model-F is a formal model of events that satisfies all six functional requirements it identifies: participation of objects in events, temporal duration and spatial extension, structural relationships (mereological, causal, correlative), documentary support, and event interpretations. The paper shows this by instantiating the Descriptions and Situations pattern for each requirement, so each aspect of an event becomes a situation that satisfies a description defining typed roles. It also claims that this combination is what separates Event-Model-F from existing event models: none of the surveyed models offers full structural support together with support for multiple interpretations of the same event. The conclusion states this distinction explicitly.

Load-bearing premise

The causal and correlative parts of the model depend on the assumption that reifying a causal or correlative statement as a situation with a justification role preserves the statement's intended meaning—yet the ontology supplies no axioms that actually constrain what Cause, Effect, or Correlate may do, and if that reification is semantically inadequate the claim of comprehensive structural support breaks down.

Editorial extensions

If this is right

  • Event descriptions built with Event-Model-F can be exchanged between heterogeneous systems and checked automatically for consistency with the model's axioms, not just their syntax.
  • Domain ontologies can be plugged into the pattern roles, such as a Citizen or AffectedBuilding role in an emergency-response ontology, so existing domain knowledge is reused without being remodeled.
  • One real-world occurrence can be represented under multiple event interpretations simultaneously by binding separate participation, composition, causality, correlation, and documentation situations under an interpretation pattern.
  • Composition constraints let events be related by arbitrary temporal orderings, including disjointness and overlap, using Allen-style relations; relative spatial constraints are expressed through participating objects' locations.
  • The model explicitly represents correlation as a common-cause relation, so correlated effects can be recorded even when the common cause itself is unknown.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The paper leaves the causal and correlative roles unconstrained by axioms; a natural follow-up is to define consistency conditions, such as Cause and Effect being distinct events with a shared Justification, and then test whether real causal narratives remain representable.
  • Because every relation is reified as a situation, event descriptions become large graphs of interconnected situations; this may make querying and reasoning more expensive than in flat event models, so an empirical comparison of reasoning performance on realistic event logs is a direct way to probe the model's practical interoperability claim.
  • The interpretation pattern suggests an integration strategy the paper does not itself develop: map each proprietary event model's relations onto one of the six F patterns, and use interpretations to keep divergent views separate while sharing the common event core.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

4 major / 4 minor

Summary. The paper presents Event-Model-F, a pattern-based event ontology aligned with DOLCE+DnS Ultralite (DUL). It introduces six patterns, namely participation, mereology, causality, correlation, documentation, and interpretation, and claims that they together provide comprehensive formal support for representing time and space, objects and persons, and mereological, causal, and correlative relationships between events. The model is modular and designed to be extended by domain ontologies. The paper evaluates the model against six functional and five non-functional requirements and compares it with eight existing event models, concluding that Event-Model-F is the only one offering full support for structural relationships and multiple event interpretations.

Significance. If the formal claims are substantiated, the model would be a valuable contribution to event-based systems interoperability: it is modular, grounded in a foundational ontology, and explicitly addresses the underrepresented aspects of causality, correlation, and multiple interpretations. The comparative analysis of eight event models is also useful. However, the current manuscript does not deliver the promised formal axiomatization; the patterns are described informally through diagrams and text, and the requirement coverage is self-assessed rather than formally demonstrated. The paper's significance therefore remains conditional until the DL axioms and formal evaluations are actually provided.

major comments (4)
  1. [Sections 5.3 and 5.4] The causality and correlation patterns are semantically unconstrained. In Section 5.3, F:Cause and F:Effect are introduced as EventTypes that classify events included in an F:EventCausalitySituation, and F:Justification classifies some DUL:Description, but no axiom is presented that requires the Description to contain a causal theory, that the cause precedes the effect, or that the situation constitutes a causal explanation. Consequently, any arbitrary pair of events can be labeled Cause/Effect under some Description, and the pattern does not distinguish causality from co-classification. In Section 5.4, F:Correlate is defined as a Role but no axiom links an F:EventCorrelationSituation to an F:EventCausalitySituation or to a common cause, despite the section's own definition of correlation as sharing a common cause. The structural support for causality and correlation is therefore purely syntactic in the manuscript, which contradicts the claim of comprehensive formal support in Section 8.
  2. [Section 5, opening; Section 4.2(b)] The paper repeatedly asserts that the model is axiomatized in Description Logics, but no DL axioms, class definitions, role/property definitions, or reasoning results appear in the manuscript. The sentence 'The axiomatization of the Event-Model-F has been conducted in Description Logics and is available online at: http://isweb.uni-koblenz.de/eventmodel' is an external pointer, not a specification. Because non-functional requirement (b) explicitly demands sufficient formality and axiomatization for automatic semantic checks, the absence of the axioms in the paper makes the central formal claims unverifiable and prevents a reader from checking whether the online artifact matches the patterns described here.
  3. [Sections 4.1 and 7] The functional requirements are synthesized by the authors from a scenario and existing models, and the model is then evaluated against these same requirements in Sections 5 and 7. The claim that Event-Model-F 'supports all of them' (Section 7) is an assertion based on the design, not a formal demonstration: the paper provides no consistency check, no entailment tests, and no independent benchmark. The comparative table in Figure 3 is also not based on an explicit scoring rubric, so the degrees of support ('Yes', 'No', 'Lim.') are not independently reproducible. This self-assessment does not by itself invalidate the model, but it does mean the full-support conclusion is partly self-referential and should be supported by formal evaluation or at least by a clearly defined criterion.
  4. [Section 5.2 (Mereology Pattern)] The claim that events may be 'arbitrarily temporally related to each other' using 'the provided means of DOLCE such as the formalization of Allen's Time Calculus' is not substantiated. The F:EventCompositionConstraint is described only informally as an instance that 'formalizes' constraints, but no constraints are defined for temporal, spatial, or spatio-temporal cases, and no mapping from Allen's relations to the ontology is given. Without these details, the mereology pattern does not demonstrate the required formal support for relative temporal and spatial relations between events.
minor comments (4)
  1. [Section 2] The sentence 'Such enduring entities unfold over space, i.e., they are in time' appears self-contradictory; the authors likely mean that objects endure over time or that they exist in space, and the text should be reworded for clarity.
  2. [Figure 3] The comparison table is difficult to parse: columns such as 'Abs.Rel.' are not explained, some cells contain multiple check marks, and the abbreviation 'Lim.' is not defined in the caption or the text.
  3. [Section 5.1] The notation 'DUL:hasRegion of a SpaceRegion' should be made precise, for example as a property that relates a Quality to a SpaceRegion, to avoid confusion between the class and the property.
  4. [Sections 5 and 9] The URLs for the online ontology are given as bare links (http://isweb.uni-koblenz.de/eventmodel and the GitHub repository in the header); the authors should provide stable identifiers, such as DOIs, or include the axioms as supplementary material.

Circularity Check

0 steps flagged · score 0.0 of 10

No significant circularity: Event-Model-F is a constructed ontology assessed against its own design checklist, not a derivation whose output equals its input; the causality/correlation gaps are formal-adequacy risks, not circularities.

full rationale

The paper's contribution is an ontology artifact, not a derived prediction, so the standard circularity patterns (fitted inputs, uniqueness theorems, ansatz-by-citation) do not apply. Section 4.1 synthesizes functional requirements from the event models E and Eventory plus the emergency scenario ('We have blend the aspects in E and interrogatives of the Eventory system and have synthesized them into our requirements'), and Section 7 compares F against those same requirements, concluding 'the Event-Model-F supports all of them.' This is a self-referential evaluation loop in a weak sense, because the same authors chose the checklist and built the model. It is not circular, however: the checklist is not defined in terms of F, and each requirement is implemented by a new DnS-based pattern (participation, mereology, causality, correlation, documentation, interpretation) with structure that could fail the requirement. The self-citations in Sections 4.2 and 5.7 (refs [1,8,20,21]) support methodological background and are not load-bearing; the alignment with DUL and the pattern diagrams are presented in the paper itself. The absence of DL axioms constraining F:Cause/F:Effect and F:Correlate is a semantic-adequacy limitation, and the paper itself states in Section 8 that reasoning on pattern instantiations is future work, but labeling a role 'Correlate' is not an input-output identity. No equation or citation chain makes the central claim equal to its own input, so there is no circular step to report.

Assumptions & free parameters 0 free parameters · 5 assumptions · 2 invented entities

No numbers are fitted and no empirical predictions are made. The ledger consists of the foundational ontology's metaphysical commitments (the event and object distinction), the presumption that DnS reification is formally adequate, and ad hoc choices for modeling causality and correlation. The model is a representational framework, so its correctness depends on whether the ontology axioms, not shown in this text, are coherent and expressive enough to encode the intended semantics.

assumptions (5)
  • domain assumption Events are perduring entities that unfold over time, while material objects are enduring entities that exist in space.
    Adopted from DOLCE/DUL in Section 2; the paper acknowledges this metaphysical distinction is disputed, so it is an assumed foundation rather than a derived result.
  • domain assumption The Descriptions and Situations (DnS) pattern from DUL provides formally precise representations of contextualized views and can reify n-ary relations among events and objects.
    Invoked in Section 5 to justify every pattern; the paper cites prior work [9] but presents no formal semantics or proof in this paper.
  • ad hoc to paper Causal relationships can be adequately represented by classifying events as F:Cause and F:Effect under a Description justified by an F:Justification.
    This is the modeling choice in Section 5.3; no constraints or semantics for Cause and Effect are given.
  • domain assumption Correlation can be represented by F:Correlate roles and a F:Justification description, assuming the common-cause definition of correlation.
    Section 5.4 defines correlation as common cause after Shipley; the reified representation is asserted, not proven.
  • domain assumption OWL and Description Logics semantics is sufficient for automatic semantic validation of exchanged event knowledge.
    Sections 4.2(b) and 5.7 state DL axiomatization enables reasoning and validity checks, but no DL reasoning experiment is reported.
invented entities (2)
  • EventInterpretationSituation (with Interpretant and RelevantSituation roles)
    purpose: To bind several Event-Model-F pattern instances into different, context-dependent interpretations of the same event.
    Introduced in Section 5.6 as a new construct; it is a representational device with no independent empirical handle.
  • Justification (role applied to a DUL:Description)
    purpose: To attach a causal or correlation theory to a causality or correlation situation.
    Introduced in Sections 5.3 and 5.4; it reifies the theory behind a causal or correlative claim, but no external evidence tests it.

how reviews work

0 comments
Cite this review

Pith. "Pith review of F -- A Model of Events based on the Foundational Ontology DOLCE+DnS Ultralite." pith.science (2026). https://pith.science/paper/AY2T462R

@misc{pith2026241116609,
  author       = {Pith},
  title        = {Pith review of: F -- A Model of Events based on the Foundational Ontology DOLCE+DnS Ultralite},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/AY2T462R}},
  note         = {Machine review of arXiv:2411.16609}
}
read the original abstract

The lack of a formal model of events hinders interoperability in distributed event-based systems. In this paper, we present a formal model of events, called Event-Model-F. The model is based on the foundational ontology DOLCE+DnS Ultralite (DUL) and provides comprehensive support to represent time and space, objects and persons, as well as mereological, causal, and correlative relationships between events. In addition, the Event-Model-F provides a flexible means for event composition, modeling event causality and event correlation, and representing different interpretations of the same event. The Event-Model-F is developed following the pattern-oriented approach of DUL, is modularized in different ontologies, and can be easily extended by domain specific ontologies.

Figures

Figures reproduced from arXiv: 2411.16609 by the authors.

Figure 1
Figure 1. A distributed event-based system for emergency response In an incident of a heavy storm a major flooding may happen. (i) During the flooding a power outage oc￾curs. (ii) Some citizens are lacking power supply and are calling the emergency hotline to report about the outage. The officers at the emergency hotline record these calls and type in an event description for each call to document them in their system. (iii) … view at source ↗
Figure 2
Figure 2. The patterns of F, namely (a) participation, (b) mereology, (c) causality, (d) correlation, [PITH_FULL_IMAGE:figures/full_fig_p006_2.png] view at source ↗
Figure 3
Figure 3. Comparison of Event Models Our analysis shows that the existing event models al￾most fully support the participative, temporal, spatial, and documentary aspects. However, existing event mod￾els substantially lack in supporting the structural as￾pect, i.e., mereological, causal, and correlation relation￾ships, and representation of different interpretations of the same event. Here, we find different variations of lim… view at source ↗

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

39 extracted references · 39 canonical work pages

  1. [1]

    F -- A Model of Events based on the Foundational Ontology DOLCE+DnS Ultralite

    INTRODUCTION The explicit modeling of events and event-based sys- tems are increasingly gaining widespread attention by Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this noti...

    work page Pith review arXiv 2009

  2. [2]

    One of them are objects

    EVENTS AND OBJECTS In philosophical literature, there are different discus- sions of how to discriminate events from other cate- gories [2]. One of them are objects. Although not undis- puted, there are standard differences between events and (physical) objects [2]: Events are said to occur or happen. They are considered perduring entities that unfold ove...

    work page

  3. [3]

    Here, different profes- sional entities are involved such as the emergency hot- line, police department, fire department, emergency con- trol center, and forward liaison officers

    SCENARIO An example of a distributed event-based system is the emergency response use case of the EU project We- KnowIt2 depicted in Figure 1. Here, different profes- sional entities are involved such as the emergency hot- line, police department, fire department, emergency con- trol center, and forward liaison officers. Please note 1http://ontologydesign...

    work page

  4. [4]

    REQUIREMENTS ON F We have derived functional as well as non-functional requirements on our Event-Model-F. These base on an analysis of existing event models and related work in Section 7, the emergency response scenario in Section 2, and reported and own experience in designing core on- tologies [21, 20, 1, 8]. 4.1 Functional Requirements To derive the fu...

    work page

  5. [5]

    whole” and the component events are its “parts

    DESIGN OF THE EVENT-MODEL-F For designing the Event-Model-F and implementing the functional requirements, we have carefully aligned it with the DOLCE+DnS Ultralite (DUL) ontology. DUL defines the class DUL:Event next to the disjoint upper classes DUL:Object, DUL:Abstract, and DUL:Quality. The definition of Event has been specialized from the formal defini...

    work page 2006

  6. [6]

    We demon- strate the use of our ontology at the emergency response scenario described in Section 3

    USE OF EVENT-MODEL-F With the Event-Model-F, we can create and exchange sophisticated, formal descriptions of events. We demon- strate the use of our ontology at the emergency response scenario described in Section 3. For describing an event, the different patterns defined in the Event-Model-F are combined, each providing a specific part of the event de- ...

    work page

  7. [7]

    resulted in

    EXISTING EVENT MODELS For designing the Event-Model-F, we analyzed existing event-based systems and event models with respect to the functional requirements. These models are moti- vated from different domains such as the Eventory [28] system for journalism, the Event Ontology [23] as part of a music ontology framework, the ISO-standard of the Internation...

    work page

  8. [8]

    By the use of this ontology and a pattern-oriented design approach, we are able to fulfill the non-functional requirements stated in Section 4

    CONCLUSIONS We designed a formal model of events based on the foun- dational ontology DOLCE+DnS Ultralite. By the use of this ontology and a pattern-oriented design approach, we are able to fulfill the non-functional requirements stated in Section 4. For the functional requirements, we introduced specific ontology patterns based on the Descriptions and Si...

    work page

Show all 39 references
  1. [9]

    Arndt, R

    R. Arndt, R. Troncy, S. Staab, L. Hardman, and M. Vacura. COMM: Designing a well-founded multimedia ontology for the web. In ISWC. Springer, 2007

    2007

  2. [10]

    Casati and A

    R. Casati and A. Varzi. Events. Stanford Encyclopedia of Philosophy, 2006. http://plato.stanford.edu/entries/events

    2006

  3. [11]

    Cervesato, M

    I. Cervesato, M. Franceschet, and A. Montanari. A guided tour through some extensions of the event calculus. Computational Intelligence, 16:200–0, 1999

    1999

  4. [12]

    Doerr, C.-E

    M. Doerr, C.-E. Ore, and S. Stead. The CIDOC conceptual reference model: a new standard for knowledge sharing. In Conceptual modeling. Australian Computer Society, Inc., 2007

    2007

  5. [13]

    A. Ekin, A. M. Tekalp, and R. Mehrotra. Integrated semantic-syntactic video modeling for search and browsing. IEEE Transactions on Multimedia, 6(6), 2004

    2004

  6. [14]

    Ericsson and M

    A. Ericsson and M. Berndtsson. Rex, the rule and event explorer. In H.-A. Jacobsen, G. M¨ uhl, and M. A. Jaeger, editors, DEBS. ACM, 2007

    2007

  7. [15]

    A. R. J. Francois, R. Nevatia, J. Hobbs, and R. C. Bolles. VERL: An ontology framework for representing and annotating video events. IEEE MultiMedia, 12(4), 2005

    2005

  8. [16]

    Franz, S

    T. Franz, S. Staab, and R. Arndt. The X-COSIM integration framework for a seamless semantic desktop. In Knowledge capture. ACM, 2007

    2007

  9. [17]

    A. Gangemi. Norms and plans as unification criteria for social collectives. Autonomous Agents and Multi-Agent Systems, 17(1), 2008

    2008

  10. [18]

    Gangemi, N

    A. Gangemi, N. Guarino, C. Masolo, A. Oltramari, and L. Schneider. Sweetening Ontologies with DOLCE. In EKA W. Springer, 2002

    2002

  11. [19]

    EventML, 2008

    IPTC. EventML, 2008. http://iptc.org/

    2008

  12. [20]

    E. Itkonen. Causality in Linguistic Theory. Indiana Univ. Press, 1983

    1983

  13. [21]

    L. Lombard. Events: A metaphysical study. Routledge & Kegan Paul, 1986

    1986

  14. [22]

    Masolo, S

    C. Masolo, S. Borgo, A. Gangemi, N. Guarino, and A. Oltramari. WonderWeb deliverable D18 ontology library; IST WonderWeb project, 2003

    2003

  15. [23]

    W. May, J. J. Alferes, and R. Amador. An ontology- and resources-based approach to evolution and reactivity in the semantic web. In OTM. Springer, 2005

    2005

  16. [24]

    E. T. Mueller. Handbook of Knowledge Representation, chapter Event Calculus. Elsevier, 2008

    2008

  17. [25]

    M¨ uhl, L

    G. M¨ uhl, L. Fiege, and P. Pietzuch.Distributed Event-Based Systems. Springer, 2006

    2006

  18. [26]

    Nevatia, J

    R. Nevatia, J. Hobbs, and B. Bolles. An ontology for video event representation. In Computer Vision and Pattern Recognition. IEEE, 2004

    2004

  19. [27]

    D. Oberle. Semantic Management of Middleware. Springer, 2006

    2006

  20. [28]

    Oberle and et al

    D. Oberle and et al. Towards ontologies for formalizing modularization and communication in large software systems. Appl. Ontol., 1(2):163–202, 2006

    2006

  21. [29]

    Oberle and et al

    D. Oberle and et al. DOLCE ergo SUMO: On foundational & domain models in the SmartWeb Integrated Ontology. Web Semant., 5(3), 2007

    2007

  22. [30]

    A. Quinton. Objects and events. Mind, 88(350), 1979

    1979

  23. [31]

    Raimond and S

    Y. Raimond and S. Abdallah. The event ontology,

  24. [33]

    Scherp, S

    A. Scherp, S. Agaram, and R. Jain. Event-centric media management. In SPIE, 2008

    2008

  25. [34]

    B. Shipley. Cause and Correlation in Biology. Cambridge Univ. Press, 2002

    2002

  26. [35]

    Sinclair, M

    P. Sinclair, M. Addis, F. Choi, and et al. The use of CRM core in multimedia annotation. In Semantic Web Annotations for Multimedia, 2006

    2006

  27. [36]

    Vaculin and K

    R. Vaculin and K. Sycara. Specifying and monitoring composite events for semantic web services. In ECOWS. IEEE, 2007

    2007

  28. [37]

    X. Wang, S. Mamadgi, A. Thekdi, A. Kelliher, and H. Sundaram. Eventory – an event based media repository. In Semantic Computing. IEEE, 2007

    2007

  29. [38]

    Westermann and R

    U. Westermann and R. Jain. Toward a common event model for multimedia applications. IEEE MultiMedia, 14(1), 2007

    2007

  30. [39]

    S. B. Zdonik, M. Stonebraker, M. Cherniack, and et al. The Aurora and Medusa projects. IEEE Data Eng., 26(1), 2003

    2003

  31. [2007]

    http://motools.sf.net/event

Pith tools

Reviewed August 12, 2026 · model on record in the stance chip above.