From ralli at tid.es Tue Feb 5 15:14:58 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 05 Feb 2013 14:14:58 +0000 Subject: [Fiware-data] Conference call this week - Thursday 10:30-11:30 Message-ID: <1971FF81B8E01C45991F6F92B9E3B250551918F7@EX10-MB2-MAD.hi.inet> Dear Colleagues, We are having our regular conf call on Thursday at 10:30. Powwownow bridge, PIN 050662 will be used as well. I'm sending the googledoc with the agenda tomorrow morning, Thanks for your collaboration, 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 ralli at tid.es Wed Feb 6 17:42:52 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 06 Feb 2013 16:42:52 +0000 Subject: [Fiware-data] Conference call this week - Thursday 10:30-11:30 In-Reply-To: <1971FF81B8E01C45991F6F92B9E3B250551918F7@EX10-MB2-MAD.hi.inet> References: <1971FF81B8E01C45991F6F92B9E3B250551918F7@EX10-MB2-MAD.hi.inet> Message-ID: <1971FF81B8E01C45991F6F92B9E3B25055193DCE@EX10-MB2-MAD.hi.inet> Dear Colleagues, Here you are: https://docs.google.com/document/d/1dtWjuyovC_U0Q5QKv9UjLQYcXOnIllXWcRn4v5-4BHE/edit talk to you tomorrow at 10:30. Do not forget to complete the attendees list and potential AoB in the googledoc. Thanks, Best regards, ________________________________ De: fiware-data-bounces at lists.fi-ware.eu [fiware-data-bounces at lists.fi-ware.eu] en nombre de CARLOS RALLI UCENDO [ralli at tid.es] Enviado el: martes, 05 de febrero de 2013 15:14 Para: fiware-data at lists.fi-ware.eu Asunto: [Fiware-data] Conference call this week - Thursday 10:30-11:30 Dear Colleagues, We are having our regular conf call on Thursday at 10:30. Powwownow bridge, PIN 050662 will be used as well. I'm sending the googledoc with the agenda tomorrow morning, Thanks for your collaboration, 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 ________________________________ 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 marcus.laumer.ext at siemens.com Wed Feb 6 18:32:40 2013 From: marcus.laumer.ext at siemens.com (Laumer, Marcus) Date: Wed, 6 Feb 2013 18:32:40 +0100 Subject: [Fiware-data] Conference call this week - Thursday 10:30-11:30 In-Reply-To: <1971FF81B8E01C45991F6F92B9E3B25055193DCE@EX10-MB2-MAD.hi.inet> References: <1971FF81B8E01C45991F6F92B9E3B250551918F7@EX10-MB2-MAD.hi.inet> <1971FF81B8E01C45991F6F92B9E3B25055193DCE@EX10-MB2-MAD.hi.inet> Message-ID: <750211B1279EFC489DB5D8B39550E0741DCF2457C4@DEMCHP99E15MSX.ww902.siemens.net> Dear Carlos, it seems that access to the googledoc is restricted. Can you please check? Best regards, Marcus From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO Sent: Mittwoch, 6. Februar 2013 17:43 To: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Conference call this week - Thursday 10:30-11:30 Dear Colleagues, Here you are: https://docs.google.com/document/d/1dtWjuyovC_U0Q5QKv9UjLQYcXOnIllXWcRn4v5-4BHE/edit talk to you tomorrow at 10:30. Do not forget to complete the attendees list and potential AoB in the googledoc. Thanks, Best regards, _____ De: fiware-data-bounces at lists.fi-ware.eu [fiware-data-bounces at lists.fi-ware.eu] en nombre de CARLOS RALLI UCENDO [ralli at tid.es] Enviado el: martes, 05 de febrero de 2013 15:14 Para: fiware-data at lists.fi-ware.eu Asunto: [Fiware-data] Conference call this week - Thursday 10:30-11:30 Dear Colleagues, We are having our regular conf call on Thursday at 10:30. Powwownow bridge, PIN 050662 will be used as well. I'm sending the googledoc with the agenda tomorrow morning, Thanks for your collaboration, 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 _____ 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 ralli at tid.es Tue Feb 12 17:04:59 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 12 Feb 2013 16:04:59 +0000 Subject: [Fiware-data] Data/Context Conference Call next Thu at 10:30 as usual Message-ID: <1971FF81B8E01C45991F6F92B9E3B25055199EB2@EX10-MB2-MAD.hi.inet> Dear Colleagues, Just to let you know we are having our regular call at 10:30 next Thursday. I'll be circulating the googledoc link tomorrow morning. However, the agenda draft is included hereby: 1) Status of on-going technical activities as discussed in the previous Telco. (45') 2) Short review of Miguels' commebts on the Backlog if available. (15') 3) AoB (15') We will be using powwow now with PIN 050662 as usual too. Thanks for your feedback/comments. 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 ralli at tid.es Thu Feb 14 09:39:01 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 14 Feb 2013 08:39:01 +0000 Subject: [Fiware-data] Google-doc for today's call. Agenda remains the same. Talk to you at 10:30 Message-ID: <1971FF81B8E01C45991F6F92B9E3B2505519B94D@EX10-MB2-MAD.hi.inet> Dear Colleagues, Here you are. Agenda is the same I sent yesterday although I added an intermediate point (2) to update actions (if any) on the current tasks during this sprint. https://docs.google.com/document/d/1aBxMMoJ4EwXlU0_cpJXRkZOPbM8rHn09NGBTx2SMlZA/edit 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 boris.moltchanov at telecomitalia.it Thu Feb 14 17:57:34 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 14 Feb 2013 17:57:34 +0100 Subject: [Fiware-data] CEP<->P/S Message-ID: 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. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fermin at tid.es Thu Feb 14 18:09:00 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 14 Feb 2013 18:09:00 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: References: Message-ID: <511D1A2C.9060806@tid.es> 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]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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From GUYSH at il.ibm.com Thu Feb 14 21:31:55 2013 From: GUYSH at il.ibm.com (Guy Sharon) Date: Thu, 14 Feb 2013 22:31:55 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <511D1A2C.9060806@tid.es> References: <511D1A2C.9060806@tid.es> Message-ID: Of course the interfaces are documented - please look at the catalogue entry and the wiki 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: and within IBM on: Haifa University, Mount Carmel Haifa, HA 31905 Israel From: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 14/02/2013 19:09 Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu 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 _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 467 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 494 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 360 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Fri Feb 15 07:17:45 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 15 Feb 2013 07:17:45 +0100 Subject: [Fiware-data] CEP<->P/S Message-ID: 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. [cid:00000000000000000000000000000003 at TI.Disclaimer]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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Mon Feb 18 16:11:19 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Mon, 18 Feb 2013 15:11:19 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: References: Message-ID: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> 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]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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Mon Feb 18 16:23:05 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Mon, 18 Feb 2013 16:23:05 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: Hi Fano, I?m very glad to see your explanation and notice that we?re perfectly alligned. That was also my understanding of the overall scenario. And CEP is a sort of event reasoned driven by its internal logic and taking the context data from the P/S for the event reasoning. Then, of course, those intelligent reasoning results are provided to the P/S and then to the application subscribed for those events. It seems to be so simple that I?m not sure whether we need that sort of schema (two components exchanging info CEP<->P/S where CEP is containing the reasoning event logic and P/S is connected to its providers and to subscribed applications). What we really need is the middleware between the CEP and P/S and I got an idea that Carlos was not considering it as a difficulty during the last call. We need to find that WHO who will take NGSI spec and attach it to the CEP. I recall that the NGSI is a sort of conventional standard de-facto for such king of communications in FI-WARE. Best Regards, Boris From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Monday, February 18, 2013 4:11 PM To: Moltchanov Boris; fermin at tid.es; fiware-data at lists.fi-ware.eu Cc: BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S 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. [cid:00000000000000000000000000000003 at TI.Disclaimer]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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon Feb 18 17:04:33 2013 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Mon, 18 Feb 2013 17:04:33 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: <51225111.9020909@tid.es> Dear Fano, all, I agree in that drawing the overall architecture and dataflow would be very desirable. A first sketch is in the last audio minutes (https://docs.google.com/document/d/1aBxMMoJ4EwXlU0_cpJXRkZOPbM8rHn09NGBTx2SMlZA/edit): A) A1) Outmart IoT -> PubSub -> CEP -> PubSub -> OutSmat App A2) Outmart IoT -> PubSub -> BigData (Let's focus in A1 from now on, A2 doesn't involve CEP). 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. 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. (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]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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From TALI at il.ibm.com Mon Feb 18 17:29:50 2013 From: TALI at il.ibm.com (Tali Yatzkar-Haham) Date: Mon, 18 Feb 2013 18:29:50 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51225111.9020909@tid.es> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51225111.9020909@tid.es> Message-ID: Dear Ferm?n, all, I agree with looking on both ways of communications. Please let me correct the CEP API involved: 1. PubSub -> (Adaptator1) -> CEP - In this case the CEP receives events and the API is either http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Getting_Events_API that activates an external REST service to pull (GET) events from it. OR a new API that we implemented for Release 2 (not yet in the wiki), in which the CEP expose a REST service that allow external application to send input events to the CEP. 2. CEP -> (Adaptator2) -> PubSub - in this case the CEP sends output events and the API is http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification_%28PRELIMINARY%29#Sending_Events_API In this case the CEP activates an external REST service and sends events to it. As oppose to what you stated, the CEP productively sends events to the external application REST service. The JSON format of the CEP events is all cases is the same as described in the wiki. Please tell me if the API are not clear. 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: Ferm?n Gal?n M?rquez To: fano.ramparany at orange.com, Cc: BELLABAS Alia OLNC/OLPS , "fiware-data at lists.fi-ware.eu" Date: 18/02/2013 06:04 PM Subject: Re: [Fiware-data] CEP<->P/S Sent by: fiware-data-bounces at lists.fi-ware.eu Dear Fano, all, I agree in that drawing the overall architecture and dataflow would be very desirable. A first sketch is in the last audio minutes ( https://docs.google.com/document/d/1aBxMMoJ4EwXlU0_cpJXRkZOPbM8rHn09NGBTx2SMlZA/edit ): A) A1) Outmart IoT -> PubSub -> CEP -> PubSub -> OutSmat App A2) Outmart IoT -> PubSub -> BigData (Let's focus in A1 from now on, A2 doesn't involve CEP). 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 . 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. (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 _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Mon Feb 18 17:44:05 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Mon, 18 Feb 2013 16:44:05 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: <8616_1361205849_51225A59_8616_245_1_4040df39-fdcd-4ccc-98ef-dccb310fc32d@PEXCVZYH01.corporate.adroot.infra.ftgroup> Hi Boris and all, My feedback in line below. De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it] Objet : RE: [Fiware-data] CEP<->P/S ... It seems to be so simple that I?m not sure whether we need that sort of schema (two components exchanging info CEP<->P/S where CEP is containing the reasoning event logic and P/S is connected to its providers and to subscribed applications). [FR] As simple as it could be, that schema would make explicit the type of data those two components would exchange and which protocol they would use to exchange this information. In the simplest case, as you suggest the protocol would be OMA NGSI for CEP to connect to P/S. A decision has then to be made on how the P/S will connect to CEP. Still in the simplest case, the data to be exchanged between the two components are event descriptions in both direction. In which case, as you suggest a convention has to be decided on how data about ?entity? in the P/S event description should be converted in the CEP event description and on how data about ?entity? should be retrieved from CEP events description. Unless we know all this type of information, It is not easy for Carlos to evaluate the amount of work required nor identify who can do the job. From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: Monday, February 18, 2013 4:11 PM To: Moltchanov Boris; fermin at tid.es; fiware-data at lists.fi-ware.eu Cc: BELLABAS Alia OLNC/OLPS Subject: RE: [Fiware-data] CEP<->P/S 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]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. _________________________________________________________________________________________________________________________ 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: From fano.ramparany at orange.com Mon Feb 18 17:44:07 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Mon, 18 Feb 2013 16:44:07 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51225111.9020909@tid.es> References: <17244_1361200283_5122449B_17244_271_6_06b36419-604a-46b1-b5f7-6992bd1c5f30@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51225111.9020909@tid.es> Message-ID: <22008_1361205852_51225A5B_22008_2771_1_f029539d-a2cf-45d7-b776-6e10a2bf550f@PEXCVZYH02.corporate.adroot.infra.ftgroup> 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. 1. 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]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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From TALI at il.ibm.com Tue Feb 19 08:11:49 2013 From: TALI at il.ibm.com (Tali Yatzkar-Haham) Date: Tue, 19 Feb 2013 09:11:49 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <22008_1361205852_51225A5B_22008_2771_1_f029539d-a2cf-45d7-b776-6e10a2bf550f@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> Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Tue Feb 19 11:32:44 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 19 Feb 2013 10:32:44 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: 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> Message-ID: <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.corporate.adroot.infra.ftgroup> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: queryContextResponse-VehicleLocation0.xml Type: application/xml Size: 1057 bytes Desc: queryContextResponse-VehicleLocation0.xml URL: From fano.ramparany at orange.com Tue Feb 19 11:37:13 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 19 Feb 2013 10:37:13 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.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> Message-ID: <19934_1361270234_512355DA_19934_41_1_35bfec8a-13a5-465e-abdc-ff15958af0d5@PEXCVZYH02.corporate.adroot.infra.ftgroup> ?obviously, we need the same info (CEP event xml document) from your side. De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de fano.ramparany at orange.com Envoy? : mardi 19 f?vrier 2013 11:33 ? : Tali Yatzkar-Haham Cc : fiware-data at lists.fi-ware.eu Objet : 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. _________________________________________________________________________________________________________________________ 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: From TALI at il.ibm.com Tue Feb 19 12:27:38 2013 From: TALI at il.ibm.com (Tali Yatzkar-Haham) Date: Tue, 19 Feb 2013 13:27:38 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <32694_1361269964_512354CC_32694_1116_1_DC254E6D1212F24EAE0D7766A11FE28906F261@PEXCVZYM12.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> Message-ID: 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Tue Feb 19 13:10:17 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 19 Feb 2013 13:10:17 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: 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> Message-ID: <51236BA9.5090402@tid.es> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Tue Feb 19 13:19:29 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 19 Feb 2013 12:19:29 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51236BA9.5090402@tid.es> 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> Message-ID: <3084_1361276375_51236DD7_3084_6626_1_afc9c0f3-4d4b-4e33-8a8c-c04bc62679aa@PEXCVZYH01.corporate.adroot.infra.ftgroup> Hi Fermin, As I was also summarizing the discussion I received your mail announcing this shared google doc. This is an excellent initiative, which will avoid mail traffic and enable anybody to jump in the topic, without having to read all messages exchanged. I couldn?t edit the document so I added my ?version? of the summary as a comment at the end of the document. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : mardi 19 f?vrier 2013 13:10 ? : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S 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 _________________________________________________________________________________________________________________________ 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: From GUYSH at il.ibm.com Tue Feb 19 13:22:16 2013 From: GUYSH at il.ibm.com (Guy Sharon) Date: Tue, 19 Feb 2013 14:22:16 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51236BA9.5090402@tid.es> 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> Message-ID: 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: and within IBM on: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 467 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 494 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 360 bytes Desc: not available URL: From fano.ramparany at orange.com Tue Feb 19 13:31:01 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 19 Feb 2013 12:31:01 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51236BA9.5090402@tid.es> 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> Message-ID: <3082_1361277066_5123708A_3082_2768_1_8717a066-5a8f-4036-b24c-6db72f60650d@PEXCVZYH01.corporate.adroot.infra.ftgroup> Hi Fermin, I'll find the right persons in Outsmart who can provide the info and a realistic scenario. In the meantime, I'll serve as a proxy. Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Objet : Re: [Fiware-data] CEP<->P/S ... 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? _________________________________________________________________________________________________________________________ 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: From TALI at il.ibm.com Tue Feb 19 16:06:00 2013 From: TALI at il.ibm.com (Tali Yatzkar-Haham) Date: Tue, 19 Feb 2013 17:06:00 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51236BA9.5090402@tid.es> 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> Message-ID: Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Tue Feb 19 18:22:13 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 19 Feb 2013 17:22:13 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: 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> Message-ID: <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Tali and all, Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain experts. They know what info about the lamp is contained in the event message produced by IDAS (I think IDAS plays the role of the IoT Gateway in the FIWARE core platform architecture). I think that for the same reason we need adapters between CEP and P/S we need an adapter between IDAS and P/S. Probably this adapter will do the job of POSTing a contextUpdate message in the appropriate format (including the ?scope? attribute) to the P/S. In parallel to this ?design/implementation? discussion, we are defining a realistic scenario within OUTSMART that will fit to this demo. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Tali Yatzkar-Haham Envoy? : mardi 19 f?vrier 2013 16:06 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Tue Feb 19 18:55:45 2013 From: fermin at tid.es (=?UTF-8?B?RmVybcOtbiBHYWzDoW4gTcOhcnF1ZXo=?=) Date: Tue, 19 Feb 2013 18:55:45 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <5123BCA1.2050000@tid.es> Hi, @SantanderUC: we have a Google Doc in which we are capturing information related with the integration needed for the demo at https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. I have added a section at the end named "Context/Event Data model". Could you fulfill that section with the entities/attributes information that will be used during the demo, please? (Tell me your google ids, so I can provide you modification permissions on the shared document). Thanks! Best regards, ------ Ferm?n El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: Hi Tali and all, Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain experts. They know what info about the lamp is contained in the event message produced by IDAS (I think IDAS plays the role of the IoT Gateway in the FIWARE core platform architecture). I think that for the same reason we need adapters between CEP and P/S we need an adapter between IDAS and P/S. Probably this adapter will do the job of POSTing a contextUpdate message in the appropriate format (including the ?scope? attribute) to the P/S. In parallel to this ?design/implementation? discussion, we are defining a realistic scenario within OUTSMART that will fit to this demo. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Tali Yatzkar-Haham Envoy? : mardi 19 f?vrier 2013 16:06 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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. ________________________________ 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 Wed Feb 20 10:33:02 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Wed, 20 Feb 2013 09:33:02 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <51248C86.60201@tlmat.unican.es> 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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> <5123BCA1.2050000@tid.es> <51248C86.60201@tlmat.unican.es> Message-ID: <29528_1361352783_5124984F_29528_1951_1_DC254E6D1212F24EAE0D7766A11FE28907268E@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Javier, Fermin has highlighted some questions for you at the end of the document, which doesn't require that you read and understand the rest of the document. Regards, Fano De : Javier Cuesta [mailto:jcuesta at tlmat.unican.es] Envoy? : mercredi 20 f?vrier 2013 09:43 ? : Ferm?n Gal?n M?rquez Cc : 'Ignacio Elicegui Maestro'; RAMPARANY Fano OLNC/OLPS; Tali Yatzkar-Haham; fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin, I just read this mails and I'm still a little bit "lost" on what you expect to get from us, but suppose this will clarify when I can check the google doc. My google ID is javiercuest at gmail.com Best regards. Javier. El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: Hi, @SantanderUC: we have a Google Doc in which we are capturing information related with the integration needed for the demo at https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. I have added a section at the end named "Context/Event Data model". Could you fulfill that section with the entities/attributes information that will be used during the demo, please? (Tell me your google ids, so I can provide you modification permissions on the shared document). Thanks! Best regards, ------ Ferm?n El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: Hi Tali and all, Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain experts. They know what info about the lamp is contained in the event message produced by IDAS (I think IDAS plays the role of the IoT Gateway in the FIWARE core platform architecture). I think that for the same reason we need adapters between CEP and P/S we need an adapter between IDAS and P/S. Probably this adapter will do the job of POSTing a contextUpdate message in the appropriate format (including the ?scope? attribute) to the P/S. In parallel to this ?design/implementation? discussion, we are defining a realistic scenario within OUTSMART that will fit to this demo. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Tali Yatzkar-Haham Envoy? : mardi 19 f?vrier 2013 16:06 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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. ________________________________ 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 -- Javier Cuesta Ca?as Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 506 Fax: +34 942 201 488 mailto: jcuesta at tlmat.unican.es web: http://www.tlmat.unican.es _________________________________________________________________________________________________________________________ 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: From ralli at tid.es Wed Feb 20 15:32:08 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 20 Feb 2013 14:32:08 +0000 Subject: [Fiware-data] There will be no Data/Context conference call tomorrow Message-ID: <1971FF81B8E01C45991F6F92B9E3B250551A3512@EX10-MB2-MAD.hi.inet> Dear Colleagues, We are still working hard to have the backlog and wiki ready for the committed deliverables so we have decided to wait for next week to keep on our discussions. However, you can still come up with any urgent issue through the mailing list. Additionally, please keep on discussions related to the technical tasks that are already happening. Thanks 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 IEMaestro at tlmat.unican.es Wed Feb 20 09:30:18 2013 From: IEMaestro at tlmat.unican.es (Ignacio Elicegui Maestro) Date: Wed, 20 Feb 2013 09:30:18 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <5123BCA1.2050000@tid.es> 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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> <5123BCA1.2050000@tid.es> Message-ID: <5124899A.90606@tlmat.unican.es> Hello, Fermin. In order to progress with our collaboration, during this morning I will provide examples of the SensorML files we're sending to IDAS (IoT Backend) where you can see the data and its structure we're dealing with. We're a little busy these days building our PoC for OutSmart review but we will manage (together with TID) to provide you the info requested. My google ID is "emaestro at gmail.com". Regards El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: > Hi, > > @SantanderUC: we have a Google Doc in which we are capturing > information related with the integration needed for the demo at > https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. > I have added a section at the end named "Context/Event Data model". > Could you fulfill that section with the entities/attributes > information that will be used during the demo, please? (Tell me your > google ids, so I can provide you modification permissions on the > shared document). > > Thanks! > > Best regards, > > ------ > Ferm?n > > El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: >> >> Hi Tali and all, >> >> Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain >> experts. They know what info about the lamp is contained in the event >> message produced by IDAS (I think IDAS plays the role of the IoT >> Gateway in the FIWARE core platform architecture). I think that for >> the same reason we need adapters between CEP and P/S we need an >> adapter between IDAS and P/S. Probably this adapter will do the job >> of POSTing a contextUpdate message in the appropriate format >> (including the ?scope? attribute) to the P/S. >> >> In parallel to this ?design/implementation? discussion, we are >> defining a realistic scenario within OUTSMART that will fit to this demo. >> >> Regards, >> >> >> Fano >> >> *De :*fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] *De la part de* Tali >> Yatzkar-Haham >> *Envoy? :* mardi 19 f?vrier 2013 16:06 >> *? :* Ferm?n Gal?n M?rquez >> *Cc :* fiware-data at lists.fi-ware.eu >> *Objet :* Re: [Fiware-data] CEP<->P/S >> >> Hi Fermin and all, >> >> Thank you for putting this summary doc. I updated the CEP part, and >> gave example for event based on the event you used. >> >> I have a question - >> In the example you gave of a Lamp entity, can a context event include >> any subset of attributes of the Lamp entity in every context event? >> does it send all the attributes in any context event? I remember that >> there used to be a "scope" attribute that defined the list of >> attributes that are sent. Could you please elaborate? >> >> >> 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: Ferm?n Gal?n M?rquez >> To: fiware-data at lists.fi-ware.eu, >> Date: 19/02/2013 02:10 PM >> 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 thewiki >> ): >> >> 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. > > > ------------------------------------------------------------------------ > > 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 -- Ignacio Elicegui Maestro Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 505 Fax: +34 942 201 488 mailto: IEMaestro at tlmat.unican.es web: http://www.tlmat.unican.es -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcuesta at tlmat.unican.es Wed Feb 20 09:42:46 2013 From: jcuesta at tlmat.unican.es (Javier Cuesta) Date: Wed, 20 Feb 2013 09:42:46 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <5123BCA1.2050000@tid.es> 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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> <5123BCA1.2050000@tid.es> Message-ID: <51248C86.60201@tlmat.unican.es> Hi Fermin, I just read this mails and I'm still a little bit "lost" on what you expect to get from us, but suppose this will clarify when I can check the google doc. My google ID is javiercuest at gmail.com Best regards. Javier. El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: > Hi, > > @SantanderUC: we have a Google Doc in which we are capturing > information related with the integration needed for the demo at > https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. > I have added a section at the end named "Context/Event Data model". > Could you fulfill that section with the entities/attributes > information that will be used during the demo, please? (Tell me your > google ids, so I can provide you modification permissions on the > shared document). > > Thanks! > > Best regards, > > ------ > Ferm?n > > El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: >> >> Hi Tali and all, >> >> Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain >> experts. They know what info about the lamp is contained in the event >> message produced by IDAS (I think IDAS plays the role of the IoT >> Gateway in the FIWARE core platform architecture). I think that for >> the same reason we need adapters between CEP and P/S we need an >> adapter between IDAS and P/S. Probably this adapter will do the job >> of POSTing a contextUpdate message in the appropriate format >> (including the ?scope? attribute) to the P/S. >> >> In parallel to this ?design/implementation? discussion, we are >> defining a realistic scenario within OUTSMART that will fit to this demo. >> >> Regards, >> >> >> Fano >> >> *De :*fiware-data-bounces at lists.fi-ware.eu >> [mailto:fiware-data-bounces at lists.fi-ware.eu] *De la part de* Tali >> Yatzkar-Haham >> *Envoy? :* mardi 19 f?vrier 2013 16:06 >> *? :* Ferm?n Gal?n M?rquez >> *Cc :* fiware-data at lists.fi-ware.eu >> *Objet :* Re: [Fiware-data] CEP<->P/S >> >> Hi Fermin and all, >> >> Thank you for putting this summary doc. I updated the CEP part, and >> gave example for event based on the event you used. >> >> I have a question - >> In the example you gave of a Lamp entity, can a context event include >> any subset of attributes of the Lamp entity in every context event? >> does it send all the attributes in any context event? I remember that >> there used to be a "scope" attribute that defined the list of >> attributes that are sent. Could you please elaborate? >> >> >> 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: Ferm?n Gal?n M?rquez >> To: fiware-data at lists.fi-ware.eu, >> Date: 19/02/2013 02:10 PM >> 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 thewiki >> ): >> >> 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. > > > ------------------------------------------------------------------------ > > 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 -- Javier Cuesta Ca?as Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 506 Fax: +34 942 201 488 mailto: jcuesta at tlmat.unican.es web: http://www.tlmat.unican.es -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Fri Feb 22 10:36:21 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Fri, 22 Feb 2013 10:36:21 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <5124899A.90606@tlmat.unican.es> 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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> <5123BCA1.2050000@tid.es> <5124899A.90606@tlmat.unican.es> Message-ID: Dear Ignacio and Javier, I believe that the SensorML data, in long run, shall be ?intercepted? and ?converted? to the FI-WARE NGSI in IoT broker (or IoT gateway) that we have in FI-WARE. Therefore, if you may, please cut and paste (no attachments) the example directly into the body of email sent to the data and ngsi fiware (?populated? also by FI-WARE IoT people) lists I cc-ying in this email. It will be really a good example of what the expected data should (and hopefully would) be. Thank you a lot 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 Ignacio Elicegui Maestro Sent: Wednesday, February 20, 2013 9:30 AM To: Ferm?n Gal?n M?rquez Cc: 'Javier Cuesta'; fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] CEP<->P/S Hello, Fermin. In order to progress with our collaboration, during this morning I will provide examples of the SensorML files we're sending to IDAS (IoT Backend) where you can see the data and its structure we're dealing with. We're a little busy these days building our PoC for OutSmart review but we will manage (together with TID) to provide you the info requested. My google ID is "emaestro at gmail.com". Regards El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: Hi, @SantanderUC: we have a Google Doc in which we are capturing information related with the integration needed for the demo at https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. I have added a section at the end named "Context/Event Data model". Could you fulfill that section with the entities/attributes information that will be used during the demo, please? (Tell me your google ids, so I can provide you modification permissions on the shared document). Thanks! Best regards, ------ Ferm?n El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: Hi Tali and all, Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain experts. They know what info about the lamp is contained in the event message produced by IDAS (I think IDAS plays the role of the IoT Gateway in the FIWARE core platform architecture). I think that for the same reason we need adapters between CEP and P/S we need an adapter between IDAS and P/S. Probably this adapter will do the job of POSTing a contextUpdate message in the appropriate format (including the ?scope? attribute) to the P/S. In parallel to this ?design/implementation? discussion, we are defining a realistic scenario within OUTSMART that will fit to this demo. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Tali Yatzkar-Haham Envoy? : mardi 19 f?vrier 2013 16:06 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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. ________________________________ 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 -- Ignacio Elicegui Maestro Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 505 Fax: +34 942 201 488 mailto: IEMaestro at tlmat.unican.es web: http://www.tlmat.unican.es -------------- next part -------------- An HTML attachment was scrubbed... URL: From IEMaestro at tlmat.unican.es Fri Feb 22 10:59:26 2013 From: IEMaestro at tlmat.unican.es (Ignacio Elicegui Maestro) Date: Fri, 22 Feb 2013 10:59:26 +0100 Subject: [Fiware-data] CEP<->P/S In-Reply-To: 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> <30879_1361294534_5123B4C6_30879_854_1_DC254E6D1212F24EAE0D7766A11FE2890725B9@PEXCVZYM12.corporate.adroot.infra.ftgroup> <5123BCA1.2050000@tid.es> <5124899A.90606@tlmat.unican.es> Message-ID: <5127417E.1020509@tlmat.unican.es> Hello, Boris. The Sensor ML files we already sent to Fermin are also be sent to the IDAS platform (which currently -and as far as i know- is the FI-WARE IoT Backend Manager) could the IoT Broker get that info from the IoT Backend?? (the sensorML files are copied in the GoogleDoc Fermin gave me access). The fiware-data lists returns me errors (I'm not subscribed to those lists). Could you please, Boris, send this to them?? -------AMMS Reactive Power (similas SML with Active Power) --2012-09-30T02:00:00Z-OUTSMART--2936 ----- Presence Detection --2013-02-19T09:42:28Z-OUTSMART--1 -----Battery Status --2013-02-19T09:42:28Z-OUTSMART--81 ------Light level (Lux) --2013-02-19T09:42:28Z-OUTSMART--39.56 El 22/02/2013 10:36, Moltchanov Boris escribi?: > > Dear Ignacio and Javier, > > I believe that the SensorML data, in long run, shall be ?intercepted? > and ?converted? to the FI-WARE NGSI in IoT broker (or IoT gateway) > that we have in FI-WARE. > > Therefore, if you may, please cut and paste (no attachments) the > example directly into the body of email sent to the data and ngsi > fiware (?populated? also by FI-WARE IoT people) lists I cc-ying in > this email. It will be really a good example of what the expected data > should (and hopefully would) be. > > Thank you a lot 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 *Ignacio > Elicegui Maestro > *Sent:* Wednesday, February 20, 2013 9:30 AM > *To:* Ferm?n Gal?n M?rquez > *Cc:* 'Javier Cuesta'; fiware-data at lists.fi-ware.eu > *Subject:* Re: [Fiware-data] CEP<->P/S > > Hello, Fermin. > In order to progress with our collaboration, during this morning I > will provide examples of the SensorML files we're sending to IDAS (IoT > Backend) where you can see the data and its structure we're dealing > with. We're a little busy these days building our PoC for OutSmart > review but we will manage (together with TID) to provide you the info > requested. > My google ID is "emaestro at gmail.com" . > Regards > > El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: > > Hi, > > @SantanderUC: we have a Google Doc in which we are capturing > information related with the integration needed for the demo at > https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. > I have added a section at the end named "Context/Event Data > model". Could you fulfill that section with the > entities/attributes information that will be used during the demo, > please? (Tell me your google ids, so I can provide you > modification permissions on the shared document). > > Thanks! > > Best regards, > > ------ > Ferm?n > > El 19/02/2013 18:22, fano.ramparany at orange.com > escribi?: > > Hi Tali and all, > > Javier and Ignacio (in cc) are our OUTSMART/Santander UC > domain experts. They know what info about the lamp is > contained in the event message produced by IDAS (I think IDAS > plays the role of the IoT Gateway in the FIWARE core platform > architecture). I think that for the same reason we need > adapters between CEP and P/S we need an adapter between IDAS > and P/S. Probably this adapter will do the job of POSTing a > contextUpdate message in the appropriate format (including the > ?scope? attribute) to the P/S. > > In parallel to this ?design/implementation? discussion, we > are defining a realistic scenario within OUTSMART that will > fit to this demo. > > Regards, > > > Fano > > *De :*fiware-data-bounces at lists.fi-ware.eu > > [mailto:fiware-data-bounces at lists.fi-ware.eu] *De la part de* > Tali Yatzkar-Haham > *Envoy? :* mardi 19 f?vrier 2013 16:06 > *? :* Ferm?n Gal?n M?rquez > *Cc :* fiware-data at lists.fi-ware.eu > > *Objet :* Re: [Fiware-data] CEP<->P/S > > Hi Fermin and all, > > Thank you for putting this summary doc. I updated the CEP > part, and gave example for event based on the event you used. > > I have a question - > In the example you gave of a Lamp entity, can a context event > include any subset of attributes of the Lamp entity in every > context event? does it send all the attributes in any context > event? I remember that there used to be a "scope" attribute > that defined the list of attributes that are sent. Could you > please elaborate? > > > 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: Ferm?n Gal?n M?rquez > To: fiware-data at lists.fi-ware.eu > , > Date: 19/02/2013 02:10 PM > 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 thewiki > ): > > 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. > > ------------------------------------------------------------------------ > > > 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 > > > > > -- > Ignacio Elicegui Maestro > Grupo de Ingenier?a Telem?tica - DICOM > Universidad de Cantabria > Plaza de la Ciencia S/N - Planta -2 S232 > 39005 Santander - Cantabria - Espa?a > Tel: +34 942 200 919 ext. 505 > Fax: +34 942 201 488 > mailto:IEMaestro at tlmat.unican.es > web:http://www.tlmat.unican.es -- Ignacio Elicegui Maestro Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 505 Fax: +34 942 201 488 mailto: IEMaestro at tlmat.unican.es web: http://www.tlmat.unican.es -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: AMMS_Obs_SML.xml Type: text/xml Size: 355 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PD_Obs_SML.xml Type: text/xml Size: 311 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BT_Obs_SML.xml Type: text/xml Size: 301 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: LT_Obs_SML.xml Type: text/xml Size: 293 bytes Desc: not available URL: From fano.ramparany at orange.com Fri Feb 22 18:01:57 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Fri, 22 Feb 2013 17:01:57 +0000 Subject: [Fiware-data] CEP<->P/S In-Reply-To: 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> Message-ID: <4540_1361552643_5127A502_4540_2802_1_06a89940-165f-4451-a6f1-fc91c06912b2@PEXCVZYH01.corporate.adroot.infra.ftgroup> 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. -------------- 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 Wed Feb 27 12:19:40 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 27 Feb 2013 11:19:40 +0000 Subject: [Fiware-data] Data/Context call Thursday at 10.30. Message-ID: <03BE306058976141B4883174DF62D54D5272E573@EX10-MB2-MAD.hi.inet> Dear Colleagues, Tomorrow at 10.30 we will have the WP6 regular call. This is the doc for the agenda and the minutes: https://docs.google.com/document/d/1fTa8eJRsLfN0-hrWa931HQZdnROZgu8UuNS97slZ-YU/edit Please don't forget to provide your availability in the document. We will be using powwownow with PIN 050662 as usual. Thanks for your feedback/comments. Kind 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 Feb 27 15:23:01 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 27 Feb 2013 14:23:01 +0000 Subject: [Fiware-data] Fi-Ware Data Context Chapter Regular Call Message-ID: <03BE306058976141B4883174DF62D54D5272E690@EX10-MB2-MAD.hi.inet> https://docs.google.com/document/d/1fTa8eJRsLfN0-hrWa931HQZdnROZgu8UuNS97slZ-YU/edit "PowWowNow" Conference Call. PIN 050662 Phone numbers list: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ 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: 2010 bytes Desc: not available URL: From ralli at tid.es Thu Feb 28 09:26:22 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 28 Feb 2013 08:26:22 +0000 Subject: [Fiware-data] Data/Context call Thursday at 10.30 -> Please let us know your availability In-Reply-To: <03BE306058976141B4883174DF62D54D5272E573@EX10-MB2-MAD.hi.inet> Message-ID: <1971FF81B8E01C45991F6F92B9E3B250551C1213@EX10-MB2-MAD.hi.inet> Dear Colleagues, Please, do not forget to fill in the attendees list of the Googledoc provided by Sergio before our call: https://docs.google.com/document/d/1fTa8eJRsLfN0-hrWa931HQZdnROZgu8UuNS97slZ-YU/edit Thanks 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 ------------------------------------------------------------------------------------------------------------------------ De: SERGIO GARCIA GOMEZ > Fecha: mi?rcoles, 27 de febrero de 2013 12:19 Para: "fiware-data at lists.fi-ware.eu" > Asunto: [Fiware-data] Data/Context call Thursday at 10.30. Dear Colleagues, Tomorrow at 10.30 we will have the WP6 regular call. This is the doc for the agenda and the minutes: https://docs.google.com/document/d/1fTa8eJRsLfN0-hrWa931HQZdnROZgu8UuNS97slZ-YU/edit Please don?t forget to provide your availability in the document. We will be using powwownow with PIN 050662 as usual. Thanks for your feedback/comments. Kind 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 ________________________________ 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 Feb 28 13:05:55 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Thu, 28 Feb 2013 12:05:55 +0000 Subject: [Fiware-data] TR: CEP<->P/S Message-ID: <19853_1362053157_512F4825_19853_6205_1_DC254E6D1212F24EAE0D7766A11FE2890770E9@PEXCVZYM12.corporate.adroot.infra.ftgroup> Some ? business ? scenario / high-level story lines for the OUTSMART Santander Use Case that we came across, although we didn?t get any feedback from UC yet. De : RAMPARANY Fano OLNC/OLPS Envoy? : jeudi 21 f?vrier 2013 10:24 ? : 'Ignacio Elicegui Maestro'; Ferm?n Gal?n M?rquez Cc : 'Javier Cuesta'; Tali Yatzkar-Haham; Cristina Pe?a Alcega Objet : RE: [Fiware-data] CEP<->P/S Thank you Ignacio and all, I?ve seen that you?ve uploaded all this info on the googledoc. This is a very good idea as it will save us the effort of downloading the files on our own disk. The type of sensors you use can give us also an idea of which domain/business specific situation the CEP can detect. Probably you have some already in mind. I was thinking about this ones: - Upon reception of several different presence detection from different radar nodes close to each other we could infer there?s a crowed event - Upon reception of several AMMS events with no power from the lamps in the same area we could infer there?s a problem of lighting equipment - If there is a crowed event and lighting equipment we could raise an alarm with higher priority - Light level is high AMMS is high -> abnormal situation - Light level is low AMMS is low no presence detected -> abnormal situation - ? Regads, Fano De : Ignacio Elicegui Maestro [mailto:IEMaestro at tlmat.unican.es] Envoy? : jeudi 21 f?vrier 2013 09:32 ? : Ferm?n Gal?n M?rquez Cc : 'Javier Cuesta'; RAMPARANY Fano OLNC/OLPS; Tali Yatzkar-Haham; Cristina Pe?a Alcega Objet : Re: [Fiware-data] CEP<->P/S Dear all, find attached some SensorML (XML files) extracted from those we're sending to IDAS and generated by our OutSmart Metadata Preprocessing Tool. They enclose data from: AMMS (Automatic Metering & Management System) from EOn (Utility) with an example of an Active Power measurement (Reactive Power is similar) Battery (BT) status from a sensor node Presence Detection (PD) from a Radar node Light level measurement (LT) The structure of the SensorML file includes: Node ID (Obs from) Date & Time (stm) when measurement is generated (printed by the SANET Gateway / Sensor Node) Type of phenomenon (kind of measurement sent according IDAS dictionary) Identifier of the SANET generating the observation (OUTSMART in our case) GPS coordinates of the Sensor Node Type of Data (according OUTSMART descriptions), Unit of Measurement and Data value Please, for further information, don't hesitate to contact me BR El 19/02/2013 18:55, Ferm?n Gal?n M?rquez escribi?: Hi, @SantanderUC: we have a Google Doc in which we are capturing information related with the integration needed for the demo at https://docs.google.com/document/d/11bD-tWz7CA1iVww1Kteob3kf8DJ0AZRNr6pQhJnY-LI/edit. I have added a section at the end named "Context/Event Data model". Could you fulfill that section with the entities/attributes information that will be used during the demo, please? (Tell me your google ids, so I can provide you modification permissions on the shared document). Thanks! Best regards, ------ Ferm?n El 19/02/2013 18:22, fano.ramparany at orange.com escribi?: Hi Tali and all, Javier and Ignacio (in cc) are our OUTSMART/Santander UC domain experts. They know what info about the lamp is contained in the event message produced by IDAS (I think IDAS plays the role of the IoT Gateway in the FIWARE core platform architecture). I think that for the same reason we need adapters between CEP and P/S we need an adapter between IDAS and P/S. Probably this adapter will do the job of POSTing a contextUpdate message in the appropriate format (including the ?scope? attribute) to the P/S. In parallel to this ?design/implementation? discussion, we are defining a realistic scenario within OUTSMART that will fit to this demo. Regards, Fano De : fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Tali Yatzkar-Haham Envoy? : mardi 19 f?vrier 2013 16:06 ? : Ferm?n Gal?n M?rquez Cc : fiware-data at lists.fi-ware.eu Objet : Re: [Fiware-data] CEP<->P/S Hi Fermin and all, Thank you for putting this summary doc. I updated the CEP part, and gave example for event based on the event you used. I have a question - In the example you gave of a Lamp entity, can a context event include any subset of attributes of the Lamp entity in every context event? does it send all the attributes in any context event? I remember that there used to be a "scope" attribute that defined the list of attributes that are sent. Could you please elaborate? 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: Ferm?n Gal?n M?rquez To: fiware-data at lists.fi-ware.eu, Date: 19/02/2013 02:10 PM 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. ________________________________ 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 -- Ignacio Elicegui Maestro Grupo de Ingenier?a Telem?tica - DICOM Universidad de Cantabria Plaza de la Ciencia S/N - Planta -2 S232 39005 Santander - Cantabria - Espa?a Tel: +34 942 200 919 ext. 505 Fax: +34 942 201 488 mailto: IEMaestro at tlmat.unican.es web: http://www.tlmat.unican.es _________________________________________________________________________________________________________________________ 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: From peretz at athenaiss.com Sun Feb 24 17:43:12 2013 From: peretz at athenaiss.com (Peretz Gurel) Date: Sun, 24 Feb 2013 18:43:12 +0200 Subject: [Fiware-data] CEP<->P/S In-Reply-To: <4540_1361552643_5127A502_4540_2802_1_06a89940-165f-4451-a6f1-fc91c06912b2@PEXCVZYH01.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> Message-ID: <0CF527EE434D2E4BB398B0F67FB0A8983251D645E9@xchg.mertree.mer.co.il> 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 01CE12BE.A725ED90] and within IBM on: [cid:image002.jpg at 01CE12BE.A725ED90] [cid:image003.jpg at 01CE12BE.A725ED90] [cid:image004.gif at 01CE12BE.A725ED90] 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. -------------- 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: