|
Last modified date is: 2013-08-29 |
Diagram
| 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: | 1 (555) |
| Consequences: | |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The EventProcessing Content OP locally defines the following ontology elements:
SimpleEventObject (owl:Class) An event object that is not an abstraction of other event objects, nor is composed of other event objects.
SimpleEventObject page EventObject (owl:Class) An object that represents, encodes, or records an event, generally for the purpose of computer processing.
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).
EventObject page CompositeEventObject (owl:Class) An event object that is composed of a set of other event objects, i.e. its parts.
CompositeEventObject page ComplexEventObject (owl:Class) An event that summarizes, represents, or denotes a set of other events, i.e. it is an abstraction over other events. Anything that is not a complex event is instead a simple event.
ComplexEventObject page
hasEventObjectPart (owl:TransitiveProperty) This transitive property represents a partonomy relation between event objects. An event object can consist of several "partial events" that together make up the complete event object. The parts of the event object do not exist on their own, but exist to "make up" the whole of the encapsulating event, likewise the encapsulating event is not complete without its parts. Please note the difference between this stronger relation, compared to the "hasSubEvent"-property which merely relates event objects to each other, e.g. expressing the triggering of abstractions, but without implying that the events are parts of each other.
hasEventObjectPart page SensorOutput (owl:Class) Class representing the alignement to ssn:SensorOutput, expressing the restriction that an ssn:SensorOutput is either a complex event or a simple event, depending on the sensor used.
SensorOutput page hasSubEventObject (owl:TransitiveProperty) A relation that connects a complex event with the low-level events it is a higher-level representation of. An event object may reference another event, on a lower level of abstraction or granularity, upon which is it is based or from which it was derived or triggered, making that other event a "sub event" of this aggregated or more abstract event object. Note that for modelling instance data, normally, the non-transitive sub-property "hasDirectSubEventObject" should be used, based on which the presence of this transitive relation can be inferred.
hasSubEventObject page EventObjectHeader (owl:Class) Some event processing systems need to distinguish between an event object header and its body, where the event object header is the part of the event object with known content (e.g. known vocabulary) that can be directly processed by the event processing system. Although a header is considered mandatory for an event object, if not specified what the header consists of, it can be inferred by the system through the fact that it contains the "known" part, as opposed to the body that may contain a payload that the system cannot interpret.
EventObjectHeader page hasEventDuration (owl:ObjectProperty) Property for represting a time interval of an event object, rather than a time point. Alternative is to define several time points, using the subproperties of the datatype property hasEventObjectTime.
hasEventDuration page EventObjectBody (owl:Class) Some event processing systems need to distinguish between an event object header and its body, where the event object header is the part of the event object with known content (e.g. known vocabulary) that can be directly processed by the event processing system, and the body is the rest of the event object. The body may always be empty or missing.
EventObjectBody page hasEventObjectHeader (owl:ObjectProperty) Some event processing systems need to distinguish between an event object header and its body, where the event object header is the part of the event object with known content (e.g. known vocabulary) that can be directly processed by the event processing system. This property relates an event object to its header part.
hasEventObjectHeader page hasEventObjectBody (owl:ObjectProperty) Some event processing systems need to distinguish between an event object header and its body, where the event object header is the part of the event object with known content (e.g. known vocabulary) that can be directly processed by the event processing system. This property relates an event object to its body part.
hasEventObjectBody page refersToEventObjectConstituent (owl:ObjectProperty) Event objects that use a header/body structure can use this property to refer to the constituents (i.e. direct sub-events in an abstraction hierarchy) of the event object. Through a property chain axiom, the presence of a "hasDirectSubEventObject" relation can be inferred.
refersToEventObjectConstituent page refersToEventObjectComponent (owl:ObjectProperty) Event objects that use a header/body structure can use this property to refer to the components (i.e. direct parts) of the event object. Through a property chain axiom, the presence of a "hasEventObjectComponent" relation can be inferred.
refersToEventObjectComponent page hasEventObjectComponent (owl:ObjectProperty) This non-transitive property expresses the direct relation between an event object and its direct parts, i.e. its components. Using this property a hierarchy of components can be expressed for an event object. The components of the event object do not exist on their own, but exist to "make up" the whole of the encapsulating event, likewise the encapsulating event is not complete without its parts. Please note the difference between this stronger relation, compared to the "hasSubEvent"-property which merely relates event objects to each other, e.g. expressing the triggering of abstractions, but without implying that the events are parts of each other.
hasEventObjectComponent page hasSensorReadingValue (owl:ObjectProperty) Property for expresseing the alignemet to the SSN ontology, equivalent to ssn:hasValue.
hasSensorReadingValue page hasDirectSubEventObject (owl:ObjectProperty) A relation that connects a complex event with the low-level events it is a higher-level representation of. This is a non-transitive relation that can be used to create a hierarchy of levels of sub-events, that represents the reasoning/triggering or abstraction process that led up to the creation or detection of a complex event. The transitive superproperty hasSubEventObject allows for direclty querying for the transitive closure of sub-events, regardless of the hierarchy, even if only this non-transitive sub-property is used in the data.
hasDirectSubEventObject page
hasEventObjectSystemTime (owl:DatatypeProperty) The timestamp of the event according to the event processing system (in terms of its internal clock time), i.e. when the event object was received byt the event processing system through the stream.
hasEventObjectSystemTime page hasEventObjectExpirationTime (owl:DatatypeProperty) Time limit on the validity of this event object.
hasEventObjectExpirationTime page hasEventObjectSamplingTime (owl:DatatypeProperty) The time the event was detected and recorded as data, e.g. when it was recorded by a sensor in terms of the sensor's internal clock.
hasEventObjectSamplingTime page hasEventObjectApplicationTime (owl:DatatypeProperty) The timestamp assigned by the source of the data when it was transmitted, i.e. when it entered the stream.
hasEventObjectApplicationTime pageNo scenario is added to this Content OP.
This revision (revision ID 11694) takes in account the reviews: EventProcessing (VojtechSvatek about EventProcessing)
Other info at evaluation tab
|
Submission to event |
|---|
|
|
Submission to event
|
|---|
'Ontology Design Patterns'