From ralli at tid.es Thu Feb 2 16:33:09 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 02 Feb 2012 16:33:09 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki References: <4F2A45FD.8080607@tid.es> Message-ID: Dear Colleagues, Find in an e-mail below, some guidelines from Juanjo in order to get as much as possible a uniform structure of D2.3 - Architecture contributions. Generally speaking, it should be easy to adapt any previous contribution inspired in the CORBA example and the "Query Broker" example from Siemens highlighted in our meeting in Madrid. Peter, Andreas, I made myself some work to adapt your "Query Broker". I also copied the pictures from the Data Wiki to this one (so they can be displayed in the new location too). Please, check and change according to Juanjo's suggestions (in case you think that particular one would need further work. For me it should be fine except I did not find a nice way to make the "Basic concepts" section without changing the subsections presentation/storyline which seems to be fine). https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker#Introduction_to_the_Query_Broker_GE Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 2 de febrero de 2012 09:14:53 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki Hi all, I have published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions This how-to will be enriched during the following days, including a complete example. However, I believe it contains already enough detailed instructions about how to proceed. Of course, your feedback is welcome. Answering your concrete questions may help to enrich the how-to material. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ 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 2 23:58:45 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 02 Feb 2012 23:58:45 +0100 Subject: [Fiware-data] Next Data/Context Conference Call will be on Thu next week In-Reply-To: <8ACCF214-D374-4614-9674-4CB5B85E28DD@tid.es> References: <8ACCF214-D374-4614-9674-4CB5B85E28DD@tid.es> Message-ID: <02A87C25-F760-43B3-9F8E-DDF16782E8C7@tid.es> Dear WP colleagues, As agreed in our meeting in Madrid we've moved Data/Context follow up calls to Thursdays so we will not have any tomorrow. However, I will be sending some e-mails during the morning to speed up some pending actions so We keep on delivering what other WPs in the project need from us. Thanks in advance for your cooperation on this, Best regards, ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 Mon Feb 6 16:28:12 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 06 Feb 2012 16:28:12 +0100 Subject: [Fiware-data] [Fiware-wpa] [Fiware-wpl] Access to Testbed wiki (and other wikis in general) In-Reply-To: References: <4F27AC03.7010805@tid.es> Message-ID: <7F464003-2315-4C98-B715-F7EC754A5ECC@tid.es> Stefano, I've just deleted the rows highlighted in red and changed to black those that are fine. Some of them were names of assets actually belonging to Apps chapter, not to Data (we guess some previous copy&paste). Additionally, there were a number of Data assets that will not be provided in a first phase or whose development is not considered at all so they've been deleted too. Therefore, WP6 table should be ready now: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Testbed_Fact_Finding_Investigation Thanks for your patience and reminders. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 31/01/2012, a las 14:04, stefano de panfilis escribi?: dear miguel, thank you for your help. I take this opportunity to recall the wpl/wpa team colleagues that full answers are due by the end of this week (3rd Feb)!!! thank you for your help. stefano 2012/1/31 Miguel Carrillo >: Dear all, I see messages complaining about not having access to the Testbed wiki. This has also happened in the past with other wikis. Let us try to throw some light. Most of you are already members of the forge. Once you are on the forge, you can apply for access to individual projects. You can be a member of one, two, three... projects at the same time. In summary, to be able to access the Testbed wiki, you need to be a member of the project "FI-WARE Testbed" in the forge. This is not granted by default to the contributors from other WPs, each one has to apply for it (how would the Testbed team know who is in and who's not!). The way to apply for access in a project is described on this tutorial: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_join_a_FI-WARE_project_in_FusionForge If you request to join the Testbed project, please specify why you apply for access in the free textbox. Those who are not already on the forge must previously join the forge and then apply for acces to the Testbed project. The tutorial to join the forge is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_a_FusionForge_account Hope this helps Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ 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 stefano.depanfilis at eng.it Mon Feb 6 16:37:03 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 6 Feb 2012 16:37:03 +0100 Subject: [Fiware-data] [Fiware-wpa] [Fiware-wpl] Access to Testbed wiki (and other wikis in general) In-Reply-To: <7F464003-2315-4C98-B715-F7EC754A5ECC@tid.es> References: <4F27AC03.7010805@tid.es> <7F464003-2315-4C98-B715-F7EC754A5ECC@tid.es> Message-ID: dear carlos, thank you very much for your collaboration! ciao, stefano 2012/2/6 CARLOS RALLI UCENDO : > Stefano, > > I've just deleted the rows highlighted in red and changed to black those > that are fine. > > Some of them were names of assets actually belonging to Apps chapter, not to > Data (we guess some previous copy&paste). > Additionally, there were a number of Data assets that will not be provided > in a first phase or whose development is not considered at all so they've > been deleted too. > > Therefore, WP6 table should be ready now: > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Testbed_Fact_Finding_Investigation > > > Thanks for your patience and reminders. > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ------------------------------------------------------------------------------------------------------------------------ > > El 31/01/2012, a las 14:04, stefano de panfilis escribi?: > > dear miguel, > > thank you for your help. > > I take this opportunity to recall the wpl/wpa team colleagues that > full answers are due by the end of this week (3rd Feb)!!! > > thank you for your help. > stefano > > 2012/1/31 Miguel Carrillo : > > Dear all, > > > I see messages complaining about not having access to the Testbed wiki. This > > has also happened in the past with other wikis. Let us try to throw some > > light. > > > Most of you are already members of the forge. Once you are on the forge, you > > can apply for access to individual projects. You can be a member of one, > > two, three... projects at the same time.? In summary, to be able to access > > the Testbed wiki, you need to be a member of the project "FI-WARE Testbed" > > in the forge.? This is not granted by default to the contributors from other > > WPs, each one has to apply for it (how would the Testbed team know who is in > > and who's not!). The way to apply for access in a project is described on > > this tutorial: > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_join_a_FI-WARE_project_in_FusionForge > > > If you request to join the Testbed project, please specify why you apply for > > access in the free textbox. > > > Those who are not already on the forge must previously join the forge and > > then apply? for acces to the Testbed project. The tutorial to join the forge > > is here: > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_a_FusionForge_account > > > Hope this helps > > > Miguel > > > -- > > ---------------------------------------------------------------------- > > ????_/ ?????????_/_/ ????????????????????Miguel Carrillo Pacheco > > ???_/ ??_/ ????_/ ?_/ ??Telef?nica ??????Distrito Telef?nica > > ??_/ _/_/_/ ??_/ ??_/ ??Investigaci?n y ?Edifico Oeste 1, Planta 9 > > ?_/ ??_/ ????_/ ?_/ ????Desarrollo ??????Ronda de la Comunicaci?n S/N > > _/ ?????????_/_/ ????????????????????????28050 Madrid (Spain) > > ?????????????????????????????????????????Tel: ?(+34) 91 483 26 77 > > > ?????????????????????????????????????????e-mail: mcp at tid.es > > > Follow FI-WARE on the net > > > Website: ?http://www.fi-ware.eu > > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > Twitter: ?http://twitter.com/Fiware > > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > ---------------------------------------------------------------------- > > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > > situado m?s abajo. > > This message is intended exclusively for its addressee. We only send and > > receive email on the basis of the terms set out at > > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > > Fiware-wpl mailing list > > Fiware-wpl at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware-wpl > > > > > > -- > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-068307-4295 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567 > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa > > > > ________________________________ > 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 -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 From ralli at tid.es Mon Feb 6 17:15:50 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 06 Feb 2012 17:15:50 +0100 Subject: [Fiware-data] Where to contribute for D2.3 Architecture deliverable Message-ID: <15EF8906-699D-4E4B-A476-4C8FD0FCF6DA@tid.es> Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 Tue Feb 7 17:47:39 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 7 Feb 2012 17:47:39 +0100 Subject: [Fiware-data] Next Data/Context Conference Call will be on Thu next week In-Reply-To: <02A87C25-F760-43B3-9F8E-DDF16782E8C7@tid.es> References: <8ACCF214-D374-4614-9674-4CB5B85E28DD@tid.es> <02A87C25-F760-43B3-9F8E-DDF16782E8C7@tid.es> Message-ID: Dear All, i cannot participate in the calls Tuesdays and Thursdays morning before 11:00CET. Sorry for this late notice. Best Regards, Boris 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: Thursday, February 02, 2012 11:59 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Next Data/Context Conference Call will be on Thu next week Dear WP colleagues, As agreed in our meeting in Madrid we've moved Data/Context follow up calls to Thursdays so we will not have any tomorrow. However, I will be sending some e-mails during the morning to speed up some pending actions so We keep on delivering what other WPs in the project need from us. Thanks in advance for your cooperation on this, Best regards, ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From ralli at tid.es Wed Feb 8 09:50:53 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 08 Feb 2012 09:50:53 +0100 Subject: [Fiware-data] Tomorrow's Data/Context call conference Message-ID: Dear WP colleagues, As we said last week we are having our data/context follow up calls on Thursdays. Our proposal is to have them normally In the afternoons, though tomorrow -being the 1st one - we may change it if needed. Let's fix it for 15:00-16:30 CET. The agenda will be: - D2.3 status - Completing Standards contribs - UC projects tickets Please let me know who is attending and who has problems at that specific time (plus alternatives). Best regards, El 06/02/2012, a las 17:15, "CARLOS RALLI UCENDO" > escribi?: Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 jose.fuentesl at atosresearch.eu Wed Feb 8 15:49:58 2012 From: jose.fuentesl at atosresearch.eu (Jose Maria Fuentes Lopez) Date: Wed, 8 Feb 2012 15:49:58 +0100 Subject: [Fiware-data] FW: Tomorrow's Data/Context call conference Message-ID: <899C2CC8F93F6C46A7187C81852522934A7C9B@INTMAIL03.es.int.atosorigin.com> FYI From: Jose Maria Fuentes Lopez Sent: mi?rcoles, 08 de febrero de 2012 11:10 To: 'CARLOS RALLI UCENDO' Subject: RE: [Fiware-data] Tomorrow's Data/Context call conference Dear Carlos, I have reduce timetable so I?m usually leaving at 15:00 and I will not be able to join confcalls in the afternoon. Regarding tomorrows confcall, I?m available all the morning starting from 9:00 am. Best regards, Chema Fuentes. 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: mi?rcoles, 08 de febrero de 2012 9:51 To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Tomorrow's Data/Context call conference Dear WP colleagues, As we said last week we are having our data/context follow up calls on Thursdays. Our proposal is to have them normally In the afternoons, though tomorrow -being the 1st one - we may change it if needed. Let's fix it for 15:00-16:30 CET. The agenda will be: - D2.3 status - Completing Standards contribs - UC projects tickets Please let me know who is attending and who has problems at that specific time (plus alternatives). Best regards, El 06/02/2012, a las 17:15, "CARLOS RALLI UCENDO" escribi?: Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Feb 9 13:05:46 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 09 Feb 2012 13:05:46 +0100 Subject: [Fiware-data] Tomorrow's Data/Context call conference (Details) In-Reply-To: References: Message-ID: Dear WP Colleagues, Find here some details for the call: - Webex: Topic: Fi-ware Data/Context Conf Call Date: Thursday, February 9, 2012 Time: 3:30 pm, Europe Time (Paris, GMT+01:00) Meeting Number: 969 547 593 Meeting Password: 1234abcD https://telefonica.webex.com/telefonica-en/j.php?ED=190780132&UID=0&PW=NM2QzNjhkZjRk&RT=MiMyMw%3D%3D - Powownow: We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf - Minutes on Google docs (please access&contribute, that's the better way to have a common understanding on the APs related to your assets and you!) (Sorry, I will be providing this link some minutes before the call) Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 08/02/2012, a las 09:50, CARLOS RALLI UCENDO escribi?: Dear WP colleagues, As we said last week we are having our data/context follow up calls on Thursdays. Our proposal is to have them normally In the afternoons, though tomorrow -being the 1st one - we may change it if needed. Let's fix it for 15:00-16:30 CET. The agenda will be: - D2.3 status - Completing Standards contribs - UC projects tickets Please let me know who is attending and who has problems at that specific time (plus alternatives). Best regards, El 06/02/2012, a las 17:15, "CARLOS RALLI UCENDO" > escribi?: Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 boris.moltchanov at telecomitalia.it Thu Feb 9 14:46:45 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 9 Feb 2012 14:46:45 +0100 Subject: [Fiware-data] Tomorrow's Data/Context call conference (Details) In-Reply-To: References: Message-ID: Carlos, once we have selected and decided week-day/time-slot may you please also send out an Outlook event and/or Google Calendar one? I believe this will reach everyone in the list and automatically set it as audio-call basis for months. Of course I mean announcement with the finally selected week-day/time if this one 15:30 is not yet final. Thanks. Best Regards, Boris 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: Thursday, February 09, 2012 1:06 PM To: Fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Tomorrow's Data/Context call conference (Details) Dear WP Colleagues, Find here some details for the call: - Webex: Topic: Fi-ware Data/Context Conf Call Date: Thursday, February 9, 2012 Time: 3:30 pm, Europe Time (Paris, GMT+01:00) Meeting Number: 969 547 593 Meeting Password: 1234abcD https://telefonica.webex.com/telefonica-en/j.php?ED=190780132&UID=0&PW=NM2QzNjhkZjRk&RT=MiMyMw%3D%3D - Powownow: We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf - Minutes on Google docs (please access&contribute, that's the better way to have a common understanding on the APs related to your assets and you!) (Sorry, I will be providing this link some minutes before the call) Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 08/02/2012, a las 09:50, CARLOS RALLI UCENDO escribi?: Dear WP colleagues, As we said last week we are having our data/context follow up calls on Thursdays. Our proposal is to have them normally In the afternoons, though tomorrow -being the 1st one - we may change it if needed. Let's fix it for 15:00-16:30 CET. The agenda will be: - D2.3 status - Completing Standards contribs - UC projects tickets Please let me know who is attending and who has problems at that specific time (plus alternatives). Best regards, El 06/02/2012, a las 17:15, "CARLOS RALLI UCENDO" > escribi?: Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From ralli at tid.es Thu Feb 9 15:46:19 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 09 Feb 2012 15:46:19 +0100 Subject: [Fiware-data] Tomorrow's Data/Context call conference (Details) In-Reply-To: References: Message-ID: Here you are: https://docs.google.com/document/d/1OK3boX33n6F6TBStQVCu6sIHp1Jdf38jzF-Co9RmHQU/edit Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 09/02/2012, a las 13:05, CARLOS RALLI UCENDO escribi?: Dear WP Colleagues, Find here some details for the call: - Webex: Topic: Fi-ware Data/Context Conf Call Date: Thursday, February 9, 2012 Time: 3:30 pm, Europe Time (Paris, GMT+01:00) Meeting Number: 969 547 593 Meeting Password: 1234abcD https://telefonica.webex.com/telefonica-en/j.php?ED=190780132&UID=0&PW=NM2QzNjhkZjRk&RT=MiMyMw%3D%3D - Powownow: We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf - Minutes on Google docs (please access&contribute, that's the better way to have a common understanding on the APs related to your assets and you!) (Sorry, I will be providing this link some minutes before the call) Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 08/02/2012, a las 09:50, CARLOS RALLI UCENDO escribi?: Dear WP colleagues, As we said last week we are having our data/context follow up calls on Thursdays. Our proposal is to have them normally In the afternoons, though tomorrow -being the 1st one - we may change it if needed. Let's fix it for 15:00-16:30 CET. The agenda will be: - D2.3 status - Completing Standards contribs - UC projects tickets Please let me know who is attending and who has problems at that specific time (plus alternatives). Best regards, El 06/02/2012, a las 17:15, "CARLOS RALLI UCENDO" > escribi?: Dear WP Colleagues, Some of you came back to me asking whether they should be placing D2.3 contribs in Fiware Data Wiki or Fiware private Wiki. The links are: FI-WARE private Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3) or FI-WARE Data Wiki (https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_Data/Context_Contrib) If you want to chose one at this point, the best is to use the first (Fi-WARE private Wiki) as all other chapters can access then our deliverable and it will be the final placeholder before making it public. However, if you are using the second one, go on, don't lose time on this. Just let me know you are doing so for your particular asset and I will be copying your contents from time to time to keep it updated. If you were using Data Wiki and you prefer to change at this point: (1) make a copy in the fi-ware private wiki (2) replace the content in Data by a link to the private one (note that linking in the other way round wouldn't be useful as other chapters will not be able to access Data Wiki). Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 boris.moltchanov at telecomitalia.it Thu Feb 9 16:32:25 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 9 Feb 2012 16:32:25 +0100 Subject: [Fiware-data] word2wiki Message-ID: http://www.microsoft.com/download/en/details.aspx?pf=true&id=12298 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Thu Feb 9 18:48:48 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 09 Feb 2012 18:48:48 +0100 Subject: [Fiware-data] Canceled: Data/Context WP coordination Message-ID: <4FE737A7257DB84C8CB36B7DFAFCC1CB7F16260A61@EXCLU2K7.hi.inet> We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: 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: 4636 bytes Desc: not available URL: From ralli at tid.es Mon Feb 13 12:10:56 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 13 Feb 2012 12:10:56 +0100 Subject: [Fiware-data] Please, update your Architecture contribs asap Message-ID: Hi All, Juanjo is performing a review on the contents this afternoon in order to send comments to each chapter. If you have been working off-line and have some newer contrib, please update it before 14h CET so his review is useful for you. Thanks for your efforts. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 From ralli at tid.es Tue Feb 14 11:42:04 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 14 Feb 2012 11:42:04 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) Message-ID: Dear WP colleagues, You can find the minutes of the previous meeting in fi-ware docman at: https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_Minutes.doc I assume all comments are consolidated as we used google docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1R3CNTLhDM/edit Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. Thanks for your participation and efforts to improve/conclude D2.3 contribs, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 -------------- A non-text attachment was scrubbed... Name: 20120216_Data-Context_Minutes_v1.doc Type: application/msword Size: 40960 bytes Desc: 20120216_Data-Context_Minutes_v1.doc URL: From ralli at tid.es Wed Feb 15 11:21:24 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 15 Feb 2012 11:21:24 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpa] IMPORTANT: Reference example on Main Interactions section to be followed References: <4F3B8055.1050703@tid.es> Message-ID: <882C850A-1A7C-4F6A-8472-C88070989581@tid.es> Please, read carefully Juanjo's e-mail below and try to address it asap regarding your D2.3 contribs. Bear in mind that several Use Case projects and other 3rd parties have expressed a significant interest on this public document as a way for their developers/architects to understand your assets details and interrelation. Thanks for your cooperation to improve this key deliverable. Best regards. Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 15 de febrero de 2012 10:52:21 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpa] IMPORTANT: Reference example on Main Interactions section to be followed Hi, While reviewing the different drafts of the "Architecture Description" chapters, I have found that many of the descriptions of "Main Interactions" is quite poor. We have developed a good reference example for this kind of sections. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 If you have followed the reference example provided initially based on the CORBA specifications as well as the guidelines already provided, you should not have anything too far from this, but unfortunately, I'm discovering that this is not the case in many of the GE Architecture Descriptions. The guidelines for editing the "Architecture Description" deliverable have been updated accordingly. I encourage you to review them carefully and add any question on teh FAQ section you may have. You may find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ 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 15 15:18:06 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 15 Feb 2012 15:18:06 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) In-Reply-To: References: Message-ID: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> Please, do not forget to access the googledocs (mentioned in the e-mail below) & fill in with the expected attendees from your side for tomorrow's call. BTW, does any partner volunteer to discuss its UC project tickets tomorrow? (otherwise we will start a per-asset round to clarify groups of tickets and status). Marcus, do we consider Siemens tickets discussion as concluded with what we did last week? (I understand we finally processed all them). Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 14/02/2012, a las 11:42, CARLOS RALLI UCENDO escribi?: > Dear WP colleagues, > > You can find the minutes of the previous meeting in fi-ware docman at: > https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_Minutes.doc > I assume all comments are consolidated as we used google docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). > > > -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. > > In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. > At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. > > https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1R3CNTLhDM/edit > > Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. > > Thanks for your participation and efforts to improve/conclude D2.3 contribs, > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ------------------------------------------------------------------------------------------------------------------------ > > > <20120216_Data-Context_Minutes_v1.doc> 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 From boris.moltchanov at telecomitalia.it Wed Feb 15 16:41:10 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Feb 2012 16:41:10 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) In-Reply-To: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> References: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> Message-ID: I'm available to discuss the tickets assigned to me (P/S GE) in that time-slot tomorrow. There are few ones and I hope I'll be pretty brief, thus we may have another person/GE as a back-up. BR, B -----Original Message----- 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: Wednesday, February 15, 2012 3:18 PM To: Fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) Please, do not forget to access the googledocs (mentioned in the e-mail below) & fill in with the expected attendees from your side for tomorrow's call. BTW, does any partner volunteer to discuss its UC project tickets tomorrow? (otherwise we will start a per-asset round to clarify groups of tickets and status). Marcus, do we consider Siemens tickets discussion as concluded with what we did last week? (I understand we finally processed all them). Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 14/02/2012, a las 11:42, CARLOS RALLI UCENDO escribi?: > Dear WP colleagues, > > You can find the minutes of the previous meeting in fi-ware docman at: > > https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_M > inutes.doc I assume all comments are consolidated as we used google > docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). > > > -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. > > In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. > At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. > > > https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1 > R3CNTLhDM/edit > > Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. > > Thanks for your participation and efforts to improve/conclude D2.3 > contribs, Best regards, > -- > ---------------------------------------------------------------------- > -------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ---------------------------------------------------------------------- > -------------------------------------------------- > > > <20120216_Data-Context_Minutes_v1.doc> 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 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. From marcus.laumer.ext at siemens.com Wed Feb 15 17:35:54 2012 From: marcus.laumer.ext at siemens.com (Laumer, Marcus) Date: Wed, 15 Feb 2012 17:35:54 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) In-Reply-To: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> References: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> Message-ID: <750211B1279EFC489DB5D8B39550E0741D6CA22DD2@DEMCHP99E15MSX.ww902.siemens.net> Hi Carlos, I think there is no need to discuss any tickets in detail anymore. We just have some general questions about ticket handling we would like to discuss in tomorrow's PhC: - When will Juanjo provide the new status 'Split' so that we can proceed to split them? - To whom should we assign tickets that will not be addressed by Siemens (currently assigned to you (Carlos) and issuers)? - How should we handle tickets in the tracker that can be (partly) fulfilled by the combination of two GEs, e.g., ticket #1048 (currently assigned to you (Carlos))? Best regards, Marcus -----Original Message----- 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, 15. Februar 2012 15:18 To: Fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) Please, do not forget to access the googledocs (mentioned in the e-mail below) & fill in with the expected attendees from your side for tomorrow's call. BTW, does any partner volunteer to discuss its UC project tickets tomorrow? (otherwise we will start a per-asset round to clarify groups of tickets and status). Marcus, do we consider Siemens tickets discussion as concluded with what we did last week? (I understand we finally processed all them). Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 14/02/2012, a las 11:42, CARLOS RALLI UCENDO escribi?: > Dear WP colleagues, > > You can find the minutes of the previous meeting in fi-ware docman at: > https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_Minutes.doc > I assume all comments are consolidated as we used google docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). > > > -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. > > In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. > At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. > > https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1R3CNTLhDM/edit > > Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. > > Thanks for your participation and efforts to improve/conclude D2.3 contribs, > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ------------------------------------------------------------------------------------------------------------------------ > > > <20120216_Data-Context_Minutes_v1.doc> 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 From boris.moltchanov at telecomitalia.it Wed Feb 15 17:44:19 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 15 Feb 2012 17:44:19 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) In-Reply-To: <750211B1279EFC489DB5D8B39550E0741D6CA22DD2@DEMCHP99E15MSX.ww902.siemens.net> References: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> <750211B1279EFC489DB5D8B39550E0741D6CA22DD2@DEMCHP99E15MSX.ww902.siemens.net> Message-ID: Adding to this list of topics regarding the last Marcus' point: - what is how-to manual for too much generic tickets that either includes a target GE + something that eventually might be assigned to future releases of target_G/non_Target_GE or target_GE + something_out_of_scope? I have few tickets like that. BR, B -----Original Message----- From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Laumer, Marcus Sent: Wednesday, February 15, 2012 5:36 PM To: CARLOS RALLI UCENDO Cc: Fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) Hi Carlos, I think there is no need to discuss any tickets in detail anymore. We just have some general questions about ticket handling we would like to discuss in tomorrow's PhC: - When will Juanjo provide the new status 'Split' so that we can proceed to split them? - To whom should we assign tickets that will not be addressed by Siemens (currently assigned to you (Carlos) and issuers)? - How should we handle tickets in the tracker that can be (partly) fulfilled by the combination of two GEs, e.g., ticket #1048 (currently assigned to you (Carlos))? Best regards, Marcus -----Original Message----- 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, 15. Februar 2012 15:18 To: Fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) Please, do not forget to access the googledocs (mentioned in the e-mail below) & fill in with the expected attendees from your side for tomorrow's call. BTW, does any partner volunteer to discuss its UC project tickets tomorrow? (otherwise we will start a per-asset round to clarify groups of tickets and status). Marcus, do we consider Siemens tickets discussion as concluded with what we did last week? (I understand we finally processed all them). Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 14/02/2012, a las 11:42, CARLOS RALLI UCENDO escribi?: > Dear WP colleagues, > > You can find the minutes of the previous meeting in fi-ware docman at: > > https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_M > inutes.doc I assume all comments are consolidated as we used google > docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). > > > -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. > > In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. > At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. > > > https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1 > R3CNTLhDM/edit > > Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. > > Thanks for your participation and efforts to improve/conclude D2.3 > contribs, Best regards, > -- > ---------------------------------------------------------------------- > -------------------------------------------------- > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ---------------------------------------------------------------------- > -------------------------------------------------- > > > <20120216_Data-Context_Minutes_v1.doc> 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 _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-data 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. From ralli at tid.es Wed Feb 15 18:03:58 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 15 Feb 2012 18:03:58 +0100 Subject: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) In-Reply-To: References: <0C373615-2C29-4CF0-BC1D-E856B1F47CD0@tid.es> Message-ID: Thanks Boris! Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 15/02/2012, a las 16:41, Moltchanov Boris escribi?: > I'm available to discuss the tickets assigned to me (P/S GE) in that time-slot tomorrow. There are few ones and I hope I'll be pretty brief, thus we may have another person/GE as a back-up. > > BR, > B > > -----Original Message----- > 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: Wednesday, February 15, 2012 3:18 PM > To: Fiware-data at lists.fi-ware.eu > Subject: Re: [Fiware-data] Data/Context Follow up conference call details (& previous one minutes link) > > Please, do not forget to access the googledocs (mentioned in the e-mail below) & fill in with the expected attendees from your side for tomorrow's call. > > BTW, does any partner volunteer to discuss its UC project tickets tomorrow? (otherwise we will start a per-asset round to clarify groups of tickets and status). > Marcus, do we consider Siemens tickets discussion as concluded with what we did last week? (I understand we finally processed all them). > > Thanks for your cooperation. > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > ------------------------------------------------------------------------------------------------------------------------ > > El 14/02/2012, a las 11:42, CARLOS RALLI UCENDO escribi?: > >> Dear WP colleagues, >> >> You can find the minutes of the previous meeting in fi-ware docman at: >> >> https://forge.fi-ware.eu/docman/view.php/9/805/20120209_Data-Context_M >> inutes.doc I assume all comments are consolidated as we used google >> docs for this. Siemens is not able to access googledocs, so you may review now, review and submit again as version 2, if needed (please with changes highlighted, if any). >> >> >> -> For this week's call, according to your previous feedback, we will start using our new regular slot: Thursday(s) 11:30-13:00 CET. >> >> In order to avoid more e-mails, I will keep all the call details (powownow, webex, etc) in the file linked below, that we will be using for the minutes. >> At this point, you can also see in that file a tentative agenda (and a row to make your suggestions - Do indicate who is making it, please). It might be great also if you register yourself as intended attendee in the "attendees list" at the begining with the tag "available" (as I did already). Once attending, you will just remove that tag and then we know you are already connected to the conference call as expected. >> >> >> https://docs.google.com/document/d/1D42eAYk4AmyQDxXBPjlyJWeDEY5Q-YT4o1 >> R3CNTLhDM/edit >> >> Note for Siemens: find attached in this mail the current googledoc file. You can send me suggestions for the agenda and intended attendees in a private e-mail, so I can fill in on your behalf. >> >> Thanks for your participation and efforts to improve/conclude D2.3 >> contribs, Best regards, >> -- >> ---------------------------------------------------------------------- >> -------------------------------------------------- >> Carlos Ralli Ucendo (ralli at tid.es) >> Cell: +34696923588 >> Twitter: @carlosralli >> 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 >> ---------------------------------------------------------------------- >> -------------------------------------------------- >> >> >> <20120216_Data-Context_Minutes_v1.doc> > > > 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 > > 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. > 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 From boris.moltchanov at telecomitalia.it Thu Feb 16 19:47:20 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 16 Feb 2012 19:47:20 +0100 Subject: [Fiware-data] reposrt of APs done and suggestion Message-ID: Dear Carlos, I've processed the APs assigned and agreed during the WP call today. I believe that there is no sense to write more about the Semantic Annotation then is already there, at least personally I do not see any additional value in any other text. I have also a suggestion - it will be very helpful, especially when we have the APs assigned "for_tomorrow" to upload immediately just after the call the minutes into the chapter private area in order to keep everything (docs, minutes, pics, etc.) in the same place hence very easy to find. The G docs is extremely efficient and easy to use during the call, not so easy to find right URI and open thought. Thanks! BR, B 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:00000000000000000000000000000001 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_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From e.fiware1 at tid.es Fri Feb 17 07:58:50 2012 From: e.fiware1 at tid.es (Grant Croker) Date: Fri, 17 Feb 2012 07:58:50 +0100 Subject: [Fiware-data] reposrt of APs done and suggestion In-Reply-To: References: Message-ID: <000301cced41$9a6af620$cf40e260$%fiware1@tid.es> Hi Boris, I've uploaded/created a space in our wiki to hold the links to the Google doc pages as well as a download in Word format for those that don't have access to Google.docs - see https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Main_Page#Meeting_Minutes. When I get some time I'll go through and add the minutes from earlier meetings. regards grant De: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] En nombre de Moltchanov Boris Enviado el: jueves, 16 de febrero de 2012 19:47 Para: CARLOS RALLI UCENDO CC: fiware-data at lists.fi-ware.eu Asunto: [Fiware-data] reposrt of APs done and suggestion Dear Carlos, I've processed the APs assigned and agreed during the WP call today. I believe that there is no sense to write more about the Semantic Annotation then is already there, at least personally I do not see any additional value in any other text. I have also a suggestion - it will be very helpful, especially when we have the APs assigned "for_tomorrow" to upload immediately just after the call the minutes into the chapter private area in order to keep everything (docs, minutes, pics, etc.) in the same place hence very easy to find. The G docs is extremely efficient and easy to use during the call, not so easy to find right URI and open thought. Thanks! BR, B 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:image001.gif at 01CCED49.9DACBA00]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: image001.gif Type: image/gif Size: 677 bytes Desc: not available URL: From ralli at tid.es Fri Feb 17 14:39:31 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 17 Feb 2012 14:39:31 +0100 Subject: [Fiware-data] Fwd: [Fiware-wpa] Deliverable on Architecture Description References: <4F3E54C4.505@tid.es> Message-ID: FYI ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (PDI) 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 ------------------------------------------------------------------------------------------------------------------------ Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA > Fecha: 17 de febrero de 2012 14:23:16 GMT+01:00 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Asunto: [Fiware-wpa] Deliverable on Architecture Description Hi all, I will be reviewing during the weekend the final draft that all chapter teams are expected to upload on the FI-WARE Private Wiki by EOB today. I will send a reasoned report by Monday morning about the results of that review. I assume there will be essentially three scenarios to report for a given chapter: 1. Contents of the chapter are mature enough and can be made public available, therefore transferred to the public Wiki. 2. Contents of the chapter are not mature enough but, implementing a number of quick changes, they can be transferred to the public Wiki by mid of next week 3. Contents of the chapter are immature and will require more work In cases 1, 2 I will also send a proposal on how to plan peer reviews that will have to be carried out once the contents are available on the public Wiki. In case 3, we will need to plan a dedicated confcall to plan the necessary APs to recover. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Mon Feb 20 10:06:04 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 20 Feb 2012 10:06:04 +0100 Subject: [Fiware-data] reposrt of APs done and suggestion In-Reply-To: <000301cced41$9a6af620$cf40e260$%fiware1@tid.es> References: <000301cced41$9a6af620$cf40e260$%fiware1@tid.es> Message-ID: <34112C60-1AC4-4DE8-9DB2-0F1ADB580C17@tid.es> Thanks Grant!, I have completed the whole list (at least with all the minutes of the conferences I have been in). Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 17/02/2012, a las 07:58, Grant Croker escribi?: Hi Boris, I?ve uploaded/created a space in our wiki to hold the links to the Google doc pages as well as a download in Word format for those that don?t have access to Google.docs - see https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Main_Page#Meeting_Minutes. When I get some time I?ll go through and add the minutes from earlier meetings. regards grant De: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] En nombre de Moltchanov Boris Enviado el: jueves, 16 de febrero de 2012 19:47 Para: CARLOS RALLI UCENDO CC: fiware-data at lists.fi-ware.eu Asunto: [Fiware-data] reposrt of APs done and suggestion Dear Carlos, I?ve processed the APs assigned and agreed during the WP call today. I believe that there is no sense to write more about the Semantic Annotation then is already there, at least personally I do not see any additional value in any other text. I have also a suggestion ? it will be very helpful, especially when we have the APs assigned ?for_tomorrow? to upload immediately just after the call the minutes into the chapter private area in order to keep everything (docs, minutes, pics, etc.) in the same place hence very easy to find. The G docs is extremely efficient and easy to use during the call, not so easy to find right URI and open thought. Thanks! BR, B 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. ________________________________ 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 21 13:00:08 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 21 Feb 2012 13:00:08 +0100 Subject: [Fiware-data] Data/Context Conference Call (Thu 10:30, Feb 23rd) Message-ID: <9384DD25-3374-47DC-9B32-94F509DC6DEB@tid.es> Dear WP Colleagues, As agreed in our previous call, we will have our weekly Data/Context PhC this Thursday 10:30 to 12:00. You may find all details plus the agenda in the Googledocs. As we did last week, please register yourself in this file as "(available)" (attendees list). Tentative Agenda is also available in that file, so you may include your suggestions as usual. https://docs.google.com/document/d/1wEqjuZGgwPyMQXSd9G0KDBR9Vq4ppW-BbH_CWt0rh6M/edit For those not able to access the on-line doc, I've attached the current file in this e-mail for your convenience. Should you have inputs/feedback, please do send an e-mail to me & I'll be glad to do it on your behalf. Thanks in advance for your availability & cooperation. Best regards. -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 -------------- A non-text attachment was scrubbed... Name: 20120223_Data-Context_Minutes_v1.doc Type: application/msword Size: 59904 bytes Desc: 20120223_Data-Context_Minutes_v1.doc URL: From boris.moltchanov at telecomitalia.it Tue Feb 21 18:01:51 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Tue, 21 Feb 2012 18:01:51 +0100 Subject: [Fiware-data] [Fiware-ngsi] [Fiware-iot] Comments on Exposure GE in IoT Chapter In-Reply-To: <8755F290097BD941865DC4245B335D2D08BA9118@DAPHNIS.office.hd> References: <4F3E556D.3030306@tid.es> <4F41FA34.6030607@tid.es> <3F4C11BC54A36642BFB5875D599F47BD0592D6AB@DEMUEXC013.nsn-intra.net> <4F425997.7060609@tid.es> <4F438507.8080500@tid.es> <8755F290097BD941865DC4245B335D2D08BA9118@DAPHNIS.office.hd> Message-ID: Dear All, Sorry for the long mail answering many (missed) conversations in one message. [intro] Sorry, I noticed that you're discussing the Pub/Sub, which is within the WP6 of FI-WARE where we all contributes and unfortunately backlogs are not used for this matter. [push vs pull] The "pull" from the broker down to the producers is not necessarily a "better" way then the "push". Why? Because in the mobile devices world the pull is impossible (no IP addresses assigned by default), in WSN world (what probably you mainly consider as current IoT) the RX (listening) is consuming more then TX (transmitting) at RF level (an experimental proven fact). However the last assumption depends on the protocol at the PHY level (with certain beckoning and T/CDMA techniques this problem could be overcome or mitigated). We in TI used the pull connections mainly for the classic IP/Internet world where we might have many things: servers, gateways (also those hiding or representing WSNs), proxies and so on. Expecting that all that IP world will send "stupidly" huge amount of data about myriad of entities in push mode towards the brokers is unrealistic and highly inefficient. [p/s ge/broker] Then, commenting on the email attached to the previous one (where, again, neither of the mailing list WP6 nor NGSI is included), those assumption 2a....etc. are mostly wrong! Maybe this is due to the weakness in the produced documentation (this is why it would be nice to have "judgments publicly in face and not "hidden" behind the back" :) ). There is no problem with the entities unless you don't need to resolve their identities. As I mentioned in one of the previous emails the entity resolver could be an external entity, the broker itself does not care about the entities but do about the scopes (information) and do forward the request to that producer handling that specific scope. Therefore the answer given by P/S broker will be unknown if the scope is unknown to the broker (no registered producer for that scope) or undefined coming from the producer if the entity doesn't exist or undefined. I hope this is clear. Well, this is correct that the broker is not aware and therefore does not pass any subscription to the IoT nodes because there was no interface defined at that level (south-bound) except the data representation ContextML over http get. I believe it wouldn't be a problem to specify that interface once we could derive a common one (if it is possible) as M2M or more detailed NGSI-like for IoT application domains or even simple application-/ (consumer-) packets tunneling (where the apps know the lower world and encapsulate "right" primitives into the payload to pass through the broker to the south-bound interface. But, again, once we *insert it into the backlog* and *discuss it publicly in WP6 where P/S GE is living*. The difficult stuff there to the low levels is a very heterogeneous IoT World , that might even have its own applications running on the WSN nodes and GWs! For sure the IoT world generically is very heterogeneous in difference from the IP Internet and mobile cell.phones devices moving towards IP thought. Therefore a solution might be a mix: a "representative" IoT level for any type of "native" mash IoT networks hidden to PO/S broker by their specific GWs, or "FI-WARE compliant" IoT supporting CQL (ContextML +REST or anything else agreed among partners and specified in FI-WARE?) Then the native WSN GWs with two Ifs one towards P/S and another towards WSN mash NWKs may interpret pull requests from the broker down to their serving nodes and vice versa transcode IoT low-level messages to the broker. Or broker may tunnel an encapsulated message from an application directly to the WSN "router" and then node, injecting directly into low level IoT and vice versa bypassing any interpretation and transcoding. Or in the first scenario with the IoT GW a "subscriptions" from the application (consumer) or from the P/S broker could be even transformed by the respective GW into programming of the WSN node, which will send back the info when needed (on thresholds, conditions, events, etc. specifically to the IoT application domain) [possible arch] A vertical cascading of NGSI from applications to singular IoT elements or nodes is inefficient (useless overlapping roles affecting for sure energy and time consumptions, increasing complexity, reducing robustness, etc.). I see the arch more well-structured if the high-level pub/sub (WP6) is eventually (no encapsulation) vertically converted into something lower level WSN or things specific (ZigBee, 6LowPAN, etc.) in a "vertical cascade". Then that lower tech level is taking care of its resources and peculiarities, including its respective gateway between north (P/S) and south (things) bounds. While at the horizontal level we might have a federation of the pub/subs working at the same level belonging to maybe different organizations or applications domains (operators, service providers, etc.) or even in subordinated cascading global (public)/local (personal) brokerage. If we will mix two aforementioned concepts or not clear in the arch concept I'm afraid we will waste our effort. Why we: a. don't try to understand what is the current asset in core of the P/S GE under WP6 chapter? If additional info is needed in order to understand it or if something is not clear, please ask to WP6. b. don't include what is missing or eventually incorrect with P/S GE into the WP6's backlog? Cheers, Boris [operative] a. This is not true that pull is easier then push for the IoT nodes if you consider the WSN sensor nodes. Do you ever know that the listening for the nodes is heavier then the sending (I mean RF circuitry where RX is consuming fore then TX), from energy point of view? It is sufficient to measure consumptions on circuitry. I did it 4 years ago when involved into WSN works. It we're talking about client-server IP arch e.g. where IP gateways involved I'm agree there is no need to push all sensors data over the GW to From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Tuesday, February 21, 2012 1:52 PM To: Juanjo Hierro; Martin Bauer Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] [Fiware-iot] Comments on Exposure GE in IoT Chapter Hi Juanjo, So you agree that pull-style communication is needed for IoT? - This is great, because we have the same opinion. :) And you say that "the architecture becomes much clearer if we just support this pull-style of communication"? - We are more than happy with that. :) Indeed it was the TID architectural proposal had which had introduced the push-style communication. However, the pub/sub GE does not fully support the pull-style interaction, as we have pointed out in our email from yesterday. (I attach the email for your reference.) Once again: This is a restriction of the pub/sub GE. It is not a restriction of NGSI-10. The simplest solution would therefore be to remove the pub/sub broker GE from the IoT backend. Then we only have one Thing-level interface that is exposed towards apps. And we have full support for pull-style communication. What do you think? Best regards Tobias From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 21. Februar 2012 12:51 To: Martin Bauer Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] [Fiware-iot] Comments on Exposure GE in IoT Chapter Hi Martin, You are putting restriction on usage of NGSI that are over-complicated the overall IoT Architecture. Among other things, forcing to have a cascade of two brokers implementing the NGSI-10 interfaces where you may have just one. The need for support a pull-style of communication between the a Pub/Sub Broker implementing the FI-WARE NGSI API is clear and this is something that seems to be proven not because TI's experience demonstrates this (and I guess this is something worth to consider) but because the design of architectures which may have similar requirements to those in IoT (i.e., need to capture context data from sources that may be pasive rather than active or have to safe power) would require this. Just consider an example of architecture where we may need to get context data elements from mobile devices. I have to confess that the first time I read the NGSI-10 spec I though that not that the fact it didn't support this pull-style of communication was a gap, but thought that we would just need to add such extension if there were a clear requirement to support it (I assumed we would find it sooner or later, but wanted to confirm it in real, rather than speculating) ... and this is what has happened. Sorry, I don't buy your arguments. The IoT Architecture becomes much clearer and cleaner if we just support this pull-style of communication within the FI-WARE NGSI API. As I have said, that would be a feature that would not only be relevant to ease the implementation of the IoT Architecture but would be also a feature that I envision would be rather useful in other scenarios. Added value no matter from what angle you analyze it. Last but not least, I'm afraid that support of this pully-style of communication would also be needed between Pub/Sub Brokers and Consumers. This may be needed to establish federation between the backend and gateways that support a FI-WARE NGSI-10 northbound interface for forwarding of events and may not want to be pushing events but rather react on demand. As for NGSI-9, I will send soon an email elaborating on the mismatch I have found regarding the interpretation about scope and semantics of the NGSI-9 interface. Best regards, -- Juanjo On 20/02/12 15:51, Martin Bauer wrote: Hi Juanjo, One short comment on the NGSI discussion - we are currently preparing an NEC answer to your other comments. - NGSI only defines interfaces, NOT an architecture of the respective enablers. - The NGSI interfaces are to be seen as external (northbound) interfaces of the enablers - the TI architecture for implementing a context enabler is only one possibility - anything is possible as long as the northbound interface implements the NGSI functionality - NGSI can, but does not have to be used to implement (internal) Context Producer components - internally any structures, interfaces and interactions can be used (and TI conceptually uses two different subsets of NGSI-10/9 to implement the respective interfaces with the Context Sources (NGSI-10 update) and Context Providers (subset of NGSI-10 query towards context provider, subset of NGSI-9 register towards Context Broker) - from an NGSI point of view, context providers could implement the full NGSI-10 interface and register their services with a context broker using NGSI-9 - from an NGSI point of view it is also fine to implement Context Sources that use the NGSI-10 update operations to publish information (but as mentioned above this is not the only way to do it and we do not consider this to be suitable for a number of IoT scenarios) Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Monday, February 20, 2012 3:33 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] [Fiware-iot] Comments on Exposure GE in IoT Chapter Hi Denes, The queryContext operation defined in OMA NGSI-10 is to be exported by the Publish/Subscribe Broker (in OMA NGSI referred as "Context Management component". Precisely the problem is that it is nowhere specified in OMA NGSI-10 that Context producers may export the queryContext operation. The current OMA NGSI-10 spec seems to work assuming that Context Brokers gather events because Context producers have invoked the updateContext on them. This means that only a push mode of communication is used between Context producers and Brokers (Context Management components). My understanding was that NEC mentioned this may be a drawback of any OMA-compliant Publish/Subscribe Broker implementation: experience idemonstrate that there are real scenarios where it would be highly desirable that Publish/Subscribe Brokers query Context producers (i.e., support a pull mode of communication) when the Context Producer is linked to a IoT resource running on a device, since this would avoid that such IoT resource were consuming energy pushing events when may not be necessary. It was also my understanding that NEC assumed that TI's implementation of NGSI would not support this pull style of communication between producers and Brokers. Interestingly enough, as I explained, I have found (I didn't know) that TI's implementation support this pull type of communication. I guess because they have faced similar scenarios to the ones described by NEC. TI has published a description of its current asset on From my point of view, this is the typical example of something in the OMA NGSI specs that needs to be changed and we had decided to change in FI-WARE leading to this notion of FI-WARE NGSI specs Cheers, -- Juanjo On 20/02/12 13:36, Bisztray, Denes (NSN - HU/Budapest) wrote: Hi Juajo, I just wanted to make a quick comment: the OMA NGSI-10 does have a queryContext operation that queries the value of a contextInformation supplied by the ContextProducer. Although we have not seen neither the specs nor the implementation of the TI NGSI-10, I wonder what is the novelty? Can you please be more specific what is missing from the OMA NGSI-10 operation? Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Monday, February 20, 2012 8:46 AM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Comments on Exposure GE in IoT Chapter Hi all, Please find below my comments on the Exposure GE. === (note 1: whenever I use the term "FI-WARE NGSI" I refer to the spec based on OMA NGSI we are going to support in FI-WARE which may differ from the OMA spec for good documented reasons. We will intend to fast-track the adoption of changes into OMA to generate an update of those specs that finally aligns with FI-WARE NGSI specs. "OMA NGSI" will be used to refer to the NGSI interface as currently specified in OMA. Whenever I use the term NGSI, without qualifying it, it is because it is in a statement that would apply both to OMA NGSI and FI-WARE NGSI. Note that a clarification like this should be introduced in the Architecture Description.) (note 2: In the FI-WARE Product Vision we introduced the term "IoT resource" an used it with preference to "device" which could mean many things and may lead to misinterpretation ... However, the current IoT Service Enablement Chapter Architecture uses the term "device" prominently ... Below, I use the term "IoT resource" rather than "device".) There is no need to define two cascade layers of the FI-WARE NGSI-10 interface, one exported by the "Thing-level API" part of the "exposure GE" and another one exported by the "Publish/Subscribe Broker GE" (no matter whether the reference implementation of this last GE is provided by Telecom Italia or not), making both "cascading layers" visible to applications. As far as I understand, NEC argued that such "cascading" would be necessary mostly because the OMA specifications didn't consider the possibility that the (Publish/Subscribe) broker exporting a OMA NGSI-10 interface implements the "query" operation so that it can, in turn, invoque a query, on a context producer. NEC pointed out this might be an issue in scenarios where it is more sensible to query IoT resources at device level instead of letting them be constantly notifying observations. However, the fact that such operation is not considered in OMA NGSI-10 specs may be consider a major usability gap of OMA specs and we don't need to feel constrained (trying to find an artificial workaround) whenever we face a gap in the specs as we have mentioned several times. We may simply decide that the FI-WARE NGSI-10 specification will include a "query" operation that a Publish/Subscribe Broker can invoke on Context Producers, provided such Context Producers have registered as exporting such operation. Interestingly enough, I have found out that Telecom Italia's implementation of NGSI includes this extension, probably because real-life applications have proven to request this (I guess for scenarios similar to those described by NEC when it raised the issue). On the other hand, as already explained a couple of times, there is no need to wrap access to the Things/Resource Configuration Management GE in order to provide the FI-WARE NGSI-9 interface. It can expose this directly to applications. This would be because entities handled at FI-WARE NGSI level may be either Things or IoT resources (at device-level). You may discover the existence of an entity that refers to an IoT resource and then deal directly with the interface exported by that IoT resource using the ETSI M2M API. Is anything wrong there ? Based on the comments above, a figure that may describe a target reference architecture for the backend may look as shown below. I have renamed the "Exposure GE" as "ETSI M2M Handler" because it wouldn't deal with exposing the NGSI APIs but indeed it would act as a bridge between the NGSI and M2M worlds (besides supporting Process Handling which probably would require further discussion). Indeed, I would be in favour of splitting the GE into two, so that the "Observation Handler", "Request Handler", "Process Handler" and "Semantic Handler" components are on one side, being part of the "ETSI M2M Handler GE", and the "Device-level API" component goes apart so that, together with the "Service Control GE" and the "Device Control GE", become a GE dealing with implementation of the ETSI M2M API. Note that the channel in red represents the "query" request that is missing in the OMA NGSI-10 spec and we should include in FI-WARE NGSI-10 specs [cid:image001.png at 01CCF0B8.2123BA20] Besides the above, I believe that a component dealing with self-registration of IoT resources may be required (I'm not sure if the ETSI M2M model supports that). Such component would deal with reception of messages from lower layers (IoT gateway or IoT resources at device-level) using ETSI M2M APIs linked to registration of IoT resources. ==== Best regards, -- Juanjo On 17/02/12 14:26, Juanjo Hierro wrote: Hi all, I just want to anticipate to you that I see several issues in the description of the Exposure GE. I will sent you a detailed analysis later this evening or tomorrow. Unfortunately, I cannot do it earlier. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 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: image001.png Type: image/png Size: 133941 bytes Desc: image001.png 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 TALI at il.ibm.com Thu Feb 23 07:35:06 2012 From: TALI at il.ibm.com (Tali Yatzkar-Haham) Date: Thu, 23 Feb 2012 08:35:06 +0200 Subject: [Fiware-data] Status summary of UC tickets assigned to CEP Message-ID: Carlos, A short summary of the status of the UC tickets assigned to CEP. Maybe, if time permits, we can discuss it in our meeting today. #1120 - Realtime Exchange - "Exchange in real time a large amounts of data collected and processed in high speed mode" Very general and seems to be related to several GEs: Massive Data Gathering, BigData, Pub/Sub, CEP. Maybe this can be split to all of these GEs - each explaining what its baseline capabilities are. #491 - Complex calculation - "We refer that in a context with massive sensors providing information the system has to implement the appropriate computation capacity for coping with huge amount of data, i.e. the system will gather (all) data from different sources (sensor networks), process it and extract (and present to user) elaborated information related to the service/s required. Furthermore, this processing has to be elaborated according to the contextual information provided by adjacent infrastructure. E.g. based on the current light intensity, atmospheric pressure and humidity measured, the system will "process" fog. It "uses" the weather forecast to verify it. The car traffic sensors provides high car presence, so the system "detects" a traffic jam. A user starts its car. Based on all this processed info, and "knowing" the context of the user (common destinations), the system will automatically send the route to user's navigator which avoid the traffic jam and the fog." This ticket, similar to #1120, talks about several GEs working together - Massive Data gathering, BigData, Pub/Sub, CEP. #1088 - Geospatial alerts - "I as a service provider need to request help/attention from users depending on their position, and on the coordinates associated with the data." Status: I asked for clarifications from the issuer #1121 - Distributed database - "To provide storage systems for large amount of information, distributed database system (local, regional, etc.) " As we already agreed, it is not relevant to CEP - I assigned it to Carlos under Data-New GE 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Feb 23 12:24:24 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 23 Feb 2012 12:24:24 +0100 Subject: [Fiware-data] Minutes of Today's call Message-ID: <18153584-A2C5-404F-B9EF-4F74F6596A73@tid.es> Dear WP Colleagues, Thanks for your feedback and efforts to complete the comments discussed today before the new deadline. Let me attach here the minutes (snapshot of the current googledocs). As usual, I will upload them tomorrow morning to the Wiki (so we give some extra time for additional comments in the googledoc this afternoon) Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 -------------- A non-text attachment was scrubbed... Name: 20120223_Data-Context_Minutes_v1-1.doc Type: application/msword Size: 60416 bytes Desc: 20120223_Data-Context_Minutes_v1-1.doc URL: From boris.moltchanov at telecomitalia.it Thu Feb 23 12:46:27 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Thu, 23 Feb 2012 12:46:27 +0100 Subject: [Fiware-data] Minutes of Today's call In-Reply-To: <18153584-A2C5-404F-B9EF-4F74F6596A73@tid.es> References: <18153584-A2C5-404F-B9EF-4F74F6596A73@tid.es> Message-ID: Don't forget we have still pending from the last call the TI's backlog discussion proposed and not yet done. Just as a comment to the last APs within the minutes. One organizational suggestion to have: (MS Outlook + Google Calendar)_meeeting_Request + Dedicated session in FI-WARE Data Chapter mngmnt part with: 1. when (weekly, on Thursdays from 10:30am 1.5h duration) 2. tools: powwownow: a. phone numbers for partners countries (we are just few so less thus 10 numbers directly there + the international number available for anyone from everywhere) + link to the pdf in the network; b. meeting passcode for powwownow session; c. webex sharing direct link and passcode (for newcomers); 3. Link to the g.doc area (not direct link to the documents) but to the area (if possible) with minutes. In alternative we may have one unique per WP6 calls living document incrementally registering everything, at the same link, instead of many documents with their dedicated links. 4. the same as point 3 above for internal fi-ware servers e.g. forge uploading area (or .doc to wiki converted pages) where the same minutes document(s) is (are) converted in order to have it in our official site independently of 3rd party (G). it will really greatly improve the logistic especially for those involved in many activities, with tight agendas and maybe extensively travelling, but always connected with iPhone/PC/Android devices (they have such features as pushing reminders to users even with no connectivity). Thanks! B -----Original Message----- 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: Thursday, February 23, 2012 12:24 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Today's call Dear WP Colleagues, Thanks for your feedback and efforts to complete the comments discussed today before the new deadline. Let me attach here the minutes (snapshot of the current googledocs). As usual, I will upload them tomorrow morning to the Wiki (so we give some extra time for additional comments in the googledoc this afternoon) Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 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. From e.fiware1 at tid.es Thu Feb 23 16:49:51 2012 From: e.fiware1 at tid.es (Grant Croker) Date: Thu, 23 Feb 2012 16:49:51 +0100 Subject: [Fiware-data] Minutes of Today's call In-Reply-To: References: <18153584-A2C5-404F-B9EF-4F74F6596A73@tid.es> Message-ID: <000001ccf242$c78f6a90$56ae3fb0$%fiware1@tid.es> Hi Boris, I've collected the information in https://forge.fi-ware.eu/plugins/mediawiki/wiki/data/index.php/Meeting_Admin istrivia, use the "PDF Version" link on the left hand side to generate a PDF of the page that you can store offline. If you need additional information there, feel free to edit the page. thanks Grant -----Mensaje original----- De: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] En nombre de Moltchanov Boris Enviado el: jueves, 23 de febrero de 2012 12:46 Para: CARLOS RALLI UCENDO; fiware-data at lists.fi-ware.eu Asunto: Re: [Fiware-data] Minutes of Today's call Don't forget we have still pending from the last call the TI's backlog discussion proposed and not yet done. Just as a comment to the last APs within the minutes. One organizational suggestion to have: (MS Outlook + Google Calendar)_meeeting_Request + Dedicated session in FI-WARE Data Chapter mngmnt part with: 1. when (weekly, on Thursdays from 10:30am 1.5h duration) 2. tools: powwownow: a. phone numbers for partners countries (we are just few so less thus 10 numbers directly there + the international number available for anyone from everywhere) + link to the pdf in the network; b. meeting passcode for powwownow session; c. webex sharing direct link and passcode (for newcomers); 3. Link to the g.doc area (not direct link to the documents) but to the area (if possible) with minutes. In alternative we may have one unique per WP6 calls living document incrementally registering everything, at the same link, instead of many documents with their dedicated links. 4. the same as point 3 above for internal fi-ware servers e.g. forge uploading area (or .doc to wiki converted pages) where the same minutes document(s) is (are) converted in order to have it in our official site independently of 3rd party (G). it will really greatly improve the logistic especially for those involved in many activities, with tight agendas and maybe extensively travelling, but always connected with iPhone/PC/Android devices (they have such features as pushing reminders to users even with no connectivity). Thanks! B -----Original Message----- 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: Thursday, February 23, 2012 12:24 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] Minutes of Today's call Dear WP Colleagues, Thanks for your feedback and efforts to complete the comments discussed today before the new deadline. Let me attach here the minutes (snapshot of the current googledocs). As usual, I will upload them tomorrow morning to the Wiki (so we give some extra time for additional comments in the googledoc this afternoon) Best regards, -- ---------------------------------------------------------------------------- -------------------------------------------- Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 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. _______________________________________________ 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 From ralli at tid.es Thu Feb 23 17:29:11 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 23 Feb 2012 17:29:11 +0100 Subject: [Fiware-data] Minutes of Today's call In-Reply-To: References: <18153584-A2C5-404F-B9EF-4F74F6596A73@tid.es> Message-ID: <04A2E12F-3D22-4265-A204-1D432DC72BFB@tid.es> Boris, Ok, I'll try to remember for our next call. My colleague Grant took an action on the rest and we'll try to improve some procedures as you suggest to make your life easier. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli 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 ------------------------------------------------------------------------------------------------------------------------ El 23/02/2012, a las 12:46, Moltchanov Boris escribi?: > Don't forget we have still pending from the last call the TI's backlog discussion proposed and not yet done. Just as a comment to the last APs within the minutes. > > One organizational suggestion to have: > > (MS Outlook + Google Calendar)_meeeting_Request + Dedicated session in FI-WARE Data Chapter mngmnt part with: > 1. when (weekly, on Thursdays from 10:30am 1.5h duration) > 2. tools: powwownow: > a. phone numbers for partners countries (we are just few so less thus 10 numbers directly there + the international number available for anyone from everywhere) + link to the pdf in the network; > b. meeting passcode for powwownow session; > c. webex sharing direct link and passcode (for newcomers); > 3. Link to the g.doc area (not direct link to the documents) but to the area (if possible) with minutes. In alternative we may have one unique per WP6 calls living document incrementally registering everything, at the same link, instead of many documents with their dedicated links. > 4. the same as point 3 above for internal fi-ware servers e.g. forge uploading area (or .doc to wiki converted pages) where the same minutes document(s) is (are) converted in order to have it in our official site independently of 3rd party (G). > > it will really greatly improve the logistic especially for those involved in many activities, with tight agendas and maybe extensively travelling, but always connected with iPhone/PC/Android devices (they have such features as pushing reminders to users even with no connectivity). > > Thanks! > > B > > -----Original Message----- > 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: Thursday, February 23, 2012 12:24 PM > To: fiware-data at lists.fi-ware.eu > Subject: [Fiware-data] Minutes of Today's call > > Dear WP Colleagues, > > Thanks for your feedback and efforts to complete the comments discussed today before the new deadline. > > Let me attach here the minutes (snapshot of the current googledocs). As usual, I will upload them tomorrow morning to the Wiki (so we give some extra time for additional comments in the googledoc this afternoon) > > > Best regards, > -- > ------------------------------------------------------------------------------------------------------------------------ > Carlos Ralli Ucendo (ralli at tid.es) > Cell: +34696923588 > Twitter: @carlosralli > 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 > > 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. > 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 From jhierro at tid.es Tue Feb 28 13:18:35 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 Feb 2012 13:18:35 +0100 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Message-ID: <4F4CC61B.2010806@tid.es> Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: * "Context Elements" (which certainly map to the concepts defined in OMA) * "Data Elements" (= Context Elements but without EntityId) * "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris.moltchanov at telecomitalia.it Wed Feb 29 19:04:40 2012 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Wed, 29 Feb 2012 19:04:40 +0100 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE In-Reply-To: <4F4CC61B.2010806@tid.es> References: <4F4CC61B.2010806@tid.es> Message-ID: Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I'm not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO's attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be "encoded" into the EO's entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a "third" module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same "third" module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this "third" component. Let's have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: * "Context Elements" (which certainly map to the concepts defined in OMA) * "Data Elements" (= Context Elements but without EntityId) * "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 GUYSH at il.ibm.com Wed Feb 29 20:27:14 2012 From: GUYSH at il.ibm.com (Guy Sharon) Date: Wed, 29 Feb 2012 21:27:14 +0200 Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE In-Reply-To: References: <4F4CC61B.2010806@tid.es> Message-ID: Hi all, "Third" module responsibility of conversion - this could be done by implementing specific input and output adapters of our CEP engine These adapters support JMS meaning we can subscribe to a topic or listen to a queue for incoming events and we can publish to a topic or send to a queue outgoing events \ complex events. These adapters also support REST as clients. Meaning we can REST GET events from a RESTfull service as incoming events to CEP and we can REST POST events to a RESTfull service as outgoing \ complex events Regards, Guy Sharon Manager, Event-based Middleware & Solutions 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: Moltchanov Boris To: Juanjo Hierro Cc: "fiware-data at lists.fi-ware.eu" Date: 29/02/2012 20:04 Subject: Re: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Sent by: fiware-data-bounces at lists.fi-ware.eu Hi Juanjo, Ok. Got your point and never used it differently. Sorry if sometimes seemed differently. I would confirm that the PubSub based on the context broker is unable to handle any request without an valuated entityID notation. Thus, as stated from very beginning and discussed with Guy and as you suggested (after conversation with Carlo during the last f2f) we have to comply with the context data structure (Within the vision document). Otherwise the query, subscription and entity resolution all based on the context broker will not work (confirmation from Telecom Italia developers). Therefore regarding the third point (Event Objects) of your email below the PubSub shall receive EventsObjects, and then eventually republishing them to the consumers, with an entityID and will provide to anyone CEP included the context data elements with entityIDs. You have suggested, if I?m not wrong, to put this enityID either fixed or fixed but configurable. I suggest, as discussed with Guy and tried to explain in the call, that we derive the entityID from the EO?s attributes if there is at least one. If there is no one a fixed entityID such as entityID=CEP shall be introduces. And viceversa an entityID coming from the PubSub into the CEP might be ?encoded? into the EO?s entity attribute element. However both such conversions are out of scope of the current components and shall be performed by a ?third? module that will accomplish an EO into the context element (EO(event,opt.entityID) -> context(entityID, scope=event) and viceversa will rebuild an EO from a context element (context(entityID,scope)->EO(scope+attr.entityID)). Moreover, the same ?third? module could perform subscription to the PubSub for the events/scopes that the CEP needs to derive the EO, as far as, if I remember well, the CEP is unable to perform the subscription and shall be feeded (pushed) by the events or contexts_as_events, Guy confirm? And the PubSub does not perform subscription on itself, but on behalf of a consumer. There may be no explicit specific consumer for feeding the CEP, thus this subscription task to the PubSub on behalf of the CEP will be taken by this ?third? component. Let?s have a closer look to this proposed architectural/functional vision in tomorrow AC. Best Regards, Boris From: fiware-data-bounces at lists.fi-ware.eu [ mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Tuesday, February 28, 2012 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: [Fiware-data] PLEASE: Regarding integration between Pub/Sub Broker GE and the CEP GE Hi Boris, PLEASE, while making your proposal for the solution on how to map concepts between the Pub/Sub Broker GE and CEP pleas DO FOLLOW the terms and definitions proposed in the FI-WARE Product Vision: "Context Elements" (which certainly map to the concepts defined in OMA) "Data Elements" (= Context Elements but without EntityId) "Event Objects": the programming structure that will be used by the CEP into which Context Elements and Data Elements should be mapped. Let's try to avoid the term "Event" which may introduce confusion and doesn't add to much the technical discussion which is indeed about how to map between the data structures listed above (the term Event can be used but should then be under the definition provided in the FI-WARE Product Vision). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: