m (Review has been assigned.) |
EvaBlomqvist (Talk | contribs) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
{{Graphical representation | {{Graphical representation | ||
− | |ImageName= | + | |ImageName=EP_ODP.png |
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
− | |SubmittedBy=EvaBlomqvist | + | |SubmittedBy=EvaBlomqvist, MikkoRinne |
|Name=EventProcessing | |Name=EventProcessing | ||
|ContentODPAlsoKnownAs=ComplexEventProcessing | |ContentODPAlsoKnownAs=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. | |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. | ||
|Domain=Event Processing, General | |Domain=Event Processing, General | ||
− | |CompetencyQuestion=What event objects are this complex event object and abstraction of?, What is the header/body of this event object?, What | + | |CompetencyQuestion=What event objects are this complex event object and abstraction of?, What is the header/body of this event object?, What are the parts of this composite event object?, What is the timestamp of this event object?, By what sensor was this event object recorded?, What actual event does this event object document?, What are the attribute values of this event object? |
− | |ContentODPDescription= | + | |ContentODPDescription=See WOP2013 pattern abstract, and full paper. |
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl | |ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl | ||
|CPInstantiationExample=http://www.ontologydesignpatterns.org/cp/examples/eventprocessing/eventexample.owl | |CPInstantiationExample=http://www.ontologydesignpatterns.org/cp/examples/eventprocessing/eventexample.owl | ||
Line 17: | Line 17: | ||
{{Element list header}} | {{Element list header}} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=SimpleEventObject |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
Line 23: | Line 23: | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=CompositeEventObject |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=ComplexEventObject |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=hasEventObjectPart |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=SensorOutput |
+ | }} | ||
+ | {{Has Element Template | ||
+ | |HasElement=hasSubEventObject | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
Line 38: | Line 41: | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=hasEventObjectTime |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=hasEventDuration |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
− | |HasElement= | + | |HasElement=hasEventObjectAttributeValue |
+ | }} | ||
+ | {{Has Element Template | ||
+ | |HasElement=hasEventObjectAttributeDataValue | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
Line 51: | Line 57: | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=EventObjectPart | |HasElement=EventObjectPart | ||
− | |||
− | |||
− | |||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
Line 111: | Line 114: | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=hasEventObjectApplicationTime | |HasElement=hasEventObjectApplicationTime | ||
+ | }} | ||
+ | {{Takes in account review | ||
+ | |TakesInAccountReview=VojtechSvatek about EventProcessing | ||
}} | }} | ||
{{Additional information header}} | {{Additional information header}} | ||
− | + | [[Category:Review assigned]] | |
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
Line 121: | Line 127: | ||
|Event=WOP:2013 | |Event=WOP:2013 | ||
}} | }} | ||
− | + | {{Submission to event}} | |
− | + | ||
− | + |
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:
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).
No 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
|
---|