Submissions:EventProcessing
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: 11694 |
Graphical representation
Diagram
General description
Name: | EventProcessing |
---|---|
Submitted by: | EvaBlomqvist, MikkoRinne |
Also Known As: | ComplexEventProcessing |
Intent: | To model event objects (in the context of complex event processing), their attributes, and their relations actual events, and sensor readings producing the events. Different types of event objects, such as complex, composite, and simple events are modelled, preoperties for expressing relations between event objects, such as constituency and componency are expressed, and attributes of event objects, such as timestamps and other data values. This pattern is aligned both to the SSN (Semantic Sensor Network) ontology, and the Event-F model, which in turn both use DUL as an upper layer. |
Domains: | |
Competency Questions: |
|
Solution description: | See WOP2013 pattern abstract, and full paper. |
Reusable OWL Building Block: | http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl (944) |
Consequences: | |
Scenarios: | |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
Elements
The EventProcessing Content OP locally defines the following ontology elements:
An event object may consist of an event object header and a body, where the header is defined as the part of the event object that can be interpreted by the event processing system, i.e. and event object needs to contain at least some information (e.g. with a known vocabulary) that can be used by the event processing system. Note that the open world assumption allows us to choose not to explicitly specify a header, despite the restriction that it exists.
An event object is either a complex event, i.e. an event object that has some relation (either through abstraction or componency) to other event objects, or a simple event.
An event object records information about an actual event, which is then by implication a documented event (i.e. participating in an event documentation situation).
Additional information
Scenarios
No scenario is added to this Content OP.
Reviews
Review article | Posted on | About revision (current is 11694) |
---|---|---|
VojtechSvatek about EventProcessing | 24565127 August 2013 | 1164611,646 |
This revision (revision ID 11694) takes in account the reviews: VojtechSvatek about EventProcessing
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
Submission to event |
---|
Submission to event
|
---|