DEBS 2011 - accepted papers and tutorials

DEBS 2O11 -  here are the list of accepted papers and tutorials.
The registration site is now open:  

Papers accepted to the Research Track

1	Qiong Zou, Bugra Gedik and Kun Wang.	SpamWatcher: A Streaming Social Network Analytic on the IBM Wire-speed Processor
2	Nihal Dindar, Peter M. Fischer, Merve Soner and Nesime Tatbul.	Efficiently Correlating Complex Events over Live and Archived Data Streams
3	Richard Hull, Elio Damaggio, Riccardo De Masellis, Fabiana Fournier, Manmohan Gupta, Fenno Heath Iii, Stacy Hobson, Mark Linehan, Sridhar Maradugu, Anil Nigam, Piyawadee Sukaviriya and Roman Vaculin.	Business Entities with Guard-Stage-Milestone Lifecycles: Managing Entity Interactions with Conditions and Events
4	Jonas Buys, Vincenzo De Florio and Chris Blondia.	Towards context-aware adaptive fault tolerance in SOA applications
5	Jatinder Singh, David Eyers and Jean Bacon.	Disclosure control in multi-domain publish/subscribe systems
6	Ella Rabinovich, Opher Etzion and Avigdor Gal	Pattern Rewriting Framework for Event Processing Optimization
7	Yagil Engel and Opher Etzion.	Towards Proactive Event-Driven Computing
8	Amer Farroukh, Mohammad Sadoghi and Hans-Arno Jacobsen.	Towards Vulnerability-Based Intrusion Detection with Event Processing
9	Gianpaolo Cugola and Alessandro Margara.	High Performance Content-Based Matching Using GPUs
10	Rohit Wagle, Henrique Andrade, Kirsten Hildrum, Chitra Venkatramani and Michael Spicer.	Distributed Middleware Reliability and Fault Tolerance Support in System S
11	Michael Olson, Annie Liu, Matthew Faulkner and K. Mani Chandy.	Rapid Detection of Rare Geospatial Events: Earthquake Warning Applications
12	Vana Kalogeraki, Adam Dou, Dimitrios Gunopulos, Taneli Mielikinen and Ville Tuulos.	Scheduling for Real-Time Mobile MapReduce Systems
13	Sangjeong Lee, Youngki Lee, Byoungjip Kim, K. Selçuk Candan, Yunseok Rhee and Junehwa Song	. High-Performance Composite Event Monitoring System Supporting Large Numbers of Queries and Sources
14	Siddarth Ganesan, Young Yoon and Hans-Arno Jacobsen.	Take Five: The Management Infrastructure for Distributed Event-Driven Workflows
15	Bibudh Lahiri, Srikanta Tirthapura and Jaideep Chandrashekar	Space-efficient Tracking of Persistent Items in a Massive Data Stream
16	Amirhossein Malekpour, Antonio Carzaniga, Fernando Pedone and Giovanni Toffetti Carughi.	End-to-End Reliability for Best-Effort Content-Based  Publish/Subscribe Networks
17	Eberhard Grummt.	Fine-grained Parallel XML Filtering for Content-based Publish/Subscribe Systems
18	Szabolcs Rozsnyai, Aleksander Slominski and Geetika Lakshmanan.	Discovering Event Correlation Rules for Semi-Structured Business Processes
19	Mark Linehan, Sylvain Dehors, Ella Rabinovich and Fabiana Fournier	Controlled English Language for Production and Event Processing Rules
20	Gabriela Jacques Da Silva, Bugra Gedik, Henrique Andrade, Kun-Lung Wu and Ravishankar K. Iyer.	Fault Injection-based Assessment of Partial Fault Tolerance in Stream Processing Applications
21	Xinxin Wang, K.Selcuk Candan and Junehwa Song	Complex Pattern Ranking (CPR): Evaluating Top-k Pattern Queries Over Event Streams
22	K R Jayaram and Patrick Eugster.	Program Analysis for Event-based Distributed Systems
23	Ming Li and Murali Mani.	Complex Event Pattern Detection over Streams with Interval-Based Temporal Semantics

Papers accepted to the industry track

1	Jimi Wen, Guyuan Lin, David Wu, Today Sung, Minsiong Liang and Gary Tsai.	A Complex Event Processing Architecture For Energy and Operation Management
2	Florian Kerschbaum.	Securely Disseminating RFID Events
3	Pekka Kaarela, Mika Varjola and Lucas Noldus.	PRONTO – Support for real-time decision making
4	Ashish Kulkarni.	ARCADE - ABSTRACTION AND REALIZATION OF COMPLEX EVENT SCENARIOS USING DYNAMIC RULE CREATION
5	Alexandre Alves.	A General Extension System for Event Processing Languages
6	Ruediger Klein, Jingquan Xie and Andrij Usov	Complex Events and Actions to Control Cyber-Physical Systems
7	Naomi Seyfer, Richard Tibbetts and Nathaniel Mishkin.	Capture Fields: Modularity in a Stream-Relational Event Processing Language
8	Hannes Obweger, Josef Schiefer, Martin Suntinger, Peter Kepplinger and Szabolcs Rozsnyai.	User-Oriented Rule Management for Event-Based Applications
9	Pål Evensen and Hein Meling.	A Paradigm Comparison for Collecting TV Channel Statistics from High-volume Channel Zap Events
10	Nenad Stojanovic, Dejan Milenovic, Yongchun Xu, Ljiljana Stojanovic and Darko Anicic.	An intelligent event-driven approach for efficient energy consumption in commercial buildings: smart office use case

Accepted tutorials

1	Gianpaolo Cugola and Alessandro Margara	Processing Flows of Information: From Data Stream to Complex Event Processing
2	Opher Etzion and Ella Rabinovich	Non Functional properties of event processing
3	Chathura Herath	Programming abstraction for Event processing in e?sciences – Dilemma of managing high data event rates with high resource consuming computations
4	Nenad Stojanovic, Pedro Bizzaro and Mani Chandy	Event Processing Grand Challenges
5	Scott De Deugd and Dave Locke	Open Messaging in the Real World
6	Paul Vincent, Adrian Paschke,  Catherine Moxey and Alexandre Alves	Architectural and Functional Design Patterns for Event Processing

Briefing a USA federal committee

In this picture you can see me and a tiger during my family vacation in Thailand, in 2007.
Today I met another TIGER - the standing committee for Technology Insight-Gauge, Evaluate & Review which is a committee of the USA National Academics that works on behalf of the USA intelligence community. 

I am still unsure how they picked me up, but they invited me to participate in a meeting with the committee members and some other participants through video conference and brief them on the state of the practice, my vision for event processing in 2020, and the challenges on the way to get there.  This is an indication that event processing has caught the attention of  defense sector as well.    The vision part talked about the Event Fabric devised as the grand challenge in the Dagstuhl event processing seminar,  published as chapter 5 in the event processing manifesto (BTW - in DEBS 2011 there will be a tutorial about this grand challenge). 
Another topic was of course, the proactive world, my favorite topic.  


I was asked what is the killer application that will drive the 2020 vision, and said there is no single killer application, there are multiple of them, and I see many of them outside the corporate IT domain, such as autonomic robots and computing embedded in biological systems.   Of course, defense applications will also be part of the driving forces.    More on this topics -- later

DEBS 2011 news

The DEBS 2011 track chairs have sent acceptance (and rejection) notes to the authors.  This time there has been substantial growth in the number of submissions, and also seems that there were quite a lot of quality papers, not all of the high quality papers could be accepted.


Some statistics: 


 The research track accepted 23 papers 
 The industry track accepted 10 papers  
 The tutorial track accepted  6 tutorials 


PhD workshop notifications will be made shortly.   Accepted papers co-authored by PhD students qualify the students also the right to participate in the PhD workshop and get feedback in a mentoring atmosphere by some of the leading figures of the area.


Next call is the posters and demos call - open until May 2nd.   This gives a chance to present work in progress, and also provides opportunity to authors of rejected papers to present a poster and interact with the participants on their research.

On predictive and proactive processing

Recently, there was a notification about IBM Research project, from the Almaden Research Center, that deal with prediction of traffic jams.  Prediction of traffic jams is always useful,  as you don't want to get caught by surprise,   this afternoon we are going to celebrate the holiday in the traditional family "Passover Seder".  The radio already predicts that all routes will be loaded,  which is good to prepare yourself for a long stay on the road, but don't help much in resolving it.    Prediction is an important step, but to complete the loop we need also the proactive behavior, in which one can also do something about it.    The proactive solution may be to go via another route, which may not be helpful today - since all roads will be jammed.   Anyway - the ability to predict future events is a key aspect in proactive computing, and they are used as a basis for proactive decisions. 


Going also tomorrow morning for a few days vacation in Barcelona.   Back - next week.

On event processing related standards

One of the items in the EPTS charter talked about incubating standards related to event processing.   When EPTS was established, three years ago, the general opinion was that it was still premature to deal with standards.
Recently, there have been two developments related to standards:

1. The event processing manifesto work includes a chapter that surveyed related standards and recommended some action items.   It has been presented within the EPTS virtual symposium last month by Paul Vincent.
2. OMG has renewed its call to express interest in work towards a standard on Event meta-modeling and profile  (in essence:  event structure).

Today, a vote request was sent to all EPTS members to answer two questions:  whether EPTS should establish a work-group to view standards in a strategic way, and whether EPTS should support/play a role in the OMG standard.   


Standards have a potential to give a big push to the area (this has happened in other areas);  the grand challenge presented in the event processing manifesto, the "event fabric" in an internet scale requires the existence of standards as a prerequisite,  however there need to be a shorter term business motivation to make it fly.

On events vs. data - the semantic view

I have written in the past about events vs. data, talking about the various roles that data stores can play in event processing.   recently I had a discussion in the more semantic level., about the differences between events and data.   The first distinction is that data (and also objects) do not have semantics in general, since anything can be stored in data, however event has a semantic meaning: something that happens!.    So the best comparison is to semantic data models, and in the picture above you can see the most simple (and common) semantic data model - the entity-relationship model.    As seen in this picture, entity is a term that designates some common name for individual beings that are classified to that term.   Person, department, equipment and experiment show in the picture are all entities.   None of them represent events,  since event is a different creature,  as mentioned it designates something that happens.   An event typically references entities.  For example, the event - Paul sold the bike to Peter is an event of type "sell" (if this is a general auction domain)  or "bike sell" (if this is a bicycle store domain).    In this case the event references three entities: 

• Buyer:  entity of type person
• Seller:  entity of type person
• Item:   entity of type bike

Of course, in more general case the buyer and the seller can be corporates, and the item can be of any item type.    If we look at the description as a sentence,  the entity type is represented by a noun, while the event type is represented by a verb.    Note that not all verbs represent events though,  if we look at the picture above, the relationship  "requires" is a verb that designates that an experiment requires equipment, but it is not an event,  it is a static relationship among two entities,  so verb is not a sufficient condition for event, event represents a verb that indicate that something happened.     Models like the entity relationships model should be extended to include events.    

Reviewing project for the European Commission

Dortmund, Germany.     Morning -- packing to start the way home.
In the last couple of days I have participated as a reviewer in two reviews of  EU projects which are centered around event processing -- Play (in Brussels) and Pronto (here in the fire fighters instruction center).   Play is in his first year,  building infrastructure for  "events marketplace",  Pronto in its third (and last) year, deals with events that arrive from multi-media sources, you can read some details about them on their websites.   Getting more event processing centered projects funded by government agencies is an indication of the growing importance of this area.    Got some interesting observations out of these reviews, which I'll write about later.