Events must be complete in event processing!

Authors:
Raman Adaikkalavan;Sharma Chakravarthy
Affiliations:
Indiana University South Bend, South Bend, IN;The University of Texas At Arlington, Arlington, TX
Venue:
Proceedings of the 2008 ACM symposium on Applied computing
Year:
2008

Citing 6
Cited 1

Snoop: an expressive event specification language for active databases

Data & Knowledge Engineering
Active Database Systems: Triggers and Rules for Advanced Database Processing

Active Database Systems: Triggers and Rules for Advanced Database Processing
Two Approaches to Event Definition

DEXA '02 Proceedings of the 13th International Conference on Database and Expert Systems Applications
SnoopIB: interval-based event specification and detection for active databases

Data & Knowledge Engineering
Generalization and enforcement of role-based access control using a novel event-based approach

Generalization and enforcement of role-based access control using a novel event-based approach
Event specification and processing for advanced applications: generalization and formalization

DEXA'07 Proceedings of the 18th international conference on Database and Expert Systems Applications

Towards efficient event aggregation in a decentralized publish-subscribe system

Proceedings of the Third ACM International Conference on Distributed Event-Based Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

Current event detection systems are based on event completeness, which alone is insufficient for supporting new and advanced applications. In this paper, we discuss the need for events that are not complete. We briefly discuss their modeling and specification.