Dear All, Detailed agenda proposal for the cross WP5/WP6 meeting, from WP6, including a request for extension of the duration to 4 hours. We tentatively said yes. Thanks & Br, Lorant From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Wednesday, January 11, 2012 4:03 PM To: thierry.nagellen at orange.com Cc: CARLOS RALLI UCENDO; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest); RICARDO DE LAS HERAS MARTIN; jhierro >> "Juan J. Hierro" Subject: Re: Joint IoT - Data/Context Management Chapters meeting during plenary in Madrid On 11/01/12 15:03, thierry.nagellen at orange.com wrote: Der all, As you know we sent our agenda at the beginning of this week and we have a positive answer from I2ND for the cross-WP meeting on Wednesday. On the condition there is a detailed agenda for a 4 hours meeting and that I2ND is willing to shift to early afternoon our cross-WP meeting, we could have this full morning with WP6. Of course, to have a fruitful meeting, we would have a clear architecture description of WP6 issues related to WP5 Internet of Things to be able to prepare the meeting from our side. For the time being, we have planned to exchange on NGSI 9-10 and how can reach a common format. I believe we should be able to cover CEP (Complex Event Processing) as well. What is the role expected in IoT and how it relates with CEP GEs to be developed in the Data/Context Management Chapter. Regarding CEP, first we have to evaluate whether a single CEP implementation would be feasible, which could be instantiated both in centralized data centers of a Cloud-oriented IoT solution as well as in distributed nodes of a IoT network, of if we have to go with two different variants of CEP implementations, one "fully-equipped" from a functional perspective, designed to handle large amount of data and expected to run on centralized servers and another "lite" one suited to run on distributed nodes of the IoT network. If we go for the second case, then we should solve how the different type of CEP implementation instances are going to be federated in a distributed architecture. My proposal would be to devote 2h45m to discuss on NGSI which is the most crucial thing. Then followed by a break of 15m, and then devote 1h to discuss on CEP. Regarding the agenda, about NGSI, I would propose the following agenda: * Presentation on proposed approach about the role of NGSI at the Things/Resource Management Layer (30 mins) * Here I propose to elaborate on the proposal made by Telefonica, integrating the results of the discussions that will take place until the f2f meeting in Madrid (which, nicely, have just started on the mailing list). * I suggest that Telefonica makes this presentation (I have included Ricardo in this email so that he gets aware of the discussion) * Data (Context Elements) format requirements from an IoT perspective (30 mins) * We should make sure that NGSI helps us to deal with the kind of data coming from sensors that is required in the IoT space. The idea of this presentation would be that of making it clear what are the requirements in this respect, that implementations of the NGSI interface have to support * You know better than me who should be assigned to made this presentation also from the IoT team. * Issues with current OMA NGSI specifications (30 mins) * Telecom Italia has expressed their concerns about trying to be "to strict" with respect to going for a full compliance of the OMA NGSI specs as they are today. They argue that there are some gaps but also some aspects that has been better to drop or fix, when trying to deliver a product that works, from a pragmatic point of view. It's time then to learn what these concrete points are, and try to start agreeing what things of the OMA NGSI we will take as they are, and what others we will simply fix it (with the intend to fast-track them as changes in OMA) * Clearly, Telecom Italia may take this slot. Another possibility is that NEC makes a complementary presentation (the two being 40 mins maximum) * Brainstorming discussion. I would suggest booking 45 mins at least * Focused on making progress on agreements and overall view of the Architecture. * Wrap-up of conclusions and next steps: 30 mins. Regarding the agenda about CEP, my first take would be: * CEP in a distributed IoT architecture (20 mins) * I would suggest someone from the IoT team illustrates how CEP could be collocated in distributed nodes and then elaborate on how the different CEPs (running on distributed nodes and the central servers, may be federated). A particular topic I'm interested in is to learn how we are envisioning CEP engines at the distributed nodes be able to coexist with usage of the M2M-ETSI API * You know better than me who should be assigned to made this presentation also from the IoT team. * Detailed view of the CEP GE under development in the Data/Context Management chapter (20 mins) * Self-explanatory * IBM would take care of it * Brainstorming Discussion (20 mins?) * Wrap-up (20 mins?) As you see, even 4 hours may not be enough ... One thing we could do is to split the two topics and discuss then in separate timeslots. The issue there is that I believe that putting them together gives us more flexibility because we can extend the NGSI slot at the price of reducing the one on CEP if that is required (NGSI certainly has to be solved with the highest priority). We will ask I2ND to move our common slot only if we have these 2 elements (agenda and architecture description)the latest by Thursday next week to be able to exchange with all IoT partners involved into the relevant tasks. I agree. That's why, as per the agenda, I have put a first draft on the table ;-) Regarding the architecture, I expect that the discussion over the email may lead to some fruits before the meeting and, as a consequence, there will be something. Feedback is welcome. Best regards, -- Juanjo Best regards Thierry -----Message d'origine----- De : Juanjo Hierro [mailto:jhierro at tid.es] Envoyé : mercredi 11 janvier 2012 12:20 À : NAGELLEN Thierry RD-BIZZ-SOP; Farkas, Lorant (NSN - HU/Budapest) Cc : CARLOS RALLI UCENDO; jhierro >> "Juan J. Hierro" Objet : Joint IoT - Data/Context Management Chapters meeting during plenary in Madrid Hi Thierry and Lorant, We have to book a joint IoT-Data meeting during the week in Madrid. I would suggest to spend the whole morning one of these days ... we definitively have to settle down how the Reference Architecture in IoT will be capable to integrate with the Data Reference Architecture in the Data/Context Management chapter and how we can agree on a single approach for implementing the Publish/Subscribe GE. I believe that we agreed on Wednesday morning. I suggest to book the whole Wednesday morning. Please confirm. I copy Carlos Ralli, who has been appointed leader of the Data/Context Management Chapter (I was performing as "acting" until he could join the project) Looking forward your response, -- ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120111/808e074d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy