Submissions:ReportingEvent
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 12848 |
Graphical representation
Diagram
General description
| Name: | ReportingEvent |
|---|---|
| Submitted by: | EwaKowalczuk |
| Also Known As: | |
| Intent: | The intent of the pattern is to allow for modelling situations in which the knowledge about an event cannot be treated as certain. It is particularly useful for cases in which two or more agents provide different, contradictory information about the same event.
It can be also used for modelling situation in which a single agent provided contradictory information about the same event in different points in time. In general the pattern allows for stating different circumstances of an act of the information provision. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | There are in total 3 different types of events included in the pattern. The most important one is the ActualEvent, which is the physical event -- event that actually happened or is said to have happened. All the circumstances of the event (contexts) are not directly linked to the ActualEvent. They are attached to the ReportedEvent, which constitutes a view of the actual event included in a particular description/report/statement.
By making the ReportedEvent an Event, we can use all properties that could be used in case of an ordinary event, like place, time interval, cause and consequences. They are grouped in a class ReportedEventContext and are attached by hasContext property or its specialisations. As ReportedEvent provides an information about the ActualEvent entity, it can be viewed as InformationObject. It is connected to an ActualEvent using the isAbout property. The third event included in our pattern is the act of reporting the actual event -- the ReportingEvent. Its result is an ReportedEvent (linked using property reports). By modelling the act of reporting as an event, we can expose its different circumstances, for example the timestamp at which the particular reporting took place. The ReportingEvent can be also viewed as an activity, performed by a certain agent (person or organisation) -- EventReporter, utilising defined sources. |
| Reusable OWL Building Block: | http://semantic.cs.put.poznan.pl/ontologies/reportingevent.owl (713) |
| Consequences: | The pattern is rather complex and should only be used if the circumstances of the events are expected to be uncertain (to differ in different event reports). |
| Scenarios: | Two History professors have different opinion about the same actual event. The exemplary actual event is baptism of prince Mieszko I. The baptism exact place is a subject to historical debate. According to professor Hanna Kóčka-Krenz the likely place was Poznań. She bases her claim on Poznań excavations that she conducted. However the late professor Labuda pointed to Lednica Holm. He also based his claims on the local excavations but also on historical annals. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The ReportingEvent Content OP locally defines the following ontology elements:
Additional information
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 12848) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
| Submission to event |
|---|
