[Fiware-data] Fwd: RE: Peer review of the IoT and Data/Context Management chapters

[Guy Sharon]

On the CEP GE I answered some comments in bold - only one I would actually 
do something in the text


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:   Juanjo Hierro <jhierro at tid.es>
To:     "fiware-data at lists.fi-ware.eu" <fiware-data at lists.fi-ware.eu>
Date:   11/07/2011 08:26
Subject:        [Fiware-data] Fwd: RE: Peer review of the IoT and 
Data/Context    Management chapters
Sent by:        fiware-data-bounces at lists.fi-ware.eu




  A first input from the review carried by members of the IoT chapter.

  I haven't processed the information.   I'm just fowarding it to you as 
soon as I have received it.  Therefore, I don't have any opinion/feedback 
to provide on my side yet.   I hope to hear about yours.

  Best regards,

-- Juanjo

-------- Original Message -------- 
Subject: 
RE: Peer review of the IoT and Data/Context Management chapters
Date: 
Mon, 11 Jul 2011 00:47:51 +0200
From: 
thierry.nagellen at orange-ftgroup.com <thierry.nagellen at orange-ftgroup.com>
To: 
JUAN JOSE HIERRO SUREDA <jhierro at tid.es>, "lorant.farkas at nsn.com" 
<lorant.farkas at nsn.com>


Hi Juanjo

Here is my review of the data and context management part.

My first comment is that there is no description of the architecture in 
the way that you have some arrows on the first pictures and no one are 
explained so you have a collection of GE but we do not know how they work 
together. And there is no comment on the relationships with the other WP. 
I found once a reference to WSN just to write that the GE could be used in 
this environment. This is really weak for some GE which are previously 
named "Support Services".

My second comment is that what you call "high-level standard context 
wrappers" are not related to context but are some specific cases of 
data-mining for dedicated use-cases (social networks, opinion, 
mobility...) The concrete GE is toolbox for Data and Events mining but you 
cannot keep some dedicated applications in this way in data & context 
management.

My third comment is that we are describing, for this first version, a 
high-level architecture. In this part, we have partners who have described 
their tools without any efforts to adapt vocabulary. I'm really not happy 
to have pushed IoT team to work on a generic architecture with clear 
functionalities (and everybody did the job) and to find partners assets as 
part of the architecture in Data & Context management WP. Some of the 
descriptions are dealing with API and you expect that the Usage Area 
projects with partners which are not ICT oriented, will agree with this 
kind of description?

In the same way, the unique selling points are sometimes dedicated to 
developers directly and not really for the stakeholder as ASP for example.

Regarding more specifically the question marks with IoT, the CEP refers to 
the "Event Processing in Action" a book which is not in the list of 
reference. The approach is too much related to a defined sequence of 
actions which is a static view and does not take into account cross-domain 
activities (which is the baseline of the PPP FI itself) because this 
approach is a silo-approach. You have to know the processes in your silo 
to be able to prepare the right rules. CEP and pub/sub mechanisms are 
fully complementary because pub/sub with no official broker but datamarket 
places will propose the relevant openness to share data through several 
silos. The GE Big Data should be very relevant for that. I don't know if 
people who have described CEP are aware of physical pub/sub routers when 
you don't need a broker. We need this kind of networks for IoT and we 
should replace these real routers by middleware hosted in different places 
and our gateways are one of these places.
Another point is that nothing is explained regarding multi-brokers systems 
and how it is possible to build a whole process through their environments 
and their knowledge of published data.

We can discuss all these issues tomorrow morning but we have also to other 
partners who will provide some comments on this part for Wednesday 
morning.

BR

Thierry

-----Message d'origine-----
De : Juanjo Hierro [mailto:jhierro at tid.es] 
Envoyé : vendredi 8 juillet 2011 14:22
À : NAGELLEN Thierry RD-BIZZ-SOP; Farkas, Lorant (NSN - HU/Budapest)
Cc : jhierro >> "Juan J. Hierro"
Objet : Peer review of the IoT and Data/Context Management chapters

Hi Thierry and Lorant,

   We hadn't contact to sync on how we are planning to orchestrate the 
peer-review of the IoT and Data/Context Management chapters ...

   I can tell you that, on the side of the Data/Context Management 
chapter, we will carry out a peer review of it and provide comments by
Monday EOB as planned.   This peer review will mostly involve other
members of the Data/Context Management WP since I already did my peer 
review as you know :-)

   Regarding review of our chapter by you, I want to let you know in 
advance that we plan to update the section dealing with the description of 
the Publish/Subscribe Broker GE and the Semantic-related GEs ... They 
should be delivered in an update to you by monday, around 11:00am ... so
you may leave review of these sections to the very end ...   When do you
plan to have it ready ?   I believe we can relaxed a bit the milestone
(monday EOB) to be tuesday 12:00pm so that you have the necessary time to 
review the updates on these sections.

   Looking forward your feedback,

-- Juanjo



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



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[attachment "Data and Context 
management-TNA comments-10072011.docx" deleted by Guy Sharon/Haifa/IBM] 
[attachment "jhierro.vcf" deleted by Guy Sharon/Haifa/IBM] 
_______________________________________________
Fiware-data mailing list
Fiware-data at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-data

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110711/8c16cbf9/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-data/attachments/20110711/8c16cbf9/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Data and Context management-TNA comments-10072011_GuyAnswer.doc
Type: application/octet-stream
Size: 3257344 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110711/8c16cbf9/attachment.obj>