From syntactic point of view, CEP looks for patterns and derives event / trigger action based on each pattern detected, however, detecting the patten is the mechanic work, the patterns designate a "situation" which is an "event" in the customer's frame of reference to which the customer wants to react to (there are also "internal" situation for further processing. There is obviously a gap between the intention (situation) and the way it is detected (patter no the event flow). In many cases,satisfying the pattern is sufficient condition to detect the intended situation, however, in other cases, this serves as "best approximation". This leads to the phenomenon of false positives (detecting of patterns, but the situation did not really happen) and post negatives (situation occurred but pattern has not been detected). Some reasons are:
- Raw events are missed - do not get at all, or do not get on time (source or communication issues).
- Raw events are not accurate - values are not accurate (source issues).
- Temporal order issues - Uncertainty in correct order of events.
- Pattern does not accurately reflect the conditions for situation (e.g. there are probabilistic elements)
- (other reasons) ?
Like the time constraints case there are various utility functions to designate the damage from either false positives or false negatives.
More on that issue - later.