SnoopIB: Interval-based event specification and detection for active databases

EVA: An event algebra supporting complex event specification

“…The history of events that a service processes is then tr t 0 ;1 with t 0 being the point in time the service started observing events. 3 We need a mechanism to refer to each event in a trace. Because a trace behaves essentially as a list, we can use the operations commonly defined for lists: We apply an arbitrary local order that assigns an index number i A N to each event.…”

“…We define the semantics of a conjunction of events as follows: Let us consider the event classes E 1 , E 2 with E 1 ¼ feje A E; p 1 ⊏eg and E 2 ¼ feje A E; p 2 ⊏eg. The set of matching events of a given trace tr is then defined as tr [2,2] tr [3,1] tr [3,2] tr [4,1] tr [4,2] tr [4,3] . .…”

“…The Snoop language of the Sentinel introduced parameter contexts to control the semantics of each operator [43,29]. SnoopIB extends Snoop to events with durations [1,3]. Rapide's language covers complex situation such as causality and event equivalences [80].…”

“…Chakravarthy refers to point semantics as detectionbased semantics as the event time is typically defined by the end of the detection interval, whereas interval semantics is referred to as occurrence-based [27,3].…”

Middleware for heterogeneous subsystems interoperability in intelligent buildings

“…The ECA interoperation schema is based on Event-Condition-Action (ECA) rules. ECA rules were first introduced in the domain of database technology [26]. ECA rules take the form "on" some event "if" some condition then some actions.…”