PeaCE-Ful Web Event Extraction and Processing as Bitemporal Mutable Events

Autoren
T. Furche, G. Grasso, M. Huemer, C. Schallhart, M. Schrefl
Paper
Huem16a (2016)
Zitat
Journal ACM Transactions on the Web (TWEB), Volume 10, Issue 3, August 2016, ACM Press, ISSN 1559-1131, pp. 16:1-16:47, 2016.
Ressourcen
Kopie  (Senden Sie ein Email mit  Huem16a  als Betreff an dke.win@jku.at um diese Kopie zu erhalten)

Kurzfassung (Englisch)

The web is the largest bulletin board of the world. Events of all types, from flight arrivals to business meetings, are announced on this board. Tracking and reacting to such event announcements, however, is a tedious manual task, only slightly alleviated by email or similar notifications. Announcements are published with human readers in mind, and updates or delayed announcements are frequent. These characteristics have hampered attempts at automatic tracking.

PeaCE provides the first integrated framework for event processing on top of web event ads, consisting of event extraction, complex event processing, and action execution in response to these events. Given a schema of the events to be tracked, the framework populates this schema by extracting events from announcement sources. This extraction is performed by little programs called wrappers that produce the events including updates and retractions. PeaCE then queries these events to detect complex events, often combining announcements from multiple sources. To deal with updates and delayed announcements, PeaCE’s schemas are bitemporal, to distinguish between occurrence and detection time. This allows complex event specifications to track updates and to react upon differences in occurrence and detection time. In case of new, changing, or deleted events, PeaCE allows one to execute actions, such as tweeting or sending out email notifications. Actions are typically specified as web interactions, for example, to fill and submit a form with attributes of the triggering event.

Our evaluation shows that PeaCE’s processing is dominated by the time needed for accessing the web to extract events and perform actions, allotting to 97.4%. Thus, PeaCE requires only 2.6% overhead, and therefore, the complex event processor scales well even with moderate resources. We further show that simple and reasonable restrictions on complex event specifications and the timing of constituent events suffice to guarantee that PeaCE only requires a constant buffer to process arbitrarily many event announcements.