From mev at tid.es Mon Jun 3 09:05:46 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 03 Jun 2013 07:05:46 +0000 Subject: [Fiware-wpa] webinars - update - request for action Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89051FD7@EX10-MB2-MAD.hi.inet> Dear Partners, Let me a few comments reminding of issues around the webinars: 1. There are 5 sessions with no wrap up, please, provide feedback so that we know whether they took place and how many attendees [cid:image001.png at 01CE6037.B3DE2130] [cid:image002.png at 01CE6037.B3DE2130] [cid:image003.png at 01CE6037.B3DE2130] [cid:image004.png at 01CE6037.B3DE2130] [cid:image005.png at 01CE6038.366002E0] 2. Please, be aware there're a number of webinars scheduled for tomorrow: 9 sessions, please, advertise them on FIWARE twitter 3. Please, don't forget about scheduling those still missing: 14 GE Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4994 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 4319 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 4244 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 3467 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 3430 bytes Desc: image005.png URL: From mcp at tid.es Mon Jun 3 10:32:19 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 03 Jun 2013 10:32:19 +0200 Subject: [Fiware-wpa] Link for the minutes today Message-ID: <51AC5493.60102@tid.es> Dear all, I anticipate the link. Work in progress, still editing :) https://docs.google.com/document/d/1R2dOqbpmWG3Uj6JQ5X6HQtFbMaFJu9X-l_OC_GCHj8k/edit?pli=1# BR 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 From jhierro at tid.es Mon Jun 3 11:28:32 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Jun 2013 11:28:32 +0200 Subject: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review In-Reply-To: <51A6F867.70305@tid.es> References: <51A6F867.70305@tid.es> Message-ID: <51AC61C0.5040107@tid.es> Hi all, Based on recent discussions on the matter, all WPLs must please take care of the following APs regarding the FI-WARE Catalogue: * make sure that already existing entries linked to GEis in your template are complete, i.e., all tabs completed and based on the defined guidelines (see below) * make sure that new GEis planned for Release 2 create their entry For the defined template: * Please follow the updated guidelines available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * Check the description of the WireCloud GEi as a reference (although it should change to fully align with the guidelines, it is still a good reference): http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud 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) Coordinator and 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 stefano.depanfilis at eng.it Mon Jun 3 11:32:54 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 3 Jun 2013 11:32:54 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Attendee list and ID numbers In-Reply-To: <51A8A716.8050409@tid.es> References: <51A8A716.8050409@tid.es> Message-ID: dear Miguel, for sure i miss something here. btw, i confirm my attendance to the review and rehearsal. indeed i'll be in brussels since sunday evening. if you need myid (but i guess you have it since previous times) i'll send it again, no problem. ciao, stefano 2013/5/31 Miguel Carrillo > Dear all, > > After receving a complaint from SAP I have decided to delete the column > with the ID numbers. I have kept a private copy of the ones already on > the table so I do not need to collect those. If anyone else adds his > name on the table let me know and send me your ID number (or passport) > privately > > Best regards, > > 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 > https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From manieri at eng.it Mon Jun 3 11:40:25 2013 From: manieri at eng.it (Andrea Manieri) Date: Mon, 03 Jun 2013 11:40:25 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Attendee list and ID numbers In-Reply-To: References: <51A8A716.8050409@tid.es> Message-ID: <51AC6489.7090703@eng.it> I do confirm as well. A. Il 03/06/2013 11:32, stefano de panfilis ha scritto: > dear Miguel, > for sure i miss something here. > btw, i confirm my attendance to the review and rehearsal. indeed i'll > be in brussels since sunday evening. > if you need myid (but i guess you have it since previous times) i'll > send it again, no problem. > ciao, > stefano > > > 2013/5/31 Miguel Carrillo > > > Dear all, > > After receving a complaint from SAP I have decided to delete the > column > with the ID numbers. I have kept a private copy of the ones already on > the table so I do not need to collect those. If anyone else adds his > name on the table let me know and send me your ID number (or passport) > privately > > Best regards, > > 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 > https://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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 3 13:37:18 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Jun 2013 13:37:18 +0200 Subject: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review In-Reply-To: <51AC61C0.5040107@tid.es> References: <51A6F867.70305@tid.es> <51AC61C0.5040107@tid.es> Message-ID: <51AC7FEE.4010100@tid.es> Hi, For those who have not been able to attend the call this morning: Miguel has an AP (deadline today evening) to send a description of what is going to be the new approval/revision process for entries in the FI-WARE Catalogue. I have asked him to come with a proposal that tries to avoid remaining a bottle-neck. This may come at the price of allowing some entries to be published with some errors in it, but we hope we'll be able to detect and fix them. In the meantime, please submit all your proposed changes on existing entries or new entries in the FI-WARE Catalogue. Cheers, -- Juanjo On 03/06/13 11:28, Juanjo Hierro wrote: Hi all, Based on recent discussions on the matter, all WPLs must please take care of the following APs regarding the FI-WARE Catalogue: * make sure that already existing entries linked to GEis in your template are complete, i.e., all tabs completed and based on the defined guidelines (see below) * make sure that new GEis planned for Release 2 create their entry For the defined template: * Please follow the updated guidelines available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * Check the description of the WireCloud GEi as a reference (although it should change to fully align with the guidelines, it is still a good reference): http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud 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) Coordinator and 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 thorsten.sandfuchs at sap.com Mon Jun 3 14:08:47 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 3 Jun 2013 12:08:47 +0000 Subject: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review In-Reply-To: <51AC7FEE.4010100@tid.es> References: <51A6F867.70305@tid.es> <51AC61C0.5040107@tid.es> <51AC7FEE.4010100@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610A01CB@DEWDFEMB11A.global.corp.sap> As nobody seem to outline what has changed in these "updated guidelines", here is my shot: "Main changes" in this updated version: 1. How to apply the right "Terms and Condition" statements - there are new guidelines (at least to me they are new) which seem to date back to November 2011 - linked on as doc-file https://forge.fi-ware.eu/docman/view.php/27/2540/FI-WARE+Use+Terms+and+Conditions+12-11-20.docx 2. suggested text for how open specifications are linked-back from the catalogue 3. updated format for providing instance information and service endpoints are there other major changes to the guidelines that somebody sees? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 3. Juni 2013 13:37 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review Hi, For those who have not been able to attend the call this morning: Miguel has an AP (deadline today evening) to send a description of what is going to be the new approval/revision process for entries in the FI-WARE Catalogue. I have asked him to come with a proposal that tries to avoid remaining a bottle-neck. This may come at the price of allowing some entries to be published with some errors in it, but we hope we'll be able to detect and fix them. In the meantime, please submit all your proposed changes on existing entries or new entries in the FI-WARE Catalogue. Cheers, -- Juanjo On 03/06/13 11:28, Juanjo Hierro wrote: Hi all, Based on recent discussions on the matter, all WPLs must please take care of the following APs regarding the FI-WARE Catalogue: * make sure that already existing entries linked to GEis in your template are complete, i.e., all tabs completed and based on the defined guidelines (see below) * make sure that new GEis planned for Release 2 create their entry For the defined template: * Please follow the updated guidelines available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * Check the description of the WireCloud GEi as a reference (although it should change to fully align with the guidelines, it is still a good reference): http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud 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) Coordinator and 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 jhierro at tid.es Mon Jun 3 16:07:05 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Mon, 03 Jun 2013 14:07:05 +0000 Subject: [Fiware-wpa] FI-WARE review preparation (continuation) Message-ID: <936DECD07EB54B4BAA44E7B823EC894184E4979F@EX10-MB2-MAD.hi.inet> When: Wednesday, June 05, 2013 3:30 PM-5:00 PM. (UTC+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* We will continue the review preparation (last point we didn't cover in previous confcall was coverage of checkpoint 11c) 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: 4088 bytes Desc: not available URL: From jhierro at tid.es Mon Jun 3 17:21:10 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Jun 2013 17:21:10 +0200 Subject: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A01CB@DEWDFEMB11A.global.corp.sap> References: <51A6F867.70305@tid.es> <51AC61C0.5040107@tid.es> <51AC7FEE.4010100@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD664610A01CB@DEWDFEMB11A.global.corp.sap> Message-ID: <51ACB466.5070508@tid.es> The guidelines for the "Use Terms and Conditions" have not changed and, yes, they are from november 2012 (not 2011 :-) and indeed most of the entries followed them. However, we will carry out a second review. An enhanced description of what should go in each tab is provided. And, when suitable, I have provided some example text so that we don't end with a myriad of variants. It should be rather straightforward for a FI-WARE GEi for which an already complete version was already available. Only few changes would be needed in their case. Cheers, -- Juanjo On 03/06/13 14:08, Sandfuchs, Thorsten wrote: As nobody seem to outline what has changed in these "updated guidelines", here is my shot: "Main changes" in this updated version: 1. How to apply the right "Terms and Condition" statements - there are new guidelines (at least to me they are new) which seem to date back to November 2011 - linked on as doc-file https://forge.fi-ware.eu/docman/view.php/27/2540/FI-WARE+Use+Terms+and+Conditions+12-11-20.docx 2. suggested text for how open specifications are linked-back from the catalogue 3. updated format for providing instance information and service endpoints are there other major changes to the guidelines that somebody sees? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 3. Juni 2013 13:37 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] TASK FORCE regarding the FI-WARE catalogue before next project review Hi, For those who have not been able to attend the call this morning: Miguel has an AP (deadline today evening) to send a description of what is going to be the new approval/revision process for entries in the FI-WARE Catalogue. I have asked him to come with a proposal that tries to avoid remaining a bottle-neck. This may come at the price of allowing some entries to be published with some errors in it, but we hope we'll be able to detect and fix them. In the meantime, please submit all your proposed changes on existing entries or new entries in the FI-WARE Catalogue. Cheers, -- Juanjo On 03/06/13 11:28, Juanjo Hierro wrote: Hi all, Based on recent discussions on the matter, all WPLs must please take care of the following APs regarding the FI-WARE Catalogue: * make sure that already existing entries linked to GEis in your template are complete, i.e., all tabs completed and based on the defined guidelines (see below) * make sure that new GEis planned for Release 2 create their entry For the defined template: * Please follow the updated guidelines available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * Check the description of the WireCloud GEi as a reference (although it should change to fully align with the guidelines, it is still a good reference): http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud 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) Coordinator and 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: From mev at tid.es Mon Jun 3 18:21:46 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 03 Jun 2013 16:21:46 +0000 Subject: [Fiware-wpa] webinars - 9 scheduled for 4.June Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905230B@EX10-MB2-MAD.hi.inet> Dear Partners, I've just market green the webinars scheduled for tomorrow. There are 9 sessions. Please, follow the guidelines - it's important to advertise them properly http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_inform_and_adversite_webinars_of_GE Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Jun 3 20:16:54 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 03 Jun 2013 20:16:54 +0200 Subject: [Fiware-wpa] If you want to attend the review ... Message-ID: <51ACDD96.8000402@tid.es> Dear all, Just a reminder. You have to put your name here (be conscious that I will not do it for anyone, even if you send me an email): * https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?pli=1# And then you send me the ID card number privately by email. Those who put the ID number before removing it from the table do not need to send it to me, I already took it from there. Those who fail to do this will not be able to come join the review. There are names I still miss on the list. Deadline: June, 5 Thanks, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 4 08:29:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Jun 2013 08:29:02 +0200 Subject: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments Message-ID: <51AD892E.4000408@tid.es> Hi, I have completed a first draft of part B of the form to be delivere to the EC elaborating on FI-WARE achievements. Please provide your comments before tomorrow noon. Please place them under the sections we have created "Comments by " and don't edit the existing draft (unless to fix a typo). Don't hesitate to involve members of your chapters if you find it suitable. I will resume editing of the rest of sections in the form later this evening. It would be nice if someone volunteers to provide some input there. Filling the form was not a task just for Telefonica to complete. It should be considered a cooperative effort !!! 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) Coordinator and 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 From jhierro at tid.es Tue Jun 4 09:51:52 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Jun 2013 09:51:52 +0200 Subject: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments In-Reply-To: <51AD892E.4000408@tid.es> References: <51AD892E.4000408@tid.es> Message-ID: <51AD9C98.6070307@tid.es> Hi, You should know already, but just in case I remind you the URL of the document where we are drafting the contents of the form: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit 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) Coordinator and 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 On 04/06/13 08:29, Juanjo Hierro wrote: Hi, I have completed a first draft of part B of the form to be delivere to the EC elaborating on FI-WARE achievements. Please provide your comments before tomorrow noon. Please place them under the sections we have created "Comments by " and don't edit the existing draft (unless to fix a typo). Don't hesitate to involve members of your chapters if you find it suitable. I will resume editing of the rest of sections in the form later this evening. It would be nice if someone volunteers to provide some input there. Filling the form was not a task just for Telefonica to complete. It should be considered a cooperative effort !!! 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) Coordinator and 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 https://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 jhierro at tid.es Tue Jun 4 10:01:28 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Jun 2013 10:01:28 +0200 Subject: [Fiware-wpa] [Fiware-ga] Creation of new WP as a result of incorporatingbeneficiaries of the 2nd Open Call In-Reply-To: References: <1369242099348.391269701@boxbe> Message-ID: <51AD9ED8.4050207@tid.es> Hi, Just an update on this. Based on the inputs received by several of you, we will go for creating this new WP/chapter but the activities considered in the FI-INMEDIA proposal will be integrated in the Data/Context Management chapter, where they will staty together with those linked to the Compressed-domain Video Analysis GE. Therefore, the new WP/chapter will be focused on Advanced Middleware and Web-based User Interfaces. Of course, we will incorporate references to the need to coordinate their work with that of other chapters. 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) Coordinator and 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 On 22/05/13 19:54, stefano de panfilis wrote: dear juanjo, i basically do agree, but for the sake of better consistency i do suggest to keep the two ges fi-inmedia and Compressed Domain Video Analysis together. in fact the fi-inmedia was born and agreed at the level of the fi-ppp ab to extend and complement with what already specified and provided by the Compressed Domain Video Analysis ge. keeping them separate, i mean in two different wps, migth generate inconsistencies and/or overlaps. so either both in the data chapter or both in the new wp. the argument of size of a wp you put forward is a bit articial in the sense that if we believe a new chapter needs to be in the overall fi-ware architecture than the size per se does not matter at all while keeping things together in an almost unconsistent way foir sure migth generate incomprehensions as well as communication and exploiation issues. so my proposal is to very much welcome the new wp, but also to keep together the content geis well defined in the data chapter. ciao, stefano 2013/5/22 Juanjo Hierro > [Boxbe] [http://www.boxbe.com/stfopen?tc_serial=14203782183&tc_rand=626565837&utm_source=stf&utm_medium=email&utm_campaign=ANNO_AFA&utm_content=001] You chose to allow Juanjo Hierro (jhierro at tid.es) even though this message failed authentication Click to disallow Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) 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) Coordinator and 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-ga mailing list Fiware-ga at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-ga -- 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 ________________________________ 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 jhierro at tid.es Tue Jun 4 10:27:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Jun 2013 10:27:25 +0200 Subject: [Fiware-wpa] Information about how to handle the "OIL" release for the minutes and distribution? In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A2027@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610A2027@DEWDFEMB11A.global.corp.sap> Message-ID: <51ADA4ED.5070403@tid.es> Hi, I have added the following paragraph to the minutes our last joint WPLs/WPAs follow-up confcall: * We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. I would suggest that you share it with members of your chapter. We will send an email elaborating on the matter (approach, examples of quality measures to be considered, etc) once we finalize the 2nd project review. 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) Coordinator and 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 thorsten.sandfuchs at sap.com Tue Jun 4 12:31:12 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 4 Jun 2013 10:31:12 +0000 Subject: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments In-Reply-To: <51AD9C98.6070307@tid.es> References: <51AD892E.4000408@tid.es> <51AD9C98.6070307@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610A268F@DEWDFEMB11A.global.corp.sap> Hi Juanjo, others that might be able to comment, Is a components of v2.3 be needed to have an entry in part A of this list? Thanks for clarifying /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 4. Juni 2013 09:52 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments Hi, You should know already, but just in case I remind you the URL of the document where we are drafting the contents of the form: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit 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) Coordinator and 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 On 04/06/13 08:29, Juanjo Hierro wrote: Hi, I have completed a first draft of part B of the form to be delivere to the EC elaborating on FI-WARE achievements. Please provide your comments before tomorrow noon. Please place them under the sections we have created "Comments by " and don't edit the existing draft (unless to fix a typo). Don't hesitate to involve members of your chapters if you find it suitable. I will resume editing of the rest of sections in the form later this evening. It would be nice if someone volunteers to provide some input there. Filling the form was not a task just for Telefonica to complete. It should be considered a cooperative effort !!! 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) Coordinator and 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 https://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 jhierro at tid.es Tue Jun 4 14:38:17 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Jun 2013 14:38:17 +0200 Subject: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A268F@DEWDFEMB11A.global.corp.sap> References: <51AD892E.4000408@tid.es> <51AD9C98.6070307@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD664610A268F@DEWDFEMB11A.global.corp.sap> Message-ID: <51ADDFB9.9020808@tid.es> During our confcall, we reached the agreement of placing there (in the form) only information about FI-WARE GEis that would match to a published entry in the FI-WARE Catalogue. That way, the link to tabs in entries that we make will work. If you manage to publish entries in the FI-WARE Catalogue corresponding to new GEis that will be delivered in 2.3, then you could provide info about those GEis in the form. We will send the form by the end of this week, so it really depends on whether you manage to publish information about those GEis in the FI-WARE Catalogue during this week. We will inform the EC that we will send them an updated version of the form by end of July, which should incorporate info about all FI-WARE GEis that will be delivered in Release 2, which will have an entry in the FI-WARE Catalogue by that date. Hope this answers the question. 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) Coordinator and 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 On 04/06/13 12:31, Sandfuchs, Thorsten wrote: Hi Juanjo, others that might be able to comment, Is a components of v2.3 be needed to have an entry in part A of this list? Thanks for clarifying /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 4. Juni 2013 09:52 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-wpa] Part B of form to be delivered to the EC elaborating on FI-WARE achievements available for comments Hi, You should know already, but just in case I remind you the URL of the document where we are drafting the contents of the form: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit 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) Coordinator and 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 On 04/06/13 08:29, Juanjo Hierro wrote: Hi, I have completed a first draft of part B of the form to be delivere to the EC elaborating on FI-WARE achievements. Please provide your comments before tomorrow noon. Please place them under the sections we have created "Comments by " and don't edit the existing draft (unless to fix a typo). Don't hesitate to involve members of your chapters if you find it suitable. I will resume editing of the rest of sections in the form later this evening. It would be nice if someone volunteers to provide some input there. Filling the form was not a task just for Telefonica to complete. It should be considered a cooperative effort !!! 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) Coordinator and 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 https://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 ________________________________ 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 mcp at tid.es Tue Jun 4 18:51:28 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 04 Jun 2013 18:51:28 +0200 Subject: [Fiware-wpa] Populating the catalogue Message-ID: <51AE1B10.4050504@tid.es> Dear all, After a bit of struggling we have delivered WP8 - this completes the set of deliverables associated to the SW. Now we can look into the catalogue. As Juanjo anticipated, the reference is: ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write and a good example, kindly modified today by the UPM to be 100% compliant is: ? http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud (use this one as a template and you will be safe) This is how we are going to proceed: 1) I will go entry by entry blindly approving all the ones for GEs in R1 (with no review). I will start right now. 2) Talk to your teams and a. Ask them to update all the catalogue entries for entries in R1 - if they were redelivered in R2, modify accordingly b. Ask them also to create new the new GEis. Agree with them to create a subset of the new ones or maybe all. Up to you. Insist a lot on reading the guidelines and using wirecloud as a good example. Please avoid the mess of non-compliances that we had to face in many installation manuals, etc. mostly caused by not reading or ignoring the guidelines. We can use our time better. c. Please send me the list of new GEi from R2 that you are adding by the end of tomorrow Deadline for all this : end of thursday 6/06/2013 Then we will review the ones in R1 and ask for urgent changes if needed. As many of them are present in R1 and in R2 I will never be completely sure of what I am approving but let us get out of this paralysing situation! I expect the messages by the end of Thursday confirming the GEis from R2 that you are adding. On previous iterations for any of the docs, reviews, etc. I had to chase up people one by one (with exceptions) and waste hours and hours for each step. This is not a serious behaviour. Your responsibility is very high and we cannot be so inefficient, particularly when we have a review looming upon us. In summary, ACTION POINTS ? AP on GE owners: update GEis from R1 on the catalogue (deadline 6/06/2013) ? AP on GE owners: create (or update) a subset or all the GEis in R2 on the catalogue (on GE owners - deadline 6/06/2013) ? AP on WPL: please circulate this info immediately! ? AP on WPL: send me an email with the new GEi from R2 on the catalogue (deadline: 6/06/2013) ? AP on me: approve pending edits from GEis in R1 (deadline: tomorrow at noon - 12am) - I'll try to have irt sooner, starting now! Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Wed Jun 5 07:58:24 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 05 Jun 2013 05:58:24 +0000 Subject: [Fiware-wpa] webinars - daily update Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905255D@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you of webinars for today: ? Scheduled: 1 - Apps ? Update status: 4 - All belong to Security ? Schedule Pending: 30 sessions - 12-Security,4 - IoT, 8-I2ND, Cloud - 5, Apps-1 Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Wed Jun 5 09:16:03 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 05 Jun 2013 09:16:03 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Platform for FI-WARE Webinars In-Reply-To: <51A49A51.2010703@eng.it> References: <51A49A51.2010703@eng.it> Message-ID: <51AEE5B3.7070206@eng.it> Dear partners, I remind you about the possibility to attend to this webinars. Please circulate it again to WPs. Best Regards, Davide On 28/05/2013 13:51, Davide Dalle Carbonare wrote: > Dear parters, > in order to provide FI-WARE webinars I notify you about the > possibility of using the MeshMe.tv platform made available by UPM. > > To understand how this platform works and how to use it, > It's possible to attend to a dedicated presentation on these dates: > > 1) Wednesday 5th of June from 14h to 15h > 2) Thursday 6th of June from 14h to 15h > > To facilitate the organization of these sessions, please, confirm your > attendance by sending a message to both: > - Juan Quemada Vives > - Abel Carril > > To enter the webinar session click on: > http://www.mashme.tv/M/2qvRiO?mode=1 > > Requirements for accessing the platform: > A browser which supports HTML5 must be used. > This includes the last versions of Chrome, Firefox, Opera, > Internet Explorer 9 or 10, etc. > > @WPLs, please, circulate this message in your WP mailing lists > in order to involve all the potential users. > > Thank you and > Kind Regards, > Davide > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > From mcp at tid.es Wed Jun 5 09:37:31 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 05 Jun 2013 09:37:31 +0200 Subject: [Fiware-wpa] Populating the catalogue In-Reply-To: <51AE1B10.4050504@tid.es> References: <51AE1B10.4050504@tid.es> Message-ID: <51AEEABB.6010601@tid.es> Hi, I finally managed to finish yesterday so all the GEi edites in R1 should be approved now. Check and come back to me if you miss any. Best regards, Miguel El 04/06/2013 18:51, Miguel Carrillo escribi?: Dear all, After a bit of struggling we have delivered WP8 - this completes the set of deliverables associated to the SW. Now we can look into the catalogue. As Juanjo anticipated, the reference is: ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write and a good example, kindly modified today by the UPM to be 100% compliant is: ? http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud (use this one as a template and you will be safe) This is how we are going to proceed: 1) I will go entry by entry blindly approving all the ones for GEs in R1 (with no review). I will start right now. 2) Talk to your teams and a. Ask them to update all the catalogue entries for entries in R1 - if they were redelivered in R2, modify accordingly b. Ask them also to create new the new GEis. Agree with them to create a subset of the new ones or maybe all. Up to you. Insist a lot on reading the guidelines and using wirecloud as a good example. Please avoid the mess of non-compliances that we had to face in many installation manuals, etc. mostly caused by not reading or ignoring the guidelines. We can use our time better. c. Please send me the list of new GEi from R2 that you are adding by the end of tomorrow Deadline for all this : end of thursday 6/06/2013 Then we will review the ones in R1 and ask for urgent changes if needed. As many of them are present in R1 and in R2 I will never be completely sure of what I am approving but let us get out of this paralysing situation! I expect the messages by the end of Thursday confirming the GEis from R2 that you are adding. On previous iterations for any of the docs, reviews, etc. I had to chase up people one by one (with exceptions) and waste hours and hours for each step. This is not a serious behaviour. Your responsibility is very high and we cannot be so inefficient, particularly when we have a review looming upon us. In summary, ACTION POINTS ? AP on GE owners: update GEis from R1 on the catalogue (deadline 6/06/2013) ? AP on GE owners: create (or update) a subset or all the GEis in R2 on the catalogue (on GE owners - deadline 6/06/2013) ? AP on WPL: please circulate this info immediately! ? AP on WPL: send me an email with the new GEi from R2 on the catalogue (deadline: 6/06/2013) ? AP on me: approve pending edits from GEis in R1 (deadline: tomorrow at noon - 12am) - I'll try to have irt sooner, starting now! Best regards, 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jun 5 14:15:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Jun 2013 14:15:23 +0200 Subject: [Fiware-wpa] REMINDER about confcall this afternoon and little delay of 15 mins Message-ID: <51AF2BDB.4010001@tid.es> Hi all, I remind you all that we will have a continuation meeting regarding the review preparation this afternoon. I'm afraid that I might be 15 mins late. So let's start at 15:15 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) Coordinator and 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 From thierry.nagellen at orange.com Wed Jun 5 14:16:06 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 5 Jun 2013 12:16:06 +0000 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins In-Reply-To: <51AF2BDB.4010001@tid.es> References: <51AF2BDB.4010001@tid.es> Message-ID: <23096_1370434567_51AF2C07_23096_186_1_976A65C5A08ADF49B9A8523F7F81925C0F2D79@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Juanjo Your meeting invitation starts at 3:30PM not 3PM so it should be ok BR Thierry -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: mercredi 5 juin 2013 14:15 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins Hi all, I remind you all that we will have a continuation meeting regarding the review preparation this afternoon. I'm afraid that I might be 15 mins late. So let's start at 15:15 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) Coordinator and 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. From jhierro at tid.es Wed Jun 5 15:05:11 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Jun 2013 15:05:11 +0200 Subject: [Fiware-wpa] [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins In-Reply-To: <23096_1370434567_51AF2C07_23096_186_1_976A65C5A08ADF49B9A8523F7F81925C0F2D79@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <51AF2BDB.4010001@tid.es> <23096_1370434567_51AF2C07_23096_186_1_976A65C5A08ADF49B9A8523F7F81925C0F2D79@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51AF3787.8080402@tid.es> True. Sorry then for the confussion. The meeting shall start at 15:30 then. 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) Coordinator and 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 On 05/06/13 14:16, thierry.nagellen at orange.com wrote: > Hi Juanjo > > Your meeting invitation starts at 3:30PM not 3PM so it should be ok > > BR > Thierry > > -----Message d'origine----- > De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro > Envoy? : mercredi 5 juin 2013 14:15 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins > > Hi all, > > I remind you all that we will have a continuation meeting regarding the review preparation this afternoon. > > I'm afraid that I might be 15 mins late. So let's start at 15:15 > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > . > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Wed Jun 5 15:07:01 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Jun 2013 15:07:01 +0200 Subject: [Fiware-wpa] Review preparation CONFCALL WILL START AT 15:30 In-Reply-To: <23096_1370434567_51AF2C07_23096_186_1_976A65C5A08ADF49B9A8523F7F81925C0F2D79@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <23096_1370434567_51AF2C07_23096_186_1_976A65C5A08ADF49B9A8523F7F81925C0F2D79@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51AF37F5.60906@tid.es> Hi all, As pointed out by Thierry, the initial invitation was at 15:30, so we should start then and not at 15:15. Apologizes for the confusion. 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) Coordinator and 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 -------- Original Message -------- Subject: RE: [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins Date: Wed, 5 Jun 2013 12:16:06 +0000 From: To: Juanjo Hierro , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" Hi Juanjo Your meeting invitation starts at 3:30PM not 3PM so it should be ok BR Thierry -----Message d'origine----- De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 5 juin 2013 14:15 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] REMINDER about confcall this afternoon and little delay of 15 mins Hi all, I remind you all that we will have a continuation meeting regarding the review preparation this afternoon. I'm afraid that I might be 15 mins late. So let's start at 15:15 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) Coordinator and 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. . ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jun 5 15:32:16 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Jun 2013 15:32:16 +0200 Subject: [Fiware-wpa] Fwd: RE: REMINDER about confcall this afternoon and little delay of 15 mins In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A42B0@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610A42B0@DEWDFEMB11A.global.corp.sap> Message-ID: <51AF3DE0.1070803@tid.es> Hi, We can use the webconference facility offered by SAP to share slides if needed: https://sap.emea.pgiconnect.com/sandfuchs Thanks to Thorsten for providing the facility Dialing now ... -- 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) Coordinator and 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 -------- Original Message -------- Subject: RE: [Fiware-wpa] REMINDER about confcall this afternoon and little delay of 15 mins Date: Wed, 5 Jun 2013 12:44:25 +0000 From: Sandfuchs, Thorsten To: Juanjo Hierro Juanjo, If interested we could use the sap-connect session to directly share and jointly work on slides? Web conference: https://sap.emea.pgiconnect.com/sandfuchs Participant Code: 651 183 4120 Country Number Blackberry Friendly Format Android Friendly Germany, Frankfurt tel:+4969222210764 tel:+4969222210764x6511834120# tel:+4969222210764;6511834120# Europe Austria, Vienna tel:+431253021750 tel:+431253021750x6511834120# tel:+431253021750;6511834120# France, Paris tel:+33170701777 tel:+33170701777x6511834120# tel:+33170701777;6511834120# Italy, Milan tel:+390236009839 tel:+390236009839x6511834120# tel:+390236009839;6511834120# Spain, Madrid tel:+34917699443 tel:+34917699443x6511834120# tel:+34917699443;6511834120# Switzerland, Zurich tel:+41434569248 tel:+41434569248x6511834120# tel:+41434569248;6511834120# UK, London tel:+442033645639 tel:+442033645639x6511834120# tel:+442033645639;6511834120# Oversea Australia, Sydney tel:+61290090688 tel:+61290090688x6511834120# tel:+61290090688;6511834120# India, Bangalore tel:+918061275055 tel:+918061275055x6511834120# tel:+918061275055;6511834120# USA, New York tel:+16464340499 tel:+16464340499x6511834120# tel:+16464340499;6511834120# -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 5. Juni 2013 14:15 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] REMINDER about confcall this afternoon and little delay of 15 mins Hi all, I remind you all that we will have a continuation meeting regarding the review preparation this afternoon. I'm afraid that I might be 15 mins late. So let's start at 15:15 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) Coordinator and 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 https://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 jhierro at tid.es Wed Jun 5 17:53:15 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Jun 2013 17:53:15 +0200 Subject: [Fiware-wpa] PLEASE DON'T FORGET: checking cockpit document regarding the review ... Message-ID: <51AF5EEB.1080609@tid.es> ... we have finally covered it during our confcall this afternoon. Those who were not at the confcall (or during the whole of it), please check its contents, overall regarding review of the presentations to be elaborated per chapter. Thanks to all for the very productive meeting this afternoon. 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) Coordinator and 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 From jhierro at tid.es Thu Jun 6 07:03:49 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 06 Jun 2013 07:03:49 +0200 Subject: [Fiware-wpa] Fwd: Agenda of the FI-WARE project review In-Reply-To: <51B01737.5070207@tid.es> References: <51B01737.5070207@tid.es> Message-ID: <51B01835.6040207@tid.es> Folks, Find attached the agenda finally sent to the EC for comments. I have added a slot on Testbed related activities (20 min) during the 1st day so that Stefano can summarize activities regarding the Testbed WP. That is also updated in the shared spreadsheet with the agenda at: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdG5ELVBEZ0xmdHluT3VDV1RPbmFHeXc&pli=1#gid=0 Cheers, -- Juanjo -------- Original Message -------- Subject: Agenda of the FI-WARE project review Date: Thu, 06 Jun 2013 06:59:35 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu CC: Miguel Carrillo , "jhierro >> \"Juan J. Hierro\"" , FI-WARE project EC mailbox Dear Arian, Ragnar, Please find enclosed our proposal of agenda for the FI-WARE project 2nd year review next week. As you can see, we have booked a slot to deal with open and friendly discussion about those deliverables that were rejected in our last review. We believe that it would be helpful for reviewers that we explain them what we have done in their respect and why. It will also be helpful for us to better understand the point of views of the reviewers. However, we would like to hear your opinion. Besides, I would like to point out that a possibility might be to place it at the end of the 1st day, rather than in the slot we have placed it. You may think that the time we have assigned to the Live demo is too large, but there are a lot of things to show (new or enhanced/consolidated since the previous demo), and show running, so we definitively we believe it requires the allocated time. We look forward your comments. 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) Coordinator and 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE project - agenda of 2nd year review.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 14958 bytes Desc: not available URL: From mcp at tid.es Fri Jun 7 10:14:47 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 07 Jun 2013 10:14:47 +0200 Subject: [Fiware-wpa] Meeting room for monday Message-ID: <51B19677.104@tid.es> Dear all, We got a last minute cancellation yesterday due to a unexpected meeting of a Telef?nica top executive in Brussels. We need to change the arrangements for monday, 10 and now we are going to a meeting room that the CDTI (NCP of the Spanish Ministry) is kindly provinding. Rue du Tr?ne, 62 6th floor 1050 Brussels I have added the details to the online agenda at * https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?pli=1#heading=h.9avmtalh4led There will be signs to the meeting room. BR 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri Jun 7 10:29:25 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 7 Jun 2013 08:29:25 +0000 Subject: [Fiware-wpa] REHEARSAL - proposal on fade-out slide for our chapter presentations In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A6A0D@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610A6A0D@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610A885B@DEWDFEMB11A.global.corp.sap> Dear colleagues, we took another step back and tried to compile a new template for the "last" slide of each of the chapters. The initial proposal touched on "Highs" and "lows" - especially if this is the last "standing" slide drawing the attention towards "lows" and discussing "counter measures" might not be the message that we would like to convey, do we? Our proposal is to rephrase the notion of the slide like the following - focusing on 1. Highlights (capturing like the "highs" below basically the summary of the things the reviewers saw before) 2. Roadmap & activities (capturing things like UC2 engagements, webinars, OIL and other things that are forward looking and with a positive connotation) Nevertheless, we in WP3 are currently of course preparing the slide in the form discussed/agreed upon yesterday in the Telco besides this idea discussion, so that we have it ready as requested. What do you think? /Thorsten [cid:image003.jpg at 01CE62C7.44C7C5C0] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 23450 bytes Desc: image001.jpg URL: From jhierro at tid.es Fri Jun 7 12:39:41 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Jun 2013 12:39:41 +0200 Subject: [Fiware-wpa] TASK FORCE for FI-WARE GEi owners towards the 2nd year project review Message-ID: <51B1B86D.8080902@tid.es> Dear all, As you know, we are facing the 2nd year official project review next week. During the last preparation meeting we had this Wednesday, we agreed to prepare a revision of the FI-WARE GEi planned availability and usage cockpit that we are currently sharing with the UC projects. This revision would be enriched with information about status, planned terms and conditions in the different environments, base line assets, etc. Please we need to complete this task force by EOB Monday at the latest. It is a pretty simple exercise, so it won't take so much time. I have prepared a shared spreadsheet in Google docs that will help us to work in the new version of the cockpit without creating so much noise in front of the UC projects. You can find it available at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 You have to complete columns N (already filled, just double-check) and the new columns, namely columns O to X. Columns O-Q deal with info about availability for the FI-PPP partners (which includes availability on the FI-WARE Testbed being used by UC projects to run their experiments). All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Columns R-T deal with info about availability within the FI-WARE Open Innovation Lab (OIL). I guess you all know about the FI-WARE OIL so I don't need to elaborate. Despite the concrete legal terms and conditions are under definition, you can assume that this will be an environment where GEis will be offered (in whatever mode is decided per GEi) for free to third parties (i.e., anyone) who wish to experiment with the technology. The GEis will be provided "as-is" without no warranty and only committing a best-effort support. They will be provided for non-comercial experimental-only use by those third parties. All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Why is there a distinction between availability within the FI-PPP and within OIL ? Mainly because the mode in which you will offer a GEi may vary. Actually, within the FI-PPP you are more constrained and have to comply with the signed Collaboration Agreement. Thus, you may decide to support "Dedicated SaaS instance, binaries" for FI-PPP partners, but may decide to only support "Dedicated SaaS instance" to users of the FI-WARE OIL. Columns U-V deal with info about availability beyond the FI-PPP. Again, all relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Column W has to contain a link to the place in the "materializing the FI-WARE vision" part of the wiki where you described the baseline assets used for your GEi. Adding the proper link is pretty straight forward. Go to the wiki page associated to "materializing the FI-WARE vision" for your chapter and then, click on the "Baseline assets" section of your GEi in the Table of Contents of that wiki page. That action, besides it will place you at the right place in the wiki page, will imply that the URL in your browser will then be precisely pointing to that section. Column X has to contain the link to the corresponding entry in the FI-WARE Catalogue. I guess I don't need to explain how to fill it. WPLs are encouraged to follow-up this process and make sure it gets finalized on time for GEis in their chapters. Don't hesitate to ask if you have any doubt on how to fill the spreadsheet. 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) Coordinator and 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 thorsten.sandfuchs at sap.com Fri Jun 7 20:37:55 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 7 Jun 2013 18:37:55 +0000 Subject: [Fiware-wpa] REHEARSAL - first draft of apps chapter presentation Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610A9226@DEWDFEMB11A.global.corp.sap> Dear colleagues, FYI - we uploaded our first draft of the review presentation for comments and feedback on https://forge.fi-ware.eu/docman/view.php/27/2581/FI-WARE+M24+Review+Apps+report+v0.1.pptx Looking forward to see you all on Monday. Best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Fri Jun 7 21:40:31 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 7 Jun 2013 22:40:31 +0300 Subject: [Fiware-wpa] [Fiware-wpl] REHEARSAL - proposal on fade-out slide for our chapter presentations In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A885B@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610A6A0D@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD664610A885B@DEWDFEMB11A.global.corp.sap> Message-ID: I like the idea of keeping the last slide positive. But I also think that we need to elaborate on risks/issues/etc, of two kinds: those that we experienced & addressed in the past, and those that we are facing now or expect to face in the near future (and probably have some ideas how to address). My suggestion is to merge them into "achievements" and "roadmap" slides, as follows. Start with 1-2 slides providing broader summary of the last 6 months (including addressed issues etc), and then 1 slides summarizing focus areas for the upcoming 6 months (again, not just features to be developed). If we make these slides more inclusive, and make sure we also cover there some issues/risks (in both parts), we can drop the "analysis and conclusions" slide altogether. This way the two parts are more self-contained, and we don't need to repeat things. Thoughts? Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: "Sandfuchs, Thorsten" To: "fiware-wpa at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" , Date: 07/06/2013 11:29 AM Subject: [Fiware-wpl] REHEARSAL - proposal on fade-out slide for our chapter presentations Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear colleagues, we took another step back and tried to compile a new template for the ?last? slide of each of the chapters. The initial proposal touched on ?Highs? and ?lows? ? especially if this is the last ?standing? slide drawing the attention towards ?lows? and discussing ?counter measures? might not be the message that we would like to convey, do we? Our proposal is to rephrase the notion of the slide like the following ? focusing on 1. Highlights (capturing like the ?highs? below basically the summary of the things the reviewers saw before) 2. Roadmap & activities (capturing things like UC2 engagements, webinars, OIL and other things that are forward looking and with a positive connotation) Nevertheless, we in WP3 are currently of course preparing the slide in the form discussed/agreed upon yesterday in the Telco besides this idea discussion, so that we have it ready as requested. What do you think? /Thorsten _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 23450 bytes Desc: not available URL: From markus.heller at sap.com Sat Jun 8 08:54:58 2013 From: markus.heller at sap.com (Heller, Markus) Date: Sat, 8 Jun 2013 06:54:58 +0000 Subject: [Fiware-wpa] REHEARSAL - first draft of apps chapter presentation In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610A94B9@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610A9226@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD664610A94B9@DEWDFEMB11A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B19AB3859@DEWDFEMB14A.global.corp.sap> Dear all, let me add that we yesterday interrupted work and wanted to share with your / let you see how we tackle things. We currently see that the PPT has less content that we want to have for 20 min, so we add stuff (are currentlxy on this) also. My main message: We are not complete, we need to improve and we are currently still trying here in WP3. Two man thoughts I want to ask you for your opinion and approach: * What other topics do you advertise or address in your PPTs? E.g. how to address impact-oriented reviewer comments. Currently we walk through the reviever comments to see what is missing and need to addressed...eg most importantly UC phase 2 projects successes and how the GEs prove to be useful, used and reusable....what about phase 3 UC projects currently the beyond friend&family perspective which is utmost important in my personal view for review cannot be addressed with UC phase 2 successes (too much) and we think how to put a bit more of the "needed by reviewer request" stuff into our PPT / presentation... * Other topic: "exploitation ...really". E.g. reviewers asked if/how industry partners really productize their GE's, what the roadmaps are for this etc. that our GE are there and work with UC projects, has been judged by reviwers as expected now (not a success...). Legal questions also are to be addressed urgently they said. So we tried to address this in our PPT with the licenses per GE and per timeline slide in the PPT which we find very useful for this. How do YOU address these topics, can we align here? Ok, just wanted to add our thoughts not only share PPT without comments.....So let us meet on Monday/Tuesday for rehearsal to align us finally. We are happy to meet you there.. Best wishes Markus From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Freitag, 7. Juni 2013 20:38 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: Heller, Markus Subject: [Fiware-wpa] REHEARSAL - first draft of apps chapter presentation Dear colleagues, FYI - we uploaded our first draft of the review presentation for comments and feedback on https://forge.fi-ware.eu/docman/view.php/27/2581/FI-WARE+M24+Review+Apps+report+v0.1.pptx Looking forward to see you all on Monday. Best regards, /Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Sat Jun 8 13:43:19 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 08 Jun 2013 13:43:19 +0200 Subject: [Fiware-wpa] Fwd: RE: Agenda of the FI-WARE project review In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06DC9E03@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06DC9E03@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <51B318D7.5060805@tid.es> Final agenda, as suggested by Arian. ATOS: Note that the presentation on Exploitation should be ready for the 1st day of the review. I have updated the on-line version accordingly. 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) Coordinator and 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 -------- Original Message -------- Subject: RE: Agenda of the FI-WARE project review Date: Fri, 7 Jun 2013 17:42:10 +0000 From: To: CC: , , Dear Juanjo, We will use the attached version. I am not going to have a slot dealing with rejected deliverables. Best regards, Arian. From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, June 07, 2013 6:40 AM To: ZWEGERS Arian (CNECT) Cc: BERGSTROM Ragnar (CNECT); mcp at tid.es; CNECT-ICT-285248 Subject: Re: Agenda of the FI-WARE project review Hi, What about the attached version ? I have implemented the following changes: ? I have moved discussion on FI-WARE ecosystem and exploitation to the first day ? I have moded discussion on rejected deliverables to the second day ? I have added a first slot in the second day dealing with Q&A from first day (there might be questions from the first day that it might be a good idea to answer/review the second day) Please confirm it would be ok. 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) Coordinator and 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 On 06/06/13 09:23, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, Please introduce the following changes to the agenda: - "FI-WARE innovation ecosystem: vision, sustainability, first steps, ..." and "Exploitation" must be on the first day, before the chapters. I think I mentioned before that exploitation should be on June 12, because Michele Marzola will only participate on June 12. - "Discussion on rejected deliverables from last project review" can be part of a general discussion at the end of day 2. Please send me an updated agenda this week. Best regards, Arian. -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Thursday, June 06, 2013 7:00 AM To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: Miguel Carrillo; jhierro >> "Juan J. Hierro"; CNECT-ICT-285248 Subject: Agenda of the FI-WARE project review Dear Arian, Ragnar, Please find enclosed our proposal of agenda for the FI-WARE project 2nd year review next week. As you can see, we have booked a slot to deal with open and friendly discussion about those deliverables that were rejected in our last review. We believe that it would be helpful for reviewers that we explain them what we have done in their respect and why. It will also be helpful for us to better understand the point of views of the reviewers. However, we would like to hear your opinion. Besides, I would like to point out that a possibility might be to place it at the end of the 1st day, rather than in the slot we have placed it. You may think that the time we have assigned to the Live demo is too large, but there are a lot of things to show (new or enhanced/consolidated since the previous demo), and show running, so we definitively we believe it requires the allocated time. We look forward your comments. 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) Coordinator and 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE project - agenda of 2nd year review revised.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 14658 bytes Desc: not available URL: From jhierro at tid.es Sat Jun 8 21:01:06 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 08 Jun 2013 21:01:06 +0200 Subject: [Fiware-wpa] IMPORTANT: NEW template for presentations by chapters Message-ID: <51B37F72.80800@tid.es> Hi all, I have carefully analyzed the several constructive comments received in the last hours and I have compiled a new version of the template to be used for the presentations of chapters during the review. The major reasons for the changes: * I have tried to keep as much as possible alignment with the initial template, thus avoiding that those who had already worked following that template have to repeat work. * I believe that Thorsten, Markus and Alex raised a good point when they suggested to avoid finishing the presentation with a slide elaborating on lows. However, I agree with Alex that this doesn't mean we shouldn't tackle how we had faced some problems and solve them. * The way I saw this could be solved was to shift the "Lows/countermeasurements" into a slide right after "Main achievements" I have titled "Challenges and Actions" (which sounds like a bit more positive). Since "Highs" would be rather similar to "Main achievements", we could then drop the final slide on "Analysis/Conclusions". * SAP had added a slide that is titled: "FI-WARE Apps and Services Business Flow: Joined value creation among the Future Internet players". I believe it's fine to start with a slide that elaborates on the Value proposition, so I have added this initial slide but I suggest that it is titled the same way: "Value proposition: ". In the case of the Apps chapter, it might be: "Value proposition: Joined value creation among Future Internet players". * I believe that adding a slide titled "Towards Adoption by Phase 2 UC Projects" as suggested by SAP is also nice and should be easy to create (just a zoom on the relevant rows linked to the chapter within the cockpit spreadsheets that already exists) * Adding a slide elaborating on licenses and planning as suggested by SAP is also nice, but we are dealing, as you know, with a task force on the matter that should end on Monday EOB which should help to produce a slide similar to the one proposed by SAP but creating it would be much simpler because it would be just a matter of capturing what we are developing as new version of the cockpit for planned usage and availability of GEis. Indeed, the idea would be to navigate to the new spreadsheet we have generated during the review meeting. * Finally, an agenda slide doesn't apply. I have uploaded the new version of the template at: https://forge.fi-ware.eu/docman/view.php/27/2541/FI-WARE+M24+Official+Review+WP+report+template+v2.pptx Note that we this new template we end providing positive messages, so it should be fine. Please stick to this template. We have to stop changing the definition of the template. Please note that the number of slides are absolutely MAXIMUM. Going beyond 11 slides for a 25 min slot is simply unrealistic. 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) Coordinator and 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 jhierro at tid.es Sun Jun 9 08:33:22 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 09 Jun 2013 08:33:22 +0200 Subject: [Fiware-wpa] Presentation in the last SB and AdvC that may help to provide some slides Message-ID: <51B421B2.4000906@tid.es> Hi all, I have uploaded the presentation that I made in the last SB and Advisory Council meeting at: https://forge.fi-ware.eu/docman/view.php/7/2583/FI-WARE+and+AB+presentation+to+SB+and+Advisory+Council+13-05-22.pptx I believe that slides 11, 13 and 18 may work as the slides elaborating on GE integration within the Data, IoT and Security chapters, respectively. Just in case you find them useful. Regarding the presentation itself, I believe it doesn't provide info you don't know already. 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) Coordinator and 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 mcp at tid.es Sun Jun 9 23:47:10 2013 From: mcp at tid.es (Miguel Carrillo) Date: Sun, 09 Jun 2013 23:47:10 +0200 Subject: [Fiware-wpa] Fwd: Meeting room for monday In-Reply-To: <51B19677.104@tid.es> References: <51B19677.104@tid.es> Message-ID: <51B4F7DE.8060508@tid.es> Dear all, After getting some questions, I resend this reminder to make the details for tomorrow easily available. START TIME: 11 am See you there!! Best regards, Miguel -------- Mensaje original -------- Asunto: Meeting room for monday Fecha: Fri, 07 Jun 2013 10:14:47 +0200 De: Miguel Carrillo Para: fiware-wpa at lists.fi-ware.eu , fiware-wpl at lists.fi-ware.eu , Kennedy, John M , Alvaro Arranz , FERMIN GALAN MARQUEZ , Nuria De-Lama Sanchez Dear all, We got a last minute cancellation yesterday due to a unexpected meeting of a Telef?nica top executive in Brussels. We need to change the arrangements for monday, 10 and now we are going to a meeting room that the CDTI (NCP of the Spanish Ministry) is kindly provinding. Rue du Tr?ne, 62 6th floor 1050 Brussels I have added the details to the online agenda at * https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?pli=1#heading=h.9avmtalh4led There will be signs to the meeting room. BR 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Mon Jun 10 09:17:52 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 10 Jun 2013 07:17:52 +0000 Subject: [Fiware-wpa] webinars - update Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89055489@EX10-MB2-MAD.hi.inet> Dear Partners, Thanks for the effort devoted to the webinars. Please, be aware there're 5 webinars scheduled for today. Please, have a look at the guidelines, if needed. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_inform_and_adversite_webinars_of_GE Please, don't forget to advertise them through on twitter by sending messages to . at FIWARE. Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Mon Jun 10 12:40:16 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 10 Jun 2013 10:40:16 +0000 Subject: [Fiware-wpa] Important for review preparation: Dissemination Plan info Message-ID: <1971FF81B8E01C45991F6F92B9E3B2508909D845@EX10-MB2-MAD.hi.inet> Dear Colleagues, I hope I did not miss any of your e-mails on this, but I think I only have the info for Security and partially for Data (miss M24-M36 plan for the latter). I have uploaded a google doc to make much easier your contributions (Security and Data are updated there). https://docs.google.com/document/d/1vpcOpj69fTN-EeCKzC1jtZgj4RLuSGBRyaI6UF3nkaE/edit It will not take long time for you or your partners to provide this: - In the first table is just to say if your chapter team attended or not (also nice if you complete which partner attended and what was done in the "role" column). - The second table is just a list of 3-4 events for M24-M36 that your team considers to attend. If I did overlook one of your e-mails on this let me apologize, just re-send it to me. Please send this information ASAP, deadline is tomorrow noon time, but I really appreciate if I have them today EoB. BR -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Jun 10 16:10:50 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 10 Jun 2013 16:10:50 +0200 Subject: [Fiware-wpa] Update on State of the Art deliverable (action required) Message-ID: <51B5DE6A.8070109@tid.es> Dear all, This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP. The last contribution came extremely late (last tuesday) so delivering now could even be backfiring: * If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs) * If we do not deliver, they will complain about not having the deliverable Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it. Things to do/change: * Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter. * Some follow the original convention, some other write [1], [2] .... We want the original one. * Please make sure that the contributions are in alphabetical order (sorted by reference code) In summary: * Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take the table in Data as the reference). Please use the table format (same as Data) * IoT to add such a table * I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right). Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work. Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time: * Contributions not using the attached doc as starting point * Contributions not following the naming convention (also the format - capital letters, table format, etc.) * Contributions with more than one table * Contributions not in alphabetical order * Mismatches between the references in the text and the references table Deadline: Tuesday, 18th of June It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.2 State of the Art Analysis ? Emerging Technologies_20130610.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3247250 bytes Desc: not available URL: From jhierro at tid.es Mon Jun 10 16:38:06 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Jun 2013 16:38:06 +0200 Subject: [Fiware-wpa] Current draft of periodic report Message-ID: <51B5E4CE.5020708@tid.es> Hi, I pass it to you as it stands now in case you can provide some early feedback. 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) Coordinator and 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 -------------- A non-text attachment was scrubbed... Name: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v6_jhierro.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 4206532 bytes Desc: not available URL: From jhierro at tid.es Mon Jun 10 17:35:28 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Jun 2013 17:35:28 +0200 Subject: [Fiware-wpa] Agreed changes on slides regarding status of chapters Message-ID: <51B5F240.5030508@tid.es> Hi, Here you are my notes regarding changes on slides regarding status of chapters: * Slide on Analysis/conclusions. We will finally drop it. However, instead of the standard "Thanks" slide, we will create a standard slide with "Questions ?" where we will bring on the right some nice photos linked to a summary of positive statements to bring at the end of the presentation (based on proposal by SAP). Juanjo will produce this standard slide. * Come with an alternative icon legend for slide on Overall Architecture/Status. Juanjo will come with this legend. * Don't forget that in slide regarding Major achievements we should mention to M13-24 instead of M19-24. * The slide on Technical Roadmap should include "(r2.3 and r3.x)" in the title but then, we have to clarify whether each high-level features goes to r2.3 or r3.x by adding "(r2.3)" or "(r3.x)" at the end of the text describing each features. Regarding features that go to r3.x, you don't need to specify the minor release unless you wish to highlight that you want to prioritize the feature, typically linking it to r3.1. You have to send me a version of your slides no later than tonight 23:30h. I may come with some proposed changes by tomorrow. 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) Coordinator and 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 GLIKSON at il.ibm.com Mon Jun 10 19:31:09 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 10 Jun 2013 20:31:09 +0300 Subject: [Fiware-wpa] [Fiware-wpl] Important for review preparation: Dissemination Plan info In-Reply-To: <1971FF81B8E01C45991F6F92B9E3B2508909D845@EX10-MB2-MAD.hi.inet> References: <1971FF81B8E01C45991F6F92B9E3B2508909D845@EX10-MB2-MAD.hi.inet> Message-ID: FYI, in order to change the color of a cell, select the cell(s) then go to "Table" -> "Table properties...", change "Cell background color". Alex From: CARLOS RALLI UCENDO To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 10/06/2013 01:40 PM Subject: [Fiware-wpl] Important for review preparation: Dissemination Plan info Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear Colleagues, I hope I did not miss any of your e-mails on this, but I think I only have the info for Security and partially for Data (miss M24-M36 plan for the latter). I have uploaded a google doc to make much easier your contributions (Security and Data are updated there). https://docs.google.com/document/d/1vpcOpj69fTN-EeCKzC1jtZgj4RLuSGBRyaI6UF3nkaE/edit It will not take long time for you or your partners to provide this: - In the first table is just to say if your chapter team attended or not (also nice if you complete which partner attended and what was done in the "role" column). - The second table is just a list of 3-4 events for M24-M36 that your team considers to attend. If I did overlook one of your e-mails on this let me apologize, just re-send it to me. Please send this information ASAP, deadline is tomorrow noon time, but I really appreciate if I have them today EoB. BR -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From manieri at eng.it Mon Jun 10 22:02:16 2013 From: manieri at eng.it (Andrea Manieri) Date: Mon, 10 Jun 2013 22:02:16 +0200 Subject: [Fiware-wpa] [REHEARSHAL]Fi-ware tools - WP9 - presentation for the review - candidate final Message-ID: <51B630C8.6020807@eng.it> DEar All, please find enclosed the presentation for the Tools chapter. I've included back-up slides on the specific tools if needed. Any comment is welcome. Best A. p.s. the SOPECO video il too big and need to be managed locally. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M24 WP9 Tools Chapter 2013-06-12_candidate final.zip Type: application/octet-stream Size: 2542235 bytes Desc: not available URL: From thierry.nagellen at orange.com Tue Jun 11 10:35:50 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 11 Jun 2013 08:35:50 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report In-Reply-To: <51B5E4CE.5020708@tid.es> References: <51B5E4CE.5020708@tid.es> Message-ID: <24933_1370939751_51B6E167_24933_1207_1_976A65C5A08ADF49B9A8523F7F81925C0F3CA1@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all: 2 minor comments but the second one need action from WPL to update the doc: 1- P24: organisation of Open Calls We have to be more explicit on delays putting dates when the new partners were selected and then when they really were integrated into the consortium because administrative issues (amendments). It is critical to exchange with the Commission on some potential delays which are not the fact of FI-Ware. 2- Some WP put in their description the list of deliverables: we have to be homogeneous for this part. So the one who have not included the list of deliverables have to do it. BR Thierry -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: lundi 10 juin 2013 16:38 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. 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) Coordinator and 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. From markus.heller at sap.com Tue Jun 11 11:10:52 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 11 Jun 2013 09:10:52 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report --> SAP feedback / Change requests Message-ID: <393554EDCF801348BC53C7813C6CB73B19AB5EDA@DEWDFEMB14A.global.corp.sap> Dear Juanjo, I send you our SAP feedback for your draft version of the Periodic Report. Please incorporate our change requests (TRACK CHANGES) and please let me know when some of the proposed corrections are not ok. So far this is our input to you. If we find other topics, we might as well contact you to see if/how to proceed. Best wishes Markus -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 10. Juni 2013 16:38 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. Cheers, -- Juanjo -------------- next part -------------- A non-text attachment was scrubbed... Name: D 1 2 4-FI-WARE_Periodic_Peport-M13-M24-v6_jhierro__SAPFeedback.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 4131110 bytes Desc: D 1 2 4-FI-WARE_Periodic_Peport-M13-M24-v6_jhierro__SAPFeedback.docx URL: From pierangelo.garino at telecomitalia.it Tue Jun 11 14:12:29 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Jun 2013 14:12:29 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Current draft of periodic report In-Reply-To: <51B5E4CE.5020708@tid.es> References: <51B5E4CE.5020708@tid.es> Message-ID: Hi Juanjo, although much later than the deadline here is my feedback concerning the report. Main things: - Comments added in WP2 (possible duplicated text) - One modification to WP6 text - Some modifications to WP7 - a few typos (easily found with track changes BR Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: luned? 10 giugno 2013 16:38 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. 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) Coordinator and 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v6_jhierro-revpg.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 4191146 bytes Desc: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v6_jhierro-revpg.docx URL: From ralli at tid.es Tue Jun 11 14:47:32 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 11 Jun 2013 12:47:32 +0000 Subject: [Fiware-wpa] First draft of Dissemination & Collaboration presentation Message-ID: <1971FF81B8E01C45991F6F92B9E3B2508909F1CC@EX10-MB2-MAD.hi.inet> Dear colleagues, I've just uploaded it to the private Fi_WARE dolman. https://forge.fi-ware.eu/docman/view.php/27/2590/FI-WARE+M24+Official+Review+Communication+Collaboration+Dissemination+v1.pptx As the file weights 24Mb I've uploaded to the same folder another version removing the embedded video (only 10Mb). BR -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Tue Jun 11 15:30:15 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 11 Jun 2013 13:30:15 +0000 Subject: [Fiware-wpa] live demo yed files and jpg version Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610AEBD0@DEWDFEMB11A.global.corp.sap> Hi, I compiled as mentioned the architecture diagram with the GE in orange which contributed to the live demonstrator - at least the ones that I know - please fix any errors or raise it. Best, /Thorsten -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v8_live_demo.graphml Type: application/octet-stream Size: 78237 bytes Desc: fiware-cross-chapter_v8_live_demo.graphml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v8_live_demo.jpg Type: image/jpeg Size: 199647 bytes Desc: fiware-cross-chapter_v8_live_demo.jpg URL: From sergg at tid.es Tue Jun 11 15:53:49 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 11 Jun 2013 13:53:49 +0000 Subject: [Fiware-wpa] live demo yed files and jpg version In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610AEBD0@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610AEBD0@DEWDFEMB11A.global.corp.sap> Message-ID: <03BE306058976141B4883174DF62D54D8659AA6B@EX10-MB2-MAD.hi.inet> Hi Thorsten, From Data, it's the context (PubSub) broker, not the Query Broker, the GE that should be highlighted. Best Regards, Sergiio -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Tuesday, June 11, 2013 3:30 PM To: JUAN JOSE HIERRO SUREDA; FERMIN GALAN MARQUEZ Cc: Heller, Markus; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] live demo yed files and jpg version Hi, I compiled as mentioned the architecture diagram with the GE in orange which contributed to the live demonstrator - at least the ones that I know - please fix any errors or raise it. Best, /Thorsten ________________________________ 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 thorsten.sandfuchs at sap.com Tue Jun 11 16:12:15 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 11 Jun 2013 14:12:15 +0000 Subject: [Fiware-wpa] live demo yed files and jpg version In-Reply-To: <03BE306058976141B4883174DF62D54D8659AA6B@EX10-MB2-MAD.hi.inet> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610AEBD0@DEWDFEMB11A.global.corp.sap> <03BE306058976141B4883174DF62D54D8659AA6B@EX10-MB2-MAD.hi.inet> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610AEC4E@DEWDFEMB11A.global.corp.sap> Fixed - and attached. -----Original Message----- From: SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] Sent: Dienstag, 11. Juni 2013 15:54 To: Sandfuchs, Thorsten; JUAN JOSE HIERRO SUREDA; FERMIN GALAN MARQUEZ Cc: Heller, Markus; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: RE: live demo yed files and jpg version Hi Thorsten, From Data, it's the context (PubSub) broker, not the Query Broker, the GE that should be highlighted. Best Regards, Sergiio -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Tuesday, June 11, 2013 3:30 PM To: JUAN JOSE HIERRO SUREDA; FERMIN GALAN MARQUEZ Cc: Heller, Markus; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] live demo yed files and jpg version Hi, I compiled as mentioned the architecture diagram with the GE in orange which contributed to the live demonstrator - at least the ones that I know - please fix any errors or raise it. Best, /Thorsten ________________________________ 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: fiware-cross-chapter_v9_live_demo.graphml Type: application/octet-stream Size: 78242 bytes Desc: fiware-cross-chapter_v9_live_demo.graphml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v9_live_demo.jpg Type: image/jpeg Size: 199740 bytes Desc: fiware-cross-chapter_v9_live_demo.jpg URL: From pierangelo.garino at telecomitalia.it Tue Jun 11 16:26:07 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Jun 2013 16:26:07 +0200 Subject: [Fiware-wpa] Draft slides I2ND chapter Message-ID: Dear Juanjo, I have uploaded at the link FI-WARE M24 Review I2ND (FI-WARE M24 Review I2ND report v1 7.pptx) the slide set prepared for I2ND chapter. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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 manieri at eng.it Tue Jun 11 16:57:57 2013 From: manieri at eng.it (Andrea Manieri) Date: Tue, 11 Jun 2013 16:57:57 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report In-Reply-To: <51B5E4CE.5020708@tid.es> References: <51B5E4CE.5020708@tid.es> Message-ID: <51B73AF5.1070503@eng.it> Dear Juanjo, below the changes requested from the ENG side. Some further contributions to the WP10 will arrive from Stefano directly. Please, consider to perform a global reading, I found some typos and several partial texts. Best E-IIS changes: in Publishable Summary The following text ?Evolution of the FI-WARE Catalogue and design of the FI-WARE Open Innovation Lab as base instruments of the target FI-WARE innovation ecosystem; should be split in - Evolution of the FI-WARE Catalogue and finalisation of the Development Tools, including the eLearning Platform whose need was recently spotted; - initial integration of Development Tools into the Fi-CoDE - Design of the FI-WARE Open Innovation Lab as base instruments of the target FI-WARE innovation ecosystem; BTW, any such design is hidden somewhere, since It seems impossible to find anywhere. Please provide the reference. in ch 2.1.7 Add the following sentence at the very end. "WRT FI-CoDE is has been considered an enhancement of the constituent tools to take into account the needs of training, not just webinars. An eLearning Platform, a customisation of the open Source tool Moodle, has been set up and is available at edu.fi-ware.eu. During the next weeks a specific set of training material on the Fi-CoDE and all development tools will be created and uploade. The eLearning platform will be also available for the training from GEis owner and to host recorded sessions of webinars for future access. An initial design of the Fi-CoDE based on the initial UC projects feedback on the handbook has been done." in Ch 2.2 the following text " ?*FI-CoDE Basic Framework *(formerly known as DevComE). The collaborative tools were ready at an early stage of the project to allow for a rapid adaptation and start of interaction of all the partners. The use of Fusion Forge endows the consortium with a powerful, very comprehensive and integrated work environment that provides the typical tools for a large scale collaborative project (source code repositories, tracking systems, mailing lists, wikis, documentation repositories...). These tools are suitable for the use of agile methods, like the ones we have adopted in FI-WARE. Related to this, the System/software Engineering Method for FI-WARE was also delivered. " should be replaced by the following ?*FI-CoDE Basic Framework *(formerly known as DevComE). The collaborative tools and related methodology were ready at an early stage of the project to allow for a rapid adaptation and start of interaction of all the partners. The use of Fusion Forge endows the consortium with a powerful, very comprehensive and integrated work environment that provides the typical tools for a large scale collaborative project (source code repositories, tracking systems, mailing lists, wikis, documentation repositories...). These and the other tools developed in the period (namely, several Eclipse Plug-ins, Trace Analyser, PROSA, SOPECO) are now available and suitable for the use of System/software Engineering methods defined in the Handbook. in ch 2.3.10 replace "Set up of the eLearnong Platform " with "Set up of the eLearning Platform at edu.fi-ware.eu" replace " Concerning OSCL, after the new requirements collected and the acknowledgment of the OSCL tools status, E-IIS decided to close this task and give priority to new ones, such as the RESTful API testing functionality and the clients for the GEs to be provided in the Eclipse Environment. " with "Concerning OSCL, after the new requirements collected and the acknowledgment of the OSCL tools status, E-IIS decided to close this task and give priority to the more critical one, the integration of Fi-CoDe and the provisioning of the training content for the UC projects." in 2.13.10.1 replace The progress in this task 9.1 towards objectives is in line with the planned activities, aiming at realizing a set of functionalities to foster the developer's collaboration using Eclipse Plugins to interact with the preferred forge directly from Eclipse environment. In addition to this, it was designed (and started the development) that the FI-CoDE web interface integrates the CDE Manager, the Catalogue, the eLearning platform and the FI-CoDE User Management System.// with The progress in this task 9.1 towards objectives is in line with the planned activities, aiming at realizing a set of functionalities to foster the developer's collaboration using Eclipse Plugins to interact with the preferred forge directly from Eclipse environment. In addition to this, it was designed (and started the development) of the FI-CoDE web interface that integrates the CDE Manager, the Catalogue, the eLearning platform and providing a Single Sign-on feature. // 2.3.10.3 remove the paragraph " ?E-IIS is also going to finalize the design and specification of unit & functional testing framework useful to test the Generic Enablers (before their integration in a FIapp) as well as web services exposed by FIApps. This functionality was not planned at the beginning and it is new driven by the sensitiveness of the UC projects to this aspect of the development lifecycle. Moreover, as concerns the deployment of a FIApp for testing purposes, the proposed solution is ETICS.// " same chapter replace "There are no deviations in this task 9.3." with "the initial analysis of deployment tools was focusing on using Eclipse as main entry point. Give the adoption of Chef by the Cloud Chapter for deployng GEis, the work has been re-orientered to re-use, as much as possible the interfaces provided by the Cloud Chapter" page 121 remove the following " ?E-IIS: the reason is that E-IIS planned effort is based on a linear planning not always realistic. In particular, in this period - and in the next six months - an overspending is foreseen due to the need to provide the final FICODE and the eLearning environment for the benefit of the Open Call projects. This overspending will be compensated with the expected under-spending in the last six months of the project. " because 0,72mm over 33 is not *significantly higher* 2.13.11 substitute reference to Engineering with E-IIS (please, check also elsewhere) WRT WP11 and 12, as a Warning to everybody, there are no reference of the contribution to each partner. this may rise some concerns from reviewers perspective, given the effort allocated to major players. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nuria.delama at atosresearch.eu Tue Jun 11 17:17:01 2013 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Tue, 11 Jun 2013 17:17:01 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report In-Reply-To: <51B5E4CE.5020708@tid.es> References: <51B5E4CE.5020708@tid.es> Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A023596CD@INTMAIL03.es.int.atosorigin.com> I went quickly through the periodic report, especially regarding checkpoints. My only comment is that checkpoint 5 points out the integration with FIRE infrastructures (Testbed in operation, feedback from UC projects on using the Testbed, and potential integration with FIRE infrastructures) but there is no reference to it at all in the text. Current description only includes the relationship with Use Case projects. Nuria de Lama Research & Innovation Representative to the European Commission ?? T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net? ? -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: lunes, 10 de junio de 2013 16:38 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. 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) Coordinator and 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 ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From stefano.depanfilis at eng.it Tue Jun 11 17:36:00 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 11 Jun 2013 17:36:00 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report In-Reply-To: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A023596CD@INTMAIL03.es.int.atosorigin.com> References: <51B5E4CE.5020708@tid.es> <66E3B1FDDB04BE4D92DC3A2BA8D98D9A023596CD@INTMAIL03.es.int.atosorigin.com> Message-ID: dear nuria, don't get your observation. in case only text about fire is missing, isn't it? ciao, stefano 2013/6/11 Nuria De-Lama Sanchez > I went quickly through the periodic report, especially regarding > checkpoints. > > My only comment is that checkpoint 5 points out the integration with FIRE > infrastructures (Testbed in operation, feedback from UC projects on using > the Testbed, and potential integration with FIRE infrastructures) but there > is no reference to it at all in the text. Current description only includes > the relationship with Use Case projects. > > Nuria de Lama > > Research & Innovation > Representative to the European Commission > > T +34 91214 9321 > F +34 91754 3252 > nuria.delama at atosresearch.eu > Albarrac?n 25 > 28037 Madrid > Spain > www.atosresearch.eu > es.atos.net > > > > -----Original Message----- > From: fiware-wpl-bounces at lists.fi-ware.eu [mailto: > fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro > Sent: lunes, 10 de junio de 2013 16:38 > To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: [Fiware-wpl] Current draft of periodic report > > Hi, > > I pass it to you as it stands now in case you can provide some early > feedback. > > 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) Coordinator and 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 > ------------------------------------------------------------------ > 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. > ------------------------------------------------------------------ > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nuria.delama at atosresearch.eu Tue Jun 11 18:12:53 2013 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Tue, 11 Jun 2013 18:12:53 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Current draft of periodic report In-Reply-To: References: <51B5E4CE.5020708@tid.es><66E3B1FDDB04BE4D92DC3A2BA8D98D9A023596CD@INTMAIL03.es.int.atosorigin.com> Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A02359718@INTMAIL03.es.int.atosorigin.com> Yes, only that part. The rest is there. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net From: stefano de panfilis [mailto:stefano.depanfilis at eng.it] Sent: martes, 11 de junio de 2013 17:36 To: Nuria De-Lama Sanchez Cc: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Current draft of periodic report dear nuria, don't get your observation. in case only text about fire is missing, isn't it? ciao, stefano 2013/6/11 Nuria De-Lama Sanchez I went quickly through the periodic report, especially regarding checkpoints. My only comment is that checkpoint 5 points out the integration with FIRE infrastructures (Testbed in operation, feedback from UC projects on using the Testbed, and potential integration with FIRE infrastructures) but there is no reference to it at all in the text. Current description only includes the relationship with Use Case projects. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net -----Original Message----- From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: lunes, 10 de junio de 2013 16:38 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Current draft of periodic report Hi, I pass it to you as it stands now in case you can provide some early feedback. 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) Coordinator and 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 ------------------------------------------------------------------ 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. ------------------------------------------------------------------ _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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 ------------------------------------------------------------------ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From jhierro at tid.es Tue Jun 11 18:37:21 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Jun 2013 18:37:21 +0200 Subject: [Fiware-wpa] Draft presentation about overal achievements and innovation ecosystem first steps Message-ID: <51B75241.9000403@tid.es> You can download the presentation from the following URL: https://forge.fi-ware.eu/docman/view.php/27/2593/FI-WARE+Achievements+and+steps+ahead+13-06-11.pptx I remind you that you have to upload your chapter presentations this evening on the docman system of the FI-WARE Private presentation. It is important that you clearly point out the differential aspects of your value propositions to application developers/providers in the first slide of your presentation. I will use those elements to incorporate content and enrich slides 7-14 of the presentation above. 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) Coordinator and 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 thierry.nagellen at orange.com Tue Jun 11 18:45:30 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 11 Jun 2013 16:45:30 +0000 Subject: [Fiware-wpa] Review M24 final version IoT Message-ID: <3119_1370969132_51B7542C_3119_655_1_976A65C5A08ADF49B9A8523F7F81925C0F4212@PEXCVZYM13.corporate.adroot.infra.ftgroup> Here is the link https://forge.fi-ware.eu/docman/view.php/27/2595/FI-WARE+M24+Official+Review+IoT+report+vfinal.pptx BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nuria.delama at atosresearch.eu Tue Jun 11 18:46:49 2013 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Tue, 11 Jun 2013 18:46:49 +0200 Subject: [Fiware-wpa] Statements by others about FI-WARE_for concluding remarks Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A0235972D@INTMAIL03.es.int.atosorigin.com> Hi Juanjo, all, Find attached some slides with content coming from Use Case projects stating positive and negative comments about FI-WARE. As agreed, you can pick up content from them for your concluding remarks. The first 3 slides have statements that offer the vision of an SME (Ariadna, from the SmartAgrifood project). I have used red colour for the statement I would personally provide in the last slide. The fourth slide contains statements from the validation reports of UC projects (thanks for the link Thorsten), positive and negative (only a sample). Take the ones you prefer for your presentation. Best regards, Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: martes, 11 de junio de 2013 18:37 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Draft presentation about overal achievements and innovation ecosystem first steps You can download the presentation from the following URL: https://forge.fi-ware.eu/docman/view.php/27/2593/FI-WARE+Achievements+and+steps+ahead+13-06-11.pptx I remind you that you have to upload your chapter presentations this evening on the docman system of the FI-WARE Private presentation. It is important that you clearly point out the differential aspects of your value propositions to application developers/providers in the first slide of your presentation. I will use those elements to incorporate content and enrich slides 7-14 of the presentation above. 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) Coordinator and 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 ------------------------------------------------------------------ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE_feedback from others.pptx Type: application/octet-stream Size: 124149 bytes Desc: FIWARE_feedback from others.pptx URL: From pascal.bisson at thalesgroup.com Tue Jun 11 18:50:15 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 11 Jun 2013 18:50:15 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Draft presentation about overal achievements and innovation ecosystem first steps In-Reply-To: <51B75241.9000403@tid.es> References: <51B75241.9000403@tid.es> Message-ID: <27708_1370969417_51B75549_27708_17146_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E867D85D@THSONEA01CMS04P.one.grp> Done already for Security Chapter slides. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 11 juin 2013 18:37 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Draft presentation about overal achievements and innovation ecosystem first steps You can download the presentation from the following URL: https://forge.fi-ware.eu/docman/view.php/27/2593/FI-WARE+Achievements+and+steps+ahead+13-06-11.pptx I remind you that you have to upload your chapter presentations this evening on the docman system of the FI-WARE Private presentation. It is important that you clearly point out the differential aspects of your value propositions to application developers/providers in the first slide of your presentation. I will use those elements to incorporate content and enrich slides 7-14 of the presentation above. 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) Coordinator and 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 juan.bareno at atosresearch.eu Tue Jun 11 19:46:39 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Tue, 11 Jun 2013 19:46:39 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Draft slides WP11 Exploitation Message-ID: Dear Juanjo I uploaded the Exploitation presentation for M24 Review in the following link https://forge.fi-ware.eu/docman/view.php/27/2598/WP11+Review+M24v1206.pptx Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: martes, 11 de junio de 2013 16:26 To: Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Draft slides I2ND chapter Dear Juanjo, I have uploaded at the link FI-WARE M24 Review I2ND (FI-WARE M24 Review I2ND report v1 7.pptx) the slide set prepared for I2ND chapter. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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. ------------------------------------------------------------------ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: From pierangelo.garino at telecomitalia.it Tue Jun 11 20:00:56 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Jun 2013 20:00:56 +0200 Subject: [Fiware-wpa] I2ND slides re-uploaded... Message-ID: ... following a small change. File renamed v1.8 (it was 1.7), here the new link: https://forge.fi-ware.eu/docman/view.php/27/2592/FI-WARE+M24+Review+I2ND+report+v1.8.pptx BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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 sergg at tid.es Tue Jun 11 20:26:21 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 11 Jun 2013 18:26:21 +0000 Subject: [Fiware-wpa] Final version of WP6 slides Message-ID: <03BE306058976141B4883174DF62D54D8659AC55@EX10-MB2-MAD.hi.inet> Juanjo, The final version for WP6 slides is v.0.6: https://forge.fi-ware.eu/docman/view.php/27/2588/FI-WARE+M24+Review+WP6+Data+report+v0.6.pptx Best Regards, Sergio -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 11 20:30:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Jun 2013 20:30:23 +0200 Subject: [Fiware-wpa] [Fiware] TASK FORCE for FI-WARE GEi owners towards the 2nd year project review In-Reply-To: <51B1B86D.8080902@tid.es> References: <51B1B86D.8080902@tid.es> Message-ID: <51B76CBF.3020103@tid.es> Dear all, First of all, let me rather thank all of you who have already completed the requested exercise ... This is a clear sign of your commitment. There are few partners who haven't completed the task force, and the reviewers will notice: * Cloud chapter: * INRIA: Job Scheduler * Technicolor: Cloud Proxy * IoT chapter: * Surrey University: IoT Discovery * Fraunhofer: IoT Gateway Device Management * Security chapter: * Thales: Secure Storage * I2ND chapter: * ALU-I: VNEIC * Technicolor: Cloud Proxy Best regards, -- Juanjo Hierro ------------- 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) Coordinator and 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 On 07/06/13 12:39, Juanjo Hierro wrote: Dear all, As you know, we are facing the 2nd year official project review next week. During the last preparation meeting we had this Wednesday, we agreed to prepare a revision of the FI-WARE GEi planned availability and usage cockpit that we are currently sharing with the UC projects. This revision would be enriched with information about status, planned terms and conditions in the different environments, base line assets, etc. Please we need to complete this task force by EOB Monday at the latest. It is a pretty simple exercise, so it won't take so much time. I have prepared a shared spreadsheet in Google docs that will help us to work in the new version of the cockpit without creating so much noise in front of the UC projects. You can find it available at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 You have to complete columns N (already filled, just double-check) and the new columns, namely columns O to X. Columns O-Q deal with info about availability for the FI-PPP partners (which includes availability on the FI-WARE Testbed being used by UC projects to run their experiments). All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Columns R-T deal with info about availability within the FI-WARE Open Innovation Lab (OIL). I guess you all know about the FI-WARE OIL so I don't need to elaborate. Despite the concrete legal terms and conditions are under definition, you can assume that this will be an environment where GEis will be offered (in whatever mode is decided per GEi) for free to third parties (i.e., anyone) who wish to experiment with the technology. The GEis will be provided "as-is" without no warranty and only committing a best-effort support. They will be provided for non-comercial experimental-only use by those third parties. All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Why is there a distinction between availability within the FI-PPP and within OIL ? Mainly because the mode in which you will offer a GEi may vary. Actually, within the FI-PPP you are more constrained and have to comply with the signed Collaboration Agreement. Thus, you may decide to support "Dedicated SaaS instance, binaries" for FI-PPP partners, but may decide to only support "Dedicated SaaS instance" to users of the FI-WARE OIL. Columns U-V deal with info about availability beyond the FI-PPP. Again, all relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Column W has to contain a link to the place in the "materializing the FI-WARE vision" part of the wiki where you described the baseline assets used for your GEi. Adding the proper link is pretty straight forward. Go to the wiki page associated to "materializing the FI-WARE vision" for your chapter and then, click on the "Baseline assets" section of your GEi in the Table of Contents of that wiki page. That action, besides it will place you at the right place in the wiki page, will imply that the URL in your browser will then be precisely pointing to that section. Column X has to contain the link to the corresponding entry in the FI-WARE Catalogue. I guess I don't need to explain how to fill it. WPLs are encouraged to follow-up this process and make sure it gets finalized on time for GEis in their chapters. Don't hesitate to ask if you have any doubt on how to fill the spreadsheet. 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) Coordinator and 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 mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware ________________________________ 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 mcp at tid.es Tue Jun 11 20:46:32 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 11 Jun 2013 20:46:32 +0200 Subject: [Fiware-wpa] Draft slides WP1 Management In-Reply-To: References: Message-ID: <51B77088.8090306@tid.es> Dear all, This is what we have for Management: https://forge.fi-ware.eu/docman/view.php/27/2600/FI-WARE+M24+Review+Management+v3.pptx Best regards, 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 From markus.heller at sap.com Wed Jun 12 01:29:41 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 11 Jun 2013 23:29:41 +0000 Subject: [Fiware-wpa] FW: Final Version of WP3 Presentation uploaded to Docman In-Reply-To: <393554EDCF801348BC53C7813C6CB73B19AB6E7A@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B19AB6E7A@DEWDFEMB14A.global.corp.sap> Message-ID: <393554EDCF801348BC53C7813C6CB73B19AB6E8D@DEWDFEMB14A.global.corp.sap> Dear Juanjo, Please use this message to avoid confusion: I have uploaded the final version of the WP3 PPT to docman. This new version 1.0 is the only version now in the "Draft" folder there, I deleted the previous ones to avoid confusion: Please use this version to upload it your computer or otherwise I can use my own laptop for my WP3 slot - whatever you prefer is ok with me. This is the correct URL to PPT WP3 is: https://forge.fi-ware.eu/docman/view.php/27/2602/FI-WARE+M24+Review+Apps+report+v1.pptx Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jun 12 11:23:41 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 12 Jun 2013 11:23:41 +0200 Subject: [Fiware-wpa] PPts for the review Message-ID: <51B83E1D.40007@tid.es> Dear all, I uploaded the whole lot to my dropbox. Please take the pack from this address. * https://dl.dropboxusercontent.com/u/25916180/Pres_M24%20-%20final.zip I just changes the "Thanks" one with the new "Questions" slide. Download, check and use these ones. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed Jun 12 11:40:20 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 12 Jun 2013 11:40:20 +0200 Subject: [Fiware-wpa] wp10 at the review Message-ID: dear juanjo and all the slides are now in the forge as requested. ciao, stefano -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Jun 12 11:54:22 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 12 Jun 2013 09:54:22 +0000 Subject: [Fiware-wpa] Folder for Live Demo videos Message-ID: <4379_1371030863_51B8454F_4379_39_5_976A65C5A08ADF49B9A8523F7F81925C0F4477@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, I've just created a dedicated folder for the videos of this second live demo and uploaded the first video that Fermin sent yesterday evening so everybody will be able to use them for other dissemination activities. https://forge.fi-ware.eu/docman/admin/index.php?group_id=27&selected_doc_group_id=448&language_id=&selected_stateid=1 BR Thierry PS : I am going to inform Fermin after the demo to avoid any email pop-up now _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Jun 12 12:03:41 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 12 Jun 2013 12:03:41 +0200 Subject: [Fiware-wpa] R: Folder for Live Demo videos In-Reply-To: <4379_1371030863_51B8454F_4379_39_5_976A65C5A08ADF49B9A8523F7F81925C0F4477@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <4379_1371030863_51B8454F_4379_39_5_976A65C5A08ADF49B9A8523F7F81925C0F4477@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: Hi Thierry, the link is the one used for modifying the entry, it might be better using the following: https://forge.fi-ware.eu/docman/view.php/27/2607/AccessControlDemo.mp4 (right click with mouse then save the file, or run the video directly in the browser...) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 12 giugno 2013 11:54 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Folder for Live Demo videos Hi all, I've just created a dedicated folder for the videos of this second live demo and uploaded the first video that Fermin sent yesterday evening so everybody will be able to use them for other dissemination activities. https://forge.fi-ware.eu/docman/admin/index.php?group_id=27&selected_doc_group_id=448&language_id=&selected_stateid=1 BR Thierry PS : I am going to inform Fermin after the demo to avoid any email pop-up now _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. 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 mcp at tid.es Wed Jun 12 19:10:15 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 12 Jun 2013 19:10:15 +0200 Subject: [Fiware-wpa] PPts for the review In-Reply-To: <51B83E1D.40007@tid.es> References: <51B83E1D.40007@tid.es> Message-ID: <51B8AB77.4030200@tid.es> Hi, I still saw some old ones. I insist! :) If you are adding changes, please incorporate them on top of these. Download them and use this set in any case, not the old ones. Thanks, Miguel El 12/06/2013 11:23, Miguel Carrillo escribi?: Dear all, I uploaded the whole lot to my dropbox. Please take the pack from this address. * https://dl.dropboxusercontent.com/u/25916180/Pres_M24%20-%20final.zip I just changes the "Thanks" one with the new "Questions" slide. Download, check and use these ones. Best regards, 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Jun 13 13:07:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 13 Jun 2013 13:07:50 +0200 Subject: [Fiware-wpa] Presentation on reccomendations Message-ID: <51B9A806.9030000@tid.es> Hi, I believe we may close with a presentation on statements about their recommendations in the last review report. I have prepared the presentation I have uploaded to the docman system at: https://forge.fi-ware.eu/docman/view.php/27/2612/FI-WARE+M24+Review+Answers+to+Recommendations+13-06-12+v1.pptx Please revise and provide feedback ASAP 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) Coordinator and 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 stefano.depanfilis at eng.it Thu Jun 13 13:17:07 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Thu, 13 Jun 2013 13:17:07 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Presentation on reccomendations In-Reply-To: <51B9A806.9030000@tid.es> References: <51B9A806.9030000@tid.es> Message-ID: dear juanjo and all, i think the answer to recommendation 1 is bit week. i mean the live demo is the wonderful approach we have to follow, but the live demo as it is now isw not that "sexy". it is good for developers as it shows very well how to use the generic enablers, but from the "usability" point of view improvements can be done (although this is Always true for software). thus i suggest to add a sub-bullet saying: - provide a more marketable version of the live demo ciao, stefano 2013/6/13 Juanjo Hierro > Hi, > > I believe we may close with a presentation on statements about their > recommendations in the last review report. > > I have prepared the presentation I have uploaded to the docman system at: > > > https://forge.fi-ware.eu/docman/view.php/27/2612/FI-WARE+M24+Review+Answers+to+Recommendations+13-06-12+v1.pptx > > > Please revise and provide feedback ASAP > > 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) Coordinator > and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Jun 13 13:17:42 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 13 Jun 2013 13:17:42 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Presentation on reccomendations In-Reply-To: <51B9A806.9030000@tid.es> References: <51B9A806.9030000@tid.es> Message-ID: Hi Juanjo here is my feedback: . Slide 4: in line about I2ND, it is better removing ETSI ISGNVF, as there aren't yet 'clear plans' for contributing to it . Slide 6: typo (targed -> targeted) For all other slides, messages conveyed are fine. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 13 giugno 2013 13:08 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Presentation on reccomendations Hi, I believe we may close with a presentation on statements about their recommendations in the last review report. I have prepared the presentation I have uploaded to the docman system at: https://forge.fi-ware.eu/docman/view.php/27/2612/FI-WARE+M24+Review+Answers+to+Recommendations+13-06-12+v1.pptx Please revise and provide feedback ASAP 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) Coordinator and 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 manieri at eng.it Thu Jun 13 14:31:33 2013 From: manieri at eng.it (Andrea Manieri) Date: Thu, 13 Jun 2013 14:31:33 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Presentation on reccomendations In-Reply-To: <51B9A806.9030000@tid.es> References: <51B9A806.9030000@tid.es> Message-ID: <51B9BBA5.3080103@eng.it> Dear Juanjo, All, overal replies are fine with me. Two comments: - please state clearly to the PO that we cannot afford anymore to received recommendations after 4 months from the review. Any of the acceptable suggestion can be taken into account. Considering the next Campuseros meeting in September, any recomms in that respect need to be know, say Today! - with respect the OIL at the Campus party I would recommend to have asap a quick (say next week) and open discussion about what-how-whom. The general (and agreedable) statements you made in some slides, may imply a lot for work that may start only now. An overal suggestion. Please anticipate any criticism wrt the PPR (if not already addressed with Arian privately). Best, A. Il 13/06/2013 13:07, Juanjo Hierro ha scritto: > Hi, > > I believe we may close with a presentation on statements about their > recommendations in the last review report. > > I have prepared the presentation I have uploaded to the docman > system at: > > https://forge.fi-ware.eu/docman/view.php/27/2612/FI-WARE+M24+Review+Answers+to+Recommendations+13-06-12+v1.pptx > > > Please revise and provide feedback ASAP > > 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) Coordinator > and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Jun 13 18:51:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 13 Jun 2013 18:51:02 +0200 Subject: [Fiware-wpa] Notes of the preliminary feedback of the review meeting Message-ID: <51B9F876.7000006@tid.es> Dear colleagues, Here it goes my notes regarding the early feedback provided by the EC/reviewers after the review meeting. Overall statement: Technology is there but go to market requires improvement. Positive points: * Technology work has been improved and this has to be recognized * New technology implementations - a whole good package * GEs with potential are there * I2ND has improved a lot addressing concerns in the past despite still some references to legacies * IoT has improved also a lot - more focus between integration of IoT and BigData is necessary * They look for the delivery of the State of the Art deliverable as a mean to check how the GEi owners see their GEis benchmark with those of incumbent players * Attention for smart cities is welcome because it helps to bring focus * Live Demo is good - lot of GEis - it shows that integration was not that much an issue as reviewers initially were afraid * The potential of some GEis is backed by the market analysis * Market analysis is very good deliverable * Seems not to be big delays regarding delivery of Release 2 - which is excellent - they feel more confident that the Release 2 will be ready for the launch of OIL in the planned dates * OIL is the very focus and that is right * Indeed, they see a real commitment of the consortium towards launch of the FI-WARE OIL in the Campus Party (providing the pressure they hadn't manage to achieve during previous reviews) * Impression of team work * Consortium shows confidence and commitment specially certain individuals * They appreciate that we are looking for ways to on-board new projects / third-parties although we have to be careful (see not so-positive points) * Overall: quite good impression Not so-positive points: * Some missing deliverables * Periodic report should be available prior the meeting * Backlog might be more clean but there are some indications that it still requires some work * Technical roadmap still a wish list * Open Specs that were rejected were improved although still they are difficult to read. This doesn't only apply to document deliverables but also the wiki. * Validation has to be improved. Acceptable that is how it was defined in the AB but some improvement is possible there - note: I believe that the recommendations by the reviewers to the EC, explained by Man-sze Li (see below) may have to do with this opportunity to improve * Third party involvement: they like to see the deliverable submitted * Some concerns about limiting third parties to Campus Party is like putting all eggs in one basket so that we have to avoid that. * FI-WARE Catalogue is the window to the world and has to be more appealing and, of course, clear terms and conditions should be there for the GEis * Concerns about attitude towards some recommendations ("we are big so we decide") - note: I guess that this mostly apply to the accountability issue * More needs and effort on evangelism * About expanding FI-WARE to allow other GEis and overall othe GEis from third parties you have to be careful to avoid that what you are going to provide now gets diluted - Useful to have some guidelines/rules about what will be considered a GE * Some concern about how FI-WARE can really gain the attention of the campuseros community - you should find a strategy to connect to the geeks that attend, maybe involve people (the youngers in your development teams) that can speak their same language Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Regarding acceptance/rejection of deliverables they said that they haven't finished their evaluation and that they couldn't provide us a report yet. Man-Sze Li took the floor and informed us about recommendations that the reviewers will officially submit to the EC. In particular the following two: * They will recommend to the EC that it takes actions to ensure that UC projects really assume their mission to use as many GEis as they can, validate GEis, provide feedback and work together with FI-WARE to solve those issues that may appear. * They will recommend to the EC that it takes actions to ensure that the OIL/XiFi facilities will continue available after the FI-WARE and XiFi projects finish I believe this is all. If someone else took more notes, please circulate so that we can all share them. Last but not least, let me thank to all of you for your contribution to this review. Let's cross fingers for the best. 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) Coordinator and 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 pierangelo.garino at telecomitalia.it Fri Jun 14 08:58:45 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 14 Jun 2013 08:58:45 +0200 Subject: [Fiware-wpa] R: [Fiware-demo] Notes of the preliminary feedback of the review meeting In-Reply-To: <51B9F876.7000006@tid.es> References: <51B9F876.7000006@tid.es> Message-ID: Dear Juanjo and All, Thanks a lot for these notes, I'm very happy to see that this time the positive points are more than the not so-positive (ok, let's wait the report, surprises might always come there...). I'm also happy to see that there was some positive remark on I2ND too. Overall, I wish to thank you for the massive effort you have put and continue to put in making FI-WARE progress towards its objectives. Thanks also for the huge work done by all, first of all the Telefonica Team, and of course the support by all the other Partners and Teams deeply involved in making the project successful. If we look at the different review meetings we had so far, I see that the efforts pay! However we still have a long way to go, so we need to concentrate on the next FI-WARE challenges! Best Regards Pier Da: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 13 giugno 2013 18:51 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-demo at lists.fi-ware.eu Oggetto: [Fiware-demo] Notes of the preliminary feedback of the review meeting Dear colleagues, Here it goes my notes regarding the early feedback provided by the EC/reviewers after the review meeting. Overall statement: Technology is there but go to market requires improvement. Positive points: * Technology work has been improved and this has to be recognized * New technology implementations - a whole good package * GEs with potential are there * I2ND has improved a lot addressing concerns in the past despite still some references to legacies * IoT has improved also a lot - more focus between integration of IoT and BigData is necessary * They look for the delivery of the State of the Art deliverable as a mean to check how the GEi owners see their GEis benchmark with those of incumbent players * Attention for smart cities is welcome because it helps to bring focus * Live Demo is good - lot of GEis - it shows that integration was not that much an issue as reviewers initially were afraid * The potential of some GEis is backed by the market analysis * Market analysis is very good deliverable * Seems not to be big delays regarding delivery of Release 2 - which is excellent - they feel more confident that the Release 2 will be ready for the launch of OIL in the planned dates * OIL is the very focus and that is right * Indeed, they see a real commitment of the consortium towards launch of the FI-WARE OIL in the Campus Party (providing the pressure they hadn't manage to achieve during previous reviews) * Impression of team work * Consortium shows confidence and commitment specially certain individuals * They appreciate that we are looking for ways to on-board new projects / third-parties although we have to be careful (see not so-positive points) * Overall: quite good impression Not so-positive points: * Some missing deliverables * Periodic report should be available prior the meeting * Backlog might be more clean but there are some indications that it still requires some work * Technical roadmap still a wish list * Open Specs that were rejected were improved although still they are difficult to read. This doesn't only apply to document deliverables but also the wiki. * Validation has to be improved. Acceptable that is how it was defined in the AB but some improvement is possible there - note: I believe that the recommendations by the reviewers to the EC, explained by Man-sze Li (see below) may have to do with this opportunity to improve * Third party involvement: they like to see the deliverable submitted * Some concerns about limiting third parties to Campus Party is like putting all eggs in one basket so that we have to avoid that. * FI-WARE Catalogue is the window to the world and has to be more appealing and, of course, clear terms and conditions should be there for the GEis * Concerns about attitude towards some recommendations ("we are big so we decide") - note: I guess that this mostly apply to the accountability issue * More needs and effort on evangelism * About expanding FI-WARE to allow other GEis and overall othe GEis from third parties you have to be careful to avoid that what you are going to provide now gets diluted - Useful to have some guidelines/rules about what will be considered a GE * Some concern about how FI-WARE can really gain the attention of the campuseros community - you should find a strategy to connect to the geeks that attend, maybe involve people (the youngers in your development teams) that can speak their same language Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Regarding acceptance/rejection of deliverables they said that they haven't finished their evaluation and that they couldn't provide us a report yet. Man-Sze Li took the floor and informed us about recommendations that the reviewers will officially submit to the EC. In particular the following two: * They will recommend to the EC that it takes actions to ensure that UC projects really assume their mission to use as many GEis as they can, validate GEis, provide feedback and work together with FI-WARE to solve those issues that may appear. * They will recommend to the EC that it takes actions to ensure that the OIL/XiFi facilities will continue available after the FI-WARE and XiFi projects finish I believe this is all. If someone else took more notes, please circulate so that we can all share them. Last but not least, let me thank to all of you for your contribution to this review. Let's cross fingers for the best. 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) Coordinator and 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 jhierro at tid.es Fri Jun 14 10:42:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 14 Jun 2013 10:42:25 +0200 Subject: [Fiware-wpa] URGENT: Your input to the form to send to the EC is urgently needed Message-ID: <51BAD771.4000500@tid.es> Hi all, I want to remind you that your input to the contents of the form to be sent to the EC regarding results of phase 1 are urgently needed. I plan to work on its content along the weekend based on your input and circulate a version Monday early morning that you will have to review along Monday. Nevertheless, contents are on-line, so you wil have the opportunity to check drafts as they are being completed: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Please also confirm that all information regarding FI-WARE GEis in your chapter has been submitted. My plan is to send this document to the EC no later than this coming Tuesday noon. Please send your input ASAP if you want your vision to be taken into account and allocate time on Monday to review what I will send along the weekend. During the follow-up confcall (morning session) we will allocate time to discuss any conflicting points. 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) Coordinator and 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 thorsten.sandfuchs at sap.com Fri Jun 14 11:48:44 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 14 Jun 2013 09:48:44 +0000 Subject: [Fiware-wpa] exploitation plans of industry partners - gathering the needed information and requirements from EC Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F02F0A5@DEWDFEMB11A.global.corp.sap> Dear colleagues, I'd like to share my notes in relation to the exploitation plan-request/recommendation communicated by the EC. Please add your points or possible corrections to my notes in order to unify the potential submission a bit. In the end this consolidated "requirements" and the concrete plan needs to be communicated ASAP to the pcc or all industry partners on WP level Thanks for contributions & all the best, /Thorsten Juanjo notes: - Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Further notes and background how it was communicated - Recommendation by EC o Individual exploitation plans would be changed if requested - tour de chamber was made - most companies said they would change o That is what needs to be done ? Timing: 3 weeks from "now" - max 2 pages. ? Submission deadline would then be 05. July 2013 (right?) o Basically - from everybody on the consortium o If partner won't change it - just send the current one - that's fine o EC would like to know what your plans are - how seriously are you with the whole thing? Further comments that were made during the review (day before) to this topic: - JH: we have exploitation plan which are in common but will have addition internal plans o "This statement is not written anywhere, and needs to be submitted and accepted by the EC" - Reviewer: If exploitation plans are declared confidential, then they potentially can't be reviewed and accepted o JH: other project support the confidential nature of exploitation plan - NK meeting on C-level o Arian saw the meeting and it was not concrete enough to him o Exploitation plan: If nobody gets killed, then we will continue... this is not how it should be - Needed: o Budget & people dedicated to exploitation planned and committed o Budget dedicated people and efforts to describe exploitation effort in a report and not only a plan o Exploitation reports are not tangible now, they need a lot to be detailed o Private exploitation sessions proposed/accepted o Something that proves activities - Arian: We are mostly targeting the time after FI-WARE with this question o Impression of EC: Big players in major countries and little true traction felt from the report & no actions taken -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri Jun 14 12:10:27 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 14 Jun 2013 12:10:27 +0200 Subject: [Fiware-wpa] exploitation plans of industry partners - gathering the needed information and requirements from EC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6647F02F0A5@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6647F02F0A5@DEWDFEMB11A.global.corp.sap> Message-ID: <51BAEC13.6040306@tid.es> Dear Thorsten, dear all, Just one detail that may benefit from clarification: Reviewer: If exploitation plans are declared confidential, then they potentially can't be reviewed and accepted JH: other project support the confidential nature of exploitation plan I believe that the answer from Juanjo intended that the PPP Programme members are protected by a confidentiality clauses so the restricted info they give to the Commission is and must be treated as confidential. Best regards, Miguel El 14/06/2013 11:48, Sandfuchs, Thorsten escribi?: Dear colleagues, I'd like to share my notes in relation to the exploitation plan-request/recommendation communicated by the EC. Please add your points or possible corrections to my notes in order to unify the potential submission a bit. In the end this consolidated "requirements" and the concrete plan needs to be communicated ASAP to the pcc or all industry partners on WP level Thanks for contributions & all the best, /Thorsten Juanjo notes: - Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Further notes and background how it was communicated - Recommendation by EC o Individual exploitation plans would be changed if requested - tour de chamber was made - most companies said they would change o That is what needs to be done ? Timing: 3 weeks from "now" - max 2 pages. ? Submission deadline would then be 05. July 2013 (right?) o Basically - from everybody on the consortium o If partner won't change it - just send the current one - that's fine o EC would like to know what your plans are - how seriously are you with the whole thing? Further comments that were made during the review (day before) to this topic: - JH: we have exploitation plan which are in common but will have addition internal plans o "This statement is not written anywhere, and needs to be submitted and accepted by the EC" - Reviewer: If exploitation plans are declared confidential, then they potentially can't be reviewed and accepted o JH: other project support the confidential nature of exploitation plan - NK meeting on C-level o Arian saw the meeting and it was not concrete enough to him o Exploitation plan: If nobody gets killed, then we will continue... this is not how it should be - Needed: o Budget & people dedicated to exploitation planned and committed o Budget dedicated people and efforts to describe exploitation effort in a report and not only a plan o Exploitation reports are not tangible now, they need a lot to be detailed o Private exploitation sessions proposed/accepted o Something that proves activities - Arian: We are mostly targeting the time after FI-WARE with this question o Impression of EC: Big players in major countries and little true traction felt from the report & no actions taken -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri Jun 14 15:43:29 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 14 Jun 2013 13:43:29 +0000 Subject: [Fiware-wpa] R: Notes of the preliminary feedback of the review meeting Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F030628@DEWDFEMB11A.global.corp.sap> Dear colleagues, Please find a transcript (everything that I could write) in relation to the EC/reviewer statements down below. I put less people in the "To"-line on purpose as the statements written are not as polished as the summary provided by Juanjo - please do use this text only internally & for your eyes only. Please do not distribute it. There is no filter applied and some missing statements are outline in brackets: <{{{{ }}}}> If I got it correctly, the referenced "other side of the medal" was/is not always reflected in the not-so-positive points - but my transcript might be as well wrong here. Please provide your insights and your opinion on the top X things we should target as follow-ups - or share similar notes as Juanjo requested. DISCLAIMER: this is written in Bulletpoint-style with some corrections applied afterwards, so statements might be not reflected 1:1 and errors might have been introduced "Verdict" - Transcript - As usual review report - preliminary now - Conclusion: technology is there - but go-to-market needs some improvements - Comparable with M24 of a lot of projects - but different: - This is NOT business as usual and more for fi-ppp and fi-ware concrete and relevant points will be outlined Positive points - You have very little time, so very incomplete understandable - GE has improved and very clear and considerable improvements - There has been new technology implemented and a whole good packages available at the moment - Some GEs with potential - I2ND improved a lot - some concern in the past o Situation improved a lot in this WP - IoT similar situation o Concerns largely answered in the presentation - In General: looking more out of the box o State of the art deliverable will see what will be really new and what - 3rd party involvement o More and more considered, but <{{{{ MISSSING ..}}}}}> - Attention for Smart Cities as focal point welcomed and right direction - but there is another side of the medal - see below - Live demo was good - much more together - and more than previously o Integration is not so much an issue as we thought it might be! o More GEs - Market analysis showed potential with some GEs - gives more confidents of the fi-ware results - Market results o Praised before and again - very good - excellent deliverable - Release 2 of the Testbed everything seems to be on plan - therefore excellence - hope delivery to end of July runs smoothly - OIL identified as central focus for upcoming period - leading up to campus party - We see a real commitment to the campus party - and a pressure to deliver - EC give you pressure - we see some pressure and real commitment now from this - and the goal to strive for this o Because of OIL we recognize a good spin of collaboration o EC will be always be outsiders - Consortium is showing confidence and commitment as a whole - Certain individuals demonstrated a strong desire making FI-WARE a success - Maturity improving - best showing until so far - Other project that bring value can and should be brought in - spirit is there and should be more reflected in the collaborations o Some possible downsides to this as well - see below - Overall quite good impressions Not so positive points - Missing deliverables - it is ok, but only if this has been explained and communicated - If you hear it at the review first, this is not good - The period report - it is always helpful - even "only" in a draft at the review meeting - we previously even stopped the review for this reason... we don't do that anymore, but: o At least draft must be provided - WP2 o Requirement backlog might be cleaned - some indication seem to be not considered - but the chapters demonstrated in their presentation that overall it seems to work o Architecture deliverable more or less ok o Technical roadmap - more or less a wish list o Open spec - in the past ? Cloud and ioT reject in past, difficult to read in the documents - a lot of abbreviations and little amount of text - but the wiki is as well difficult to read which might discourage developers o Testing deliverable - was resubmitted. o Testplan - Not so much a plan - can be improved o User and programmers guide - are all OK - OIL o Focuses the effort o FI-WARE and current WP still in the driver seat o Let not so much do the new call 3 partners - this still is a collective effort o There might not be a lot of time for a lot _new_ GEs in the upcoming month ... & FI-PPP will go on o Feedback expected from OIL events - Validation o Process can be improved - questionnaire not acceptable - contains some weird questions, some improvements possible there - Then: some concerns about campus party o Attending: 3rd party & campusors, but as well enterprise developers - all are different parties o Do not put all eggs in one basket - Before December 10 - there is a danger for a different mode - change from execution to proposal writing - This is a potential risk ... fi-ware progress endangered if this would happen - 3rd party o Proper processes need to be in place o Catalogue need to be clear (T&C) it is the window to the world o Internal pressure is better means to motivate the consortium - Sustainability of OIL and 3rd parties - this is a concern o Ecosystem strategy in WP11 - but you don't get that feeling from the partner industry exploitation part - General attitude of the <{{{{ consortium, team, on the review ??? }}}}> o We are picking they decide o Need for justification and accountability o Market - interaction - feedback - ... - We praised the commitment by some people, but can they put their companies along? - More evangelize - not only on events - but there is more than that out there - Collaboration WP was not so much consolidated o Germany, France activities, which not presented centrally - and there potentially were others out there. o Consolidation seems to be focused too much in one country - Market again (negative parts) o Public Sector as a target not considered o Smart enterprises not considered o But you can't cover all - Bringing more o Reference implementation, developer kits - not to die lose the speed - o If you accept everything as a GE this is bad - then we will have a lot overlaps, incompatibilities o Need to be properly selected o As a positive results in 1 year from now would be ? Guidelines how to define new generic enablers - Interaction with phase 2 projects o What can the commission do? Welcoming activities: ? Architects week ? Webinars ? Architecture check at the end of this month - Goals should be to improve fi-PPP - Reviewers will have recommendation to the EC and not only to the consortium - Concern raised o Does fi-ware completely understand the campus party? o How to get the message across to those people o The people here - institutional thinking - that is the way you work so this is OK - but campus party attendees might think differently: free spirit, happy thinking o You can't convince a 17 year old with a 70 year old o Suggestion: infiltrate the community by light-minded people of your company o Highly depending on the people room - Recommendation by EC (only one at the moment) o Individual exploitation plans would be changed - tour de chamber was made - most companies said they would change o That is what needs to be done ? 3 weeks from "now" - max 2 pages o Basically - from everybody on the table o If SAP won't change it - just send the current one - that's fine o EC would like to know what your plans are - how seriously are you with the whole thing? REVIEWERS - Li o Recommendations to EC have been done before o Interaction with UC projects - importance with validation of GEs o UC are mend to the be there and they should give your project o Should work much better as we learned from their experience o 1. Recommendation to EC ? Ask the EC to ensure phase 2 UC projects in validation the FI-WARE platform ? Starting point would be: make use of as many GE as possible ? If there is a problem with use - work collaboratively to resolve it with the fi-ware team ? That should be the main program goal ? We will write it down and will be get to the EC o Fi-ware should ensure collaborative work on the UC - good spirit of the collaboration ? We need a very good set of GE, what the world would adopt o 2. Recommendation to EC: Make the Testbed recognized - well beyond the fi-ppp ? Run and potential optimize ? All obstacles would and should be removed ? Xifi and fi-ware must work collaboratively ? Continue to grow - lifetime beyond the projects - DG - only one comment/remark o Viral community - campus party - get it right o If it gets wrong, you can't get it right the second time o If FI-WARE is irrelevant in 2013 it will be hard to reconcile this in 2014 Arian closing statement - Work has improved - Don't lean back From: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Freitag, 14. Juni 2013 08:59 To: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-demo at lists.fi-ware.eu Subject: [Fiware-demo] R: Notes of the preliminary feedback of the review meeting Dear Juanjo and All, Thanks a lot for these notes, I'm very happy to see that this time the positive points are more than the not so-positive (ok, let's wait the report, surprises might always come there...). I'm also happy to see that there was some positive remark on I2ND too. Overall, I wish to thank you for the massive effort you have put and continue to put in making FI-WARE progress towards its objectives. Thanks also for the huge work done by all, first of all the Telefonica Team, and of course the support by all the other Partners and Teams deeply involved in making the project successful. If we look at the different review meetings we had so far, I see that the efforts pay! However we still have a long way to go, so we need to concentrate on the next FI-WARE challenges! Best Regards Pier Da: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 13 giugno 2013 18:51 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-demo at lists.fi-ware.eu Oggetto: [Fiware-demo] Notes of the preliminary feedback of the review meeting Dear colleagues, Here it goes my notes regarding the early feedback provided by the EC/reviewers after the review meeting. Overall statement: Technology is there but go to market requires improvement. Positive points: * Technology work has been improved and this has to be recognized * New technology implementations - a whole good package * GEs with potential are there * I2ND has improved a lot addressing concerns in the past despite still some references to legacies * IoT has improved also a lot - more focus between integration of IoT and BigData is necessary * They look for the delivery of the State of the Art deliverable as a mean to check how the GEi owners see their GEis benchmark with those of incumbent players * Attention for smart cities is welcome because it helps to bring focus * Live Demo is good - lot of GEis - it shows that integration was not that much an issue as reviewers initially were afraid * The potential of some GEis is backed by the market analysis * Market analysis is very good deliverable * Seems not to be big delays regarding delivery of Release 2 - which is excellent - they feel more confident that the Release 2 will be ready for the launch of OIL in the planned dates * OIL is the very focus and that is right * Indeed, they see a real commitment of the consortium towards launch of the FI-WARE OIL in the Campus Party (providing the pressure they hadn't manage to achieve during previous reviews) * Impression of team work * Consortium shows confidence and commitment specially certain individuals * They appreciate that we are looking for ways to on-board new projects / third-parties although we have to be careful (see not so-positive points) * Overall: quite good impression Not so-positive points: * Some missing deliverables * Periodic report should be available prior the meeting * Backlog might be more clean but there are some indications that it still requires some work * Technical roadmap still a wish list * Open Specs that were rejected were improved although still they are difficult to read. This doesn't only apply to document deliverables but also the wiki. * Validation has to be improved. Acceptable that is how it was defined in the AB but some improvement is possible there - note: I believe that the recommendations by the reviewers to the EC, explained by Man-sze Li (see below) may have to do with this opportunity to improve * Third party involvement: they like to see the deliverable submitted * Some concerns about limiting third parties to Campus Party is like putting all eggs in one basket so that we have to avoid that. * FI-WARE Catalogue is the window to the world and has to be more appealing and, of course, clear terms and conditions should be there for the GEis * Concerns about attitude towards some recommendations ("we are big so we decide") - note: I guess that this mostly apply to the accountability issue * More needs and effort on evangelism * About expanding FI-WARE to allow other GEis and overall othe GEis from third parties you have to be careful to avoid that what you are going to provide now gets diluted - Useful to have some guidelines/rules about what will be considered a GE * Some concern about how FI-WARE can really gain the attention of the campuseros community - you should find a strategy to connect to the geeks that attend, maybe involve people (the youngers in your development teams) that can speak their same language Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Regarding acceptance/rejection of deliverables they said that they haven't finished their evaluation and that they couldn't provide us a report yet. Man-Sze Li took the floor and informed us about recommendations that the reviewers will officially submit to the EC. In particular the following two: * They will recommend to the EC that it takes actions to ensure that UC projects really assume their mission to use as many GEis as they can, validate GEis, provide feedback and work together with FI-WARE to solve those issues that may appear. * They will recommend to the EC that it takes actions to ensure that the OIL/XiFi facilities will continue available after the FI-WARE and XiFi projects finish I believe this is all. If someone else took more notes, please circulate so that we can all share them. Last but not least, let me thank to all of you for your contribution to this review. Let's cross fingers for the best. 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) Coordinator and 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]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.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jhierro at tid.es Sun Jun 16 19:58:52 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 16 Jun 2013 19:58:52 +0200 Subject: [Fiware-wpa] URGENT: Your input to the form to send to the EC is urgently needed In-Reply-To: <51BAD771.4000500@tid.es> References: <51BAD771.4000500@tid.es> Message-ID: <51BDFCDC.9000209@tid.es> Dear all, Frankly speaking, it's rather frustrating to see that nobody has added any input to the form we have been asked to fulfill. Still, there is only the input provided some days (or week) ago by SAP and ATOS. 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) Coordinator and 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 On 14/06/13 10:42, Juanjo Hierro wrote: Hi all, I want to remind you that your input to the contents of the form to be sent to the EC regarding results of phase 1 are urgently needed. I plan to work on its content along the weekend based on your input and circulate a version Monday early morning that you will have to review along Monday. Nevertheless, contents are on-line, so you wil have the opportunity to check drafts as they are being completed: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Please also confirm that all information regarding FI-WARE GEis in your chapter has been submitted. My plan is to send this document to the EC no later than this coming Tuesday noon. Please send your input ASAP if you want your vision to be taken into account and allocate time on Monday to review what I will send along the weekend. During the follow-up confcall (morning session) we will allocate time to discuss any conflicting points. 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) Coordinator and 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 GLIKSON at il.ibm.com Sun Jun 16 21:11:34 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 16 Jun 2013 22:11:34 +0300 Subject: [Fiware-wpa] [Fiware-wpl] URGENT: Your input to the form to send to the EC is urgently needed In-Reply-To: <51BDFCDC.9000209@tid.es> References: <51BAD771.4000500@tid.es> <51BDFCDC.9000209@tid.es> Message-ID: Added some comments to Part B. Regards, Alex From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 16/06/2013 08:57 PM Subject: Re: [Fiware-wpl] URGENT: Your input to the form to send to the EC is urgently needed Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear all, Frankly speaking, it's rather frustrating to see that nobody has added any input to the form we have been asked to fulfill. Still, there is only the input provided some days (or week) ago by SAP and ATOS. 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) Coordinator and 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 On 14/06/13 10:42, Juanjo Hierro wrote: Hi all, I want to remind you that your input to the contents of the form to be sent to the EC regarding results of phase 1 are urgently needed. I plan to work on its content along the weekend based on your input and circulate a version Monday early morning that you will have to review along Monday. Nevertheless, contents are on-line, so you wil have the opportunity to check drafts as they are being completed: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Please also confirm that all information regarding FI-WARE GEis in your chapter has been submitted. My plan is to send this document to the EC no later than this coming Tuesday noon. Please send your input ASAP if you want your vision to be taken into account and allocate time on Monday to review what I will send along the weekend. During the follow-up confcall (morning session) we will allocate time to discuss any conflicting points. 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) Coordinator and 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Mon Jun 17 04:08:38 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 17 Jun 2013 04:08:38 +0200 Subject: [Fiware-wpa] [Fiware-wpl] URGENT: Your input to the form to send to the EC is urgently needed In-Reply-To: <51BDFCDC.9000209@tid.es> References: <51BAD771.4000500@tid.es> <51BDFCDC.9000209@tid.es> Message-ID: dear juanjo, i provided some text and comments in section b and c (q3). ciao, stefano 2013/6/16 Juanjo Hierro > Dear all, > > Frankly speaking, it's rather frustrating to see that nobody has added > any input to the form we have been asked to fulfill. Still, there is only > the input provided some days (or week) ago by SAP and ATOS. > > 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) Coordinator > and 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 > > On 14/06/13 10:42, Juanjo Hierro wrote: > > Hi all, > > I want to remind you that your input to the contents of the form to be > sent to the EC regarding results of phase 1 are urgently needed. > > I plan to work on its content along the weekend based on your input and > circulate a version Monday early morning that you will have to review along > Monday. Nevertheless, contents are on-line, so you wil have the > opportunity to check drafts as they are being completed: > > > https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit > > > Please also confirm that all information regarding FI-WARE GEis in your > chapter has been submitted. > > My plan is to send this document to the EC no later than this coming > Tuesday noon. > > Please send your input ASAP if you want your vision to be taken into > account and allocate time on Monday to review what I will send along the > weekend. During the follow-up confcall (morning session) we will > allocate time to discuss any conflicting points. > > 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) Coordinator > and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 17 08:06:45 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Jun 2013 08:06:45 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Message-ID: <51BEA775.3080206@tid.es> Hi, We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. This will help that you free at least 3 hours to provide input/comments to the form to be delivered to the EC. Therefore you don't have any excuse :-) 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) Coordinator and 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 From markus.heller at sap.com Fri Jun 14 17:32:57 2013 From: markus.heller at sap.com (Heller, Markus) Date: Fri, 14 Jun 2013 15:32:57 +0000 Subject: [Fiware-wpa] Thank you Message-ID: <393554EDCF801348BC53C7813C6CB73B19ACAF19@DEWDFEMB14A.global.corp.sap> Dear Juanjo and Miguel, Yesterday I forgot to thank you two for your very hard work in the recent time for the project and for the review and its preparation, so I would like to do this per E-mail now. Let me also extend and tell you that on the personal side I am really quite impressed how many tasks / work streams you can handle at the same time simultaneously for this FI-WARE endeavor and that you managed our FI-WARE ship through this review - paired with the consortiums work and results, of course (let's all keep fingers crossed for the upcoming reviewer results). Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Mon Jun 17 08:28:02 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 17 Jun 2013 06:28:02 +0000 Subject: [Fiware-wpa] Webinars - update - request for action Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89058774@EX10-MB2-MAD.hi.inet> Dear Partners, Let me refresh the guidelines for this task: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_inform_and_adversite_webinars_of_GE I have three main comments which I'd appreciate being taken into consideration: 1. Advertising at twitter is low. I'd appreciate more dissemination by using this channel 2. Some enablers (9) have not been scheduled yet: [cid:image009.png at 01CE6B34.1AE6AE40] [cid:image010.png at 01CE6B34.1AE6AE40] [cid:image011.png at 01CE6B34.1AE6AE40] [cid:image012.png at 01CE6B34.1AE6AE40] [cid:image013.png at 01CE6B34.B18F40F0] [cid:image014.png at 01CE6B34.B18F40F0] [cid:image015.png at 01CE6B34.B18F40F0] [cid:image016.png at 01CE6B34.B18F40F0] 3. Updating status goes a bit behind. There're a few webinars pending (8) [cid:image001.png at 01CE6B33.2CD0D230] [cid:image002.png at 01CE6B33.2CD0D230] [cid:image003.png at 01CE6B33.2CD0D230] [cid:image004.png at 01CE6B33.815616D0] [cid:image005.png at 01CE6B33.815616D0] [cid:image006.png at 01CE6B33.815616D0] [cid:image007.png at 01CE6B33.815616D0] [cid:image008.png at 01CE6B33.D25C1FC0] Thanks for cooperation!!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5610 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6528 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 4222 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 5678 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 4832 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 5395 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 7082 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 4336 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 5598 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 2958 bytes Desc: image010.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image011.png Type: image/png Size: 2693 bytes Desc: image011.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.png Type: image/png Size: 2983 bytes Desc: image012.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image013.png Type: image/png Size: 3989 bytes Desc: image013.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image014.png Type: image/png Size: 3579 bytes Desc: image014.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image015.png Type: image/png Size: 2857 bytes Desc: image015.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image016.png Type: image/png Size: 7371 bytes Desc: image016.png URL: From pierangelo.garino at telecomitalia.it Mon Jun 17 08:42:15 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 17 Jun 2013 08:42:15 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51BEA775.3080206@tid.es> References: <51BEA775.3080206@tid.es> Message-ID: Hi Juanjo, my comments to Part B of the form have been added yesterday. One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. BR Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: luned? 17 giugno 2013 08:07 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Hi, We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. This will help that you free at least 3 hours to provide input/comments to the form to be delivered to the EC. Therefore you don't have any excuse :-) 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) Coordinator and 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl 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 jhierro at tid.es Mon Jun 17 09:21:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Jun 2013 09:21:50 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: References: <51BEA775.3080206@tid.es> Message-ID: <51BEB90E.5030607@tid.es> I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 thorsten.sandfuchs at sap.com Mon Jun 17 10:50:17 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 17 Jun 2013 08:50:17 +0000 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51BEB90E.5030607@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:image002.jpg at 01CE6B48.73873060] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 18322 bytes Desc: image002.jpg URL: From mcp at tid.es Mon Jun 17 11:48:55 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 17 Jun 2013 11:48:55 +0200 Subject: [Fiware-wpa] Update on State of the Art deliverable (action required) In-Reply-To: <51B5DE6A.8070109@tid.es> References: <51B5DE6A.8070109@tid.es> Message-ID: <51BEDB87.4070205@tid.es> Dear all, This is to remind you that I expect the contributions from WP3, WP4, WP5 and WP8 by the end of tomorrow. Please take a look at the checkpoint list at the end of the message below. By sending your chapter contribution to me you are acknowledging that you have verified that they are respected - i.e you as WPL/WPA will personally verify it internally to make sure that we do not have the usual iterations. Best regards, Miguel El 10/06/2013 16:10, Miguel Carrillo escribi?: Dear all, This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP. The last contribution came extremely late (last tuesday) so delivering now could even be backfiring: * If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs) * If we do not deliver, they will complain about not having the deliverable Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it. Things to do/change: * Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter. * Some follow the original convention, some other write [1], [2] .... We want the original one. * Please make sure that the contributions are in alphabetical order (sorted by reference code) In summary: * Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take the table in Data as the reference). Please use the table format (same as Data) * IoT to add such a table * I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right). Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work. Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time: * Contributions not using the attached doc as starting point * Contributions not following the naming convention (also the format - capital letters, table format, etc.) * Contributions with more than one table * Contributions not in alphabetical order * Mismatches between the references in the text and the references table Deadline: Tuesday, 18th of June It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met. Best regards, 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 17 12:12:51 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Jun 2013 12:12:51 +0200 Subject: [Fiware-wpa] exploitation plans of industry partners - gathering the needed information and requirements from EC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6647F02F0A5@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD6647F02F0A5@DEWDFEMB11A.global.corp.sap> Message-ID: <51BEE123.4020909@tid.es> On 14/06/13 11:48, Sandfuchs, Thorsten wrote: Dear colleagues, I'd like to share my notes in relation to the exploitation plan-request/recommendation communicated by the EC. Please add your points or possible corrections to my notes in order to unify the potential submission a bit. In the end this consolidated "requirements" and the concrete plan needs to be communicated ASAP to the pcc or all industry partners on WP level Thanks for contributions & all the best, /Thorsten Juanjo notes: - Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Further notes and background how it was communicated - Recommendation by EC o Individual exploitation plans would be changed if requested - tour de chamber was made - most companies said they would change o That is what needs to be done ? Timing: 3 weeks from "now" - max 2 pages. ? Submission deadline would then be 05. July 2013 (right?) o Basically - from everybody on the consortium This was requested only from industry partners. I believe that the EC and reviewers agreed there is no need for academia partners to submit exploitation plans. o If partner won't change it - just send the current one - that's fine It would not be a matter of re-submitting what was already there but a one-page letter stating that there are no changes of more elaborated plans from what can be read in the exploitation deiverable. o EC would like to know what your plans are - how seriously are you with the whole thing? Further comments that were made during the review (day before) to this topic: - JH: we have exploitation plan which are in common but will have addition internal plans o "This statement is not written anywhere, and needs to be submitted and accepted by the EC" - Reviewer: If exploitation plans are declared confidential, then they potentially can't be reviewed and accepted o JH: other project support the confidential nature of exploitation plan - NK meeting on C-level o Arian saw the meeting and it was not concrete enough to him o Exploitation plan: If nobody gets killed, then we will continue... this is not how it should be - Needed: o Budget & people dedicated to exploitation planned and committed I believe that neither the EC nor the reviewers have asked for budget or resource figures assiged to exploitation plans. A more "high-level" description (but still relevant enough in terms of commitment) is feasible. o Budget dedicated people and efforts to describe exploitation effort in a report and not only a plan I understand this is the same point as the previous, so same comment applies. o Exploitation reports are not tangible now, they need a lot to be detailed o Private exploitation sessions proposed/accepted o Something that proves activities Again, what the EC and reviewers are asking is for one-two pages document describing what is there in the confidential exploitation plans that may help to assess the commitment of the partner with regard to exploitation of results. - Arian: We are mostly targeting the time after FI-WARE with this question o Impression of EC: Big players in major countries and little true traction felt from the report & no actions taken This doesn't require any comment. Cheers, -- Juanjo -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 mev at tid.es Mon Jun 17 12:53:06 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 17 Jun 2013 10:53:06 +0000 Subject: [Fiware-wpa] Backlog - JIRA Instance - GEis with backlog for the Users Cases - Request for information Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89058946@EX10-MB2-MAD.hi.inet> Dear Partners, In order to prepare backlogs/trackers on a JIRA instance for the uses cases, I'd appreciate having your quick feedback on the amount of GEi needing them. Right now I get the following amount of enablers: Apps (11) + Cloud (11) + IoT (22) + Data (11) + I2ND (4) + Security (8) = 67 Enablers from the Forge Trackers. I'd also appreciate having the corresponding person contact data (Name and email). You've got below those available on the Forge Tracker as well. On this regard, WP5 - IoT has many dependences on two people who seems not to be active user on Forge anymore. All the others I'd appreciate having confirmation or alternative names. >From the trackers I get the following enablers: ? WP3 -Apps (@Thorsten) - 11 Enablers o Application Mashup - Rafael Fernandez - UPM o Composition Editor - Miguel Huerta - ATOS RESEARH o Execution Engine - Calin Curescu - ERICSSON o Light Semantic Composition - Joaquin Iranzo - ATOS o Marketplace - Torsten Leidig - SAP o Mediation - Joaquin Iranzo - ATOS RESEARCH o RSSS - Pablo Arozarena - TID o Service Registry - Torsten Leidig - SAP o Service Repository - Andreas Kein - SAP o Service Composition - Calin Curescu - ERICSSON o Store - Francisco de la Vega - CONWET o USDL - Markus Heller - SAP ? WP4 - Cloud (@Alex) - 11 Enablers o Cloud Edge - Henk Heijnen - TECHNICOLOR o Cloud Edge PaaS - Lionel Besson - THALES o Cloud Proxy - Serge Defrance - TECHNICOLOR o Job Scheduler - Lorenzo Cantelmi - INRIA o Monitoring - Andy Edmonds - INTEL o Object Storage - Andy Edmonds - INTEL o PaaS Manager - Sergio Garc?a - TID o Resource Manager - Alex Glikson - IBM o Self Service Interfaces - Andy Edmonds - INTEL o Service Manager - Fernando Lopez - TID o SDC Manager - Sergio Garc?a Gomez - TID ? WP5 - IoT(@Thierry/Carlos) - 22 Enablers o Backend Advanced Connectivity - D?nes Bisztray (?) o Backend Device Management - D?nes Bisztray (?) o Backend Broker - Tobias Jacobs - NECLAB o Backend Discovery Engine - Tarek Elsaleh - SURREY o Backend Resource Level Exposure - D?nes Bisztray (?) o Backend Security - Lorant Farkas (?) o Backend Template handler - D?nes Bisztray (?) o Backend Things Management - D?nes Bisztray (?) o Gateway Advanced Connectivity - D?nes Bisztray (?) o Gateway Data Access Policy - D?nes Bisztray (?) o Gateway Data Handling - Laurent Artusio - ORANGE o Gateway Data Pooling - D?nes Bisztray (?) o Gateway Device Management - D?nes Bisztray (?) o Gateway Local Storage - D?nes Bisztray (?) o Gateway Protocol Adapter - Lorant Farkas (?) o Gateway Resource Level Exposure - Lorant Farkas (?) o Gateway Resource Management - Lorant Farkas (?) o Gateway Security - D?nes Bisztray (?) o Semantic Context Collector - D?nes Bisztray (?) o Semantic Context Mediator - D?nes Bisztray (?) o Semantic Intelligent Decision Making - D?nes Bisztray (?) o Semantic Mediator - D?nes Bisztray (?) ? WP6 - Data(@Sergio) - 11 Enablers o Context Broker - Fermin Galan -TID o BigData-Analysis - Juanjo Hierro - TID o BigData -Francisco Romero - TID o Complex Event Processing - Tali Yatzkar - IBM o Compressed Domain Video Analysis - Boris Motchanov - TELECOMITALIA o Localization Platform - Tanguy Bourgault - THALES o Metadata Preprocessing - Peter Amon - SIEMENS o Publish Subscribe - Boris Motchanov - TELECOMITALIA o Query Broker - Thomas Rieges - SIEMENS o Semantic Annotation - Boris Motchanov - TELECOMITALIA o Semantic Annotation Support - Mauricio Ciprian - ATOS RESEARCH ? WP7 - I2ND(@Pier) - 4 Enablers o Connected Devices Interfaces - Pierangelo Garino - TELECOMITALIA o Cloud Edge - Henk Heijnen - TECHNICOLOR o Network Information and Control - Pascuale Donadio - AlCATEL - LUCENT o Service, Capability, Connectivity and Control - Marius Corici - FOKUS-FRAUNHOFER ? WP8 - Security(@Pascal) - 8 Enablers o AccessControl - Cyril Dangerville - THALES o Context-based Security and Compliance - Antonio Garc?a-V?zquez - ATOS RESEARCH o Data Handling - Francesco Di Cerbo - SAP o Identity Management - Robert Seidl - NSN o Identity Enabler - Wolfgang Steigerwald - TELEKOM o Optional Security Enablers - Richard Egan - THALES o Privacy - Franz-Stefan Preiss - IBM o Monitoring - Daniel Gidoin - THALES Thanks for cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 17 15:03:32 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Jun 2013 15:03:32 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> Message-ID: <51BF0924.7010104@tid.es> Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:part8.03050003.08050803 at tid.es] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 18322 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Mon Jun 17 15:30:16 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 17 Jun 2013 15:30:16 +0200 Subject: [Fiware-wpa] R: R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51BEB90E.5030607@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> Message-ID: Hi Juanjo, can you confirm that section D will need to be max 150 words (in which case we have to shorten it a lot...), or do we have some more flexibility? BR Pier -----Messaggio originale----- Da: Juanjo Hierro [mailto:jhierro at tid.es] Inviato: luned? 17 giugno 2013 09:22 A: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu > [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo > Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are > cancelled IN ORDER TO free time to provide contributions to the form > to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 Mon Jun 17 16:05:44 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Jun 2013 16:05:44 +0200 Subject: [Fiware-wpa] R: R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> Message-ID: <51BF17B8.1070100@tid.es> I realized about the point but, to be honest, I believe we should not be tied to such a restriction. My take on this is sending a complete and meaningful text to the EC and let them make whatever summary is more suitable for their purpose (which we don't know, therefore we can argue that we cannot make a suitable proposal). 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) Coordinator and 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 On 17/06/13 15:30, Garino Pierangelo wrote: > Hi Juanjo, can you confirm that section D will need to be max 150 words (in which case we have to shorten it a lot...), or do we have some more flexibility? > > BR > Pier > > > -----Messaggio originale----- > Da: Juanjo Hierro [mailto:jhierro at tid.es] > Inviato: luned? 17 giugno 2013 09:22 > A: Garino Pierangelo > Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: Re: R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > > I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. > > Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. > > I'm pretty sure that you may provide some more info that the one > currently provided to the part B, C and D sections. You just have to > think about what you will write if you were assigned the task to write > down the answer to those sections. You haven't contributed any input > to part C nor D. > > BTW, there is already content for section D you may be willing to revise. > > 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) Coordinator and 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 > > On 17/06/13 08:42, Garino Pierangelo wrote: >> Hi Juanjo, >> >> my comments to Part B of the form have been added yesterday. >> One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. >> >> BR >> Pier >> >> >> -----Messaggio originale----- >> Da: fiware-wpl-bounces at lists.fi-ware.eu >> [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo >> Hierro >> Inviato: luned? 17 giugno 2013 08:07 >> A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu >> Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are >> cancelled IN ORDER TO free time to provide contributions to the form >> to be delivered to the EC >> >> Hi, >> >> We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. >> >> This will help that you free at least 3 hours to provide >> input/comments to the form to be delivered to the EC. Therefore you >> don't have any excuse :-) >> >> 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) Coordinator and 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-wpl mailing list >> Fiware-wpl at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-wpl >> >> 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 > . > ________________________________ 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 thorsten.sandfuchs at sap.com Tue Jun 18 10:04:45 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 18 Jun 2013 08:04:45 +0000 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51BF0924.7010104@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." ? My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? ? For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:image002.jpg at 01CE6C0B.3FCA36A0] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:image003.jpg at 01CE6C0B.3FCA36A0] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA Terms of use PPP-CA PPP-CA Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:image001.jpg at 01CE6C09.D76578A0] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 18322 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 16997 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 8622 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE availability levels.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 303166 bytes Desc: FI-WARE availability levels.pptx URL: From jhierro at tid.es Tue Jun 18 10:35:40 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 18 Jun 2013 10:35:40 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> Message-ID: <51C01BDC.1050408@tid.es> On 18/06/13 10:04, Sandfuchs, Thorsten wrote: Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. Why should we make things so complicated ? IMHO, a suggestion like this will directly lead us to failure. If any target user finally find things so complicated to use in FI-WARE OIL, they will refuse using the FI-WARE OIL. This is similarly to the single sign-on. Users do not accept well portals that do not implement a single sign-on. Terms and conditions should be common and would need to be signed to create a user account in the FI-WARE OIL. Then, everything that has been made available to FI-WARE OIL users will be subject to the FI-WARE OIL terms and conditions. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope You seem to forget that launching the FI-WARE OIL was part of the DoW, therefore the Grant Agreement you have signed. Did you sign anything with someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a contract with the EC where it was stated that you had to do so :-) I don't believe that nothing else has to be signed. You are not providing software of your GE to anyone else to install it in the FI-WARE OIL on your behalf and then make it accessible to third parties. Same as it happened with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis in the FI-WARE OIL Cloud and make them accessible to third parties (through the Service End Point they will advertise through the FI-WARE Catalogue) or setup blueprint templates that will allow third parties to deploy dedicated FI-WARE GEi instances on their own. The exercise is pretty simple: do you want to comply with the Grant Agreement you have signed and make your GEi accessible in OIL ? You can a) go there and deploy your GEi, advertise the Service End Point through the FI-WARE Catalogue (where it will be clearly stated that it is provided through the OIL so use terms and conditions apply) and/or b) go there and configure a blueprint template that can be used in combination with Cloud blueprint management tools allowing third parties to create and deploy in OIL their own dedicated instances: an action that can only be made by registered users of the OIL (i.e., users who have created an account) who have had to adhere to the FI-WARE OIL terms and conditions. 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." ? My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? You are making things unnecessarily complicated. Best regards, -- Juanjo ? For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:part1.09000607.06010609 at tid.es] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:part2.08070004.00070102 at tid.es] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA Terms of use PPP-CA PPP-CA Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:part10.08060505.07020309 at tid.es] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 ________________________________ 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: image/jpeg Size: 16997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 8622 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 18322 bytes Desc: not available URL: From depa at eng.it Tue Jun 18 12:48:19 2013 From: depa at eng.it (depa at eng.it) Date: Tue, 18 Jun 2013 10:48:19 +0000 Subject: [Fiware-wpa] R: Re: [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51C01BDC.1050408@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> Message-ID: <854624967-1371552540-cardhu_decombobulator_blackberry.rim.net-503161073-@b14.c14.bise7.blackberry> Dear Juanjo, I agree on your points although some refinements migth be needed. Btw, in wp9, as you migth know, we already almost completed a single sign-on and i'd like to discuss it more with you and the rest of the consortium. Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Tue, 18 Jun 2013 10:35:40 To: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] [Fiware-wpa] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From thorsten.sandfuchs at sap.com Tue Jun 18 14:09:56 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 18 Jun 2013 12:09:56 +0000 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51C01BDC.1050408@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> Hi Juanjo, Actually the world is complex - and I only depicted this complexity and tried to simplify or find a reasonable solution that I can understand and talk about in front of others. But failed initially. In the end legal relationships are quite easy, especially if you pin it down to one or more parties interconnecting between each other and the need to have some kind of contractual agreement between these parties. I learned now (as well from your comments) that the FI-PPP CA & GA actually _is_ governing the OIL contributions by GE-software providers towards the FI-WARE instance provider hosting the OIL, in some sense. This simplifies already a lot, as you outlined. Furthermore the CA&GA seems to allow the FI-WARE instance provider to enable others to host "Dedicated SaaS" instances - The FI-WARE instance provider only should make sure that they sign the T&U of the OIL. Responsible party of the provisioned service still is the acting body (in one hand the GE instance provider on the other hand the FI-WARE instance provider.) Additionally the CA&GA "commitments" will hold for the period after M36. The CA & GA obviously do not complete regulate how this access will be allowed, but outline the intension and the final result. Therefore we are on the same page. I still can't clearly see how the services requests will be (on a technical level) governed to be allowed from parties only that signed the OIL T&U - but I'm happy to learn here as well. I updated the table down below - so some cells are now filled. Others are still open: who acts as the FI-WARE instance provider in case of OIL? The Cloud blueprint Manager, TID, Red.IS or a given set of these parties? In any case I'm happy for these insights. They will allow me and hopefully others to clarify this as well towards our GE contributors within the WPs. As similar questions might arise, once this fully hits the consortium. Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 18. Juni 2013 10:36 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC On 18/06/13 10:04, Sandfuchs, Thorsten wrote: Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. Why should we make things so complicated ? IMHO, a suggestion like this will directly lead us to failure. If any target user finally find things so complicated to use in FI-WARE OIL, they will refuse using the FI-WARE OIL. This is similarly to the single sign-on. Users do not accept well portals that do not implement a single sign-on. Terms and conditions should be common and would need to be signed to create a user account in the FI-WARE OIL. Then, everything that has been made available to FI-WARE OIL users will be subject to the FI-WARE OIL terms and conditions. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope You seem to forget that launching the FI-WARE OIL was part of the DoW, therefore the Grant Agreement you have signed. Did you sign anything with someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a contract with the EC where it was stated that you had to do so :-) I don't believe that nothing else has to be signed. You are not providing software of your GE to anyone else to install it in the FI-WARE OIL on your behalf and then make it accessible to third parties. Same as it happened with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis in the FI-WARE OIL Cloud and make them accessible to third parties (through the Service End Point they will advertise through the FI-WARE Catalogue) or setup blueprint templates that will allow third parties to deploy dedicated FI-WARE GEi instances on their own. The exercise is pretty simple: do you want to comply with the Grant Agreement you have signed and make your GEi accessible in OIL ? You can a) go there and deploy your GEi, advertise the Service End Point through the FI-WARE Catalogue (where it will be clearly stated that it is provided through the OIL so use terms and conditions apply) and/or b) go there and configure a blueprint template that can be used in combination with Cloud blueprint management tools allowing third parties to create and deploy in OIL their own dedicated instances: an action that can only be made by registered users of the OIL (i.e., users who have created an account) who have had to adhere to the FI-WARE OIL terms and conditions. 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." => My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? You are making things unnecessarily complicated. Best regards, -- Juanjo => For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:image001.jpg at 01CE6C16.553E4E30] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:image002.jpg at 01CE6C16.553E4E30] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA PPP-CA PPP-CA Terms of use PPP-CA PPP-CA OIL-T&U OIL-T&U Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:image003.jpg at 01CE6C16.553E4E30] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 ________________________________ 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.jpg Type: image/jpeg Size: 16997 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8622 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 18322 bytes Desc: image003.jpg URL: From mcp at tid.es Tue Jun 18 15:33:44 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 18 Jun 2013 15:33:44 +0200 Subject: [Fiware-wpa] Deadline for delivery of GEs in June: 28TH of JUNE Message-ID: <51C061B8.20305@tid.es> Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 18 16:20:06 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 18 Jun 2013 16:20:06 +0200 Subject: [Fiware-wpa] Fwd: [Fiware-demo] Live Demo review M24 videos In-Reply-To: <51C065F6.8050302@tid.es> References: <51C065F6.8050302@tid.es> Message-ID: <51C06C96.7040808@tid.es> FYI in case you are not in the fiware-demo mailint list. -------- Original Message -------- Subject: [Fiware-demo] Live Demo review M24 videos Date: Tue, 18 Jun 2013 15:51:50 +0200 From: Ferm?n Gal?n M?rquez To: fiware-demo at lists.fi-ware.eu Hi, I have uploaded several Live Demo videos to the M24 Review folder. Thanks Thierry for creating the "LiveDemo-Video" placeholder and to Javier Soriano for carrying out the production of most of them. [cid:part1.09060501.05090000 at tid.es] These videos are suitable for internal use but we discourage its use in external channels such as twitter of the FI-WARE public web page due to the several typos we have found, the English language in subtitles that can be improved and the need to polish the script of what is show in some of them. Best regards, ------ Ferm?n ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 26468 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Fiware-demo mailing list Fiware-demo at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-demo From jhierro at tid.es Wed Jun 19 00:35:31 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 19 Jun 2013 00:35:31 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> Message-ID: <51C0E0B3.3010301@tid.es> On 18/06/13 14:09, Sandfuchs, Thorsten wrote: Hi Juanjo, Actually the world is complex - and I only depicted this complexity and tried to simplify or find a reasonable solution that I can understand and talk about in front of others. But failed initially. In the end legal relationships are quite easy, especially if you pin it down to one or more parties interconnecting between each other and the need to have some kind of contractual agreement between these parties. I learned now (as well from your comments) that the FI-PPP CA & GA actually _is_ governing the OIL contributions by GE-software providers towards the FI-WARE instance provider hosting the OIL, in some sense. This simplifies already a lot, as you outlined. Furthermore the CA&GA seems to allow the FI-WARE instance provider to enable others to host "Dedicated SaaS" instances - The FI-WARE instance provider only should make sure that they sign the T&U of the OIL. Responsible party of the provisioned service still is the acting body (in one hand the GE instance provider on the other hand the FI-WARE instance provider.) Additionally the CA&GA "commitments" will hold for the period after M36. The CA & GA obviously do not complete regulate how this access will be allowed, but outline the intension and the final result. Therefore we are on the same page. Great ! I still can't clearly see how the services requests will be (on a technical level) governed to be allowed from parties only that signed the OIL T&U - but I'm happy to learn here as well. Let me elaborate on the vision ... First of all, we will have to implement the concept of "user account" in FI-WARE OIL. That is normal and I trust that potential users will understand that they have to create user accounts in order to use FI-WARE OIL. Second, we will have to implement a mechanism that will force potential users to read and accept the FI-WARE OIL terms and conditions if they want to create a user account. The UPM (Juan Quemada's team, working in the Cloud chapter) will deal will implementation of the FI-WARE OIL portal that deals with creation and management of user accounts, so they will implement the mechanism mentioned above. Last but not least, users will have to authenticate to make use of services provided by GEi. On the other hand, client applications will be required to obtain a valid OAuth2 token in order to issue any request to any FI-WARE GEi. Creation of such a token will require the authentication of users on behalf of which client applications will issue requests, otherwise the token will not be recognized as valid. This should prevent requests from non-valid users. I updated the table down below - so some cells are now filled. Others are still open: who acts as the FI-WARE instance provider in case of OIL? The Cloud blueprint Manager, TID, Red.IS or a given set of these parties? I'm not sure I understand the table ... I would need that you clarify what will be the exact meaning of each cell ... I prefer to wait for that explanation before giving my take on possible values ... In any case I'm happy for these insights. They will allow me and hopefully others to clarify this as well towards our GE contributors within the WPs. As similar questions might arise, once this fully hits the consortium. I agree that all this exercise is useful. Thanks for raising your concerns because many people may have similar ones. Best regards, -- Juanjo Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 18. Juni 2013 10:36 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC On 18/06/13 10:04, Sandfuchs, Thorsten wrote: Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. Why should we make things so complicated ? IMHO, a suggestion like this will directly lead us to failure. If any target user finally find things so complicated to use in FI-WARE OIL, they will refuse using the FI-WARE OIL. This is similarly to the single sign-on. Users do not accept well portals that do not implement a single sign-on. Terms and conditions should be common and would need to be signed to create a user account in the FI-WARE OIL. Then, everything that has been made available to FI-WARE OIL users will be subject to the FI-WARE OIL terms and conditions. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope You seem to forget that launching the FI-WARE OIL was part of the DoW, therefore the Grant Agreement you have signed. Did you sign anything with someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a contract with the EC where it was stated that you had to do so :-) I don't believe that nothing else has to be signed. You are not providing software of your GE to anyone else to install it in the FI-WARE OIL on your behalf and then make it accessible to third parties. Same as it happened with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis in the FI-WARE OIL Cloud and make them accessible to third parties (through the Service End Point they will advertise through the FI-WARE Catalogue) or setup blueprint templates that will allow third parties to deploy dedicated FI-WARE GEi instances on their own. The exercise is pretty simple: do you want to comply with the Grant Agreement you have signed and make your GEi accessible in OIL ? You can a) go there and deploy your GEi, advertise the Service End Point through the FI-WARE Catalogue (where it will be clearly stated that it is provided through the OIL so use terms and conditions apply) and/or b) go there and configure a blueprint template that can be used in combination with Cloud blueprint management tools allowing third parties to create and deploy in OIL their own dedicated instances: an action that can only be made by registered users of the OIL (i.e., users who have created an account) who have had to adhere to the FI-WARE OIL terms and conditions. 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." => My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? You are making things unnecessarily complicated. Best regards, -- Juanjo => For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:part1.04090900.02010300 at tid.es] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:part2.09090700.08060501 at tid.es] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA PPP-CA PPP-CA Terms of use PPP-CA PPP-CA OIL-T&U OIL-T&U Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:part13.03040208.03050306 at tid.es] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 16997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 8622 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 18322 bytes Desc: not available URL: From daniel.gidoin at thalesgroup.com Wed Jun 19 13:00:03 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 19 Jun 2013 13:00:03 +0200 Subject: [Fiware-wpa] Update on State of the Art deliverable (action required) In-Reply-To: <51B5DE6A.8070109@tid.es> References: <51B5DE6A.8070109@tid.es> Message-ID: <32175_1371639617_51C18F3F_32175_11711_1_599118a2-6461-420a-bc3f-e04ac2371798@THSONEA01HUB05P.one.grp> Dear Miguel, Please find attached the SOTA deliverable with the security chapter updates. Best regards Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : lundi 10 juin 2013 16:11 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpa] Update on State of the Art deliverable (action required) Dear all, This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP. The last contribution came extremely late (last tuesday) so delivering now could even be backfiring: * If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs) * If we do not deliver, they will complain about not having the deliverable Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it. Things to do/change: * Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter. * Some follow the original convention, some other write [1], [2] .... We want the original one. * Please make sure that the contributions are in alphabetical order (sorted by reference code) In summary: * Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take the table in Data as the reference). Please use the table format (same as Data) * IoT to add such a table * I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right). Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work. Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time: * Contributions not using the attached doc as starting point * Contributions not following the naming convention (also the format - capital letters, table format, etc.) * Contributions with more than one table * Contributions not in alphabetical order * Mismatches between the references in the text and the references table Deadline: Tuesday, 18th of June It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.2-Sota-Analysis-Security.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3248317 bytes Desc: D.2.6.2-Sota-Analysis-Security.docx URL: From mcp at tid.es Wed Jun 19 14:06:36 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 19 Jun 2013 14:06:36 +0200 Subject: [Fiware-wpa] Update on State of the Art deliverable (action required) In-Reply-To: <32175_1371639617_51C18F3F_32175_11711_1_599118a2-6461-420a-bc3f-e04ac2371798@THSONEA01HUB05P.one.grp> References: <51B5DE6A.8070109@tid.es> <32175_1371639617_51C18F3F_32175_11711_1_599118a2-6461-420a-bc3f-e04ac2371798@THSONEA01HUB05P.one.grp> Message-ID: <51C19ECC.9090207@tid.es> Dear Daniel, dear all, @Daniel: thanks for that, I will check @all:status: * IoT - delivered on time, I will review it (thanks, Thierry) * Security - delivered one day late, I will review it (thanks, Daniel) * Apps - delayed - some partners did not finish their part * Cloud - delayed - no news (Alex, what's the situation?) Best regards, Miguel El 19/06/2013 13:00, GIDOIN Daniel escribi?: Dear Miguel, Please find attached the SOTA deliverable with the security chapter updates. Best regards Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : lundi 10 juin 2013 16:11 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpa] Update on State of the Art deliverable (action required) Dear all, This message is to update you on the status of this deliverable and also to allow direct forwarding to your teams if you like( you are very busy these days). @WPL: be aware that you have to unify the contributions of the partners in your WP. The last contribution came extremely late (last tuesday) so delivering now could even be backfiring: * If we deliver, they will complain about delivering 3-4 days before the review (this will irritate them) and also that the document could be seen as a muddle of different contributions put together with no accord (the references section is largely different across WPs) * If we do not deliver, they will complain about not having the deliverable Assuming that they will complain anyway (and they will be right in doing so), let us get this properly done. After putting all your contributions together and reformatting all the whole lot, it became apparent that each chapter was using a different approach. Theoretically we should have followed the convention from the DoW, that is the one that I circulated in the initial "skeleton" I sent. It is essential to unify it. Things to do/change: * Some have a table at the end, some have more than a table (one at the end of each intra-WP section). We need a single unified table at the end of each chapter. * Some follow the original convention, some other write [1], [2] .... We want the original one. * Please make sure that the contributions are in alphabetical order (sorted by reference code) In summary: * Apps, Cloud and Security to reformat their references (not numbers) and to add a single table at the end (take the table in Data as the reference). Please use the table format (same as Data) * IoT to add such a table * I2ND do not follow it 100% but we can take it as it is. Just convert it into a table (now it is just plain text if I am right). Please use the attached document as the starting point to do this work. It took hours to reformat and we cannot lose all that work. Let us prevent the usual iterations. The way to do it is to get it right from the start. These are the checkpoints would cause a rejection so please avoid them and all of us will make good use of our time: * Contributions not using the attached doc as starting point * Contributions not following the naming convention (also the format - capital letters, table format, etc.) * Contributions with more than one table * Contributions not in alphabetical order * Mismatches between the references in the text and the references table Deadline: Tuesday, 18th of June It is the time to start applying the new rules that we discussed in out latest WPL/WPA call. So please note that if a given WPL sends me a contribution, it means that he has personally checked that the above list of checkpoints is met. Best regards, 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed Jun 19 19:19:44 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 19 Jun 2013 19:19:44 +0200 Subject: [Fiware-wpa] [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <51C0E0B3.3010301@tid.es> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> <51C0E0B3.3010301@tid.es> Message-ID: dear juanjo, the wp9 team is already working with a single sign-on mechanism, actually it is about ready and it involves also people from upm. besides it has an interface that, following the simplicity of the google interface, can be used for the oil portal allowing access to all the services and applications (attached a ppt). can we discuss about this and do not waste effort in parallel tasks? ciao, stefano 2013/6/19 Juanjo Hierro > On 18/06/13 14:09, Sandfuchs, Thorsten wrote: > > Hi Juanjo, > > Actually the world is complex ? and I only depicted this complexity and > tried to simplify or find a reasonable solution that I can understand and > talk about in front of others. But failed initially. In the end legal > relationships are quite easy, especially if you pin it down to one or more > parties interconnecting between each other and the need to have some kind > of contractual agreement between these parties. > > > > I learned now (as well from your comments) that the FI-PPP CA & GA > actually _*is*_ governing the OIL contributions by GE-software providers > towards the FI-WARE instance provider hosting the OIL, in some sense. This > simplifies already a lot, as you outlined. Furthermore the CA&GA seems to > allow the FI-WARE instance provider to enable others to host ?Dedicated > SaaS? instances ? The FI-WARE instance provider only should make sure that > they sign the T&U of the OIL. Responsible party of the provisioned service > still is the acting body (in one hand the GE instance provider on the other > hand the FI-WARE instance provider.) > > Additionally the CA&GA ?commitments? will hold for the period after M36. > > The CA & GA obviously do not complete regulate how this access will be > allowed, but outline the intension and the final result. > > > > Therefore we are on the same page. > > > Great ! > > > > > I still can?t clearly see how the services requests will be (on a > technical level) governed to be allowed from parties only that signed the > OIL T&U ? but I?m happy to learn here as well. > > > Let me elaborate on the vision ... > > First of all, we will have to implement the concept of "user account" in > FI-WARE OIL. That is normal and I trust that potential users will > understand that they have to create user accounts in order to use FI-WARE > OIL. > > Second, we will have to implement a mechanism that will force potential > users to read and accept the FI-WARE OIL terms and conditions if they want > to create a user account. > > The UPM (Juan Quemada's team, working in the Cloud chapter) will deal > will implementation of the FI-WARE OIL portal that deals with creation and > management of user accounts, so they will implement the mechanism mentioned > above. > > Last but not least, users will have to authenticate to make use of > services provided by GEi. On the other hand, client applications will be > required to obtain a valid OAuth2 token in order to issue any request to > any FI-WARE GEi. Creation of such a token will require the > authentication of users on behalf of which client applications will issue > requests, otherwise the token will not be recognized as valid. This > should prevent requests from non-valid users. > > > > > I updated the table down below ? so some cells are now filled. Others are > still open: who acts as the FI-WARE instance provider in case of OIL? The > Cloud blueprint Manager, TID, Red.IS or a given set of these parties? > > > I'm not sure I understand the table ... I would need that you clarify > what will be the exact meaning of each cell ... I prefer to wait for that > explanation before giving my take on possible values ... > > > > In any case I?m happy for these insights. They will allow me and hopefully > others to clarify this as well towards our GE contributors within the WPs. > As similar questions might arise, once this fully hits the consortium. > > > I agree that all this exercise is useful. Thanks for raising your > concerns because many people may have similar ones. > > Best regards, > > -- Juanjo > > > > > Best, > > /Thorsten > > > > > > > > *From:* Juanjo Hierro [mailto:jhierro at tid.es ] > *Sent:* Dienstag, 18. Juni 2013 10:36 > *To:* Sandfuchs, Thorsten > *Cc:* Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; > fiware-wpa at lists.fi-ware.eu > *Subject:* Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC > > > > On 18/06/13 10:04, Sandfuchs, Thorsten wrote: > > Thanks for the comments, I compiled a list of open questions/matrix and > drew a picture to outline at least what I so far understood ? see > attachment for high-res and the graphml-version of the thing. > > > > Can we perhaps jointly fill the missing cells and clarify open questions? > > > > Especially as we seem to not have a legal framework for the OIL, my > current assumption would be > > 1. That every ?using company? (Target audience) needs to sign a > respective ?Terms of Use? bilaterally with all the GE instance providers in > order to request allowance to a single GE instance. The GE-instance > provider takes full responsibility for his own GE instance. > > > Why should we make things so complicated ? IMHO, a suggestion like > this will directly lead us to failure. If any target user finally find > things so complicated to use in FI-WARE OIL, they will refuse using the > FI-WARE OIL. > > This is similarly to the single sign-on. Users do not accept well > portals that do not implement a single sign-on. Terms and conditions > should be common and would need to be signed to create a user account in > the FI-WARE OIL. Then, everything that has been made available to FI-WARE > OIL users will be subject to the FI-WARE OIL terms and conditions. > > > 2. For providing and redistributing software outside of the PPP, > the PPP-CA does not hold any more, therefore all GE-*software* providers > (FI-WARE partners) need to sign something with the ?*FI-WARE Instance*Provider? to allow the latter to redistribute their software within the OIL > scope > > > You seem to forget that launching the FI-WARE OIL was part of the DoW, > therefore the Grant Agreement you have signed. Did you sign anything with > someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a > contract with the EC where it was stated that you had to do so :-) I > don't believe that nothing else has to be signed. You are not providing > software of your GE to anyone else to install it in the FI-WARE OIL on your > behalf and then make it accessible to third parties. Same as it happened > with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis > in the FI-WARE OIL Cloud and make them accessible to third parties (through > the Service End Point they will advertise through the FI-WARE Catalogue) or > setup blueprint templates that will allow third parties to deploy dedicated > FI-WARE GEi instances on their own. > > The exercise is pretty simple: do you want to comply with the Grant > Agreement you have signed and make your GEi accessible in OIL ? You can a) > go there and deploy your GEi, advertise the Service End Point through the > FI-WARE Catalogue (where it will be clearly stated that it is provided > through the OIL so use terms and conditions apply) and/or b) go there and > configure a blueprint template that can be used in combination with Cloud > blueprint management tools allowing third parties to create and deploy in > OIL their own dedicated instances: an action that can only be made by > registered users of the OIL (i.e., users who have created an account) who > have had to adhere to the FI-WARE OIL terms and conditions. > > > 3. If a 3rd party wants to act as GE-Instance provider (Dedicated > SaaS), he needs to sign > > a. Something with the FI-WARE Instance Provider (in order to allow > him to host software) > > b. Something with the GE-software provider (in order to get > allowance for redistribution of the GE software) ? if this allowance is not > given explicitly already with ?2.? > > > > ? My assumption: The OIL ?Terms of Use? currently in preparation would > only cover Point 3 and not point 1 and 2. > > > > What do you think ? did I miss something? > > > You are making things unnecessarily complicated. > > Best regards, > > -- Juanjo > > > > ? For all the relevant contracting it might be good to establish a set > of blueprints to ease up use and consumption of this construct. I doubt > that all of this can be handled by a single ?Terms of Use? for the OIL, as > currently prepared. But please correct me if I?m wrong. > > > > The architecture depicts the instances provided by different entities from > left to right in order of ?more public? use ? e.g. left is the Testbed and > right are the various commercial clouds for 2014++ > > > > In the Platform part itself I tried to make the various involved roles > explicit with an example of UPM ? on the left side UPM is proving the > software ?Application Mashup? (bottom right ?**?) and the instance. > While on the right side it is depicted how e.g. ENVIROFI would host a > dedicated SaaS instance of the UPM GE. > > > > As said ? I tried to gather these dimensions in the following table (as > well as part of the attached pptx). Dimensions and related names are not > fixed, just a first shot to get hold of the complexity. > > > > > > > > *Dimension* > > *Testbed > M27 (v2.3)* > > *XIFI > M30 (v3)* > > *OIL > M29-M36* > > *OIL > M36+* > > *Com. > 2014+* > > *FI-WARE Instance Provider* > > TID (?) > > > > Individual > > *FI-WARE Hosting Provider* > > Red.IS > > > > Individual > > *GE Instance Provider* > > FI-WARE Partners (FP) > > FI-WARE Partners (FP) > > FI-WARE Partners (FP) & 3rd party > > FI-WARE Partners (FP) & 3rd party > > Individual > > *Legal Framework* > > PPP-CA > > PPP-CA > > PPP-CA > > PPP-CA > > *Terms of use* > > PPP-CA > > PPP-CA > > OIL-T&U > > OIL-T&U > > *Scope* > > Non-productive > research&exp. > > Non-productive > research&exp. > > Non-productive > research&exp. > > *Support/SLA from instance provider* > > > > > > *Support/SLA from GE provider* > > Best effort > > Bilateral with XiFi > > Best effort > > Best effort > > Bilateral > > *Target audience* > > UC Phase 1 > > UC Phase 2 > > FI-PPP externals > > FI-PPP externals > > FI-PPP externals > > > > > > > > *From:* Juanjo Hierro [mailto:jhierro at tid.es ] > *Sent:* Montag, 17. Juni 2013 15:04 > *To:* Sandfuchs, Thorsten > *Cc:* Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; > fiware-wpa at lists.fi-ware.eu > *Subject:* Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC > > > > Dear Thorsten, > > The description of the Use Cases that are listed on the wiki looked a > bit weird but I actually asked our TID legal deparment to prepare a first > draft of the terms and conditions that would apply to the FI-WARE OIL under > the assumption that we will actually support UC1 to UC3, of course, this > meaning that the proper clauses for each would have to be incorporated. > My interpretation of these UCs are as follows: > > - UC1: Third parties will be able to use the FI-WARE OIL to > play/experiment with FI-WARE GEis deployed on the FI-WARE OIL > - UC2: Third parties will be able to use the FI-WARE OIL to test > experimental applications developed based on FI-WARE GEis deployed on the > FI-WARE OIL and they will be able to deploy those experimental applications > on the FI-WARE OIL > - UC3: Experimental applications deployed on the FI-WARE OIL will be > made accessible to potential testing users or users participating in > demos/showcases > > > Note that we would support the three of them which are actually > compatible. > > I don't understand very well what we refer as UC4 and, in any case, > there were no clauses proposed to cover them which had helped to understand > the scope for that UC. We understood it was a special case of UC3, where > the experimental application can be considered itself a GE (or > domain-specific common enabler). However, this wouldn't mean any > difference with respect to terms and conditions to be defined. > > Given said the above, the following main ingredients/principles have > been considered for development of the first draft of terms and conditions > (of course, more elaborated legal wording will come in the draft but I > guess you can find this summary more comprehensive ;-): > > - FI-WARE GEis available on FI-WARE OIL can only be used for > experimental purposes. Subscribers to terms and conditions of the FI-WARE > OIL can only develop experimental applications based on FI-WARE GEis > available through the FI-WARE OIL. This means that such applications > cannot be providing any kind of service to third parties. > - FI-WARE GEis available through the FI-WARE OIL will be provided "as > is" so no responsibility will be assumed (liability) > - FI-WARE GEi owners will provide "best-effort" support to usage of > FI-WARE GEis made available through the FI-WARE OIL. > - The specific models for which support of a given FI-WARE GEi will be > provided in the FI-WARE OIL (even if we are talking about "best-effort" > support) will be described in the corresponding entry in the FI-WARE > Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi > owners to limit the models for which support is going to be provided to any > of the following ones (binaries or source code may also be made available > for download and local deployment but I would then recommend to carefully > give a though to what kind of "best-effort" support you can provide): > > > - Global SaaS instances, i.e., instances of the FI-WARE GEi that has > been deployed on the FI-WARE OIL by the GEi owner, offering its functions > "as a Service" through well-defined APIs served at defined Service End > Points > - Dedicated SaaS instances, i.e., meaning that it can be > instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE > Cloud tools > > > - FI-WARE partners will not be responsible from malicious requests or > malitious applications running on OIL > - We will not be responsible for right usage of data in the FI-WARE > OIL. It is assumed that FI-WARE OIL users will comply with any applicable > laws regarding data they are using > - We have rights to take any statistical data that help to improve > operations of the FI-WARE OIL or may help to advertise OIL (in this latter > case, being able to publish what GEis are being used, etc) > - We can interrupt or get rid of any applications running on OIL > unilaterally without prior notice if we detect any malitious behaviour or > this is required for the right performance of OIL, comply with existing > laws, etc > - We can in general break the contract with users with prior notice of > max 15 days even in the case of proper usage > - Any application that is based on FI-WARE GEis deployed on OIL should > shown "powered by FI-WARE" > - Resources offered to FI-WARE users will in any case be limited and > subject to quotas, expiration times, etc > > > As you see, most of these ingredients had been listed on the wiki. > > I hope that we will be able to share soon this first draft of the > FI-WARE OIL terms and conditions so that legal departments can agree on the > concrete wording that will support the above ingredients. > > 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) Coordinator > > and 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 > > On 17/06/13 10:50, Sandfuchs, Thorsten wrote: > > Hi Juanjo, > > Concerning the messaging around the OIL the well-known picture down below > comes to my mind. > > > > I think it is hard to have a messaging towards the outside, as long as we > don?t have a clear internal view on the ?thing?. Therefore it is vital that > you share more of the plan going forward and onboard us ? e.g. in a session > as proposed by Andrea on the topic. Currently I was quite ?astonished? > about the level of depth and engagement plan you layed out in front of the > reviewers. > > > > Let me remind everybody on the 4 basic use cases we gathered in Rome ? > documented here: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients > > For me many of the open questions are still ?open? and pending some > pragmatic decisions. > > > > Especially for the ?Archievements? document we need to have crystal clear > statements what it _*is*_ and what it?s _*not*_ - otherwise nobody can > possibly use the thing? > > > > Best, > > /Thorsten > > > > > > > > > > -----Original Message----- > From: fiware-wpa-bounces at lists.fi-ware.eu [ > mailto:fiware-wpa-bounces at lists.fi-ware.eu] > On Behalf Of Juanjo Hierro > Sent: Montag, 17. Juni 2013 09:22 > To: Garino Pierangelo > Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC > > > > > > I assume that you had booked the timeslots from 11:00 to 12:30 and > > from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. > > > > Therefore, If I'm freeing those slots they become free time for you > > but you must devote that time to review and contribute to the form, not > > to carry out any other task. > > > > I'm pretty sure that you may provide some more info that the one > > currently provided to the part B, C and D sections. You just have to > > think about what you will write if you were assigned the task to write > > down the answer to those sections. You haven't contributed any input > > to part C nor D. > > > > BTW, there is already content for section D you may be willing to > revise. > > > > 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) Coordinator > > and 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 > > > > On 17/06/13 08:42, Garino Pierangelo wrote: > > > Hi Juanjo, > > > > > > my comments to Part B of the form have been added yesterday. > > > One further comment: if you plan to have a call before submitting the > form, it would be better to know in advance to avoid issues in attending. > > > > > > BR > > > Pier > > > > > > > > > -----Messaggio originale----- > > > Da: fiware-wpl-bounces at lists.fi-ware.eu [ > mailto:fiware-wpl-bounces at lists.fi-ware.eu] > Per conto di Juanjo Hierro > > > Inviato: luned? 17 giugno 2013 08:07 > > > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > > > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are > cancelled IN ORDER TO free time to provide contributions to the form to be > delivered to the EC > > > > > > Hi, > > > > > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for > today. > > > > > > This will help that you free at least 3 hours to provide > > > input/comments to the form to be delivered to the EC. Therefore you > > > don't have any excuse :-) > > > > > > 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) Coordinator and 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-wpl mailing list > > > Fiware-wpl at lists.fi-ware.eu > > > https://lists.fi-ware.eu/listinfo/fiware-wpl > > > > > > 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 > > _______________________________________________ > > Fiware-wpa mailing list > > Fiware-wpa at lists.fi-ware.eu > > https://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 > > > ------------------------------ > > > 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 > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 8622 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 18322 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 16997 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Draft_SingleSignOn.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 437971 bytes Desc: not available URL: From jhierro at tid.es Thu Jun 20 00:55:18 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 20 Jun 2013 00:55:18 +0200 Subject: [Fiware-wpa] Fwd: FUTURIUM In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06DCD643@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06DCD643@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <51C236D6.6000403@tid.es> Dear all, Please find below an email from Jes?s Villasante that may be of interest to you. 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) Coordinator and 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 -------------------------------------- Subject: FUTURIUM Dear Mr. Hierro, I would like to draw your attention to the FUTURIUM, an online engagement platform set-up by DG CONNECT inviting our stakeholders (and those to become) to jointly discuss and define long-term visions and ideas for the future. Why is this important? Because the future European research and innovation programme Horizon 2020 will require serious, visionary, high-quality input over many years to come. You, as coordinator of an FP7 project and the partners in your project, can provide a very useful perspective towards what the new programme should offer, and the FUTURIUM provides a very concrete way of influencing it. The outcome of FUTURIUM is an input to the portfolio of needs, visions and policy reflections for the new Commission and the European Parliament. It shall help to give more impact to the stakeholder's, citizen's voice and your voice. On FUTURIUM you can: * Post policy ideas, library entries, comments, just like in a wiki * Organise webinars (our FUTURIUM collaborators will be there to guide you) * Act like a curator for those subjects where you feel particularly involved to enable you to somehow steer the discussions and inputs. This role would need more time investment but will give further opportunity to influence discussions and inputs. I would like to encourage you in particular, but also your project partners, to feed this platform with ideas resulting from your perspective, and profit from its opportunities. You are of course also welcome to pass the message any other potentially interested person so thaty they can share their ideas and concerns. Contact your project officer for more information and guidance. Be curious and have a look at what is already on the FUTURIUM ? maybe ideas that concern you are already present and you can identify others with whom to share. Thank you for your collaboration! Jesus Jesus VILLASANTE Head of Unit [cid:part3.03080602.02000808 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ 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: image/jpeg Size: 1451 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Thu Jun 20 10:06:17 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 20 Jun 2013 08:06:17 +0000 Subject: [Fiware-wpa] discussion on the road ahead was: (RE: Deadline for delivery of GEs in June: 28TH of JUNE) Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6647F03BFCC@DEWDFEMB11A.global.corp.sap> Dear colleagues, I would like to start a discussion about prioritizing the work outlined below or how to in general go forward: Baseline assumptions: ? We need to have "something" reasonable available in the "OIL" ? The OIL will mainly be a SaaS offered by an FI-WARE instance provider for GE instance providers to again offer a GE as SaaS ? There might be a PaaS aspect to it, but currently we rather foresee Mashups or the use of predefined images, than a diverse set of arbitrary runtime-containers and really a lot of "development" (at least in the first months) ? Adopting parties will mainly "consume" and test out our assets ? In most cases "something" will be the software asset installed on a virtual machine or being provided together with a blueprint to instantiate a new virtual machine in order to introduce customizations for a given GEi. ? The "user", "consuming party" aspect: o Whom are we really targeting with our approach? o I this "consuming party" really known to the heart for everybody in the consortium (Are we even targeting all the same people?) o Do we have some first-hand "consumers" that we could show or seek feedback from (not UC2 but real PPP-outsiders?) ? Keep in mind that these "new" people won't come with a lot of funding and not with a written proposal on what they want to do - therefore they need to be given time to understand and do some ideation to adopt the concepts to their specific needs (most potentially they even need some kind of consulting for this) ? Overall pretty much things that are not currently foreseen or tailored by the work that the DoW outlined us to do. Some first conclusions drawn: 1. More priority for a GE instance provider within the OIL would be the two options a. One SaaS instance ("Global SaaS") - potentially multi-tenant enabled b. Blueprint based SaaS-enablement ("Dedicated SaaS") ... only thirdly we would foresee that people start using our binary package and/or even contribute to our development. 2. We currently don't know the "customer" enough - Conclusions what the "consuming parties" needs (conclusion 3) should be verified and refined. 3. Consuming parties need to understand a. Why are we doing all of this (Motivation of FI-WARE going public and building trust and allow sustainable use) b. What is in for them c. How to grasp the functionality and "learn" what the GE _instance_ will provide (not the GE-implementation) d. How to introduce new customizations to the instance e. How to introduce custom data to the system f. ... g. How to come up with new ideas and (domain) extensions and/or possible use cases on top of the generic platform. (Ideation - just on paper and no code involved) h. Whom to contact in order to verify their ideas i. ... j. Only very much later i. develop components that would interact with our GEi ii. request missing functionalities from the existing GE-implementations iii. enhance existing GEis with aspects that have been missing previously iv. ... 4. Somebody would start firstly composing (rather than developing) new applications on top of existing GEs (like the live-demonstrator), which is more like a combination of particular baseline assets and their relevant configuration, than a "classic" software bundle. Some other possible conclusions: - Many consuming parties will o not have a clue what PPP is and why we are doing this o not read pdf-deliverables in order to understand the assets o not read our architecture - E.g. the current "Installation and Admin"-guides mainly focus on the "Installation" part. Not many consuming parties will read this as the GEis will be readily installed (as of conclusion 1 they will be mainly SaaS). At least as many components have no "public"-delivery model (e.g. open source), their binary packages for PP won't be "available" for consuming parties. - E.g. the Unit Testing Plan and Report - I think I don't have to say much to this one: I don't know anybody who really draws something positive out of them. What would be more needed are integration tests (how would somebody be able who deployed a set of GE-I in a landscape "judge" that they are rightfully setup and finally work together as planned) - E.g. the User and Programmers Guide - we have been drawn by the reviewers to document the APIs and therefore most of the content is tailored for consuming developers (which I would see as the third-hand citizens at least judging by the order of priorities I outlined in conclusion 3 Which overall is a pity as in some sense we might have been working with the wrong assumptions previously, but we need to talk about adopting our priorities to the new situation. Overall I think it's easy to grasp where I'm going to: - provide kick-starter information and material in order to understand the motivation of FI-WARE & the plans for the OIL for 3rd parties to consume it - do not only look for the DoW driven deliverable as outlined below, which only would give us the freedom of ticking of some pdf-documents. But give more guidance on how to improve from a content perspective and have the right content for the right people. This might be: o Teach GE-instance providers to decide if they want to provision their stuff as Global SaaS and/or Dedicated SaaS (and the related background in relation to the blueprints) o Compile new sections or desired content for the documentation (might be aligned with the questions raised in conclusions 3) o Increasing a review cycle won't help, as for the conclusions drawn above: the content just isn't there yet - and the pity is: it is even not clear what we really need to provided (otherwise I wouldn't feel the need to writ this :)) - Overall: work on the priorities first and let us try to forget what the DoW really would force us to do in relation to paperwork - at least for the given time until September. Well summing up, this is currently not crystal clear how to go forward. I even can't provide to you the amount of people who would be entitled to work on this - or assume which effort this will draw from us. I think it is clear that this was not planned, and although Miguel mentioned this e.g. in the WP10 telco: WP10 might have _some_ effort reserved from every partner for this, this can't be happening all on WP10. But anyway I wanted to start this discussion and seek some feedback. Might be as well that I'm seeing this one "too complicated" and we have some shortcuts that we are able to take. I would be happy for them. Comments/suggestions? /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Dienstag, 18. Juni 2013 15:34 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, As agreed on June, 3 we expect all the delivery for June ready on the 28th of June. "Ready" means all the manuals and the software. As we said, how you organize it internally in each WP is your bussines. I just want the manuals linked from the private wiki: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 I will start reviews from the links I see here, and only the blocks named "Contributions for June/2013 ". Make sure that you link the right pages from there. Given the complaints in the past, I'll say that prefer the private wiki as the source for all but I will not complain if someones goes to the public one and edits their GEs directly there. I will send an email to the general list but this does not discharge the WPL/WPAs from the obligation of communicating the procedure. In fact, my email will be deliberately shallow and deadline-oriented. I spoke privately to all WPLs in Brussels but one (there is therefore a pending conversation with one of you - I started but we could not finish). The idea is that before the 28th you will perform internal reviews of the deliverables to make sure that all is ok. When you deliver it means that you ensorse it and it has your "seal of approval", meaning the the guidelines are met. In other words, we will reduce the review cycles by delivering more quality. If a given partner refuses to comply with the guidelines you must try to convince them but if they persist in their refusal, you can let us know (a soon as you know it, do not wait for the deadline!!) I also remind you something said on the 3rd of June: We will carry out a more strict documentation review during July, ensuring that what we will put at hands of developers will meet the quality standards required by most of the developers. TID has gone for approving and submitting documentation linked to some of the FI-WARE GEis in some of the chapter to avoid delaying delivery of complete chapters (since all the info linked to GEis in one chapter are integrated as part of the same official deliverable) and because we didn't have the resources/time to carry out such detailed revision (probably the project reviewers also won't have them). However, many of the FI-WARE GEi will be tested by a significant number of developers when they will become available in the FI-WARE OIL and they will carry out a very detailed analysis of the documentation at hand. In this respect, we have to avoid the risk that the whole FI-WARE is judged because of negative comments on a single FI-WARE GEi that didn't deliver good-quality documentation. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Jun 20 14:40:15 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 20 Jun 2013 14:40:15 +0200 Subject: [Fiware-wpa] [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> <51C0E0B3.3010301@tid.es> Message-ID: <9940_1371732033_51C2F841_9940_1798_1_a6183a41-5f79-42d4-873c-5eb69e6f2ec9@THSONEA01HUB03P.one.grp> Dear Stefano, In my view this SSO mechanism you are about here should also be discussed with Security Chapter and put back into perspective of the solutions offered there (I'm considering here IdM GEs and Access Control GEs). As told already it Is important for each of the Chapters (and so WP9) to consider using what Security Chapter offer first before going to another solution. Hope you can share and that we could organize such a joint discussion. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de stefano de panfilis Envoy? : mercredi 19 juin 2013 19:20 ? : Juanjo Hierro Cc : Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] [Fiware-wpa] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC dear juanjo, the wp9 team is already working with a single sign-on mechanism, actually it is about ready and it involves also people from upm. besides it has an interface that, following the simplicity of the google interface, can be used for the oil portal allowing access to all the services and applications (attached a ppt). can we discuss about this and do not waste effort in parallel tasks? ciao, stefano 2013/6/19 Juanjo Hierro > On 18/06/13 14:09, Sandfuchs, Thorsten wrote: Hi Juanjo, Actually the world is complex - and I only depicted this complexity and tried to simplify or find a reasonable solution that I can understand and talk about in front of others. But failed initially. In the end legal relationships are quite easy, especially if you pin it down to one or more parties interconnecting between each other and the need to have some kind of contractual agreement between these parties. I learned now (as well from your comments) that the FI-PPP CA & GA actually _is_ governing the OIL contributions by GE-software providers towards the FI-WARE instance provider hosting the OIL, in some sense. This simplifies already a lot, as you outlined. Furthermore the CA&GA seems to allow the FI-WARE instance provider to enable others to host "Dedicated SaaS" instances - The FI-WARE instance provider only should make sure that they sign the T&U of the OIL. Responsible party of the provisioned service still is the acting body (in one hand the GE instance provider on the other hand the FI-WARE instance provider.) Additionally the CA&GA "commitments" will hold for the period after M36. The CA & GA obviously do not complete regulate how this access will be allowed, but outline the intension and the final result. Therefore we are on the same page. Great ! I still can't clearly see how the services requests will be (on a technical level) governed to be allowed from parties only that signed the OIL T&U - but I'm happy to learn here as well. Let me elaborate on the vision ... First of all, we will have to implement the concept of "user account" in FI-WARE OIL. That is normal and I trust that potential users will understand that they have to create user accounts in order to use FI-WARE OIL. Second, we will have to implement a mechanism that will force potential users to read and accept the FI-WARE OIL terms and conditions if they want to create a user account. The UPM (Juan Quemada's team, working in the Cloud chapter) will deal will implementation of the FI-WARE OIL portal that deals with creation and management of user accounts, so they will implement the mechanism mentioned above. Last but not least, users will have to authenticate to make use of services provided by GEi. On the other hand, client applications will be required to obtain a valid OAuth2 token in order to issue any request to any FI-WARE GEi. Creation of such a token will require the authentication of users on behalf of which client applications will issue requests, otherwise the token will not be recognized as valid. This should prevent requests from non-valid users. I updated the table down below - so some cells are now filled. Others are still open: who acts as the FI-WARE instance provider in case of OIL? The Cloud blueprint Manager, TID, Red.IS or a given set of these parties? I'm not sure I understand the table ... I would need that you clarify what will be the exact meaning of each cell ... I prefer to wait for that explanation before giving my take on possible values ... In any case I'm happy for these insights. They will allow me and hopefully others to clarify this as well towards our GE contributors within the WPs. As similar questions might arise, once this fully hits the consortium. I agree that all this exercise is useful. Thanks for raising your concerns because many people may have similar ones. Best regards, -- Juanjo Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 18. Juni 2013 10:36 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC On 18/06/13 10:04, Sandfuchs, Thorsten wrote: Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. Why should we make things so complicated ? IMHO, a suggestion like this will directly lead us to failure. If any target user finally find things so complicated to use in FI-WARE OIL, they will refuse using the FI-WARE OIL. This is similarly to the single sign-on. Users do not accept well portals that do not implement a single sign-on. Terms and conditions should be common and would need to be signed to create a user account in the FI-WARE OIL. Then, everything that has been made available to FI-WARE OIL users will be subject to the FI-WARE OIL terms and conditions. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope You seem to forget that launching the FI-WARE OIL was part of the DoW, therefore the Grant Agreement you have signed. Did you sign anything with someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a contract with the EC where it was stated that you had to do so :-) I don't believe that nothing else has to be signed. You are not providing software of your GE to anyone else to install it in the FI-WARE OIL on your behalf and then make it accessible to third parties. Same as it happened with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis in the FI-WARE OIL Cloud and make them accessible to third parties (through the Service End Point they will advertise through the FI-WARE Catalogue) or setup blueprint templates that will allow third parties to deploy dedicated FI-WARE GEi instances on their own. The exercise is pretty simple: do you want to comply with the Grant Agreement you have signed and make your GEi accessible in OIL ? You can a) go there and deploy your GEi, advertise the Service End Point through the FI-WARE Catalogue (where it will be clearly stated that it is provided through the OIL so use terms and conditions apply) and/or b) go there and configure a blueprint template that can be used in combination with Cloud blueprint management tools allowing third parties to create and deploy in OIL their own dedicated instances: an action that can only be made by registered users of the OIL (i.e., users who have created an account) who have had to adhere to the FI-WARE OIL terms and conditions. 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." => My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? You are making things unnecessarily complicated. Best regards, -- Juanjo => For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:image001.jpg at 01CE6DC3.84A8AC20] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:image002.jpg at 01CE6DC3.84A8AC20] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA PPP-CA PPP-CA Terms of use PPP-CA PPP-CA OIL-T&U OIL-T&U Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:image003.jpg at 01CE6DC3.84A8AC20] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 ________________________________ 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 16997 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8622 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 18322 bytes Desc: image003.jpg URL: From stefano.depanfilis at eng.it Thu Jun 20 17:08:00 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Thu, 20 Jun 2013 17:08:00 +0200 Subject: [Fiware-wpa] [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: <9940_1371732033_51C2F841_9940_1798_1_a6183a41-5f79-42d4-873c-5eb69e6f2ec9@THSONEA01HUB03P.one.grp> References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> <51C0E0B3.3010301@tid.es> <9940_1371732033_51C2F841_9940_1798_1_a6183a41-5f79-42d4-873c-5eb69e6f2ec9@THSONEA01HUB03P.one.grp> Message-ID: dear pascal, this is as well the thought of juanjo and the way upm is approaching the oil portal, and of course which i totally support! there was a mismatch in the communication i sent, apologises. ciao, stefano 2013/6/20 BISSON Pascal > Dear Stefano,**** > > ** ** > > In my view this SSO mechanism you are about here should also be discussed > with Security Chapter and put back into perspective of the solutions > offered there (I?m considering here IdM GEs and Access Control GEs). As > told already it Is important for each of the Chapters (and so WP9) to > consider using what Security Chapter offer first before going to another > solution. **** > > ** ** > > Hope you can share and that we could organize such a joint discussion.**** > > ** ** > > Best Regards,**** > > Pascal**** > > ** ** > > *De :* fiware-wpl-bounces at lists.fi-ware.eu [mailto: > fiware-wpl-bounces at lists.fi-ware.eu] *De la part de* stefano de panfilis > *Envoy? :* mercredi 19 juin 2013 19:20 > *? :* Juanjo Hierro > *Cc :* Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; > fiware-wpa at lists.fi-ware.eu > *Objet :* Re: [Fiware-wpl] [Fiware-wpa] R: Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC**** > > ** ** > > dear juanjo,**** > > **** > > the wp9 team is already working with a single sign-on mechanism, actually > it is about ready and it involves also people from upm.**** > > besides it has an interface that, following the simplicity of the google > interface, can be used for the oil portal allowing access to all the > services and applications (attached a ppt).**** > > **** > > can we discuss about this and do not waste effort in parallel tasks?**** > > **** > > ciao,**** > > stefano**** > > ** ** > > 2013/6/19 Juanjo Hierro **** > > On 18/06/13 14:09, Sandfuchs, Thorsten wrote:**** > > Hi Juanjo,**** > > Actually the world is complex ? and I only depicted this complexity and > tried to simplify or find a reasonable solution that I can understand and > talk about in front of others. But failed initially. In the end legal > relationships are quite easy, especially if you pin it down to one or more > parties interconnecting between each other and the need to have some kind > of contractual agreement between these parties.**** > > **** > > I learned now (as well from your comments) that the FI-PPP CA & GA > actually _*is*_ governing the OIL contributions by GE-software providers > towards the FI-WARE instance provider hosting the OIL, in some sense. This > simplifies already a lot, as you outlined. Furthermore the CA&GA seems to > allow the FI-WARE instance provider to enable others to host ?Dedicated > SaaS? instances ? The FI-WARE instance provider only should make sure that > they sign the T&U of the OIL. Responsible party of the provisioned service > still is the acting body (in one hand the GE instance provider on the other > hand the FI-WARE instance provider.)**** > > Additionally the CA&GA ?commitments? will hold for the period after M36.** > ** > > The CA & GA obviously do not complete regulate how this access will be > allowed, but outline the intension and the final result.**** > > **** > > Therefore we are on the same page.**** > > > Great !**** > > > > > **** > > **** > > I still can?t clearly see how the services requests will be (on a > technical level) governed to be allowed from parties only that signed the > OIL T&U ? but I?m happy to learn here as well.**** > > ** ** > > Let me elaborate on the vision ... > > First of all, we will have to implement the concept of "user account" in > FI-WARE OIL. That is normal and I trust that potential users will > understand that they have to create user accounts in order to use FI-WARE > OIL. > > Second, we will have to implement a mechanism that will force potential > users to read and accept the FI-WARE OIL terms and conditions if they want > to create a user account. > > The UPM (Juan Quemada's team, working in the Cloud chapter) will deal > will implementation of the FI-WARE OIL portal that deals with creation and > management of user accounts, so they will implement the mechanism mentioned > above. > > Last but not least, users will have to authenticate to make use of > services provided by GEi. On the other hand, client applications will be > required to obtain a valid OAuth2 token in order to issue any request to > any FI-WARE GEi. Creation of such a token will require the > authentication of users on behalf of which client applications will issue > requests, otherwise the token will not be recognized as valid. This > should prevent requests from non-valid users.**** > > > > > **** > > **** > > I updated the table down below ? so some cells are now filled. Others are > still open: who acts as the FI-WARE instance provider in case of OIL? The > Cloud blueprint Manager, TID, Red.IS or a given set of these parties?**** > > ** ** > > I'm not sure I understand the table ... I would need that you clarify > what will be the exact meaning of each cell ... I prefer to wait for that > explanation before giving my take on possible values ...**** > > > > **** > > **** > > In any case I?m happy for these insights. They will allow me and hopefully > others to clarify this as well towards our GE contributors within the WPs. > As similar questions might arise, once this fully hits the consortium.**** > > ** ** > > I agree that all this exercise is useful. Thanks for raising your > concerns because many people may have similar ones. > > Best regards, > > -- Juanjo**** > > > > > **** > > **** > > Best,**** > > /Thorsten* > *** > > **** > > **** > > **** > > *From:* Juanjo Hierro [mailto:jhierro at tid.es ] > *Sent:* Dienstag, 18. Juni 2013 10:36 > *To:* Sandfuchs, Thorsten > *Cc:* Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; > fiware-wpa at lists.fi-ware.eu > *Subject:* Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC**** > > **** > > On 18/06/13 10:04, Sandfuchs, Thorsten wrote:**** > > Thanks for the comments, I compiled a list of open questions/matrix and > drew a picture to outline at least what I so far understood ? see > attachment for high-res and the graphml-version of the thing.**** > > **** > > Can we perhaps jointly fill the missing cells and clarify open questions?* > *** > > **** > > Especially as we seem to not have a legal framework for the OIL, my > current assumption would be **** > > 1. That every ?using company? (Target audience) needs to sign a > respective ?Terms of Use? bilaterally with all the GE instance providers in > order to request allowance to a single GE instance. The GE-instance > provider takes full responsibility for his own GE instance.**** > > > Why should we make things so complicated ? IMHO, a suggestion like > this will directly lead us to failure. If any target user finally find > things so complicated to use in FI-WARE OIL, they will refuse using the > FI-WARE OIL. > > This is similarly to the single sign-on. Users do not accept well > portals that do not implement a single sign-on. Terms and conditions > should be common and would need to be signed to create a user account in > the FI-WARE OIL. Then, everything that has been made available to FI-WARE > OIL users will be subject to the FI-WARE OIL terms and conditions. > > **** > > 2. For providing and redistributing software outside of the PPP, > the PPP-CA does not hold any more, therefore all GE-*software* providers > (FI-WARE partners) need to sign something with the ?*FI-WARE Instance*Provider? to allow the latter to redistribute their software within the OIL > scope**** > > > You seem to forget that launching the FI-WARE OIL was part of the DoW, > therefore the Grant Agreement you have signed. Did you sign anything with > someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a > contract with the EC where it was stated that you had to do so :-) I > don't believe that nothing else has to be signed. You are not providing > software of your GE to anyone else to install it in the FI-WARE OIL on your > behalf and then make it accessible to third parties. Same as it happened > with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis > in the FI-WARE OIL Cloud and make them accessible to third parties (through > the Service End Point they will advertise through the FI-WARE Catalogue) or > setup blueprint templates that will allow third parties to deploy dedicated > FI-WARE GEi instances on their own. > > The exercise is pretty simple: do you want to comply with the Grant > Agreement you have signed and make your GEi accessible in OIL ? You can a) > go there and deploy your GEi, advertise the Service End Point through the > FI-WARE Catalogue (where it will be clearly stated that it is provided > through the OIL so use terms and conditions apply) and/or b) go there and > configure a blueprint template that can be used in combination with Cloud > blueprint management tools allowing third parties to create and deploy in > OIL their own dedicated instances: an action that can only be made by > registered users of the OIL (i.e., users who have created an account) who > have had to adhere to the FI-WARE OIL terms and conditions. > **** > > 3. If a 3rd party wants to act as GE-Instance provider (Dedicated > SaaS), he needs to sign **** > > a. Something with the FI-WARE Instance Provider (in order to allow > him to host software)**** > > b. Something with the GE-software provider (in order to get > allowance for redistribution of the GE software) ? if this allowance is not > given explicitly already with ?2.? **** > > **** > > ? My assumption: The OIL ?Terms of Use? currently in preparation would > only cover Point 3 and not point 1 and 2.**** > > **** > > What do you think ? did I miss something?**** > > > You are making things unnecessarily complicated. > > Best regards, > > -- Juanjo**** > > **** > > ? For all the relevant contracting it might be good to establish a set > of blueprints to ease up use and consumption of this construct. I doubt > that all of this can be handled by a single ?Terms of Use? for the OIL, as > currently prepared. But please correct me if I?m wrong. **** > > **** > > The architecture depicts the instances provided by different entities from > left to right in order of ?more public? use ? e.g. left is the Testbed and > right are the various commercial clouds for 2014++**** > > **** > > **** > > In the Platform part itself I tried to make the various involved roles > explicit with an example of UPM ? on the left side UPM is proving the > software ?Application Mashup? (bottom right ?**?) and the instance. > While on the right side it is depicted how e.g. ENVIROFI would host a > dedicated SaaS instance of the UPM GE.**** > > **** > > **** > > As said ? I tried to gather these dimensions in the following table (as > well as part of the attached pptx). Dimensions and related names are not > fixed, just a first shot to get hold of the complexity.**** > > **** > > **** > > **** > > *Dimension***** > > *Testbed > M27 (v2.3)***** > > *XIFI > M30 (v3)***** > > *OIL > M29-M36***** > > *OIL > M36+***** > > *Com. > 2014+***** > > *FI-WARE Instance Provider***** > > TID (?)**** > > Individual**** > > *FI-WARE Hosting Provider***** > > Red.IS**** > > Individual**** > > *GE Instance Provider***** > > FI-WARE Partners (FP)**** > > FI-WARE Partners (FP)**** > > FI-WARE Partners (FP) & 3rd party**** > > FI-WARE Partners (FP) & 3rd party**** > > Individual**** > > *Legal Framework***** > > PPP-CA**** > > PPP-CA**** > > PPP-CA**** > > PPP-CA**** > > *Terms of use***** > > PPP-CA**** > > PPP-CA**** > > OIL-T&U**** > > OIL-T&U**** > > *Scope***** > > Non-productive > research&exp.**** > > Non-productive > research&exp.**** > > Non-productive > research&exp.**** > > *Support/SLA from instance provider***** > > *Support/SLA from GE provider***** > > Best effort**** > > Bilateral with XiFi**** > > Best effort**** > > Best effort**** > > Bilateral**** > > *Target audience***** > > UC Phase 1**** > > UC Phase 2**** > > FI-PPP externals**** > > FI-PPP externals**** > > FI-PPP externals**** > > **** > > **** > > **** > > *From:* Juanjo Hierro [mailto:jhierro at tid.es ] > *Sent:* Montag, 17. Juni 2013 15:04 > *To:* Sandfuchs, Thorsten > *Cc:* Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; > fiware-wpa at lists.fi-ware.eu > *Subject:* Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC**** > > **** > > Dear Thorsten, > > The description of the Use Cases that are listed on the wiki looked a > bit weird but I actually asked our TID legal deparment to prepare a first > draft of the terms and conditions that would apply to the FI-WARE OIL under > the assumption that we will actually support UC1 to UC3, of course, this > meaning that the proper clauses for each would have to be incorporated. > My interpretation of these UCs are as follows:**** > > - UC1: Third parties will be able to use the FI-WARE OIL to > play/experiment with FI-WARE GEis deployed on the FI-WARE OIL **** > - UC2: Third parties will be able to use the FI-WARE OIL to test > experimental applications developed based on FI-WARE GEis deployed on the > FI-WARE OIL and they will be able to deploy those experimental applications > on the FI-WARE OIL **** > - UC3: Experimental applications deployed on the FI-WARE OIL will be > made accessible to potential testing users or users participating in > demos/showcases **** > > > Note that we would support the three of them which are actually > compatible. > > I don't understand very well what we refer as UC4 and, in any case, > there were no clauses proposed to cover them which had helped to understand > the scope for that UC. We understood it was a special case of UC3, where > the experimental application can be considered itself a GE (or > domain-specific common enabler). However, this wouldn't mean any > difference with respect to terms and conditions to be defined. > > Given said the above, the following main ingredients/principles have > been considered for development of the first draft of terms and conditions > (of course, more elaborated legal wording will come in the draft but I > guess you can find this summary more comprehensive ;-):**** > > - FI-WARE GEis available on FI-WARE OIL can only be used for > experimental purposes. Subscribers to terms and conditions of the FI-WARE > OIL can only develop experimental applications based on FI-WARE GEis > available through the FI-WARE OIL. This means that such applications > cannot be providing any kind of service to third parties. **** > - FI-WARE GEis available through the FI-WARE OIL will be provided "as > is" so no responsibility will be assumed (liability) **** > - FI-WARE GEi owners will provide "best-effort" support to usage of > FI-WARE GEis made available through the FI-WARE OIL. **** > - The specific models for which support of a given FI-WARE GEi will be > provided in the FI-WARE OIL (even if we are talking about "best-effort" > support) will be described in the corresponding entry in the FI-WARE > Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi > owners to limit the models for which support is going to be provided to any > of the following ones (binaries or source code may also be made available > for download and local deployment but I would then recommend to carefully > give a though to what kind of "best-effort" support you can provide): * > *** > > > - Global SaaS instances, i.e., instances of the FI-WARE GEi that has > been deployed on the FI-WARE OIL by the GEi owner, offering its functions > "as a Service" through well-defined APIs served at defined Service End > Points **** > - Dedicated SaaS instances, i.e., meaning that it can be > instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE > Cloud tools **** > > > - FI-WARE partners will not be responsible from malicious requests or > malitious applications running on OIL **** > - We will not be responsible for right usage of data in the FI-WARE > OIL. It is assumed that FI-WARE OIL users will comply with any applicable > laws regarding data they are using **** > - We have rights to take any statistical data that help to improve > operations of the FI-WARE OIL or may help to advertise OIL (in this latter > case, being able to publish what GEis are being used, etc) **** > - We can interrupt or get rid of any applications running on OIL > unilaterally without prior notice if we detect any malitious behaviour or > this is required for the right performance of OIL, comply with existing > laws, etc **** > - We can in general break the contract with users with prior notice of > max 15 days even in the case of proper usage **** > - Any application that is based on FI-WARE GEis deployed on OIL should > shown "powered by FI-WARE" **** > - Resources offered to FI-WARE users will in any case be limited and > subject to quotas, expiration times, etc **** > > > As you see, most of these ingredients had been listed on the wiki. > > I hope that we will be able to share soon this first draft of the > FI-WARE OIL terms and conditions so that legal departments can agree on the > concrete wording that will support the above ingredients. > > 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) Coordinator **** > > and 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**** > > On 17/06/13 10:50, Sandfuchs, Thorsten wrote:**** > > Hi Juanjo,**** > > Concerning the messaging around the OIL the well-known picture down below > comes to my mind.**** > > **** > > I think it is hard to have a messaging towards the outside, as long as we > don?t have a clear internal view on the ?thing?. Therefore it is vital that > you share more of the plan going forward and onboard us ? e.g. in a session > as proposed by Andrea on the topic. Currently I was quite ?astonished? > about the level of depth and engagement plan you layed out in front of the > reviewers.**** > > **** > > Let me remind everybody on the 4 basic use cases we gathered in Rome ? > documented here: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients > **** > > For me many of the open questions are still ?open? and pending some > pragmatic decisions.**** > > **** > > Especially for the ?Archievements? document we need to have crystal clear > statements what it _*is*_ and what it?s _*not*_ - otherwise nobody can > possibly use the thing?**** > > **** > > Best,**** > > /Thorsten* > *** > > **** > > **** > > **** > > **** > > **** > > -----Original Message----- > From: fiware-wpa-bounces at lists.fi-ware.eu [ > mailto:fiware-wpa-bounces at lists.fi-ware.eu] > On Behalf Of Juanjo Hierro > Sent: Montag, 17. Juni 2013 09:22 > To: Garino Pierangelo > Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up > confcalls today are cancelled IN ORDER TO free time to provide > contributions to the form to be delivered to the EC**** > > **** > > **** > > I assume that you had booked the timeslots from 11:00 to 12:30 and**** > > from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall.**** > > **** > > Therefore, If I'm freeing those slots they become free time for you**** > > but you must devote that time to review and contribute to the form, not*** > * > > to carry out any other task.**** > > **** > > I'm pretty sure that you may provide some more info that the one**** > > currently provided to the part B, C and D sections. You just have to**** > > think about what you will write if you were assigned the task to write**** > > down the answer to those sections. You haven't contributed any input**** > > to part C nor D.**** > > **** > > BTW, there is already content for section D you may be willing to > revise.**** > > **** > > 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) Coordinator**** > > and 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**** > > **** > > On 17/06/13 08:42, Garino Pierangelo wrote:**** > > > Hi Juanjo,**** > > > **** > > > my comments to Part B of the form have been added yesterday.**** > > > One further comment: if you plan to have a call before submitting the > form, it would be better to know in advance to avoid issues in attending.* > *** > > > **** > > > BR**** > > > Pier**** > > > **** > > > **** > > > -----Messaggio originale-----**** > > > Da: fiware-wpl-bounces at lists.fi-ware.eu [ > mailto:fiware-wpl-bounces at lists.fi-ware.eu] > Per conto di Juanjo Hierro**** > > > Inviato: luned? 17 giugno 2013 08:07**** > > > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu**** > > > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are > cancelled IN ORDER TO free time to provide contributions to the form to be > delivered to the EC**** > > > **** > > > Hi,**** > > > **** > > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for > today.**** > > > **** > > > This will help that you free at least 3 hours to provide**** > > > input/comments to the form to be delivered to the EC. Therefore you** > ** > > > don't have any excuse :-)**** > > > **** > > > 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) Coordinator and 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-wpl mailing list**** > > > Fiware-wpl at lists.fi-ware.eu**** > > > https://lists.fi-ware.eu/listinfo/fiware-wpl**** > > > **** > > > 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**** > > _______________________________________________**** > > Fiware-wpa mailing list**** > > Fiware-wpa at lists.fi-ware.eu**** > > https://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**** > > **** > ------------------------------ > > > 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**** > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://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**** > -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8622 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 18322 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 16997 bytes Desc: not available URL: From mev at tid.es Thu Jun 20 18:15:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 20 Jun 2013 16:15:03 +0000 Subject: [Fiware-wpa] Backlog - complete review available Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> Dear Partners, Let me inform you that complete review of the backlogs (Tracker + Wiki) are available at the following links: WP3 (@Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2652/FIWARE.backlog.apps.review.20130620-1228.xlsx WP4 (@Alex): https://forge.fi-ware.eu/docman/view.php/27/2653/FIWARE.backlog.cloud.review.20130620-1233.xlsx WP5 (@Thierry): https://forge.fi-ware.eu/docman/view.php/27/2656/FIWARE.backlog.iot.review.20130620-1300.xlsx WP6 (@Sergio): https://forge.fi-ware.eu/docman/view.php/27/2654/FIWARE.backlog.data.review.20130620-1237.xlsx WP7 (@Pier): https://forge.fi-ware.eu/docman/view.php/27/2655/FIWARE.backlog.i2nd.review.20130620-1239.xlsx WP8 (@Pascal): https://forge.fi-ware.eu/docman/view.php/27/2657/FIWARE.backlog.security.review.20130620-1303.xlsx The review scheme follows the same pattern as the previous reviews for the wiki. There's a front page with a summary of the issues with metrics, and then pages with details for each criteria group. Within the reviews you'll find embedded links to the tracker and wiki items for easy access. If you find any mistake or suggestion easing access to the items, please, let me know; it will help me improve the process and its output. I would appreciate you take action for fixing the many issues found. Additional reviews can be provided now easily, it can be done weekly/monthly or if needed on demand as well. Well, if needed I've available for clarifications, either on email, or the phone, as you wish. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Jun 21 09:55:23 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 21 Jun 2013 09:55:23 +0200 Subject: [Fiware-wpa] [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC In-Reply-To: References: <51BEA775.3080206@tid.es> <51BEB90E.5030607@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F033CDE@DEWDFEMB11A.global.corp.sap> <51BF0924.7010104@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036065@DEWDFEMB11A.global.corp.sap> <51C01BDC.1050408@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6647F036C8F@DEWDFEMB11A.global.corp.sap> <51C0E0B3.3010301@tid.es> <9940_1371732033_51C2F841_9940_1798_1_a6183a41-5f79-42d4-873c-5eb69e6f2ec9@THSONEA01HUB03P.one.grp> Message-ID: <16777_1371801331_51C406F3_16777_1429_17_37f9a5b6-344e-4c49-84e7-bf5a01d98634@THSONEA01HUB04P.one.grp> Ok so we are on the same line. And this is just a matter now to get things discussed and organized with all parties to be involved. So let's discuss this at next WPL/WPA and create the task force needed. Best Regards, Pascal De : stefano de panfilis [mailto:stefano.depanfilis at eng.it] Envoy? : jeudi 20 juin 2013 17:08 ? : BISSON Pascal Cc : Juanjo Hierro; Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; GIDOIN Daniel Objet : Re: [Fiware-wpl] [Fiware-wpa] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC dear pascal, this is as well the thought of juanjo and the way upm is approaching the oil portal, and of course which i totally support! there was a mismatch in the communication i sent, apologises. ciao, stefano 2013/6/20 BISSON Pascal > Dear Stefano, In my view this SSO mechanism you are about here should also be discussed with Security Chapter and put back into perspective of the solutions offered there (I'm considering here IdM GEs and Access Control GEs). As told already it Is important for each of the Chapters (and so WP9) to consider using what Security Chapter offer first before going to another solution. Hope you can share and that we could organize such a joint discussion. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de stefano de panfilis Envoy? : mercredi 19 juin 2013 19:20 ? : Juanjo Hierro Cc : Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] [Fiware-wpa] R: Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC dear juanjo, the wp9 team is already working with a single sign-on mechanism, actually it is about ready and it involves also people from upm. besides it has an interface that, following the simplicity of the google interface, can be used for the oil portal allowing access to all the services and applications (attached a ppt). can we discuss about this and do not waste effort in parallel tasks? ciao, stefano 2013/6/19 Juanjo Hierro > On 18/06/13 14:09, Sandfuchs, Thorsten wrote: Hi Juanjo, Actually the world is complex - and I only depicted this complexity and tried to simplify or find a reasonable solution that I can understand and talk about in front of others. But failed initially. In the end legal relationships are quite easy, especially if you pin it down to one or more parties interconnecting between each other and the need to have some kind of contractual agreement between these parties. I learned now (as well from your comments) that the FI-PPP CA & GA actually _is_ governing the OIL contributions by GE-software providers towards the FI-WARE instance provider hosting the OIL, in some sense. This simplifies already a lot, as you outlined. Furthermore the CA&GA seems to allow the FI-WARE instance provider to enable others to host "Dedicated SaaS" instances - The FI-WARE instance provider only should make sure that they sign the T&U of the OIL. Responsible party of the provisioned service still is the acting body (in one hand the GE instance provider on the other hand the FI-WARE instance provider.) Additionally the CA&GA "commitments" will hold for the period after M36. The CA & GA obviously do not complete regulate how this access will be allowed, but outline the intension and the final result. Therefore we are on the same page. Great ! I still can't clearly see how the services requests will be (on a technical level) governed to be allowed from parties only that signed the OIL T&U - but I'm happy to learn here as well. Let me elaborate on the vision ... First of all, we will have to implement the concept of "user account" in FI-WARE OIL. That is normal and I trust that potential users will understand that they have to create user accounts in order to use FI-WARE OIL. Second, we will have to implement a mechanism that will force potential users to read and accept the FI-WARE OIL terms and conditions if they want to create a user account. The UPM (Juan Quemada's team, working in the Cloud chapter) will deal will implementation of the FI-WARE OIL portal that deals with creation and management of user accounts, so they will implement the mechanism mentioned above. Last but not least, users will have to authenticate to make use of services provided by GEi. On the other hand, client applications will be required to obtain a valid OAuth2 token in order to issue any request to any FI-WARE GEi. Creation of such a token will require the authentication of users on behalf of which client applications will issue requests, otherwise the token will not be recognized as valid. This should prevent requests from non-valid users. I updated the table down below - so some cells are now filled. Others are still open: who acts as the FI-WARE instance provider in case of OIL? The Cloud blueprint Manager, TID, Red.IS or a given set of these parties? I'm not sure I understand the table ... I would need that you clarify what will be the exact meaning of each cell ... I prefer to wait for that explanation before giving my take on possible values ... In any case I'm happy for these insights. They will allow me and hopefully others to clarify this as well towards our GE contributors within the WPs. As similar questions might arise, once this fully hits the consortium. I agree that all this exercise is useful. Thanks for raising your concerns because many people may have similar ones. Best regards, -- Juanjo Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Dienstag, 18. Juni 2013 10:36 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC On 18/06/13 10:04, Sandfuchs, Thorsten wrote: Thanks for the comments, I compiled a list of open questions/matrix and drew a picture to outline at least what I so far understood - see attachment for high-res and the graphml-version of the thing. Can we perhaps jointly fill the missing cells and clarify open questions? Especially as we seem to not have a legal framework for the OIL, my current assumption would be 1. That every "using company" (Target audience) needs to sign a respective "Terms of Use" bilaterally with all the GE instance providers in order to request allowance to a single GE instance. The GE-instance provider takes full responsibility for his own GE instance. Why should we make things so complicated ? IMHO, a suggestion like this will directly lead us to failure. If any target user finally find things so complicated to use in FI-WARE OIL, they will refuse using the FI-WARE OIL. This is similarly to the single sign-on. Users do not accept well portals that do not implement a single sign-on. Terms and conditions should be common and would need to be signed to create a user account in the FI-WARE OIL. Then, everything that has been made available to FI-WARE OIL users will be subject to the FI-WARE OIL terms and conditions. 2. For providing and redistributing software outside of the PPP, the PPP-CA does not hold any more, therefore all GE-software providers (FI-WARE partners) need to sign something with the "FI-WARE Instance Provider" to allow the latter to redistribute their software within the OIL scope You seem to forget that launching the FI-WARE OIL was part of the DoW, therefore the Grant Agreement you have signed. Did you sign anything with someone to run the FI-WARE Tesbed provided to UC projects ? Yes, a contract with the EC where it was stated that you had to do so :-) I don't believe that nothing else has to be signed. You are not providing software of your GE to anyone else to install it in the FI-WARE OIL on your behalf and then make it accessible to third parties. Same as it happened with the FI-WARE Testbed, FI-WARE GEi owners will have to deploy their GEis in the FI-WARE OIL Cloud and make them accessible to third parties (through the Service End Point they will advertise through the FI-WARE Catalogue) or setup blueprint templates that will allow third parties to deploy dedicated FI-WARE GEi instances on their own. The exercise is pretty simple: do you want to comply with the Grant Agreement you have signed and make your GEi accessible in OIL ? You can a) go there and deploy your GEi, advertise the Service End Point through the FI-WARE Catalogue (where it will be clearly stated that it is provided through the OIL so use terms and conditions apply) and/or b) go there and configure a blueprint template that can be used in combination with Cloud blueprint management tools allowing third parties to create and deploy in OIL their own dedicated instances: an action that can only be made by registered users of the OIL (i.e., users who have created an account) who have had to adhere to the FI-WARE OIL terms and conditions. 3. If a 3rd party wants to act as GE-Instance provider (Dedicated SaaS), he needs to sign a. Something with the FI-WARE Instance Provider (in order to allow him to host software) b. Something with the GE-software provider (in order to get allowance for redistribution of the GE software) - if this allowance is not given explicitly already with "2." => My assumption: The OIL "Terms of Use" currently in preparation would only cover Point 3 and not point 1 and 2. What do you think - did I miss something? You are making things unnecessarily complicated. Best regards, -- Juanjo => For all the relevant contracting it might be good to establish a set of blueprints to ease up use and consumption of this construct. I doubt that all of this can be handled by a single "Terms of Use" for the OIL, as currently prepared. But please correct me if I'm wrong. The architecture depicts the instances provided by different entities from left to right in order of "more public" use - e.g. left is the Testbed and right are the various commercial clouds for 2014++ [cid:image001.jpg at 01CE6E65.72BF6060] In the Platform part itself I tried to make the various involved roles explicit with an example of UPM - on the left side UPM is proving the software "Application Mashup" (bottom right "") and the instance. While on the right side it is depicted how e.g. ENVIROFI would host a dedicated SaaS instance of the UPM GE. [cid:image002.jpg at 01CE6E65.72BF6060] As said - I tried to gather these dimensions in the following table (as well as part of the attached pptx). Dimensions and related names are not fixed, just a first shot to get hold of the complexity. Dimension Testbed M27 (v2.3) XIFI M30 (v3) OIL M29-M36 OIL M36+ Com. 2014+ FI-WARE Instance Provider TID (?) Individual FI-WARE Hosting Provider Red.IS Individual GE Instance Provider FI-WARE Partners (FP) FI-WARE Partners (FP) FI-WARE Partners (FP) & 3rd party FI-WARE Partners (FP) & 3rd party Individual Legal Framework PPP-CA PPP-CA PPP-CA PPP-CA Terms of use PPP-CA PPP-CA OIL-T&U OIL-T&U Scope Non-productive research&exp. Non-productive research&exp. Non-productive research&exp. Support/SLA from instance provider Support/SLA from GE provider Best effort Bilateral with XiFi Best effort Best effort Bilateral Target audience UC Phase 1 UC Phase 2 FI-PPP externals FI-PPP externals FI-PPP externals From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 17. Juni 2013 15:04 To: Sandfuchs, Thorsten Cc: Garino Pierangelo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC Dear Thorsten, The description of the Use Cases that are listed on the wiki looked a bit weird but I actually asked our TID legal deparment to prepare a first draft of the terms and conditions that would apply to the FI-WARE OIL under the assumption that we will actually support UC1 to UC3, of course, this meaning that the proper clauses for each would have to be incorporated. My interpretation of these UCs are as follows: * UC1: Third parties will be able to use the FI-WARE OIL to play/experiment with FI-WARE GEis deployed on the FI-WARE OIL * UC2: Third parties will be able to use the FI-WARE OIL to test experimental applications developed based on FI-WARE GEis deployed on the FI-WARE OIL and they will be able to deploy those experimental applications on the FI-WARE OIL * UC3: Experimental applications deployed on the FI-WARE OIL will be made accessible to potential testing users or users participating in demos/showcases Note that we would support the three of them which are actually compatible. I don't understand very well what we refer as UC4 and, in any case, there were no clauses proposed to cover them which had helped to understand the scope for that UC. We understood it was a special case of UC3, where the experimental application can be considered itself a GE (or domain-specific common enabler). However, this wouldn't mean any difference with respect to terms and conditions to be defined. Given said the above, the following main ingredients/principles have been considered for development of the first draft of terms and conditions (of course, more elaborated legal wording will come in the draft but I guess you can find this summary more comprehensive ;-): * FI-WARE GEis available on FI-WARE OIL can only be used for experimental purposes. Subscribers to terms and conditions of the FI-WARE OIL can only develop experimental applications based on FI-WARE GEis available through the FI-WARE OIL. This means that such applications cannot be providing any kind of service to third parties. * FI-WARE GEis available through the FI-WARE OIL will be provided "as is" so no responsibility will be assumed (liability) * FI-WARE GEi owners will provide "best-effort" support to usage of FI-WARE GEis made available through the FI-WARE OIL. * The specific models for which support of a given FI-WARE GEi will be provided in the FI-WARE OIL (even if we are talking about "best-effort" support) will be described in the corresponding entry in the FI-WARE Catalogue. Note: If you ask me, I would highly recommend FI-WARE GEi owners to limit the models for which support is going to be provided to any of the following ones (binaries or source code may also be made available for download and local deployment but I would then recommend to carefully give a though to what kind of "best-effort" support you can provide): * Global SaaS instances, i.e., instances of the FI-WARE GEi that has been deployed on the FI-WARE OIL by the GEi owner, offering its functions "as a Service" through well-defined APIs served at defined Service End Points * Dedicated SaaS instances, i.e., meaning that it can be instantiated in the FI-WARE Cloud and provided "as a Service" using FI-WARE Cloud tools * FI-WARE partners will not be responsible from malicious requests or malitious applications running on OIL * We will not be responsible for right usage of data in the FI-WARE OIL. It is assumed that FI-WARE OIL users will comply with any applicable laws regarding data they are using * We have rights to take any statistical data that help to improve operations of the FI-WARE OIL or may help to advertise OIL (in this latter case, being able to publish what GEis are being used, etc) * We can interrupt or get rid of any applications running on OIL unilaterally without prior notice if we detect any malitious behaviour or this is required for the right performance of OIL, comply with existing laws, etc * We can in general break the contract with users with prior notice of max 15 days even in the case of proper usage * Any application that is based on FI-WARE GEis deployed on OIL should shown "powered by FI-WARE" * Resources offered to FI-WARE users will in any case be limited and subject to quotas, expiration times, etc As you see, most of these ingredients had been listed on the wiki. I hope that we will be able to share soon this first draft of the FI-WARE OIL terms and conditions so that legal departments can agree on the concrete wording that will support the above ingredients. 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) Coordinator and 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 On 17/06/13 10:50, Sandfuchs, Thorsten wrote: Hi Juanjo, Concerning the messaging around the OIL the well-known picture down below comes to my mind. I think it is hard to have a messaging towards the outside, as long as we don't have a clear internal view on the "thing". Therefore it is vital that you share more of the plan going forward and onboard us - e.g. in a session as proposed by Andrea on the topic. Currently I was quite "astonished" about the level of depth and engagement plan you layed out in front of the reviewers. Let me remind everybody on the 4 basic use cases we gathered in Rome - documented here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Open_Innovation_Lab_Terms_and_Condition_Ingredients For me many of the open questions are still "open" and pending some pragmatic decisions. Especially for the "Archievements" document we need to have crystal clear statements what it _is_ and what it's _not_ - otherwise nobody can possibly use the thing... Best, /Thorsten [cid:image003.jpg at 01CE6E65.72BF6060] -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 17. Juni 2013 09:22 To: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] R: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC I assume that you had booked the timeslots from 11:00 to 12:30 and from 14:30 to 16:00 to the joint WPLs/WPAs follow-up confcall. Therefore, If I'm freeing those slots they become free time for you but you must devote that time to review and contribute to the form, not to carry out any other task. I'm pretty sure that you may provide some more info that the one currently provided to the part B, C and D sections. You just have to think about what you will write if you were assigned the task to write down the answer to those sections. You haven't contributed any input to part C nor D. BTW, there is already content for section D you may be willing to revise. 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) Coordinator and 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 On 17/06/13 08:42, Garino Pierangelo wrote: > Hi Juanjo, > > my comments to Part B of the form have been added yesterday. > One further comment: if you plan to have a call before submitting the form, it would be better to know in advance to avoid issues in attending. > > BR > Pier > > > -----Messaggio originale----- > Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro > Inviato: luned? 17 giugno 2013 08:07 > A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Oggetto: [Fiware-wpl] Joint WPLs/WPAs follow-up confcalls today are cancelled IN ORDER TO free time to provide contributions to the form to be delivered to the EC > > Hi, > > We will cancel the joint WPLs/WPAs follow-up confcalls scheduled for today. > > This will help that you free at least 3 hours to provide > input/comments to the form to be delivered to the EC. Therefore you > don't have any excuse :-) > > 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) Coordinator and 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-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > 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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://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 ________________________________ 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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 -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 16997 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8622 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 18322 bytes Desc: image003.jpg URL: From mev at tid.es Fri Jun 21 10:05:49 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 21 Jun 2013 08:05:49 +0000 Subject: [Fiware-wpa] webinars - missing wrap-ups - request for action Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89059A01@EX10-MB2-MAD.hi.inet> Dear Parners, Some webinar session's wrap-up are missing. I'd appreciate having them marked as Done (If so, or re-scheduled) and the number of attendees (?). Find below the missing sessions marked brows. [cid:image001.png at 01CE6E64.9E920E00] [cid:image002.png at 01CE6E64.9E920E00] [cid:image003.png at 01CE6E65.B993B360] [cid:image004.png at 01CE6E66.6888FA10] [cid:image005.png at 01CE6E66.6888FA10] [cid:image006.png at 01CE6E66.6888FA10] [cid:image007.png at 01CE6E66.6888FA10] [cid:image008.png at 01CE6E66.6888FA10] [cid:image009.png at 01CE6E66.E558BA80] [cid:image010.png at 01CE6E66.E558BA80] Thanks for cooperation. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6651 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6842 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5756 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 7840 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 8398 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 6385 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 7984 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 5817 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 8103 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 5793 bytes Desc: image010.png URL: From mev at tid.es Fri Jun 21 14:58:59 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 21 Jun 2013 12:58:59 +0000 Subject: [Fiware-wpa] webinars - using WP lists for coordinating action related to webinars Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89059D12@EX10-MB2-MAD.hi.inet> Dear WP Leaders, I've received suggestion for using involved work package lists for issues related to webinars. I have no objection to it considering this proposal is welcome by you. So please, those WP Leaders not accepting it, let me know so as not to cc it. Kind regards, Manuel From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: viernes, 21 de junio de 2013 10:06 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] webinars - missing wrap-ups - request for action Dear Parners, Some webinar session's wrap-up are missing. I'd appreciate having them marked as Done (If so, or re-scheduled) and the number of attendees (?). Find below the missing sessions marked brows. [cid:image001.png at 01CE6E8F.DA1F5BF0] [cid:image002.png at 01CE6E8F.DA1F5BF0] [cid:image003.png at 01CE6E8F.DA1F5BF0] [cid:image004.png at 01CE6E8F.DA1F5BF0] [cid:image005.png at 01CE6E8F.DA1F5BF0] [cid:image006.png at 01CE6E8F.DA1F5BF0] [cid:image007.png at 01CE6E8F.DA1F5BF0] [cid:image008.png at 01CE6E8F.DA1F5BF0] [cid:image009.png at 01CE6E8F.DA1F5BF0] [cid:image010.png at 01CE6E8F.DA1F5BF0] Thanks for cooperation. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 6651 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6842 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5756 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 7840 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 8398 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 6385 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 7984 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 5817 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 8103 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 5793 bytes Desc: image010.png URL: From jhierro at tid.es Sat Jun 22 11:13:41 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sat, 22 Jun 2013 11:13:41 +0200 Subject: [Fiware-wpa] Fwd: First draft of FI-WARE Open Innovation Lab (OIL) Terms and Conditions In-Reply-To: <51C55C96.7030004@tid.es> References: <51C55C96.7030004@tid.es> Message-ID: <51C56AC5.1000409@tid.es> Dear all, I have just released the first version of the FI-WARE Open Innovation Lab (OIL) Terms and Conditions to the fiware-legal mailing list where representatives of the legal departments at your companies are supposed to be subscribed. Please double-check they have received them and make sure they will devote the necessary time to get a version of them by end of July that will allow us to launch the FI-WARE OIL as planned in compliance with our contract. You know that launch of the FI-WARE OIL is a rather critical milestone for us because the FI-WARE OIL is probably the main first ingredient based on which we will build the innovation ecosystem we aim to build. It is very important that you contact your legal attorneys to make sure they undertand the relevance of this. You will see that we have setup a process with regular confcalls and gathering of comments. Please take your time to read the email I have just sent to fiware-legal. We have explained them, and you should be aware of this, that we will actually launch the FI-WARE OIL at the defined milestone (end of July) with whatever version of these terms and conditions can be generated that enough number of partners can adhere to. We, as coordinators, assume this may mean that some FI-WARE GEis from some partners may not be made available when launching the FI-WARE OIL. We know this may put them in a difficult situation in front of the EC but we cannot block launch of the FI-WARE OIL because a partner doesn't agree with the language of a particular paragraph that suits enough number of partners. We are not goint allow any mess like with the FI-WARE Legal Notice in this respect. On the other hand, such conflicts, if any, hopefully may be solved soon so that a new version of the Terms and Conditions can be produced and the affected FI-WARE GEi incorporated in the FI-WARE OIL in due time. After all, and as stated in section 1.4 of this draft of the Terms and Conditions "We may amend these Terms and Conditions at any time by posting a revised version of these Terms and Conditions in the FI-WARE OIL Site." Given said that, I rather believe that closing an agreement on a first version of the Terms and Conditions is feasible for all partners. We have spent a lot of time at Telefonica closing this first draft to make sure it was pretty complete, so there shouldn't be too many changes needed. 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) Coordinator and 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 -------- Original Message -------- Subject: First draft of FI-WARE Open Innovation Lab (OIL) Terms and Conditions Date: Sat, 22 Jun 2013 10:13:10 +0200 From: Juanjo Hierro To: fiware-legal at lists.fi-ware.eu CC: jhierro >> "Juan J. Hierro" Dear all, Please find enclosed the first draft of the FI-WARE Open Innovation Lab (OIL) Terms and Conditions prepared for the Legal Department of Telefonica for your revision. These Terms and Conditions will govern the usage of services provided by products implementing FI-WARE Generic Enablers (GEis) deployed and provided to third parties in the FI-WARE Open Innovation Lab (OIL). A very strict and unmovable milestone in the FI-WARE project is that the FI-WARE OIL must be available by end of July in compliance with our contract. This means that we have to close a first version of these Terms and Conditions by that date. Indeed, we will actually launch the FI-WARE OIL at the defined milestone (end of July) with whatever version of these terms and conditions can be generated that enough number of partners can adhere to. There is a very high expectation from the EC and the research and entrepreneurs community and this means we cannot delay launching of the FI-WARE Open Innovation Lab. We, as coordinators, assume this may mean that some FI-WARE GEis from some partners may not be made available when launching the FI-WARE OIL. We know this may put them in a difficult situation in front of the EC but we cannot block launch of the FI-WARE OIL because a partner doesn't agree with the language of a particular paragraph that suits enough number of partners. On the other hand, such conflicts, if any, hopefully may be solved soon so that a new version of the Terms and Conditions can be produced and the affected FI-WARE GEi incorporated in the FI-WARE OIL in due time. After all, and as stated in section 1.4 of this draft of the Terms and Conditions "We may amend these Terms and Conditions at any time by posting a revised version of these Terms and Conditions in the FI-WARE OIL Site." Indeed, we feel very positive that we can reach soon an agreement on the FI-WARE Open Innovation Lab (OIL) Terms and Conditions because the provided draft has been worked out very carefully. We haven't invented it from the scratch, as you can imagine, but have relied on the terms and conditions of similar services, some being known as best-of-the-breed and very consolidated services. In order to meet the defined milestone, we will setup regular confcalls every Monday from 09:30am to 11:00am CET. They will be slots to discuss on proposal changes and make progress on closing agreements. Of course, without preventing us to make progress over the email. Dial-in details will be circulated later through this mailing list. In addition, we will run two sessions next week, one on Tuesday June 25, 09:30am CET, and another on Wednesday June 26 at 16:00 CET to introduce you the general principles behind the FI-WARE OIL and the FI-WARE OIL Terms and Conditions and to solve you any first doubts you may have. Again, Dial-in details will be circulated later through this mailing list. You are asked to send your first set of comments by Thursday June 27 EOB (17:00 CET). We will open a slot for additional comments every week, from Monday 09:30am CET until Thursday 12:00pm CET (noon) that same week. Then, we will compile, circulate and use the provided comments during the following Monday session. There are a number of technical and business principles assumed in the definition of the FI-WARE OIL. Let me enumerate some of them that I believe that you should always bear in mind while reading these terms and conditions: * The FI-WARE OIL will be an environment, available to any third party for free, where third parties will be able to experiment with FI-WARE technologies (GEis) and will be able to host, develop and test Applications based on FI-WARE technologies. The FI-WARE OIL comprises a site (where a portal is deployed) through which FI-WARE Cloud Hosting Services are offered enabling third parties to setup resources for hosting their experimental applications. Besides, it comprises a number of FI-WARE GEis deployed on the FI-WARE Cloud or any other federated premise and offered "as a Service" so that applications can use them based on APIs. Some of these FI-WARE GEis will be deployed by the corresponding FI-WARE GEi owner or by third parties using tools we have provided to them to do so. * The FI-WARE OIL is provided only for experimental usage. No production service should be offered by third parties based on FI-WARE OIL services. * We do not warrant any service level or any level of support of FI-WARE OIL Services. Support will be provided in "best-effort" mode and users of the FI-WARE OIL Services will make use of it at their own risk. Of course, there are many other aspects considered in the terms and conditions to protect ourselves and our rights and interests, as well as to develop the above listed principles, but you will discover them while reviewing the attached draft. Looking forward your collaboration to get this done on due time. Best regards, -- Juanjo Hierro ------------- 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) Coordinator and 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE OIL Terms and Conditions v1.0 13-06-22.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 151923 bytes Desc: not available URL: From jhierro at tid.es Sun Jun 23 17:02:32 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 23 Jun 2013 17:02:32 +0200 Subject: [Fiware-wpa] ToDos from now and the following months In-Reply-To: <51BECEEF.30206@tid.es> References: <51BECEEF.30206@tid.es> Message-ID: <51C70E08.10506@tid.es> Dear colleagues, I would like to highlight a number of points that we have to deal with, and we have to concentrate our efforts on, during the following weeks. All these points will be followed up regularly at our joint WPLs/WPAs follow-up confcalls. Staty tuned regarding further clarifications that will come from your WPLs/WPAs or us in the following days. If someone believes there are additional points to add which require a close follow-up, please don't hesitate to comment. Now the list: * FI-WARE Catalogue: * Entries have to comply with the guidelines provided at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * A reference example can be found at: http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud * Entries which do not comply with the guidelines or whose contents are considered weak will not be made visible and corresponding FI-WARE GEis will therefore not be made available as part of the FI-WARE OIL and Testbed, with potential implications in rejection of costs * Don't forget that FI-WARE GEi have to make public their terms of availability beyond the FI-PPP ("External availability" in "Terms and Conditions") * FI-WARE Legal Notice: * All FI-WARE specifications have to be updated (if not already) to make a reference to any of the two final Legal Notices that have been finally approved: * with implicit patents license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) * with explicit license on essential patents: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) * Detailed instructions about how to update the corresponding sections will be provided * Detailed revision of FI-WARE GEi software and accompanying documentation: * A more in-depth and demanding revision will be carried out from now until end of July, targeted to avoid publication of FI-WARE GEis that we may foresee can receive criticism by developers beyond the research community. * This revision will be carried by programmers from Telefonica and Engineering, other volunteers are welcome. * Note that FI-WARE GEis that have been allowed to be part of FI-WARE r2.2 in our recent submission to the EC may be rejected to be made available in OIL. * In-depth revision of the Architecture and FI-WARE Open Specifications on the wiki * FI-WARE OIL, Testbed and internal Cloud environments setup * The teams in WP10 will have to work hard in order to setup three different FI-WARE Clouds for: * internal developments within FI-WARE (testing of patches, development of new releases) * the FI-WARE Testbed offered to UC projects * the FI-WARE OIL, dealing with quotas * Proper security mechanisms have to be put in place * The deliverables that had to do with Integration Plan and Report will have to be submitted * FI-WARE OIL: recipes for automated deployment of FI-WARE GEi dedicated instances * some FI-WARE GEis may be deployed as a global instance, accessible "as a Service" so that functions can be invoked through well-defined Service End Points and APIs * however, it is highly desirable that some FI-WARE GEis can also be instantiated by application developers on top of the virtual infrastructure they will setup to run their application (Dedicated instances). For this, it is highly recommended that FI-WARE GEi owners support one or several of the following options: * virtual machine images with the FI-WARE GEi properly installed and configured * deployment "recipes" that can be used together with the FI-WARE Cloud tools enabling automated deployment of software on individual VMs * deployment "recipes" that can be used together with the FI-WARE Cloud Blueprint management tools * webinars training on how to build "recipes" have to be organized and run * FI-WARE OIL/Testbed and GEis Support * A JIRA environment will be setup per FI-WARE GEi and for each of the three environments defined above (internal, FI-WARE Testbed and FI-WARE OIL) * A workflow will be defined regarding how tickets can be issued, monitored and resolved. * Access to the corresponding JIRA should be made available from the FI-WARE Catalogue * Generation of training material * WP9 will provide an eLearning and webinar platform which will be adopted as main vehicle for providing training contents * FI-WARE GEi owners will be requested to prepare training material targeted to developers. At least one recorded webinar should be made available per FI-WARE GEi * Organization of Campus Party * There will be a 1-hour session at the main starge of the Campus Party, either on Monday afternoon or Tuesday (most likely this second), where the FI-WARE OIL will be announced. Tentatively, the structure of this session might be (not necessarily in this order): * 15' of someone from the Kroes cabinet that will elaborate on the FI-PPP and will announce launch of the FI-WARE OIL * 15' of keynote speech from some reputed person in the Developers' Community endorsing the initiative (and helping to attract audience :-) * 30' of some sort of panel involving executives from some of the major industry partners (maybe they seating in sofas at the stage and someone acting as chairing/interviewer) * A number of workshops should be programmed, targeted to architects and developers and trying to cover programming practices/exercises that enable attendees to make "hands on" the technology: * Currently we have secured 4 2-hours slot workshops in the workshop area of the Campus Party booked for us. We had initially asked for 6 but seems to be not feasible and I'm trying to negotiate for 5. * Following are the workshops that we have currently identified as suitable for the audience of the Campus Party (programmers), we may decide which to go because there may not be enough number of workshop slots: * Cloud (every function provided through the portal, from deployment of Object Storage and individual VMs, through automated deployment of software on top of available VM instances up to the definition and deployment of blueprints) * Context/Data Management platform (combining a comprehensive review of the Context Broker, CEP and BigData GEs) * IoT, focused on how to connect sensors and make measured data available on the FI-WARE OIL * WireCloud * Identity Management and OAuth2-based Access Control to APIs (potentially to be merged with Cloud) * Advanced Middleware * Media-related GEis (subject to availability of GEis coming from FI-INMEDIA) * Advanced 3D and augmented reality (subject to availability of a first version of GEis coming from WeX) * There will be 2 1-hour sessions where we will be able to introduce the FI-PPP, FI-WARE, explain the ambition, main results, etc as well as announce the different challenges. There will be a space for the UC projects to announce their open calls * There will be a booth we will need to agree how to attend so that we can answer people who may come with questions. * We are negotiating a room for FI-WARE internal meetings for about 10 people, with whiteboard and projector. Our intention is that the different chapters may book slots during the Campus Party for them to meet there, therefore having a f2f meeting there. This way, attendance to the Campus Party may work as a kind of plenary meeting. * FI-WARE OIL terms and conditions * Telefonica has circulated a first draft of terms and conditions and legal departments has been asked to come to a final version by end of July. * The technical/business lead of the different FI-WARE partners should approach their legal departments to make sure they understand the whole thing. * The deadline by end of July is unmovable. FI-WARE GEis for which the corresponding owner do not subscribe the terms and conditions available by then will not be published in the FI-WARE OIL. * FI-WARE Backlog * A report on the status regarding revision and clean up of the FI-WARE Backlog will be submitted to the EC and reviewers by end of June. * Teams have to keep going in all regarding APs related to clean up of the FI-WARE Backlog and adoption of Agile practices * FI-WARE State of the Art deliverable: * We have to get it done. * FI-WARE 3rd Party Innovation Enablement: * We have to find out how we can finish a revised version 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) Coordinator and 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 mcp at tid.es Mon Jun 24 10:37:36 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 24 Jun 2013 10:37:36 +0200 Subject: [Fiware-wpa] Minutes for today's WPL/WPA meeting Message-ID: <51C80550.4070109@tid.es> Dear all, Still work in progress but I anticipate the link (in read only mode for the time being) * https://docs.google.com/document/d/1NGqZPL0uNvsmpnrJI5x-MxdN6YJi0hBePs6euimoUrs/edit# See you in a few minutes. BR 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Mon Jun 24 16:48:51 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 24 Jun 2013 14:48:51 +0000 Subject: [Fiware-wpa] OIL release related question to the PO Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66484D78FF7@DEWDFEMB11A.global.corp.sap> Hi Juanjo, I'd like to potentially add to the background information on the potential email to the PO in relation to how "public" he sees the delivery of FI-WARE v2 the details below. Overall this lead to my assumption that we are currently not _forced_ and therefore we can't internally really state that this is a milestone that is as fixed as you position it. In the end you might be able to incorporate this a bit in the formal question to the PO. In the end the resolution would be to internally and externally agree on: - D.10.2.b and M27 is a deadline which UC Trials will get access - Our plan is to release this one to the public in relation to the OIL endeavor towards beginning of Sept. (even if I browse your current draft of "achievements" you state: "The second major release of FI-WARE will be made available to UC projects working in the phase 2 of the FI-PPP from end of July 2013 in the FI-WARE Testbed and to third parties beyond the FI-PPP in a new environment referred as the FI-WARE Open Innovation Lab (OIL) to be launched early September 2013. Both environments will be updated as results of minor releases within the third major release ...") Best, /Thorsten 1. The list of milestones in the DoW outlines availability of the Testbed in the M27 milestone mainly towards "UC Trials" 2. WP11 - objectives In addition to the technology provided by FI-WARE, the project will work towards the establishment of an Open Innovation Lab around the FI-WARE testbed that may help third parties and not just the Use Case projects, to test how innovative applications may be developed on top of FI-WARE GEs. To maximize the impact of FI-WARE we will consider successful stories of user involvement like the ones of ENoLL. ? This is another indication that the DoW actually does not completely resolve all relevant milestones and deadlines 3. The 4th review report outlines: ? Reviewers actually do seem to not know a concrete "plan" on concrete dates and milestones or didn't expect it to be in M27, otherwise this paragraph wouldn't make much sense. I don't think that D12.2.3 or D.11.2.2 actually would present this plan, but please correct me if I'm wrong. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 74239 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 27845 bytes Desc: image002.png URL: From mev at tid.es Mon Jun 24 17:25:29 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 24 Jun 2013 15:25:29 +0000 Subject: [Fiware-wpa] JIRA - please, update your GEis, and the number of users requested Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A50B@EX10-MB2-MAD.hi.inet> Dear Partners, Following the action point for having the JIRA instance ready as soon as possible, please, provided input to the spreadsheet linked below. There're two main groups, the first with the input I collected from the tracker, the seconds collects the feedback from you, some missing, some already provided. Anyway, the number of users requested is pending. I had appointed 1 for each GEi owner, now you have a chance to request a different amount. The first proposition is to have an instance on demand for 10 months for 50 users (1 user for GEi) FIWARE - JIRA users - https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdEx0YmVHSnFDZFBUZ28wRV9fY3hla1E&usp=sharing If anything, please, let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Jun 24 19:09:48 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 24 Jun 2013 19:09:48 +0200 Subject: [Fiware-wpa] OIL release related question to the PO In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66484D78FF7@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66484D78FF7@DEWDFEMB11A.global.corp.sap> Message-ID: <51C87D5C.8040905@tid.es> Dear Thorsten, One thing is when the FI-WARE OIL is launched, i.e., officially announced to the public and another thing is when it is ready. For us, it is unnegotiable that the environment has to be ready by July 31st, and ready means not only technically ready but with a consolidated version of the terms and conditions ready. If you allow me to say it, having the consolidated version of the terms and conditions ready by July 31st is even more important. BTW, the milestone also applies to availability of complete info about the FI-WARE GEis in the FI-WARE Catalogue, in compliance with defined guidelines, as well as provided with documentation of enough quality for consumption and acceptance by third party developers. 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) Coordinator and 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 On 24/06/13 16:48, Sandfuchs, Thorsten wrote: Hi Juanjo, I'd like to potentially add to the background information on the potential email to the PO in relation to how "public" he sees the delivery of FI-WARE v2 the details below. Overall this lead to my assumption that we are currently not _forced_ and therefore we can't internally really state that this is a milestone that is as fixed as you position it. In the end you might be able to incorporate this a bit in the formal question to the PO. In the end the resolution would be to internally and externally agree on: - D.10.2.b and M27 is a deadline which UC Trials will get access - Our plan is to release this one to the public in relation to the OIL endeavor towards beginning of Sept. (even if I browse your current draft of "achievements" you state: "The second major release of FI-WARE will be made available to UC projects working in the phase 2 of the FI-PPP from end of July 2013 in the FI-WARE Testbed and to third parties beyond the FI-PPP in a new environment referred as the FI-WARE Open Innovation Lab (OIL) to be launched early September 2013. Both environments will be updated as results of minor releases within the third major release ...") Best, /Thorsten 1. The list of milestones in the DoW outlines availability of the Testbed in the M27 milestone mainly towards "UC Trials" [cid:part1.01010402.06040807 at tid.es] 2. WP11 - objectives In addition to the technology provided by FI-WARE, the project will work towards the establishment of an Open Innovation Lab around the FI-WARE testbed that may help third parties and not just the Use Case projects, to test how innovative applications may be developed on top of FI-WARE GEs. To maximize the impact of FI-WARE we will consider successful stories of user involvement like the ones of ENoLL. ? This is another indication that the DoW actually does not completely resolve all relevant milestones and deadlines 3. The 4th review report outlines: [cid:part2.05080405.03030806 at tid.es] ? Reviewers actually do seem to not know a concrete "plan" on concrete dates and milestones or didn't expect it to be in M27, otherwise this paragraph wouldn't make much sense. I don't think that D12.2.3 or D.11.2.2 actually would present this plan, but please correct me if I'm wrong. ________________________________ 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: image/png Size: 74239 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 27845 bytes Desc: not available URL: From GLIKSON at il.ibm.com Mon Jun 24 22:04:40 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 24 Jun 2013 23:04:40 +0300 Subject: [Fiware-wpa] [Fiware-wpl] Backlog - complete review available In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> Message-ID: Dear Manuel, Fantastic work! Few comments/questions: I wonder whether it makes sense spending hours on fixing items which have been closed a year ago or even more. We had different guidelines, and, frankly, not sure anyone cares.. At least for Cloud, this would require very significant effort, with (close to) zero value to anyone. Can you, please, update the labels of the new sprint/release fields to include the corresponding time periods (e.g., "Release 2.3: May 2013 - July 2013")? This would make validation easier. Can you, please, elaborate how exactly did you determine parent-child relationship? IMO, we don't have 100% deterministic guidelines about this. what do you mean by "all Functional Items ordered" and "all workitems"? regarding "url not needed but available on tracker- to be removed", I think it is actually a good practice for stories to specify URL of the corresponding Feature. If you insist -- maybe you can just remove it with a script. Some of the inconsistencies can be easily fixed using a script -- probably similar to the one you are using to gather statistics? This could save effort. Can you, please, explain the meaning of "due not dismissed backlog items not available in wiki directory", "matching tracker - wiki" and "items details already provided on the wiki"? I've checked few -- and everything seems fine.. What is the problem with name = reference? I am not aware of guidelines preventing this. Any action items from W-C4? Once again, very impressive! Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE To: "fiware-wpl at lists.fi-ware.eu" , Cc: "fiware-wpa at lists.fi-ware.eu" Date: 20/06/2013 07:16 PM Subject: [Fiware-wpl] Backlog - complete review available Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear Partners, Let me inform you that complete review of the backlogs (Tracker + Wiki) are available at the following links: WP3 (@Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2652/FIWARE.backlog.apps.review.20130620-1228.xlsx WP4 (@Alex): https://forge.fi-ware.eu/docman/view.php/27/2653/FIWARE.backlog.cloud.review.20130620-1233.xlsx WP5 (@Thierry): https://forge.fi-ware.eu/docman/view.php/27/2656/FIWARE.backlog.iot.review.20130620-1300.xlsx WP6 (@Sergio): https://forge.fi-ware.eu/docman/view.php/27/2654/FIWARE.backlog.data.review.20130620-1237.xlsx WP7 (@Pier): https://forge.fi-ware.eu/docman/view.php/27/2655/FIWARE.backlog.i2nd.review.20130620-1239.xlsx WP8 (@Pascal): https://forge.fi-ware.eu/docman/view.php/27/2657/FIWARE.backlog.security.review.20130620-1303.xlsx The review scheme follows the same pattern as the previous reviews for the wiki. There?s a front page with a summary of the issues with metrics, and then pages with details for each criteria group. Within the reviews you?ll find embedded links to the tracker and wiki items for easy access. If you find any mistake or suggestion easing access to the items, please, let me know; it will help me improve the process and its output. I would appreciate you take action for fixing the many issues found. Additional reviews can be provided now easily, it can be done weekly/monthly or if needed on demand as well. Well, if needed I?ve available for clarifications, either on email, or the phone, as you wish. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 25 08:29:13 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 25 Jun 2013 08:29:13 +0200 Subject: [Fiware-wpa] Form about Achievements of FI-WARE to be delivered to the EC Message-ID: <51C938B9.1080904@tid.es> Hi all, I have performed a final revision of the form about achievements of FI-WARE to be delivered to the EC. You can take a final look and check how I addressed your comments: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Unless I hear about any objections, I will drop all comments and inputs and generate a .docx that I will submit to the EC this evening. While reviewing the responses linked to some GEis in Part A, I found the answer to the question about market positioning a bit weak (in some cases, rather weak IMHO). I don't know if you have considered it, but I can predict that the answers will be analyzed by our reviewers and you don't know how this could be used ... I'll keep the form open for editions of Part A along today, so probably is worth asking owners of FI-WARE GEis in your chapter to make a final effort to enhance it. However, I want to make it clear that I will generate a .docx based on whatever is there at 20:00 this evening. No further inputs will be taken afterwards. 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) Coordinator and 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 mev at tid.es Tue Jun 25 10:45:32 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 25 Jun 2013 08:45:32 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Backlog - complete review available In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A70A@EX10-MB2-MAD.hi.inet> Thanks Alex, I do appreciate the comment and questions. I already offered myself for clarification/explanation, and I'm trying to schedule bilateral meeting with you all since some aspects need a closer understanding, anyway, Let me share a first explanation, which I'll expand on those bilateral meetings, if needed. ? Oh, I think it does. The proposal approved recently by the board didn't change essential aspects like structure and fields, it mainly simplified and clarified things, so the errors aren't caused by the "new guidelines". Therefore, that perception is wrong. I think it's important to fix ALL items identified: C1- sprint and release, C2-Consistency of backlog reference, C3-Backlog hierarchy, and C4- Link Tracker/Wiki and C5-Item description. Of course, having the public view of the backlog on the wiki in good shape it's important. ? That can be taken as a proposal, but there's a link where you have it available any time. It doesn't seem a big thing. ? Ah, we do have deterministic rules, it's implicit in the naming convention. I'll explain it in our bilateral meeting ? Ah, By functional items I mean (Epic, Feature and Story), they are the items covering functional development. WorkItems are for non-functional content (reporting, etc) and Bugs are for .... Bugs. ? "URL....." it points out urls whose items (stories, workitem and bugs) will not be shown in the wiki, so they aren't need anymore. Of course they are needed for the Epics and Features shown in the wiki. ? "Due not dismissed..." It means valid Epics and Features which aren't shown in the wiki. There's validation of whether the wiki shows the correct subset of items (Epics and Features) of the backlog, this is the "matching tracker/wiki". Well, I'll like to know what you found, perhaps the script has some errors or the rule/criteria is wrong. Let me know what Item ID(number) is affected so that I can check it. ? Well, I'd try to improve items with percentile below 5% - For example 3805's description is done with 2 words, which looks ... a bit "inexpressive", or perhaps 4226, it's over-expresive. It depends on you, at least you have a tool which shows the general aspect of how the public items are described. Obviously, this section is labelled as improving and aren't marked as issues. Those which are issues, are also identified in other sheets. Overall, Alex, I want to emphasize that access to the backlog items is easy, just a click on the spreadsheet. It allows you fixing items in a matter of seconds. I hope I clarified some aspects. Well, let me know when we can have the phone talk. Kind regards, Manuel From: Alex Glikson [mailto:GLIKSON at il.ibm.com] Sent: lunes, 24 de junio de 2013 22:05 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA Subject: Re: [Fiware-wpl] Backlog - complete review available Dear Manuel, Fantastic work! Few comments/questions: * I wonder whether it makes sense spending hours on fixing items which have been closed a year ago or even more. We had different guidelines, and, frankly, not sure anyone cares.. At least for Cloud, this would require very significant effort, with (close to) zero value to anyone. * Can you, please, update the labels of the new sprint/release fields to include the corresponding time periods (e.g., "Release 2.3: May 2013 - July 2013")? This would make validation easier. * Can you, please, elaborate how exactly did you determine parent-child relationship? IMO, we don't have 100% deterministic guidelines about this. * what do you mean by "all Functional Items ordered" and "all workitems"? * regarding "url not needed but available on tracker- to be removed", I think it is actually a good practice for stories to specify URL of the corresponding Feature. If you insist -- maybe you can just remove it with a script. * Some of the inconsistencies can be easily fixed using a script -- probably similar to the one you are using to gather statistics? This could save effort. * Can you, please, explain the meaning of "due not dismissed backlog items not available in wiki directory", "matching tracker - wiki" and "items details already provided on the wiki"? I've checked few -- and everything seems fine.. * What is the problem with name = reference? I am not aware of guidelines preventing this. * Any action items from W-C4? Once again, very impressive! Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE > To: "fiware-wpl at lists.fi-ware.eu" >, Cc: "fiware-wpa at lists.fi-ware.eu" > Date: 20/06/2013 07:16 PM Subject: [Fiware-wpl] Backlog - complete review available Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear Partners, Let me inform you that complete review of the backlogs (Tracker + Wiki) are available at the following links: WP3 (@Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2652/FIWARE.backlog.apps.review.20130620-1228.xlsx WP4 (@Alex): https://forge.fi-ware.eu/docman/view.php/27/2653/FIWARE.backlog.cloud.review.20130620-1233.xlsx WP5 (@Thierry): https://forge.fi-ware.eu/docman/view.php/27/2656/FIWARE.backlog.iot.review.20130620-1300.xlsx WP6 (@Sergio): https://forge.fi-ware.eu/docman/view.php/27/2654/FIWARE.backlog.data.review.20130620-1237.xlsx WP7 (@Pier): https://forge.fi-ware.eu/docman/view.php/27/2655/FIWARE.backlog.i2nd.review.20130620-1239.xlsx WP8 (@Pascal): https://forge.fi-ware.eu/docman/view.php/27/2657/FIWARE.backlog.security.review.20130620-1303.xlsx The review scheme follows the same pattern as the previous reviews for the wiki. There's a front page with a summary of the issues with metrics, and then pages with details for each criteria group. Within the reviews you'll find embedded links to the tracker and wiki items for easy access. If you find any mistake or suggestion easing access to the items, please, let me know; it will help me improve the process and its output. I would appreciate you take action for fixing the many issues found. Additional reviews can be provided now easily, it can be done weekly/monthly or if needed on demand as well. Well, if needed I've available for clarifications, either on email, or the phone, as you wish. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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 GLIKSON at il.ibm.com Tue Jun 25 11:16:29 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Tue, 25 Jun 2013 12:16:29 +0300 Subject: [Fiware-wpa] [Fiware-wpl] Backlog - complete review available In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A70A@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A70A@EX10-MB2-MAD.hi.inet> Message-ID: Thanks, Manuel. Your clarifications are helpful. We can handle this one-on-one, but I think it might be of interest for others, who might have similar questions/concerns. > access to the backlog items is easy, just a click on the spreadsheet. It allows you fixing items in a matter of seconds. Indeed, very easy -- but with over 5000 (!!) potential issues across the 6 chapters, this is simply not feasible to even check what is right and what is wrong. Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE To: Alex Glikson/Haifa/IBM at IBMIL, Cc: "fiware-wpa at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" , MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA Date: 25/06/2013 11:46 AM Subject: RE: [Fiware-wpl] Backlog - complete review available Thanks Alex, I do appreciate the comment and questions. I already offered myself for clarification/explanation, and I?m trying to schedule bilateral meeting with you all since some aspects need a closer understanding, anyway, Let me share a first explanation, which I?ll expand on those bilateral meetings, if needed. ? Oh, I think it does. The proposal approved recently by the board didn?t change essential aspects like structure and fields, it mainly simplified and clarified things, so the errors aren?t caused by the ?new guidelines?. Therefore, that perception is wrong. I think it?s important to fix ALL items identified: C1- sprint and release, C2-Consistency of backlog reference, C3-Backlog hierarchy, and C4- Link Tracker/Wiki and C5-Item description. Of course, having the public view of the backlog on the wiki in good shape it?s important. ? That can be taken as a proposal, but there?s a link where you have it available any time. It doesn?t seem a big thing. ? Ah, we do have deterministic rules, it?s implicit in the naming convention. I?ll explain it in our bilateral meeting ? Ah, By functional items I mean (Epic, Feature and Story), they are the items covering functional development. WorkItems are for non-functional content (reporting, etc) and Bugs are for ?. Bugs. ? ?URL?..? it points out urls whose items (stories, workitem and bugs) will not be shown in the wiki, so they aren?t need anymore. Of course they are needed for the Epics and Features shown in the wiki. ? ?Due not dismissed?? It means valid Epics and Features which aren?t shown in the wiki. There?s validation of whether the wiki shows the correct subset of items (Epics and Features) of the backlog, this is the ?matching tracker/wiki?. Well, I?ll like to know what you found, perhaps the script has some errors or the rule/criteria is wrong. Let me know what Item ID(number) is affected so that I can check it. ? Well, I?d try to improve items with percentile below 5% - For example 3805?s description is done with 2 words, which looks ? a bit ?inexpressive?, or perhaps 4226, it?s over-expresive. It depends on you, at least you have a tool which shows the general aspect of how the public items are described. Obviously, this section is labelled as improving and aren?t marked as issues. Those which are issues, are also identified in other sheets. Overall, Alex, I want to emphasize that access to the backlog items is easy, just a click on the spreadsheet. It allows you fixing items in a matter of seconds. I hope I clarified some aspects. Well, let me know when we can have the phone talk. Kind regards, Manuel From: Alex Glikson [mailto:GLIKSON at il.ibm.com] Sent: lunes, 24 de junio de 2013 22:05 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA Subject: Re: [Fiware-wpl] Backlog - complete review available Dear Manuel, Fantastic work! Few comments/questions: I wonder whether it makes sense spending hours on fixing items which have been closed a year ago or even more. We had different guidelines, and, frankly, not sure anyone cares.. At least for Cloud, this would require very significant effort, with (close to) zero value to anyone. Can you, please, update the labels of the new sprint/release fields to include the corresponding time periods (e.g., "Release 2.3: May 2013 - July 2013")? This would make validation easier. Can you, please, elaborate how exactly did you determine parent-child relationship? IMO, we don't have 100% deterministic guidelines about this. what do you mean by "all Functional Items ordered" and "all workitems"? regarding "url not needed but available on tracker- to be removed", I think it is actually a good practice for stories to specify URL of the corresponding Feature. If you insist -- maybe you can just remove it with a script. Some of the inconsistencies can be easily fixed using a script -- probably similar to the one you are using to gather statistics? This could save effort. Can you, please, explain the meaning of "due not dismissed backlog items not available in wiki directory", "matching tracker - wiki" and "items details already provided on the wiki"? I've checked few -- and everything seems fine.. What is the problem with name = reference? I am not aware of guidelines preventing this. Any action items from W-C4? Once again, very impressive! Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE To: "fiware-wpl at lists.fi-ware.eu" , Cc: "fiware-wpa at lists.fi-ware.eu" Date: 20/06/2013 07:16 PM Subject: [Fiware-wpl] Backlog - complete review available Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear Partners, Let me inform you that complete review of the backlogs (Tracker + Wiki) are available at the following links: WP3 (@Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2652/FIWARE.backlog.apps.review.20130620-1228.xlsx WP4 (@Alex): https://forge.fi-ware.eu/docman/view.php/27/2653/FIWARE.backlog.cloud.review.20130620-1233.xlsx WP5 (@Thierry): https://forge.fi-ware.eu/docman/view.php/27/2656/FIWARE.backlog.iot.review.20130620-1300.xlsx WP6 (@Sergio): https://forge.fi-ware.eu/docman/view.php/27/2654/FIWARE.backlog.data.review.20130620-1237.xlsx WP7 (@Pier): https://forge.fi-ware.eu/docman/view.php/27/2655/FIWARE.backlog.i2nd.review.20130620-1239.xlsx WP8 (@Pascal): https://forge.fi-ware.eu/docman/view.php/27/2657/FIWARE.backlog.security.review.20130620-1303.xlsx The review scheme follows the same pattern as the previous reviews for the wiki. There?s a front page with a summary of the issues with metrics, and then pages with details for each criteria group. Within the reviews you?ll find embedded links to the tracker and wiki items for easy access. If you find any mistake or suggestion easing access to the items, please, let me know; it will help me improve the process and its output. I would appreciate you take action for fixing the many issues found. Additional reviews can be provided now easily, it can be done weekly/monthly or if needed on demand as well. Well, if needed I?ve available for clarifications, either on email, or the phone, as you wish. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl 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 mev at tid.es Tue Jun 25 11:53:16 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 25 Jun 2013 09:53:16 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Backlog - complete review available In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890598D9@EX10-MB2-MAD.hi.inet> <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A70A@EX10-MB2-MAD.hi.inet> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905A78A@EX10-MB2-MAD.hi.inet> Yes, I understand the general interest. I think WE CAN DO IT. Manuel From: Alex Glikson [mailto:GLIKSON at il.ibm.com] Sent: martes, 25 de junio de 2013 11:16 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; JUAN JOSE HIERRO SUREDA; MIGUEL CARRILLO PACHECO Subject: RE: [Fiware-wpl] Backlog - complete review available Thanks, Manuel. Your clarifications are helpful. We can handle this one-on-one, but I think it might be of interest for others, who might have similar questions/concerns. > access to the backlog items is easy, just a click on the spreadsheet. It allows you fixing items in a matter of seconds. Indeed, very easy -- but with over 5000 (!!) potential issues across the 6 chapters, this is simply not feasible to even check what is right and what is wrong. Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE > To: Alex Glikson/Haifa/IBM at IBMIL, Cc: "fiware-wpa at lists.fi-ware.eu" >, "fiware-wpl at lists.fi-ware.eu" >, MIGUEL CARRILLO PACHECO >, JUAN JOSE HIERRO SUREDA > Date: 25/06/2013 11:46 AM Subject: RE: [Fiware-wpl] Backlog - complete review available ________________________________ Thanks Alex, I do appreciate the comment and questions. I already offered myself for clarification/explanation, and I'm trying to schedule bilateral meeting with you all since some aspects need a closer understanding, anyway, Let me share a first explanation, which I'll expand on those bilateral meetings, if needed. * Oh, I think it does. The proposal approved recently by the board didn't change essential aspects like structure and fields, it mainly simplified and clarified things, so the errors aren't caused by the "new guidelines". Therefore, that perception is wrong. I think it's important to fix ALL items identified: C1- sprint and release, C2-Consistency of backlog reference, C3-Backlog hierarchy, and C4- Link Tracker/Wiki and C5-Item description. Of course, having the public view of the backlog on the wiki in good shape it's important. * That can be taken as a proposal, but there's a link where you have it available any time. It doesn't seem a big thing. * Ah, we do have deterministic rules, it's implicit in the naming convention. I'll explain it in our bilateral meeting * Ah, By functional items I mean (Epic, Feature and Story), they are the items covering functional development. WorkItems are for non-functional content (reporting, etc) and Bugs are for .... Bugs. * "URL....." it points out urls whose items (stories, workitem and bugs) will not be shown in the wiki, so they aren't need anymore. Of course they are needed for the Epics and Features shown in the wiki. * "Due not dismissed..." It means valid Epics and Features which aren't shown in the wiki. There's validation of whether the wiki shows the correct subset of items (Epics and Features) of the backlog, this is the "matching tracker/wiki". Well, I'll like to know what you found, perhaps the script has some errors or the rule/criteria is wrong. Let me know what Item ID(number) is affected so that I can check it. * Well, I'd try to improve items with percentile below 5% - For example 3805's description is done with 2 words, which looks ... a bit "inexpressive", or perhaps 4226, it's over-expresive. It depends on you, at least you have a tool which shows the general aspect of how the public items are described. Obviously, this section is labelled as improving and aren't marked as issues. Those which are issues, are also identified in other sheets. Overall, Alex, I want to emphasize that access to the backlog items is easy, just a click on the spreadsheet. It allows you fixing items in a matter of seconds. I hope I clarified some aspects. Well, let me know when we can have the phone talk. Kind regards, Manuel From: Alex Glikson [mailto:GLIKSON at il.ibm.com] Sent: lunes, 24 de junio de 2013 22:05 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; MIGUEL CARRILLO PACHECO; JUAN JOSE HIERRO SUREDA Subject: Re: [Fiware-wpl] Backlog - complete review available Dear Manuel, Fantastic work! Few comments/questions: * I wonder whether it makes sense spending hours on fixing items which have been closed a year ago or even more. We had different guidelines, and, frankly, not sure anyone cares.. At least for Cloud, this would require very significant effort, with (close to) zero value to anyone. * Can you, please, update the labels of the new sprint/release fields to include the corresponding time periods (e.g., "Release 2.3: May 2013 - July 2013")? This would make validation easier. * Can you, please, elaborate how exactly did you determine parent-child relationship? IMO, we don't have 100% deterministic guidelines about this. * what do you mean by "all Functional Items ordered" and "all workitems"? * regarding "url not needed but available on tracker- to be removed", I think it is actually a good practice for stories to specify URL of the corresponding Feature. If you insist -- maybe you can just remove it with a script. * Some of the inconsistencies can be easily fixed using a script -- probably similar to the one you are using to gather statistics? This could save effort. * Can you, please, explain the meaning of "due not dismissed backlog items not available in wiki directory", "matching tracker - wiki" and "items details already provided on the wiki"? I've checked few -- and everything seems fine.. * What is the problem with name = reference? I am not aware of guidelines preventing this. * Any action items from W-C4? Once again, very impressive! Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: MANUEL ESCRICHE VICENTE > To: "fiware-wpl at lists.fi-ware.eu" >, Cc: "fiware-wpa at lists.fi-ware.eu" > Date: 20/06/2013 07:16 PM Subject: [Fiware-wpl] Backlog - complete review available Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear Partners, Let me inform you that complete review of the backlogs (Tracker + Wiki) are available at the following links: WP3 (@Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2652/FIWARE.backlog.apps.review.20130620-1228.xlsx WP4 (@Alex): https://forge.fi-ware.eu/docman/view.php/27/2653/FIWARE.backlog.cloud.review.20130620-1233.xlsx WP5 (@Thierry): https://forge.fi-ware.eu/docman/view.php/27/2656/FIWARE.backlog.iot.review.20130620-1300.xlsx WP6 (@Sergio): https://forge.fi-ware.eu/docman/view.php/27/2654/FIWARE.backlog.data.review.20130620-1237.xlsx WP7 (@Pier): https://forge.fi-ware.eu/docman/view.php/27/2655/FIWARE.backlog.i2nd.review.20130620-1239.xlsx WP8 (@Pascal): https://forge.fi-ware.eu/docman/view.php/27/2657/FIWARE.backlog.security.review.20130620-1303.xlsx The review scheme follows the same pattern as the previous reviews for the wiki. There's a front page with a summary of the issues with metrics, and then pages with details for each criteria group. Within the reviews you'll find embedded links to the tracker and wiki items for easy access. If you find any mistake or suggestion easing access to the items, please, let me know; it will help me improve the process and its output. I would appreciate you take action for fixing the many issues found. Additional reviews can be provided now easily, it can be done weekly/monthly or if needed on demand as well. Well, if needed I've available for clarifications, either on email, or the phone, as you wish. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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 jhierro at tid.es Wed Jun 26 03:55:39 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 26 Jun 2013 03:55:39 +0200 Subject: [Fiware-wpa] Form delivered to the EC regarding FI-WARE Achievements Message-ID: <51CA4A1B.6000306@tid.es> Hi all, Please find enclosed the version of the form that I have finally submitted to the EC. I have found the section dealing with market positioning, in boxes describing the GEis, particularly weak. We should submit an update of the form by end of July, given the fact that new GEis will be published on the FI-WARE Catalogue. FI-WARE GEi owners should take advantage of it as to review and improve Part A of the form during July. 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) Coordinator and 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Achievements in FI-PPP.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 89582 bytes Desc: not available URL: From mcp at tid.es Wed Jun 26 12:01:40 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 26 Jun 2013 12:01:40 +0200 Subject: [Fiware-wpa] Doodle poll with holidays Message-ID: <51CABC04.1030108@tid.es> Dear all, Out of experience, it is very difficult to keep track of the holidays of so many people and we all end up not knowing who's available at each point in time. Can you please provide your holidays here? http://www.doodle.com/mzup4hn9nsmnywg9#table I remind you that you need to make sure that someone is there while you are out to avoid leaving the WP adrift. In other words, we need some sort of deputy standing in for you (and effectively keeping things running!) while you are away. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jun 26 17:04:45 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 26 Jun 2013 17:04:45 +0200 Subject: [Fiware-wpa] SOTA (definite version for a final check) Message-ID: <51CB030D.3090305@tid.es> Dear all, I enclose the word and pdf versions of the SOTA document once put together in the final shape. I will send it to the EC tomorrow a bit later than 12 am. You have time until then to let me know if there are any obvious problems with this (I assume that no one will perform a deep review at this stage). Small things could be fixed on the fly but I will not block the delivery on the grounds of comments unless something is really really critical. @Pier: I took the liberty of rearranging references in a table, I hope that you do not mind @All: it seems that very few used the spell checker before delivering ... it should be a habit and it shoud be done by default in all contributions to all deliverables @All: I realise now that the citation style is reasonable close between chapters but not exactly the same. We will fix it next time. The last steps were not intelectually challenging but it was necessary. Now it looks much better. Thanks for the cooperation. Best regards, 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.2 State of the Art Analysis ? Emerging Technologies_20130627.pdf Type: application/pdf Size: 2583886 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.2 State of the Art Analysis ? Emerging Technologies_20130627.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3276500 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Thu Jun 27 11:18:15 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 27 Jun 2013 11:18:15 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] SOTA (definite version for a final check) In-Reply-To: <51CB030D.3090305@tid.es> References: <51CB030D.3090305@tid.es> Message-ID: Hi Miguel, we didn't find major issues in the document, just few typos you can find in the attached doc (just look for the changes, the formatting is as usual creating troubles in my MS Word...). Thanks a lot for the relevant work you did in merging the different contributions! BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Miguel Carrillo Inviato: mercoled? 26 giugno 2013 17:05 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-wpl] SOTA (definite version for a final check) Dear all, I enclose the word and pdf versions of the SOTA document once put together in the final shape. I will send it to the EC tomorrow a bit later than 12 am. You have time until then to let me know if there are any obvious problems with this (I assume that no one will perform a deep review at this stage). Small things could be fixed on the fly but I will not block the delivery on the grounds of comments unless something is really really critical. @Pier: I took the liberty of rearranging references in a table, I hope that you do not mind @All: it seems that very few used the spell checker before delivering ... it should be a habit and it shoud be done by default in all contributions to all deliverables @All: I realise now that the citation style is reasonable close between chapters but not exactly the same. We will fix it next time. The last steps were not intelectually challenging but it was necessary. Now it looks much better. Thanks for the cooperation. Best regards, 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 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: D 2 6 2 State of the Art Analysis Emerging Technologies_20130627-I2ND.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3295355 bytes Desc: D 2 6 2 State of the Art Analysis Emerging Technologies_20130627-I2ND.docx 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 mev at tid.es Thu Jun 27 12:29:02 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 27 Jun 2013 10:29:02 +0000 Subject: [Fiware-wpa] JIRA - please, update your GEis, and the number of users requested - deadline tomorrow. Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905AF04@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you of this spreadsheet, where it's important to have your input for knowing the number of users needed in the JIRA instance. Please, report them on column F, if needed update the GEi's or contact person on columns D and E. FIWARE - JIRA users - https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdEx0YmVHSnFDZFBUZ28wRV9fY3hla1E&usp=sharing Currently there's complete input from Cloud(thanks Alex!) and partial input from Data and Security. Deadline for this input is tomorrow. Thanks for cooperation!! If anything, please, don't hesitate to let me know. Kind regards, Manuel From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: lunes, 24 de junio de 2013 17:25 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] JIRA - please, update your GEis, and the number of users requested Dear Partners, Following the action point for having the JIRA instance ready as soon as possible, please, provided input to the spreadsheet linked below. There're two main groups, the first with the input I collected from the tracker, the seconds collects the feedback from you, some missing, some already provided. Anyway, the number of users requested is pending. I had appointed 1 for each GEi owner, now you have a chance to request a different amount. The first proposition is to have an instance on demand for 10 months for 50 users (1 user for GEi) FIWARE - JIRA users - https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdEx0YmVHSnFDZFBUZ28wRV9fY3hla1E&usp=sharing If anything, please, let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu Jun 27 14:30:20 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 27 Jun 2013 14:30:20 +0200 Subject: [Fiware-wpa] SOTA submitted Message-ID: <51CC305C.7030604@tid.es> Dear all, This is just ot let you know that we have sent the EC the following deliverable (attached): * D.2.6.2 State of the Art Analysis - Emerging Technologies It is also publicly available on: * https://forge.fi-ware.eu/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+%E2%80%93+Emerging+Technologies.pdf I remind you that the first issue (D.2.6.1) was cancelled in agreement with the EC so despite the numbering, this is actually the 1st issue. BR 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.2 State of the Art Analysis ? Emerging Technologies.pdf Type: application/pdf Size: 2581795 bytes Desc: not available URL: From stefano.depanfilis at eng.it Fri Jun 28 18:22:01 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Fri, 28 Jun 2013 18:22:01 +0200 Subject: [Fiware-wpa] Fwd: [Fiware-testbed] Testbed Integration Plan V2 In-Reply-To: <6A671820E63F0E4FB42453BD2D8A1B8804060467@itrmx010.italy.itroot.adnet> References: <6A671820E63F0E4FB42453BD2D8A1B8804060467@itrmx010.italy.itroot.adnet> Message-ID: dear all, first i'd like to introduce you all my colleague mauro pecetti (in cc) who is now the resposnible for the production of the integration plan and report. here fwd his email asking to each geis owner, as represented in the testbed team, to provide the info about integration, e.g. dependendecies among geis, and related test cases. please push your chapter colleagues to end this work within two weeks from now (i.e. 12 july). thank you in advance for your kind cooperation. ciao, stefano ---------- Forwarded message ---------- From: Pecetti Mauro Date: 2013/6/28 Subject: [Fiware-testbed] Testbed Integration Plan V2 To: fiware-testbed at lists.fi-ware.eu ** Dear all, my name is Mauro Pecetti and I?m working in the staff of Stefano De Panfilis, specifically in the FIWARE - Testbed. In order to produce the documentation about Integration testing plan for FIWARE ? testbed V2, I would need the following information for each chapter: - Dependency Chains: list of dependencies between GEs of a chapter with a GE of another chapter - Dependencies to test: list of all couples of GE dependencies with the specific testing order - Test cases: list of test cases with all information needed to make the specific test To make your work easier, I provide to you a word document template that you can use it in order to send me the required information and than I?ll update by myself the wiki. ciao, *****Mauro Pecetti* ***mauro.pecetti at eng.it* *****Engineering Ingegneria Informatica spa* Via Riccardo Morandi, 32 - 00148 Roma Mob. +39-348.1334223 ***www.eng.it* <> _______________________________________________ Fiware-testbed mailing list Fiware-testbed at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-testbed -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: geis dependencies template.doc Type: application/msword Size: 53248 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Fri Jun 28 19:10:37 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 28 Jun 2013 17:10:37 +0000 Subject: [Fiware-wpa] restricted files are not restricted for security, cloud, i2nd - FI-PPP level can not be guaranteed Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66485FB1A54@DEWDFEMB11A.global.corp.sap> Dear colleagues, the list down below shows the files which can be accessed by ANYBODY in the internet, but supposedly should have been introduced as "private" releases. Please inform your GE owners to fix this - they have to completely re-upload the release and make it "private" in step 1. You can see this list for yourself if you log OUT of the forge and then access the URL: https://forge.fi-ware.eu/frs/?group_id=23 I2ND-CloudEdge I2ND-CloudEdge - Monitor this package I2ND-CloudEdge 2.3 Filename Date Size D/L Arch Type I2ND-CloudEdge 2.3.3.tar.gz 2013-06-24 14:18 19.63 MB 5 Other Source .gz I2ND-CloudEdge 2.2.1 Filename Date Size D/L Arch Type I2ND-CloudEdge-tools-examples-2.2.tar.gz 2013-04-19 14:23 96.85 MB 2 Other .gz I2ND-S3C I2ND-S3C - Monitor this package I2ND-S3C 2.3 Filename Date Size D/L Arch Type ApplianceManager_1.0.1409.gz 2013-04-18 11:49 884 KB 6 i386 .gz I2ND-S3C-EPC-OTT-API.zip 2013-04-18 11:49 5.66 MB 0 i386 .zip libapache2-mod-osa_1.0.0.1271-nursery1_i386.deb 2013-04-18 11:49 19 KB 3 i386 .deb networkidentitymanagement.zip 2013-04-18 11:49 17.74 MB 1 x86_64 .zip oneapi-VoiceCallControl.zip 2013-04-18 11:49 73 KB 0 x86_64 .zip SeamlessNetworkConnectivity.zip 2013-04-18 11:49 7.84 MB 0 x86_64 .zip I2ND-S3C 2.2 Filename Date Size D/L Arch Type I2ND-S3C-EPC-OTT-API.zip 2013-04-18 11:47 21.42 MB 5 x86_64 .zip oneapi-sms.tar 2013-04-18 11:47 214 KB 7 i386 Other Source File s3capiproxy_install_script.zip 2013-04-18 11:47 1 KB 5 Any Source .zip IOT-Data Handling IOT-Data Handling - Monitor this package IOT-Data Handling IOT-Data Handling 2.3.1 Filename Date Size D/L Arch Type Esper4FastData-2.3.1-soapui-project.xml 2013-06-28 11:15 223 KB 0 Any Other Esper4FastData-2.3.1.war 2013-06-28 11:15 12.52 MB 0 Any Other SECURITY-AccessControlGE-Pub SECURITY-AccessControlGE-Pub - Monitor this package SECURITY-AccessControlGE-Pub 2.2.3 Filename Date Size D/L Arch Type fiware.access_control_ge.authz.api.wadl.zip 2013-05-13 12:26 11 KB 7 Any .zip SECURITY-Remediation App SECURITY-Remediation App - Monitor this package SECURITY-Remediation App 2.2.0 Filename Date Size D/L Arch Type Remediation App-2.2.0.zip 2013-05-02 12:09 28.83 MB 6 i386 .zip SECURITY-ScoredAttackPaths SECURITY-ScoredAttackPaths - Monitor this package SECURITY-ScoredAttackPaths 2.2.0 Filename Date Size D/L Arch Type ScoredAttackPaths-2.2.0.jar 2013-05-02 12:12 33 KB 2 i386 Other SECURITY.SecureStorageService SECURITY.SecureStorageService - Monitor this package SECURITY.SecureStorageService SecureStorageService-2.2.0 Filename Date Size D/L Arch Type SecureStorageService.war 2013-05-31 15:04 2.77 MB 3 i386 Other Source File Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 574 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 565 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 569 bytes Desc: image003.png URL: From mev at tid.es Sat Jun 29 12:27:34 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Sat, 29 Jun 2013 10:27:34 +0000 Subject: [Fiware-wpa] Major Release transition: From S2 to S3; At sprint level from S2.3.3-M26 to S3.1.1-M27 Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905C7DC@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you that we are finishing sprint S2.3.3-M26, closing this way the Second Major Release and about to start S3.1.1-M27, which opens the Third Major Release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog items accordingly: 1. Close the backlog items finished during M26 (if not already done) 2. Update items under execution not finished to belong to S3.1.1 - ideal would have been to meet all your targets during the major release, and therefore nothing is moved to the next Major Release 3. Proceed to identify the backlog items to be delivered during S3.1.1 - M27. Since we are at the beginning of a major release, your roadmap should be revisited and adapted after the corresponding retrospective, and prospective sessions, obviously having in mind the final targets. To WPLeaders, please, distribute the message to your teams!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: