[Fiware-iot] Fiware - Event definition agreement between WP5 & WP6

[Guy Sharon]

Hi Ricardo,

My suggestion in event and event processing terminology is not to 
reinvent.
The most elaborated and common terminology in this area can be found in 
the Event Processing Technical Society - the event glossary
http://www.ep-ts.com/component/option,com_docman/task,doc_download/gid,66/Itemid,84/
It covers events, event objects, complex and derived events etc.

Guy Sharon
Manager
Event-based Middleware & Solutions Group


Event-based Middleware & Solutions

phone : 
+972 4 8296587
mobile : 
+972 54 6976417
address : 
IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 
31905, Israel
email : 
guysh at il.ibm.com




From:   Ricardo de las Heras <rheras at tid.es>
To:     Guy Sharon/Haifa/IBM at IBMIL, "sabine.zander at orange-ftgroup.com" 
<sabine.zander at orange-ftgroup.com>, JUAN JOSE HIERRO SUREDA 
<jhierro at tid.es>
Cc:     boris.moltchanov at telecomitalia.it
Date:   26/05/2011 11:50
Subject:        Fiware - Event definition agreement between WP5 & WP6



Dear colleagues from WP6, 

in the IoT WP5, we are defining a basic glossary as common framework for 
our work and future understanding in this area.
However some of the definitions and concepts are relevant for you as well, 
because CEP, massive storage or Context mngmt. overlaps with the IoT World 
in some way, that's why I point directly to you in this mail as partners 
involved in those areas within WP6.

First, from WP5 we would like to achieve a common agreement with you about 
the concept of a 'Event', so please check the current definition we have 
and modify it if needed:

"Event. An event can be defined as an activity that happens/occurs or the 
digital representation of this activity in a an IoT backend instance, or 
more generally, in a FI-WARE instance. The second definition could be 
called ?event object?, but it can be argued that the context will always 
identify which meaning of the term is used. There is one-to-many 
relationship between the two meanings: the same activity can be 
represented by more than one event object; where each event object can 
capture different attributes of the activity. In many event processing 
systems the events are immutable, in such systems modifications of an 
event must be achieved by creating a new event. Events may be simple and 
complex. A simple event is an event that is not an abstraction or 
composition of other events. An example of a simple event is that ?smart 
meter X got broken?. A complex event is an event that is an abstraction of 
other events called its members. For example a stock market crash or a 
cellular network blackout is an abstraction denoting many thousand of 
member events. In many cases a complex event references the set of its 
members, the implication being that the event contains a reference. For 
example, the cellular network blackout may be caused by a power failure of 
the air conditioning in the operator?s data center. In other cases such a 
reference may not exist. For example, usually there is no accepted 
agreement as to which events are members of a stock market crash complex 
event."

Nevertheless the idea is that WP5 will mainly use the CEP or 
Publish/Subscribe/Notify mechanisms provided by WP6.

And second, regarding the data storage, in the WP5 we are not going to 
locally store the historic data collected from the IoT World. We have to 
discuss this important issue in the future meetings, but I understand the 
basic idea we agreed in the past between both WPS, was that WP6 collects 
and stores all those huge amount of information received from IoT and WP5 
will only store locally the gathered information in the case that 
information would not be relevant for the rest of the scope of the WP5, I 
mean the usage areas and the rest of the Fiware WPs.

Looking forward to receiving your feedback,
best,
Ricardo.
-- 
-------------------------------------
Ricardo de las Heras
Research Project Manager
E-mail: rheras at tid.es
Phone1: (+34) 983 367625
Phone2: (+34) 91 1878107 + Ext:327
Telefónica I+D
-------------------------------------

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110526/3b5bfefc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2558 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110526/3b5bfefc/attachment.gif>