From sergg at tid.es Mon Mar 4 10:36:51 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 04 Mar 2013 09:36:51 +0000 Subject: [Fiware-data] FW: [Fiware-wpl] Backlog - Sprint transition: from S2.2.2-M22 to S2.2.3-M23 In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B551EBE01@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B551EBE01@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D527304F8@EX10-MB2-MAD.hi.inet> Dear partners, The backlog deliverable has been submitted and the sprint 2.2.2 is over. It's time to update the backlog. Please, spend a while defining what's going to be done in this sprint and closing the finished items. As you may know, Manuel Escriche is now managing the scrum process in Fiware. Please have a look at his email below. Best Regards, Sergio From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Friday, March 01, 2013 1:12 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Backlog - Sprint transition: from S2.2.2-M22 to S2.2.3-M23 Dear Partners, As you know yesterday we finished Sprint 2.2.2 corresponding to M22, today we start activities belonging to Sprint 2.2.3 corresponding to M23. Please, update your backlog accordingly. 1. Close the tickets you finished along M22 (probably you already did these days when updating the tickets), otherwise, do it 2. Update tickets under execution to belong to Sprint 2.2.3-M23 During next week we should be able to identify and refine all content meant to be done during Sprint S2.2.3-M23. Next week I'll contact you to understand how your backlog for S2.2.3 is defined. During these months we'll improve the tools with a dashboard giving us visual views on how our backlog is evolving during sprints and realeases... for the different enablers, partners, etc. As soon as I can I'll share the consistency rules to be applied to the backlog, so that we all have unanimous understanding and consensus. If anything, please, don't hesitate to let me know. Have a nice weekend!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From mcp at tid.es Tue Mar 5 15:27:04 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 05 Mar 2013 15:27:04 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpa] Monitoring of log/trace files In-Reply-To: <5135FE2D.3090809@eng.it> References: <5135FE2D.3090809@eng.it> Message-ID: <513600B8.6080905@tid.es> Dear all, On behalf of Sergio's I would like to resend this to you. Can each one of the GE owners in the chapter send an example of the log files and/or traces to MARCEL at il.ibm.com and put me in CC? Please do not forget to state the name of your GE when you send this. Thanks a lot Miguel -------- Mensaje original -------- Asunto: [Fiware-wpa] Monitoring of log/trace files Fecha: Tue, 5 Mar 2013 15:16:13 +0100 De: Davide Dalle Carbonare Para: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear partners, I'd like to remind you one point we've on the minutes: "Monitoring of log/trace files" https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy @Juanjo, can you kindly send a feedback on what's your take on the purpose and technology points reported on the minutes? @WPAs, can you kindly forward to your GEi providers the request to send an example of log/trace files produced by their GE implementations? Please send the logs to Marcel Zalmanovici and to the WPA mailing list. I'm expecting to receive one example per GEi that will be available for release 2. Kind Regards, Davide ________________________________ 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: -------------- next part -------------- _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa From ralli at tid.es Wed Mar 6 15:07:06 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 06 Mar 2013 14:07:06 +0000 Subject: [Fiware-data] Two very important tasks & Conf Call Tomorrow at 10:30 Message-ID: <1971FF81B8E01C45991F6F92B9E3B250551CDCD0@EX10-MB2-MAD.hi.inet> Dear Colleagues, As discussed in our last week conf call, this friday March 8th (11AM CET) is the absolute deadline to make your "GE's Architecture in the Wiki" completely updated. Wiki Architecture contents should match the components, interfaces APIs, etc. that you are actually delivering in Release 2 implementations. After Friday 11AM, we will generate a consolidated document with those inputs, that we will provide to the IoT chapter for the first peer-review. At this point, we don?t care if you made those updates on the public or in the private Wiki, we just need to know where exactly you are/were making them. I have created a list of GEs so you can provide the exact URL of your updated architecture. It's in the googledoc (Item 1) to be used tomorrow for our conf.call: https://docs.google.com/document/d/1pOhGvRK9y-G9o96lxd-UOH_cTGoUg9yghcqQ6ufvZUc/edit Please, go ahead and provide the URL before the call in order to confirm contents will be ready on Friday 8th, 11h. Besides the URLs, it would be nice to have a few words or bullet points with the main updates (compared to R1/previous architecture). Another task that I think we should take care about is the "GE's logging report to Engineering" described in the Googledoc Item 2. Please, if you are not attending tomorrow, it is extremely important that you complete the above linked googledoc before our conf call tomorrow at 10:30. Thanks a lot for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Thu Mar 7 19:36:07 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Thu, 7 Mar 2013 18:36:07 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <0CF527EE434D2E4BB398B0F67FB0A8983251D645E9@xchg.mertree.mer.co.il> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51225111.9020909@tid.es> <22008_1361205852_51225A5B_22008_2771_1_f029539d-a2cf-45d7-b776-6e10a2bf550f@PEXCVZYH02.corporate.adroot.infra.ftgroup> <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.corporate.adroot.infra.ftgroup> <51236BA9.5090402@tid.es> <4540_1361552643_5127A502_4540_2802_1_06a89940-165f-4451-a6f1-fc91c06912b2@PEXCVZYH01.corporate.adroot.infra.ftgroup> <0CF527EE434D2E4BB398B0F67FB0A8983251D645E9@xchg.mertree.mer.co.il> Message-ID: <15359_1362681371_5138DE1A_15359_4822_1_7366e744-3d4d-492b-8fd0-a2969ac2164a@PEXCVZYH02.corporate.adroot.infra.ftgroup> Thank you for your feedback Peretz, Even the part of the code of the event sources that the CEP GET events from and the part of the code of the application the CEP POST alerts to, would be useful (1,2). The CET WEB UI seems to be easy to use (3). Anyway, once we?ve that part of the code up and running on our side (it will be in java using the Jersey library), we will be happy to share it ? Best regards, Fano De : Peretz Gurel [mailto:peretz at athenaiss.com] Envoy? : dimanche 24 f?vrier 2013 17:43 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Objet : RE: [Fiware-data] CEP<->P/S Hi Fano, In SafeCity we use the CEP engine without any additional code. No input or output format conversions are needed. We did not have to add any additional code "around" the CEP. The applications that feed the CEP, and those that are fed by the CEP, all agreed to send and receive messages according to the format enforced by the CEP, so no additional code is required to convert incoming/outgoing messages. 1. The CEP GET (REST API) the events from the event sources. Each and every event is generated by the source application as a text in a flat JSON format in the exact format that the CEP expects, so no conversions are needed. 2. After processing of the events by the CEP, it generates alerts and POST them at the target application. 3. The definition of the input events and the output alerts, as well as the processing rules of the CEP, is done solely by using the native CET WEB UI, without any additional code. Best regards, Peretz From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Friday, February 22, 2013 7:02 PM To: Peretz Gurel Cc: fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S Hi Peretz and all, Is there an easy way for us to benefit from your experience in Safecity, using the CEP. I?m thinking about a detailed spec of your architecture and source code of the component that connect to the CEP for feeding it with input events, and of the component that the CEP connects to for sending output events. This echoes a mail I just sent to the FI PPP AB for setting up such reusable stuff, and share experience within UC projects with the intent to improve the efficiency of using FIWARE GE enablers. Thank you for your suggestion Guy, Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Guy Sharon Envoy? : mardi 19 f?vrier 2013 13:22 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Another option is to look at SafeCity - they are already producing sensor data and turning it to events and then use events to drive decisions. Regards, Guy Sharon Manager, Event-based Decision Technologies Group IBM Research - Haifa ________________________________ Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: [LinkedIn: http://www.linkedin.com/profile/view?id=3618230&authType=name&authToken=7XaO&locale=en_US&pvs=pp&trk=ppro_viewmore] and within IBM on: [Lotus Connections: https://w3-connections.ibm.com/profiles/html/profileView.do?key=c22fdae3-0bc2-4626-a30b-095a0eb63ec8&lang=en] [Cattail: http://cattail.boulder.ibm.com/cattail/#view=guysh at il.ibm.com] [IBM] Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Ferm?n Gal?n M?rquez > To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 14:10 Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi, I have tried to summarize the conclusions of the discussion up to now and put them in a shared google doc that we can use from on to add more conclusions that could arise. https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit In the document, I have tried to show concrete examples of the involved messages, base on my knowledge of NGSI and the feedback that Tali has provided. It would be great Tali if you could review that last part, to check if everything is ok from CEP point of view or fix otherwise (please tell me your google id to provide writing permission in the document, if you like). As I think somebody has already mentioned, we need to know which kind of entities, attributes and CEP processings Outmart needs (note that in the document I have used a "dummy" example). Who should provide that information? Of course, everybody is welcome to read the document and provide feedback. Comments are open to everybody, so you can use that to provide your feedback in specify parts of the documents. Best regards, ------ Ferm?n El 19/02/2013 12:27, Tali Yatzkar-Haham escribi?: Hi Fano and all, In the CEP, the application developer defines the CEP input and output events types as part of the application definition that contains events, rules, producer, consumer,... This is usually done through the CEP Web UI. Each event type has a name and a set of attributes, where each attribute has a type and a name. The definition of the event types will not be done using the CEP <-> P/S adapter. At run time, the CEP expect to get only events instances from defined event type. The CEP expects to get it in a flat JSON format of key value pairs. The name (type) of the event is given in an attribute called "Name" Example(you can find them in the wiki): 1. TrafficReport input event with only one attribute called volume: {"Name":"TrafficReport", "volume":"1000"} 2. TrafficReport output event with one attribute called volume and several auto-generated CEP attributes {"Cost":"0.0","Certainty":"0.0","Name":"TrafficReport","EventSource":"","Duration":"0.0","Annotation":"", "volume":"1000","EventId":"e206b5e8-9f3a-4711-9f46-d0e9431fe215","DetectionTime":"1350311378034"} Note that all the attributes are given as Strings (the CEP parses them internally according to the attributes defined type), the attributes are not ordered. Please tell me if you have any questions about the event format. Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL, Cc: "fiware-data at lists.fi-ware.eu" Date: 19/02/2013 12:32 PM Subject: RE: [Fiware-data] CEP<->P/S ________________________________ Hi Tali, You?ll find attached a queryContextResponse xml document to give you an idea. Although in our case we need the document contained in a notifyContext message. I?ve got a message from the ngsi mailinglist with a link to such NGSI messages samples, but unfortunately and can?t find it right now? Regards, Fano De : Tali Yatzkar-Haham [mailto:TALI at il.ibm.com] Envoy? : mardi 19 f?vrier 2013 08:12 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fano, and all, Yes, as I wrote in my previous mail - the CEP can activate external REST API for sending CEP output events (In my previous mail, I point to the documentation of it). Maybe you can send us an example of an P/S event and we can see how to transform it to CEP event. If you also know what is the event data you expect the CEP to generate, we can then transform it back to P/S event. Do you have such an example? Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: fano.ramparany at orange.com To: Ferm?n Gal?n M?rquez >, Cc: BELLABAS Alia OLNC/OLPS >, "fiware-data at lists.fi-ware.eu" > Date: 18/02/2013 06:44 PM Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi Fermin and all, My feedback inline? De : Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Objet : Re: [Fiware-data] CEP<->P/S ? So, if I'm understanding correctly, we need two adaptation steps: 1. PubSub -> (Adaptator1) -> CEP. In this case, the best approach would be to subscribe Adaptator1 to notifications of Outsmart data/context events in PubSub, so when a new event is received from OutSmart IoT, then PubSub will send a NGSI10 notifyContext to Adaptator.1 Then, Adaptator1 will transform this NGSI to a REST request according to the CEP "Sending Events" API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Sending_Events_API. [FR] This seems to me the right thing to do. The content of the notifyContext message and how it should be transformed into CEP event description has to be elaborated though. 2. CEP -> (Adaptator2) -> PubSub. In this case, I understand that the CEP is not capable of pro-actively send data/context events (please, tell me if I'm wrong), so Adaptator2 will need to periodically poll CEP using the CEP "Getting events"API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Getting_Events_API, sending NGSI10 updateContext to PubSub when a new event (or change) is detected. [FR] As far as I understand, Tali can correct me if I?m wrong, CEP can pro-actively create event and there?s a CEP API for being notified of new events (based itself on a polling mechanism which is transparent to the component using this API, except for setting up the polling frequency). This simplifies your design which for the rest I agree with. (Adaptator1 and Adaptator2 are logical entities; of course they can be implemented by the same piece of software). Is my interpretation correct? If it is right, I would suggest as next step to write "reference messages" for the four cases (notifyContext, "Sending events", "Gettings events" and updateContext). Best regards, ------ Ferm?n El 18/02/2013 16:11, fano.ramparany at orange.com escribi?: Dear all, Determining the respective roles of the CEP and P/S in the overall architecture is very important and will dictate what additional components need to be implemented. In the discussion so far, it is considered that P/S is an event source that feeds the CEP with events, which I think is fine. I think that conversely the CEP should be a context provider for the P/S. Because if an application would like a pattern of events to be detected such as in the case of OUTSMART UC ?a street lamp is not switched on whereas it is dusk?, it should subscribe to the P/S. The simplest scenario I foresee is that the CEP create an event which corresponds to this situation (this pattern of events) as soon as is occurrs and push it towards the P/S. The application would then be notified, provided that it has subscribed to this event. More generally, could we draw the overall architecture depicting the GEs and the dataflow they exchange? It will then be clearer for UC projects, how they can use the GE involved. Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Moltchanov Boris Envoy? : vendredi 15 f?vrier 2013 07:18 ? : fermin at tid.es; fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S yes, P/S NGSI. BR, B ?????????? ? Samsung Mobile Ferm?n Gal?n M?rquez ???????: Dear Boris, I have two doubts regarding this topic: * Is the interface exposed by CEP documented in some place (e.g. URL in the FIWARE wiki)? * I understand you are considering NGSI as the interface exposed by P/S, right? Thanks! Best regards, ------ Ferm?n El 14/02/2013 17:57, Moltchanov Boris escribi?: Dear All, The conclusion after our AC would be that, as WP6, we need an intermediate component (converter, middleware, platform) performing the following functions between the CEP and P/S GEs: - Subscribe the P/S only for needed data/scope/entityIDs. - Enrich events containing the data, becoming the context, with entityIDs and scopes taken from events attribute; - Parse the context, becoming the events, and build the events integrating into the event structure the entityID and scopes as the attributes for feeding the CEP with the event coming from context P/S flow; - Converting JSON2XML and vice versa XML2JSON. This piece could be used also for other components , GEs, etc. in FI-WARE and UCPs. Then, given the application (UCP or generically application domain) the P/S will be subscribed only to that context, which is relevant for the event generation for that UCP, or generally speaking application domain, by the CEP. Best Regards, Boris Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. [attachment "queryContextResponse-VehicleLocation0.xml" deleted by Tali Yatzkar-Haham/Haifa/IBM] _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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_______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 518 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 467 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 494 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 360 bytes Desc: image004.gif URL: From peretz at athenaiss.com Fri Mar 8 15:45:22 2013 From: peretz at athenaiss.com (Peretz Gurel) Date: Fri, 8 Mar 2013 16:45:22 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <15359_1362681371_5138DE1A_15359_4822_1_7366e744-3d4d-492b-8fd0-a2969ac2164a@PEXCVZYH02.corporate.adroot.infra.ftgroup> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51225111.9020909@tid.es> <22008_1361205852_51225A5B_22008_2771_1_f029539d-a2cf-45d7-b776-6e10a2bf550f@PEXCVZYH02.corporate.adroot.infra.ftgroup> <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.corporate.adroot.infra.ftgroup> <51236BA9.5090402@tid.es> <4540_1361552643_5127A502_4540_2802_1_06a89940-165f-4451-a6f1-fc91c06912b2@PEXCVZYH01.corporate.adroot.infra.ftgroup> <0CF527EE434D2E4BB398B0F67FB0A8983251D645E9@xchg.mertree.mer.co.il> <15359_1362681371_5138DE1A_15359_4822_1_7366e744-3d4d-492b-8fd0-a2969ac2164a@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: <0CF527EE434D2E4BB398B0F67FB0A89832530797AB@xchg.mertree.mer.co.il> Dear Fano, The CEP GE does not require any code for the GET and POST operations. In the WEB UI of the CEP GE there is a place to write the URL for the GET operations and the URL for the POST operations. Best regards, Peretz From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Thursday, March 07, 2013 8:36 PM To: Peretz Gurel Cc: fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S Thank you for your feedback Peretz, Even the part of the code of the event sources that the CEP GET events from and the part of the code of the application the CEP POST alerts to, would be useful (1,2). The CET WEB UI seems to be easy to use (3). Anyway, once we?ve that part of the code up and running on our side (it will be in java using the Jersey library), we will be happy to share it ? Best regards, Fano De : Peretz Gurel [mailto:peretz at athenaiss.com] Envoy? : dimanche 24 f?vrier 2013 17:43 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Objet : RE: [Fiware-data] CEP<->P/S Hi Fano, In SafeCity we use the CEP engine without any additional code. No input or output format conversions are needed. We did not have to add any additional code "around" the CEP. The applications that feed the CEP, and those that are fed by the CEP, all agreed to send and receive messages according to the format enforced by the CEP, so no additional code is required to convert incoming/outgoing messages. 1. The CEP GET (REST API) the events from the event sources. Each and every event is generated by the source application as a text in a flat JSON format in the exact format that the CEP expects, so no conversions are needed. 2. After processing of the events by the CEP, it generates alerts and POST them at the target application. 3. The definition of the input events and the output alerts, as well as the processing rules of the CEP, is done solely by using the native CET WEB UI, without any additional code. Best regards, Peretz From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Friday, February 22, 2013 7:02 PM To: Peretz Gurel Cc: fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S Hi Peretz and all, Is there an easy way for us to benefit from your experience in Safecity, using the CEP. I?m thinking about a detailed spec of your architecture and source code of the component that connect to the CEP for feeding it with input events, and of the component that the CEP connects to for sending output events. This echoes a mail I just sent to the FI PPP AB for setting up such reusable stuff, and share experience within UC projects with the intent to improve the efficiency of using FIWARE GE enablers. Thank you for your suggestion Guy, Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Guy Sharon Envoy? : mardi 19 f?vrier 2013 13:22 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Another option is to look at SafeCity - they are already producing sensor data and turning it to events and then use events to drive decisions. Regards, Guy Sharon Manager, Event-based Decision Technologies Group IBM Research - Haifa ________________________________ Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: [cid:image001.jpg at 01CE1C1C.532C3070] and within IBM on: [cid:image002.jpg at 01CE1C1C.532C3070] [cid:image003.jpg at 01CE1C1C.532C3070] [cid:image004.gif at 01CE1C1C.532C3070] Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Ferm?n Gal?n M?rquez > To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 14:10 Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi, I have tried to summarize the conclusions of the discussion up to now and put them in a shared google doc that we can use from on to add more conclusions that could arise. https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit In the document, I have tried to show concrete examples of the involved messages, base on my knowledge of NGSI and the feedback that Tali has provided. It would be great Tali if you could review that last part, to check if everything is ok from CEP point of view or fix otherwise (please tell me your google id to provide writing permission in the document, if you like). As I think somebody has already mentioned, we need to know which kind of entities, attributes and CEP processings Outmart needs (note that in the document I have used a "dummy" example). Who should provide that information? Of course, everybody is welcome to read the document and provide feedback. Comments are open to everybody, so you can use that to provide your feedback in specify parts of the documents. Best regards, ------ Ferm?n El 19/02/2013 12:27, Tali Yatzkar-Haham escribi?: Hi Fano and all, In the CEP, the application developer defines the CEP input and output events types as part of the application definition that contains events, rules, producer, consumer,... This is usually done through the CEP Web UI. Each event type has a name and a set of attributes, where each attribute has a type and a name. The definition of the event types will not be done using the CEP <-> P/S adapter. At run time, the CEP expect to get only events instances from defined event type. The CEP expects to get it in a flat JSON format of key value pairs. The name (type) of the event is given in an attribute called "Name" Example(you can find them in the wiki): 1. TrafficReport input event with only one attribute called volume: {"Name":"TrafficReport", "volume":"1000"} 2. TrafficReport output event with one attribute called volume and several auto-generated CEP attributes {"Cost":"0.0","Certainty":"0.0","Name":"TrafficReport","EventSource":"","Duration":"0.0","Annotation":"", "volume":"1000","EventId":"e206b5e8-9f3a-4711-9f46-d0e9431fe215","DetectionTime":"1350311378034"} Note that all the attributes are given as Strings (the CEP parses them internally according to the attributes defined type), the attributes are not ordered. Please tell me if you have any questions about the event format. Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL, Cc: "fiware-data at lists.fi-ware.eu" Date: 19/02/2013 12:32 PM Subject: RE: [Fiware-data] CEP<->P/S ________________________________ Hi Tali, You?ll find attached a queryContextResponse xml document to give you an idea. Although in our case we need the document contained in a notifyContext message. I?ve got a message from the ngsi mailinglist with a link to such NGSI messages samples, but unfortunately and can?t find it right now? Regards, Fano De : Tali Yatzkar-Haham [mailto:TALI at il.ibm.com] Envoy? : mardi 19 f?vrier 2013 08:12 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fano, and all, Yes, as I wrote in my previous mail - the CEP can activate external REST API for sending CEP output events (In my previous mail, I point to the documentation of it). Maybe you can send us an example of an P/S event and we can see how to transform it to CEP event. If you also know what is the event data you expect the CEP to generate, we can then transform it back to P/S event. Do you have such an example? Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: fano.ramparany at orange.com To: Ferm?n Gal?n M?rquez >, Cc: BELLABAS Alia OLNC/OLPS >, "fiware-data at lists.fi-ware.eu" > Date: 18/02/2013 06:44 PM Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi Fermin and all, My feedback inline? De : Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Objet : Re: [Fiware-data] CEP<->P/S ? So, if I'm understanding correctly, we need two adaptation steps: 1. PubSub -> (Adaptator1) -> CEP. In this case, the best approach would be to subscribe Adaptator1 to notifications of Outsmart data/context events in PubSub, so when a new event is received from OutSmart IoT, then PubSub will send a NGSI10 notifyContext to Adaptator.1 Then, Adaptator1 will transform this NGSI to a REST request according to the CEP "Sending Events" API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Sending_Events_API. [FR] This seems to me the right thing to do. The content of the notifyContext message and how it should be transformed into CEP event description has to be elaborated though. 2. CEP -> (Adaptator2) -> PubSub. In this case, I understand that the CEP is not capable of pro-actively send data/context events (please, tell me if I'm wrong), so Adaptator2 will need to periodically poll CEP using the CEP "Getting events"API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Getting_Events_API, sending NGSI10 updateContext to PubSub when a new event (or change) is detected. [FR] As far as I understand, Tali can correct me if I?m wrong, CEP can pro-actively create event and there?s a CEP API for being notified of new events (based itself on a polling mechanism which is transparent to the component using this API, except for setting up the polling frequency). This simplifies your design which for the rest I agree with. (Adaptator1 and Adaptator2 are logical entities; of course they can be implemented by the same piece of software). Is my interpretation correct? If it is right, I would suggest as next step to write "reference messages" for the four cases (notifyContext, "Sending events", "Gettings events" and updateContext). Best regards, ------ Ferm?n El 18/02/2013 16:11, fano.ramparany at orange.com escribi?: Dear all, Determining the respective roles of the CEP and P/S in the overall architecture is very important and will dictate what additional components need to be implemented. In the discussion so far, it is considered that P/S is an event source that feeds the CEP with events, which I think is fine. I think that conversely the CEP should be a context provider for the P/S. Because if an application would like a pattern of events to be detected such as in the case of OUTSMART UC ?a street lamp is not switched on whereas it is dusk?, it should subscribe to the P/S. The simplest scenario I foresee is that the CEP create an event which corresponds to this situation (this pattern of events) as soon as is occurrs and push it towards the P/S. The application would then be notified, provided that it has subscribed to this event. More generally, could we draw the overall architecture depicting the GEs and the dataflow they exchange? It will then be clearer for UC projects, how they can use the GE involved. Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Moltchanov Boris Envoy? : vendredi 15 f?vrier 2013 07:18 ? : fermin at tid.es; fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S yes, P/S NGSI. BR, B ?????????? ? Samsung Mobile Ferm?n Gal?n M?rquez ???????: Dear Boris, I have two doubts regarding this topic: * Is the interface exposed by CEP documented in some place (e.g. URL in the FIWARE wiki)? * I understand you are considering NGSI as the interface exposed by P/S, right? Thanks! Best regards, ------ Ferm?n El 14/02/2013 17:57, Moltchanov Boris escribi?: Dear All, The conclusion after our AC would be that, as WP6, we need an intermediate component (converter, middleware, platform) performing the following functions between the CEP and P/S GEs: - Subscribe the P/S only for needed data/scope/entityIDs. - Enrich events containing the data, becoming the context, with entityIDs and scopes taken from events attribute; - Parse the context, becoming the events, and build the events integrating into the event structure the entityID and scopes as the attributes for feeding the CEP with the event coming from context P/S flow; - Converting JSON2XML and vice versa XML2JSON. This piece could be used also for other components , GEs, etc. in FI-WARE and UCPs. Then, given the application (UCP or generically application domain) the P/S will be subscribed only to that context, which is relevant for the event generation for that UCP, or generally speaking application domain, by the CEP. Best Regards, Boris Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. [attachment "queryContextResponse-VehicleLocation0.xml" deleted by Tali Yatzkar-Haham/Haifa/IBM] _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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_______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 518 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 467 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 494 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 360 bytes Desc: image004.gif URL: From boris.moltchanov at telecomitalia.it Fri Mar 8 18:27:32 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 8 Mar 2013 18:27:32 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <0CF527EE434D2E4BB398B0F67FB0A89832530797AB@xchg.mertree.mer.co.il> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51225111.9020909@tid.es> <22008_1361205852_51225A5B_22008_2771_1_f029539d-a2cf-45d7-b776-6e10a2bf550f@PEXCVZYH02.corporate.adroot.infra.ftgroup> <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.corporate.adroot.infra.ftgroup> <51236BA9.5090402@tid.es> <4540_1361552643_5127A502_4540_2802_1_06a89940-165f-4451-a6f1-fc91c06912b2@PEXCVZYH01.corporate.adroot.infra.ftgroup> <0CF527EE434D2E4BB398B0F67FB0A8983251D645E9@xchg.mertree.mer.co.il> <15359_1362681371_5138DE1A_15359_4822_1_7366e744-3d4d-492b-8fd0-a2969ac2164a@PEXCVZYH02.corporate.adroot.infra.ftgroup> <0CF527EE434D2E4BB398B0F67FB0A89832530797AB@xchg.mertree.mer.co.il> Message-ID: Dear Peretz. Sorry for intermixing, I?m here just to support the request from Fano, and explaining better why we?re interested in CEP/SafeCity interaction. We?re thinking that a standard NGSI interface for any type of context, data and event is possible, therefore we?re trying to assess and understand how Pub/Sub GE, including also semantic module could be integrated with the CEP. And of course the easiest way is to learn from someone or even reuse the code who already did it, so SafeCity. In exchange it will give to the SafeCity the access to any other types of data through the same component (Pub/Sub) and interface (NGSI) including at least events and context. Thus SafeCity may have also the native access to the IoT world (sensors and actuators) through the same FI-WARE NGSI on Pub/Sub GE. I don?t know whether you may share with us your development experience in this integration and maybe code? Thank you in advance. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Peretz Gurel Sent: Friday, March 08, 2013 3:45 PM To: fano.ramparany at orange.com Cc: BELLABAS Alia OLNC/OLPS; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] CEP<->P/S Dear Fano, The CEP GE does not require any code for the GET and POST operations. In the WEB UI of the CEP GE there is a place to write the URL for the GET operations and the URL for the POST operations. Best regards, Peretz From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Thursday, March 07, 2013 8:36 PM To: Peretz Gurel Cc: fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S Thank you for your feedback Peretz, Even the part of the code of the event sources that the CEP GET events from and the part of the code of the application the CEP POST alerts to, would be useful (1,2). The CET WEB UI seems to be easy to use (3). Anyway, once we?ve that part of the code up and running on our side (it will be in java using the Jersey library), we will be happy to share it ? Best regards, Fano De : Peretz Gurel [mailto:peretz at athenaiss.com] Envoy? : dimanche 24 f?vrier 2013 17:43 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Objet : RE: [Fiware-data] CEP<->P/S Hi Fano, In SafeCity we use the CEP engine without any additional code. No input or output format conversions are needed. We did not have to add any additional code "around" the CEP. The applications that feed the CEP, and those that are fed by the CEP, all agreed to send and receive messages according to the format enforced by the CEP, so no additional code is required to convert incoming/outgoing messages. 1. The CEP GET (REST API) the events from the event sources. Each and every event is generated by the source application as a text in a flat JSON format in the exact format that the CEP expects, so no conversions are needed. 2. After processing of the events by the CEP, it generates alerts and POST them at the target application. 3. The definition of the input events and the output alerts, as well as the processing rules of the CEP, is done solely by using the native CET WEB UI, without any additional code. Best regards, Peretz From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Friday, February 22, 2013 7:02 PM To: Peretz Gurel Cc: fiware-data at lists.fi-ware.eu; Guy Sharon; Ferm?n Gal?n M?rquez; BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S Hi Peretz and all, Is there an easy way for us to benefit from your experience in Safecity, using the CEP. I?m thinking about a detailed spec of your architecture and source code of the component that connect to the CEP for feeding it with input events, and of the component that the CEP connects to for sending output events. This echoes a mail I just sent to the FI PPP AB for setting up such reusable stuff, and share experience within UC projects with the intent to improve the efficiency of using FIWARE GE enablers. Thank you for your suggestion Guy, Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Guy Sharon Envoy? : mardi 19 f?vrier 2013 13:22 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Another option is to look at SafeCity - they are already producing sensor data and turning it to events and then use events to drive decisions. Regards, Guy Sharon Manager, Event-based Decision Technologies Group IBM Research - Haifa ________________________________ Phone: 972-4-8296587 | Mobile: 972-54-6976417 E-mail: GUYSH at il.ibm.com Website: www.research.ibm.com/haifa/dept/services/soms_ebs.html Find me on: [cid:image001.jpg at 01CE1C2A.98E483C0] and within IBM on: [cid:image002.jpg at 01CE1C2A.98E483C0] [cid:image003.jpg at 01CE1C2A.98E483C0] [cid:image004.gif at 01CE1C2A.98E483C0] Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Ferm?n Gal?n M?rquez > To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 14:10 Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi, I have tried to summarize the conclusions of the discussion up to now and put them in a shared google doc that we can use from on to add more conclusions that could arise. https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit In the document, I have tried to show concrete examples of the involved messages, base on my knowledge of NGSI and the feedback that Tali has provided. It would be great Tali if you could review that last part, to check if everything is ok from CEP point of view or fix otherwise (please tell me your google id to provide writing permission in the document, if you like). As I think somebody has already mentioned, we need to know which kind of entities, attributes and CEP processings Outmart needs (note that in the document I have used a "dummy" example). Who should provide that information? Of course, everybody is welcome to read the document and provide feedback. Comments are open to everybody, so you can use that to provide your feedback in specify parts of the documents. Best regards, ------ Ferm?n El 19/02/2013 12:27, Tali Yatzkar-Haham escribi?: Hi Fano and all, In the CEP, the application developer defines the CEP input and output events types as part of the application definition that contains events, rules, producer, consumer,... This is usually done through the CEP Web UI. Each event type has a name and a set of attributes, where each attribute has a type and a name. The definition of the event types will not be done using the CEP <-> P/S adapter. At run time, the CEP expect to get only events instances from defined event type. The CEP expects to get it in a flat JSON format of key value pairs. The name (type) of the event is given in an attribute called "Name" Example(you can find them in the wiki): 1. TrafficReport input event with only one attribute called volume: {"Name":"TrafficReport", "volume":"1000"} 2. TrafficReport output event with one attribute called volume and several auto-generated CEP attributes {"Cost":"0.0","Certainty":"0.0","Name":"TrafficReport","EventSource":"","Duration":"0.0","Annotation":"", "volume":"1000","EventId":"e206b5e8-9f3a-4711-9f46-d0e9431fe215","DetectionTime":"1350311378034"} Note that all the attributes are given as Strings (the CEP parses them internally according to the attributes defined type), the attributes are not ordered. Please tell me if you have any questions about the event format. Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: To: Tali Yatzkar-Haham/Haifa/IBM at IBMIL, Cc: "fiware-data at lists.fi-ware.eu" Date: 19/02/2013 12:32 PM Subject: RE: [Fiware-data] CEP<->P/S ________________________________ Hi Tali, You?ll find attached a queryContextResponse xml document to give you an idea. Although in our case we need the document contained in a notifyContext message. I?ve got a message from the ngsi mailinglist with a link to such NGSI messages samples, but unfortunately and can?t find it right now? Regards, Fano De : Tali Yatzkar-Haham [mailto:TALI at il.ibm.com] Envoy? : mardi 19 f?vrier 2013 08:12 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fano, and all, Yes, as I wrote in my previous mail - the CEP can activate external REST API for sending CEP output events (In my previous mail, I point to the documentation of it). Maybe you can send us an example of an P/S event and we can see how to transform it to CEP event. If you also know what is the event data you expect the CEP to generate, we can then transform it back to P/S event. Do you have such an example? Regards, Tali Yatzkar-Haham Event-based Middleware & Solutions Group IBM Haifa Research Lab ________________________________ Phone: 972-4-829-6320 | Mobile: 972-54-4388482 E-mail: TALI at il.ibm.com Haifa University, Mount Carmel Haifa, 31905 Israel From: fano.ramparany at orange.com To: Ferm?n Gal?n M?rquez >, Cc: BELLABAS Alia OLNC/OLPS >, "fiware-data at lists.fi-ware.eu" > Date: 18/02/2013 06:44 PM Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu ________________________________ Hi Fermin and all, My feedback inline? De : Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Objet : Re: [Fiware-data] CEP<->P/S ? So, if I'm understanding correctly, we need two adaptation steps: 1. PubSub -> (Adaptator1) -> CEP. In this case, the best approach would be to subscribe Adaptator1 to notifications of Outsmart data/context events in PubSub, so when a new event is received from OutSmart IoT, then PubSub will send a NGSI10 notifyContext to Adaptator.1 Then, Adaptator1 will transform this NGSI to a REST request according to the CEP "Sending Events" API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Sending_Events_API. [FR] This seems to me the right thing to do. The content of the notifyContext message and how it should be transformed into CEP event description has to be elaborated though. 2. CEP -> (Adaptator2) -> PubSub. In this case, I understand that the CEP is not capable of pro-actively send data/context events (please, tell me if I'm wrong), so Adaptator2 will need to periodically poll CEP using the CEP "Getting events"API described at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Getting_Events_API, sending NGSI10 updateContext to PubSub when a new event (or change) is detected. [FR] As far as I understand, Tali can correct me if I?m wrong, CEP can pro-actively create event and there?s a CEP API for being notified of new events (based itself on a polling mechanism which is transparent to the component using this API, except for setting up the polling frequency). This simplifies your design which for the rest I agree with. (Adaptator1 and Adaptator2 are logical entities; of course they can be implemented by the same piece of software). Is my interpretation correct? If it is right, I would suggest as next step to write "reference messages" for the four cases (notifyContext, "Sending events", "Gettings events" and updateContext). Best regards, ------ Ferm?n El 18/02/2013 16:11, fano.ramparany at orange.com escribi?: Dear all, Determining the respective roles of the CEP and P/S in the overall architecture is very important and will dictate what additional components need to be implemented. In the discussion so far, it is considered that P/S is an event source that feeds the CEP with events, which I think is fine. I think that conversely the CEP should be a context provider for the P/S. Because if an application would like a pattern of events to be detected such as in the case of OUTSMART UC ?a street lamp is not switched on whereas it is dusk?, it should subscribe to the P/S. The simplest scenario I foresee is that the CEP create an event which corresponds to this situation (this pattern of events) as soon as is occurrs and push it towards the P/S. The application would then be notified, provided that it has subscribed to this event. More generally, could we draw the overall architecture depicting the GEs and the dataflow they exchange? It will then be clearer for UC projects, how they can use the GE involved. Best regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Moltchanov Boris Envoy? : vendredi 15 f?vrier 2013 07:18 ? : fermin at tid.es; fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S yes, P/S NGSI. BR, B ?????????? ? Samsung Mobile Ferm?n Gal?n M?rquez ???????: Dear Boris, I have two doubts regarding this topic: * Is the interface exposed by CEP documented in some place (e.g. URL in the FIWARE wiki)? * I understand you are considering NGSI as the interface exposed by P/S, right? Thanks! Best regards, ------ Ferm?n El 14/02/2013 17:57, Moltchanov Boris escribi?: Dear All, The conclusion after our AC would be that, as WP6, we need an intermediate component (converter, middleware, platform) performing the following functions between the CEP and P/S GEs: - Subscribe the P/S only for needed data/scope/entityIDs. - Enrich events containing the data, becoming the context, with entityIDs and scopes taken from events attribute; - Parse the context, becoming the events, and build the events integrating into the event structure the entityID and scopes as the attributes for feeding the CEP with the event coming from context P/S flow; - Converting JSON2XML and vice versa XML2JSON. This piece could be used also for other components , GEs, etc. in FI-WARE and UCPs. Then, given the application (UCP or generically application domain) the P/S will be subscribed only to that context, which is relevant for the event generation for that UCP, or generally speaking application domain, by the CEP. Best Regards, Boris Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. [attachment "queryContextResponse-VehicleLocation0.xml" deleted by Tali Yatzkar-Haham/Haifa/IBM] _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data ________________________________ 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_______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 518 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 467 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 494 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 360 bytes Desc: image004.gif URL: From sergg at tid.es Tue Mar 12 10:30:53 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 12 Mar 2013 09:30:53 +0000 Subject: [Fiware-data] Reviewers for Security Ch. architecture Message-ID: <03BE306058976141B4883174DF62D54D527383FD@EX10-MB2-MAD.hi.inet> Dear all, As you know, last week Carlos requested for volunteers for peer reviewing the architecture deliverable D232 of Security chapter. So far, nobody has shown up. Please, send me an email ASAP with your availability to assign the different sections. Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: From sergg at tid.es Wed Mar 13 00:29:58 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 12 Mar 2013 23:29:58 +0000 Subject: [Fiware-data] WP6 Roadmap review Message-ID: <03BE306058976141B4883174DF62D54D52738AF1@EX10-MB2-MAD.hi.inet> Dear all, After the review of WP6 roadmap, we have a major issue because Release 3 is not planned at all. In order to make it easier, we have provided a first take of the information required based on the roadmap, backlog (both wiki and tracker) and the QuoVadis slides provided by Carlos. That means that this information may be partially outdated. Therefore, this is an urgent request for you to check the plans for release 3 of your GE and provide feedback, changes and updates along the morning. It shouldn't take more than 5-10 minutes per GE. Hint 1: Release 3 consists of three minor releases, 3.1 (September 2013), 3.2 (December 2013) and 3.3 (March 2014). Hint 2: This is a mid-term plan of what we foresee right now, and it might change due to external issues (use case projects needs), development issues, etc. For your convenience, I copy here the Release 3 plans. Just reply to me with the corrections in the email and I'll transfer them to the wiki. Best Regards, Sergio. Publish / Subscribe Broker (TI Implementation) ? Optimization of the query language for mobile applications ? Support of multiple communication protocols, as REST. ? RDF/OWL/SPARQL API implementation Publish / Subscribe Broker (TID Implementation) ? Concurrent architecture and (possibly) scalability. ? MongoDB persistence implementation. ? Integration with PubSub and BigData Complex Event Processing ? CEP interfaces\engine that can serve CEP needs in other chapters such as in IoT. ? Authentication ? Integration with PubSub and BigData ? Include JSON EPN configuration in the RESTful API. BigData Analysis ? Cosmos new implementation of the GE Compressed Domain Video Analysis ? Object detection and tracking in videos. ? Authentication. ? GE Audit operations in the API. ? Align metadata exploitation with SAS (as requested by Safecity too). ? Implement requirements from eHealth use cases. ? Internal notification: connect to CEP, PubSub Broker. Query Broker ? Authentication. It may require the usage of HTTPs. ? Querying the version ? Provide access to other DBs in Data/Chapter GE. MongoDB-BigData, etc. Meta-data Pre-processing ? Authentication. ? Configuration of streams processing (algorithms and filters) ? Integration with CEP and PubSub Broker Location Platform ? Selection of the best positioning method. ? Event triggering and processing of event reports ? Periodic retrieval of terminal locations Semantic Application Support ? Creation and management of application semantic workspace ? Integration of the ontology engineering tool (NeON) with the repository. Semantic Annotation ? Allow to connect meaningfully sever different ontology domains. ? Enable SPARQL processing for semantic queries -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: From sergg at tid.es Wed Mar 13 10:41:11 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 13 Mar 2013 09:41:11 +0000 Subject: [Fiware-data] FW: [Fiware-wpa] Fiware Live Demo list In-Reply-To: <513F5BCE.1010304@tid.es> References: <513F5BCE.1010304@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D52738D12@EX10-MB2-MAD.hi.inet> Dear partners, If you want to participate in the live application demo that is being currently defined with your GEs, just let me know and proceed as explain below. Anyway, I'll check now with Carlos who of you should be subscribed from the beginning. I'll be forwarding the first e-mails to our list, anyway. Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Tuesday, March 12, 2013 5:46 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: FERMIN GALAN MARQUEZ Subject: [Fiware-wpa] Fiware Live Demo list Dear WPLs/WPAs, Regarding the "Live application demo" item at https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu, all the WPA/WPLs have been just subscribed by Ferm?n to the fiware-demo list (fiware-demo at lists.fi-ware.eu). Note the following AP on the weekly minutes of meeting to be complete by every WPA/WPL: AP on all WPLs to send email to Miguel cc/ Ferm?n and Juanjo regarding members of their teams they wish to include in the mailing list. There are two ways of actually accomplishing this AP * Send an email to me cc/ Ferm?n and Juanjo with the emails to be subscribed. * Each people that needs subscription does it himself/herself using the fiware-demo interface: https://lists.fi-ware.eu/listinfo/fiware-demo This AP has to be completed before tomorrow Wednesday 12th EoB. Ferm?n will send the "kick-off email" on this date so if we do not get the info by Wednesday, Fermin's email could fail to get to important people and leave them out of the start of the Live Demo evolution. This is fairly straightforward and shouldn't take more that a few minutes so please try to assess internally if you need more people on the list. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sergg at tid.es Wed Mar 13 13:26:34 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 13 Mar 2013 12:26:34 +0000 Subject: [Fiware-data] WP6 Call Message-ID: <03BE306058976141B4883174DF62D54D5273909E@EX10-MB2-MAD.hi.inet> I will provide the agenda an minutes link later on. Bridge: PIN 050662 * Belgium 070 35 99 94 * France 0821 230 748 * Germany 01803 001 178 * Italy 848 390 166 * Netherlands 0870 001 909 * Spain 902 885 318 * Sweden 0939 2066 400 * Switzerland 0848 560 190 * United Kingdom 0844 4 73 73 73 cell number 87373 * Other countries and details http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf * Worldwide & SkypeOut +49 1803 001 178 +44 844 4 73 73 73 ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2344 bytes Desc: not available URL: From sergg at tid.es Wed Mar 13 15:51:15 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 13 Mar 2013 14:51:15 +0000 Subject: [Fiware-data] WP6 call agenda Message-ID: <03BE306058976141B4883174DF62D54D5273923F@EX10-MB2-MAD.hi.inet> Dear all, Please find at [1] the agenda and minutes of WP6 call for tomorrow. Please add your name and availability. Best Regards, Sergio. [1] https://docs.google.com/document/d/1koj7sMCxPB1jLBEZeddYd5vCzaPb6yEwtV_v9Q4loTc/edit -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: From sergg at tid.es Thu Mar 14 11:21:12 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Thu, 14 Mar 2013 10:21:12 +0000 Subject: [Fiware-data] FW: [Fiware-demo] Live Demo evolution kick-off In-Reply-To: <51419AC7.5040502@tid.es> References: <51419AC7.5040502@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D5273AD1C@EX10-MB2-MAD.hi.inet> FYI From: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: Thursday, March 14, 2013 10:39 AM To: fiware-demo at lists.fi-ware.eu Subject: [Fiware-demo] Live Demo evolution kick-off Hi, As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force. As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project. We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow: * The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case. * We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition. * Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints. * Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary. * We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items. Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :) Two first action points have to be accomplished as soon as possible: * @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration * @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible. We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution Don't hesitate to contact me if you have any question on doubt, please. Best regards, ------ Ferm?n PD. The current subscribers list follows. If you miss somebody, please tell me so. [cid:part4.09080407.03020401 at tid.es] ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: jddajcjf.png Type: image/png Size: 20159 bytes Desc: jddajcjf.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From sergg at tid.es Thu Mar 14 15:25:08 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Thu, 14 Mar 2013 14:25:08 +0000 Subject: [Fiware-data] FW: [Fiware-demo] Live Demo evolution kick-off In-Reply-To: <5141C7D9.8020209@tid.es> References: <51419AC7.5040502@tid.es> <5141C7D9.8020209@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D5273AF5A@EX10-MB2-MAD.hi.inet> FYI From: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: Thursday, March 14, 2013 1:52 PM To: fiware-demo at lists.fi-ware.eu Subject: Re: [Fiware-demo] Live Demo evolution kick-off Hi, Please, find in the following URL the document that was used to define Live Demo Release 1: https://docs.google.com/document/d/1DhFz9JLJ211ZXNIXUYNEdKyp0HdX46rEFWxn_B2XRWU/edit However, take into account that this document was abandoned in some point during Live Demo Release 1 preparation, so it is not completely in sync. Best regards, ------ Ferm?n El 14/03/2013 10:39, Ferm?n Gal?n M?rquez escribi?: Hi, As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force. As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project. We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow: * The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case. * We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition. * Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints. * Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary. * We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items. Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :) Two first action points have to be accomplished as soon as possible: * @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration * @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible. We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution Don't hesitate to contact me if you have any question on doubt, please. Best regards, ------ Ferm?n PD. The current subscribers list follows. If you miss somebody, please tell me so. [cid:part7.01070305.01000805 at tid.es] ________________________________ 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 _______________________________________________ Fiware-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.png Type: image/png Size: 20159 bytes Desc: ATT00001.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00004.txt URL: From sergg at tid.es Tue Mar 19 10:25:20 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 19 Mar 2013 09:25:20 +0000 Subject: [Fiware-data] Architecture Deliverable review Message-ID: <03BE306058976141B4883174DF62D54D5273C0F4@EX10-MB2-MAD.hi.inet> Dear partners, We have now available the reviews for the different GEs in the chapter. Please find them here: Publish/Subscribe Broker https://forge.fi-ware.eu/docman/view.php/27/1951/SAP_PubSub_D232_WP6_v2_generated.docx Complex Event Processing https://forge.fi-ware.eu/docman/view.php/27/1948/D232_WP6_v2_generated_Chapter5ReviewedByAtos.docx Compressed Domain Video Analysis https://forge.fi-ware.eu/docman/view.php/27/1947/D232_WP6_v2_generated_reviewOfCDVA-GE-by-NEC.docx Query Broker https://forge.fi-ware.eu/docman/view.php/27/1949/WP6-DataQueryBrokerReviewByOrange-1.docx Meta-data Pre-processing https://forge.fi-ware.eu/docman/view.php/27/1953/D232_WP6_v2_generated_TI+MetadataPreprocessing.docx Location Platform https://forge.fi-ware.eu/docman/view.php/27/1946/D232_WP6_v2_generated_DataLOcationReview.docx Semantic Application Support https://forge.fi-ware.eu/docman/view.php/27/1957/D232_WP6_v2_generated_SA_SS_USURREY_review.docx Semantic Annotation https://forge.fi-ware.eu/docman/view.php/27/1957/D232_WP6_v2_generated_SA_SS_USURREY_review.docx The deadline for the submission of the updated versions is next Friday the 22nd . Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: From sergg at tid.es Wed Mar 20 17:18:46 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 20 Mar 2013 16:18:46 +0000 Subject: [Fiware-data] Fiware Data/Context weekly Message-ID: <03BE306058976141B4883174DF62D54D5273CA85@EX10-MB2-MAD.hi.inet> Hi all, I send you the link for tomorrows call. https://docs.google.com/document/d/1DiPSfVtg00gu3eCRw0kLXaymKh1LQeIHp0vLzmvjQGU/edit Apologies for the late notice. Best Regards, Sergio. Bridge: PIN 050662 * Belgium 070 35 99 94 * France 0821 230 748 * Germany 01803 001 178 * Italy 848 390 166 * Netherlands 0870 001 909 * Spain 902 885 318 * Sweden 0939 2066 400 * Switzerland 0848 560 190 * United Kingdom 0844 4 73 73 73 cell number 87373 * Other countries and details http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf * Worldwide & SkypeOut +49 1803 001 178 +44 844 4 73 73 73 ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2519 bytes Desc: not available URL: From sergg at tid.es Thu Mar 21 13:16:59 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Thu, 21 Mar 2013 12:16:59 +0000 Subject: [Fiware-data] Presentation link Message-ID: <03BE306058976141B4883174DF62D54D5273D063@EX10-MB2-MAD.hi.inet> Hi all, This is the link to the latest version of the quo vadis presentation. https://forge.fi-ware.eu/docman/view.php/9/1976/Quo+vadis+Data-Context+%28WP6%29.pptx Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: From sergg at tid.es Wed Mar 27 10:42:28 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 27 Mar 2013 09:42:28 +0000 Subject: [Fiware-data] Next WP6 call Message-ID: <03BE306058976141B4883174DF62D54D5273EC8A@EX10-MB2-MAD.hi.inet> Dear all, The next WP6 will take placed on the April 11th . In the meantime, please take into account the following facts: * Next week we will have to review the IoT architecture doc (2nd peer review). Volunteers, please let me know. Last one was reviewed by Siemens, Telecom Italia, and TID. TID will review a tranche, Mauricio, Tali, Fano, Tanguy, may I distribute some reviews to you? It seems to be shorter than the security one. * The official deadline for the software delivery + admin and users manuals + unit tests is the 19th and not the 12th. I think this will make easier to fulfil the deadline. I will provide a shared spreadsheet where we can track the status of each task. Please, don't wait until the deadline to deliver the whole pack. As soon as you finish, let me know and we release it for review. Regarding, the open specifications, I will let you know, but it might well apply the same deadlines. * We are in the process of integrating the KIARA partners in WP6. Hopefully they will be able to attend to the next meeting. Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: