From mev at tid.es Fri Mar 1 13:12:26 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 01 Mar 2013 12:12:26 +0000 Subject: [Fiware-wpa] Backlog - Sprint transition: from S2.2.2-M22 to S2.2.3-M23 Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B551EBE01@EX10-MB2-MAD.hi.inet> Dear Partners, As you know yesterday we finished Sprint 2.2.2 corresponding to M22, today we start activities belonging to Sprint 2.2.3 corresponding to M23. Please, update your backlog accordingly. 1. Close the tickets you finished along M22 (probably you already did these days when updating the tickets), otherwise, do it 2. Update tickets under execution to belong to Sprint 2.2.3-M23 During next week we should be able to identify and refine all content meant to be done during Sprint S2.2.3-M23. Next week I'll contact you to understand how your backlog for S2.2.3 is defined. During these months we'll improve the tools with a dashboard giving us visual views on how our backlog is evolving during sprints and realeases... for the different enablers, partners, etc. As soon as I can I'll share the consistency rules to be applied to the backlog, so that we all have unanimous understanding and consensus. If anything, please, don't hesitate to let me know. Have a nice weekend!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Fri Mar 1 15:27:51 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 01 Mar 2013 14:27:51 +0000 Subject: [Fiware-wpa] FIWARE - Delivery of D.2.1.3 - Requirement Backlog Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B551EC201@EX10-MB2-MAD.hi.inet> Dear Partners, Let me inform you that D.2.1.3 Requirements Backlog has just been delivered. You can find it at: https://forge.fi-ware.eu/docman/view.php/7/1893/Backlog+20130301.xlsx We've also updated the submission cockpit accordingly. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.2.X.submission_cockpit#Progress_Tracking_and_Links_WP2_.28skeleton.29 I want to thank you all for your support during these last days despite the circumstances. Have a nice weekend - we deserve it!! 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 Mar 4 10:44:15 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 10:44:15 +0100 Subject: [Fiware-wpa] Delaying joint WPLs/WPAs follow-up confcall 30 mins Message-ID: <51346CEF.2060404@tid.es> Hi all, I have to attend a urgent call from my boss at 10:00 so apologize but we have to delay start our regular weekly confcall 30 mins. I'll send you a link to the shared minutes before 10:00 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 Mon Mar 4 11:04:32 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 11:04:32 +0100 Subject: [Fiware-wpa] Link to shared minutes Message-ID: <513471B0.9010600@tid.es> Hi all, Here it goes the link we will use for our confcall: https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kdvxhm21ro3y 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 Mar 4 14:05:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 14:05:23 +0100 Subject: [Fiware-wpa] UPM team will join us at 14:30 CET Message-ID: <51349C13.8040108@tid.es> Hi all, Just to confirm you that the UPM team (Joaqu?n Salvachua) will join us at 14:30 CET. Talk to you 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 pascal.bisson at thalesgroup.com Mon Mar 4 14:20:05 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 4 Mar 2013 14:20:05 +0100 Subject: [Fiware-wpa] [Fiware-wpl] UPM team will join us at 14:30 CET In-Reply-To: <51349C13.8040108@tid.es> References: <51349C13.8040108@tid.es> Message-ID: <20141_1362403207_51349F87_20141_11503_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E2BD1BBB@THSONEA01CMS04P.one.grp> Ok I inform Cyril accordingly for him to join this slot. -----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 4 mars 2013 14:05 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] UPM team will join us at 14:30 CET Hi all, Just to confirm you that the UPM team (Joaqu?n Salvachua) will join us at 14:30 CET. Talk to you 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From jhierro at tid.es Mon Mar 4 14:40:19 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 14:40:19 +0100 Subject: [Fiware-wpa] Fwd: Slides for today conf. In-Reply-To: <5D5A788D-2586-467B-9587-654BD5842F75@dit.upm.es> References: <5D5A788D-2586-467B-9587-654BD5842F75@dit.upm.es> Message-ID: <5134A443.6030507@tid.es> ------------- 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: Slides for today conf. Date: Mon, 4 Mar 2013 14:39:26 +0100 From: Joaqu?n Salvach?a To: Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Security 13-02-25.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 133614 bytes Desc: not available URL: From jhierro at tid.es Mon Mar 4 14:41:44 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 14:41:44 +0100 Subject: [Fiware-wpa] Fwd: join me In-Reply-To: <4AD74AF4-06D6-4DC1-8F15-65118B536D58@dit.upm.es> References: <4AD74AF4-06D6-4DC1-8F15-65118B536D58@dit.upm.es> Message-ID: <5134A498.80907@tid.es> https://join.me/182-889-334 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Mar 4 15:12:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Mar 2013 15:12:50 +0100 Subject: [Fiware-wpa] PEP based on Keystone middleware and proposed proxy Message-ID: <5134ABE2.5070107@tid.es> Attached -- ------------- 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: FI-WARE Security 13-02-25 v2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 100707 bytes Desc: not available URL: From jsalvachua at dit.upm.es Mon Mar 4 13:09:51 2013 From: jsalvachua at dit.upm.es (=?iso-8859-1?Q?Joaqu=EDn_Salvach=FAa?=) Date: Mon, 4 Mar 2013 13:09:51 +0100 Subject: [Fiware-wpa] Slides for today audiconf. about Oauth2 security into the Fi-ware cloud Message-ID: <66A275D6-EDDA-4781-8552-7EDEC728D41C@dit.upm.es> Hello, Here i include the slides we will use in todays audio conference. Best regards Joaqu?n Salvach?a ------------------------------------------------------------------------ Joaquin Salvachua tel: +34 91 549 57 00 x.3026 Associated Professor +34 91 549 57 62 x.3026 dpt. Telematica E.T.S.I. Telecomunicacion Ciudad Universitaria S/N fax: +34 91 336 73 33 E-28040 MADRID SPAIN mailto:joaquin.salvachua at upm.es // http://www.dit.upm.es/~jsr -------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Security 13-02-25.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 133614 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Mar 4 16:34:31 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 4 Mar 2013 16:34:31 +0100 Subject: [Fiware-wpa] Live application demo Message-ID: <10295_1362411502_5134BFEE_10295_645_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E2BD2156@THSONEA01CMS04P.one.grp> Dear Fermin, Dear Juanjo, Could you please update me/us on the status of the Live application demo for next EC review. This simply because it starts to be a concern for me (hope for the others ). Even if we did it well for previous review (M18) since indeed the live demo shown there was really welcomed and appreciated by the EC and the reviewers, I see nothing happening regarding this demo for next EC review (M24). As per minutes of WPls/WPAs audio confs I did notice that a mailing was supposed to be created but so far I haven't received any message from that list (???) . So could you please check and update me/us and also revive the discussion/work on this core live application demo in order to be clear on what could be shown and effort It would request and from whom. Hearing from you. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Mar 5 11:23:15 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 05 Mar 2013 11:23:15 +0100 Subject: [Fiware-wpa] Guidelines for the creation of the Architecture Message-ID: <5135C793.6040605@tid.es> Dear all, Let us condensate the procedure for the Architecture review in one message. The calendar is the one agreed yesterday in the WPL/WPA call: 1. First draft of contributions by chapter ready for peer review: end of February 2. .docx first version of chapter ready by March 8 3. Comments on first draft (.docx with traced changes) due by March 13th 4. .docx second version of chapters ready for peer review: March 22nd 5. Comments on second draft due by April 2nd 6. Final version: April 10th As you surely recall, the guidelines for the Architecture doc are under: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions The process will be like reflected on the FI-WARE Architecture peer-review cockpit: ? We can use any wiki in each chapter but we need to have all the pages of each chapter on the same wiki for the docx generation. It sounds painful but believe me, it is not thanks to the tools provided by Thorsten and his team. Do not change this until you receive a separate message that I will send with more details later today. ? Each WPL will generate a docx document per chapter (SAP will provide support to the doc generation if needed). o Upload the generated doc to "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review" o Add the link to the doc to the cockpit o Further instructions here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables ? The document from a given chapter will be taken by the reviewers in charge of reviewing it using the link in the cockpit ? The WPL of the chapter that reviews it will make sure that it is reviewed before the deadline. Up to him how to organize it internally. ? All the reviewers of a WP receive the same document but each one suggests changes for the GE (or GEs) they review. There is a line per GE, up to each WP to merge them or use them separately. Once finished, they will upload their reviews to the right folder: o "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review" o The link (or links if more than one) to the doc (or docs) will be added to the cockpit ? Each WPL will analyse with his team the comments provided and will generate a new version of the chapter docx to be further reviewed. The new version should be available on the deliverable cockpit. Note that from this point on, chapter should drive further updates on the Word document, instead of any temporary wiki ? The reviewers will have a second round of comments. ? The final version will be generated for delivery. At this point, we will merge the contributions from all chapters (it is a single monolithic deliverable) and send it to the EC. ? Chapter leaders will then coordinate updates of the public wiki to align with the Word document that was submitted to the EC This is the assignment: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue Mar 5 15:16:13 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 05 Mar 2013 15:16:13 +0100 Subject: [Fiware-wpa] Monitoring of log/trace files Message-ID: <5135FE2D.3090809@eng.it> Dear partners, I'd like to remind you one point we've on the minutes: "Monitoring of log/trace files" https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy @Juanjo, can you kindly send a feedback on what's your take on the purpose and technology points reported on the minutes? @WPAs, can you kindly forward to your GEi providers the request to send an example of log/trace files produced by their GE implementations? Please send the logs to Marcel Zalmanovici and to the WPA mailing list. I'm expecting to receive one example per GEi that will be available for release 2. Kind Regards, Davide -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Mar 5 15:17:56 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 05 Mar 2013 15:17:56 +0100 Subject: [Fiware-wpa] More on the Architecture document Message-ID: <5135FE94.20808@tid.es> Dear all, In the message with the guidelines for the Architecture doc (attached) I promised an email elaborating a bit on the work of creating the docx. Let us recapitulate for your convenience and also add some extra info. As you may recall, we need to create a cover with the basic info and a list of links. I created the skeleton of what you need on this page on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.2.3.2.submission_cockpit You just will use the "partial per chapter contributions" table (a line per chapter) for the time being. I have asked SAP to create a fresh version of the generated zip twice a day (12am and 5 pm). We can refresh it under demand as well but please ask for this just when strictly necessary only As usual, you need to: * Update the "Structure of this Document" section with the links * Update other sections as needed (note that they will be merged in the final deliverable unifying all chapters in one doc) * Once the zip is generated, follow the tutorial on https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables - this was made by SAP in the past due to time constraints but we need to learn to do it, it is reasonably simple. But yes, it needs some work on your side. Also, there is a video tutorial on https://forge.fi-ware.eu/docman/view.php/27/1526/FI-WARE_software_deliverable_front_pages.flv. Andreas and Thorsten (in CC) could also help you if you get stuck at some point. There is very good news. SAP have figured out how to produce documents mixing pages on different wikis. So what I said in my previous emails about having all on the same wiki is not an issue anymore. You just have to use the following format: Fiware Public Page :[URL_TO_PUBLIC_WIKI_PAGE NAME_OF_PUBLIC_WIKI_PAGE] Fiware Private Page :[[NAME_OF_PRIVATE_WIKI_PAGE]] Example: Fiware Public Page :[http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision FI-WARE Product Vision] Fiware Private Page :[[Deliverables cockpit]] Please keep in mind that only a new document version in the Frontpage (Changes History - {{DocVersion|}}) will lead to a complete regeneration of the deliverable including an update of all linked pictures. If you don't update the document version already cached pictures will be used for document generation. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: [Fiware-wpa] Guidelines for the creation of the Architecture Date: Tue, 05 Mar 2013 11:23:15 +0100 Size: 28855 URL: From pascal.bisson at thalesgroup.com Wed Mar 6 09:20:46 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 6 Mar 2013 09:20:46 +0100 Subject: [Fiware-wpa] FI-WARE / Security Chapter / Security Monitoring GE - Information needed Message-ID: <9153_1362558280_5136FD48_9153_1090_4_300331d7-fd5e-4f32-bc6a-9f44870ff5ec@THSONEA01HUB04P.one.grp> Dear Colleagues, Find attached to this email an excel file prepared by Daniel & I with help of the team that state the information requested by the Security Monitoring GE to get it up and running. Mainly addressed to Cloud Hosting and the thread of discussion newly created and reflected by the secure-cloud mailing list we wanted to share it also with other chapters being said Security Monitoring would also be aiming at being used in their context to protect against some specific chapter's threats that would have been identified and reported to us (let me here remind as per Rome meeting specific action which was set on this - and which is btw still pending ...). In the attached excel you will see the information requested by each of the major modules of Security Monitoring architecture (the way it has been defined) clearly stating why it is needed (the rationale) and examples of the way it is expected to be passed to us (SecMon GE owner). In order to get us moving regarding integration of the Security Monitoring GE in FI-WARE we'd like to hear how we could gain access to the information we are requested. So hearing first from people from Cloud Chapter enlisted in the secure-cloud mailing list. In the meantime this doesn't prevent other chapters to also report their views and information they could contribute from their side and in complement of information provided by Cloud. Looking forward to reading you soon on this hot topic. Best Regards, Pascal & Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware - Security Risk Analysis - Inputs.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 16163 bytes Desc: FI-Ware - Security Risk Analysis - Inputs.xlsx URL: From mcp at tid.es Thu Mar 7 07:49:56 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 07 Mar 2013 07:49:56 +0100 Subject: [Fiware-wpa] More on the Architecture document In-Reply-To: <5135FE94.20808@tid.es> References: <5135FE94.20808@tid.es> Message-ID: <51383894.1070005@tid.es> Dear all, Extra info. I am getting the feedback from the WPLs that are already generating their Architecture docs. There seems to be a common mistake that needs an explanation. When we specify page names, the name of the links on the cover pages has to be exactly the same as the name of the wiki page - it's an internal rquirement of the script. Following my example on my original message (see at the bottom of this e-mail): Right: * Fiware Public Page :[http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision FI-WARE Product Vision] Wrong * Fiware Public Page :[http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision Product Vision ] As you can see , the 2nd one would cause the script to crash because the name does not match the link URL. Hope it helps, Miguel El 05/03/2013 15:17, Miguel Carrillo escribi?: Dear all, In the message with the guidelines for the Architecture doc (attached) I promised an email elaborating a bit on the work of creating the docx. Let us recapitulate for your convenience and also add some extra info. As you may recall, we need to create a cover with the basic info and a list of links. I created the skeleton of what you need on this page on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.2.3.2.submission_cockpit You just will use the "partial per chapter contributions" table (a line per chapter) for the time being. I have asked SAP to create a fresh version of the generated zip twice a day (12am and 5 pm). We can refresh it under demand as well but please ask for this just when strictly necessary only As usual, you need to: * Update the "Structure of this Document" section with the links * Update other sections as needed (note that they will be merged in the final deliverable unifying all chapters in one doc) * Once the zip is generated, follow the tutorial on https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables - this was made by SAP in the past due to time constraints but we need to learn to do it, it is reasonably simple. But yes, it needs some work on your side. Also, there is a video tutorial on https://forge.fi-ware.eu/docman/view.php/27/1526/FI-WARE_software_deliverable_front_pages.flv. Andreas and Thorsten (in CC) could also help you if you get stuck at some point. There is very good news. SAP have figured out how to produce documents mixing pages on different wikis. So what I said in my previous emails about having all on the same wiki is not an issue anymore. You just have to use the following format: Fiware Public Page :[URL_TO_PUBLIC_WIKI_PAGE NAME_OF_PUBLIC_WIKI_PAGE] Fiware Private Page :[[NAME_OF_PRIVATE_WIKI_PAGE]] Example: Fiware Public Page :[http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision FI-WARE Product Vision] Fiware Private Page :[[Deliverables cockpit]] Please keep in mind that only a new document version in the Frontpage (Changes History - {{DocVersion|}}) will lead to a complete regeneration of the deliverable including an update of all linked pictures. If you don't update the document version already cached pictures will be used for document generation. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.bareno at atosresearch.eu Fri Mar 8 10:25:46 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Fri, 8 Mar 2013 10:25:46 +0100 Subject: [Fiware-wpa] Patent and Publication subnitted in 2012 in the context of FI-WARE Message-ID: Dear Colleagues As responsible of exploitation activities, I have to fulfill with the following request form the EC concerning the provision of data about patents and publications that were submitted or published in 2012 for the Monitoring of the FP7 Implementation in the following link http://digital-agenda-data.eu/survey/index.php/survey/index/sid/414196/token/285248/lang/en The survey will be open until 15th March 2013. So please send me the following before 13th March EOB: - FI WARE publications- Title, Author, publication magazine... - Patent applications originate from partners? work done in the context of FI-WARE (Applicant name, Inventor Name, IPC Class..) Thanks for your collaboration Br Juan ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Sun Mar 10 20:23:44 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 10 Mar 2013 21:23:44 +0200 Subject: [Fiware-wpa] Fw: [Fiware-wpl] Guidelines for the creation of the Architecture Message-ID: Cloud architecture is ready for peer review. 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 ----- Forwarded by Alex Glikson/Haifa/IBM on 10/03/2013 09:18 PM ----- From: Miguel Carrillo To: "fiware-wpa at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" , Date: 05/03/2013 12:23 PM Subject: [Fiware-wpl] Guidelines for the creation of the Architecture Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear all, Let us condensate the procedure for the Architecture review in one message. The calendar is the one agreed yesterday in the WPL/WPA call: 1. First draft of contributions by chapter ready for peer review: end of February 2. .docx first version of chapter ready by March 8 3. Comments on first draft (.docx with traced changes) due by March 13th 4. .docx second version of chapters ready for peer review: March 22nd 5. Comments on second draft due by April 2nd 6. Final version: April 10th As you surely recall, the guidelines for the Architecture doc are under: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions The process will be like reflected on the FI-WARE Architecture peer-review cockpit: ? We can use any wiki in each chapter but we need to have all the pages of each chapter on the same wiki for the docx generation. It sounds painful but believe me, it is not thanks to the tools provided by Thorsten and his team. Do not change this until you receive a separate message that I will send with more details later today. ? Each WPL will generate a docx document per chapter (SAP will provide support to the doc generation if needed). o Upload the generated doc to ?FI-WARE private? project -> Docs -> folder ??Peer reviews? -> subfolder ?Architecture Review? o Add the link to the doc to the cockpit o Further instructions here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables ? The document from a given chapter will be taken by the reviewers in charge of reviewing it using the link in the cockpit ? The WPL of the chapter that reviews it will make sure that it is reviewed before the deadline. Up to him how to organize it internally. ? All the reviewers of a WP receive the same document but each one suggests changes for the GE (or GEs) they review. There is a line per GE, up to each WP to merge them or use them separately. Once finished, they will upload their reviews to the right folder: o ?FI-WARE private? project -> Docs -> folder ??Peer reviews? -> subfolder ?Architecture Review? o The link (or links if more than one) to the doc (or docs) will be added to the cockpit ? Each WPL will analyse with his team the comments provided and will generate a new version of the chapter docx to be further reviewed. The new version should be available on the deliverable cockpit. Note that from this point on, chapter should drive further updates on the Word document, instead of any temporary wiki ? The reviewers will have a second round of comments. ? The final version will be generated for delivery. At this point, we will merge the contributions from all chapters (it is a single monolithic deliverable) and send it to the EC. ? Chapter leaders will then coordinate updates of the public wiki to align with the Word document that was submitted to the EC This is the assignment: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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 Mar 11 01:25:40 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 11 Mar 2013 01:25:40 +0100 Subject: [Fiware-wpa] Fwd: M18 review report not received In-Reply-To: <513D23CC.6040601@tid.es> References: <513D23CC.6040601@tid.es> Message-ID: <513D2484.2030208@tid.es> FYI. Official reminder sent to our PO, Mr. Arian Zwegers. -- 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: M18 review report not received Date: Mon, 11 Mar 2013 01:22:36 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: FI-WARE project EC mailbox , Miguel Carrillo , "subsidies at tid.es" , "jhierro >> \"Juan J. Hierro\"" Dear Arian, This mail is just to highlight that we haven't yet received the official report of the FI-WARE M18 review. This means that there will be little time to react to recommendations on some deliverables that are due very soon. Depending on the nature of comments/recommendations, it might be difficult to cover some of them on time for the 2nd year report period official review. 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: From jhierro at tid.es Mon Mar 11 01:31:33 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 11 Mar 2013 01:31:33 +0100 Subject: [Fiware-wpa] Message sent to evaluators of third FI-WARE Open Call and list of evaluators. In-Reply-To: <513D1D3C.6090407@tid.es> References: <513D1D3C.6090407@tid.es> Message-ID: <513D25E5.6050102@tid.es> Hi all, Please find below the message sent to evaluators finally selected for the 3rd FI-WARE Open Call. Please treat this info as strictly confidential. The list of evaluators is: Name Company Profile Other useful links Dominic Greenwood Whitestein Technologies (COO) http://ch.linkedin.com/in/dominicgreenwood Sergi Herrero BNP Parriba (COO L'Atelier NA BNP-Paribas) http://linkd.in/XtueYy http://www.bnpparibas.be/en/2013/01/18/sergi-herrero-appointed-new-ceo-of-latelier-bnp-paribas-in-san-francisco/ Thibaut Rouffineau WIP (Mobile Activist) http://www.linkedin.com/in/campbieil Daniel Ben-horin TechSoup Global (CEO) www.linkedin.com/pub/daniel-ben-horin/4/248/7b1 http://www.techsoupglobal.org/blog/daniel-ben-horin Jos? Carlos Ramos Forever Us (chairman) http://es.linkedin.com/in/josecarlosramos 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 -------- Original Message -------- Subject: PLEASE RESPOND: You have been selected as evaluator in the first FI-WARE Open Call - on the topic Date: Mon, 11 Mar 2013 00:54:36 +0100 From: Juanjo Hierro To: dgr at whitestein.com , Daniel Ben-Horin , thibaut at wipconnector.com, Sergi.herrero at mail.atelier.net, jcramos at avanzalis.com CC: jhierro >> "Juan J. Hierro" , Javier de Pedro Sanchez , CARLOS RALLI UCENDO Dear sirs, After evaluation of all candidatures, I'm glad to tell you you that you have been finally selected as evaluator of the third FI-WARE Open Call. Please read carefully all the information below. FI-WARE is a project targeted to deliver a novel service platform, building upon elements (called Generic Enablers) which offer reusable and commonly shared functions making it easier to develop Future Internet Applications in multiple sectors - building a true foundation for the Future Internet. The project will develop public and royalty-free Open Specifications of Generic Enablers, together with a reference implementation of them available for testing. You can think about FI-WARE as a platform similar to Amazon's Web Services but genuinely open (third parties can implement FI-WARE specifications royalty-free as well as deploy and operate their own FI-WARE instances) and providing more value added services in a number of areas like the Internet of Things. FI-WARE is the cornerstone of the Future Internet PPP Programme, a joint action by the European Industry and the European Commission. As mentioned in the first email we sent to you, the goal of the third FI-WARE Open Call is to incorporate new partners to the FI-WARE project who will be in charge of implementing a plan targeted to: * Take up of FI-WARE results by Internet application developers and entrepreneurs * Creation and support of a dynamic innovation ecosystem around FI-WARE results * Achieve maximum market visibility for the technologies and services developed by FI-WARE We have had to update the calendar that we sent to you in our previous mail due to the experienced delay during selection of evaluators. The final calendar to be followed during this evaluation process has been defined as follows: * Self training of evaluators (on FI-WARE project) - 10/03/13 - 17/03/13 (this can be organized as 1 and a half net day of self-training to be carried out off-line by selected evaluators on their own based on a dossier of information. In addition an on-line training and briefing session of about one and a half hour will be organized) * Assignment of Proposals for review and evaluation period - 10/03/13 - 19/03/13 * Evaluators consensus meeting - day to be agreed during the period 20/03/13-22/03/13 * Edition of Open Call Evaluation Report - 22/03/13 - 19/04/13 (this activity will be carried out by FI-WARE based on results of the evaluators consensus meeting) * Open Call Evaluation Report sent to the European Commission - 19/04/1 Please confirm that the proposed calendar is still fine with you. As you see, the self-training and evaluation period have been defined to start in parallel to provide maximum flexibility to you in organizing your time. We have received four proposals, therefore the following is our estimation about time needed (indeed upper limit) and payment offered: * two full-days training on FI-WARE, to be organized as self-training plus a training session that we will organize as described below. Payment will therefore be = 450EUR * 2 = 900 EUR * two full-days for remote evaluation of proposals. Payment will therefore be = 450EUR * 2 = 900 EUR * one additional day splitted in half-day for the consensus meeting (confcall) and the time devoted afterwards to review the final report off-line: 450 EUR * total: 2.250 EUR The Self-training period is a period during which we assume you will review some essential information about the FI-WARE project that may help you in performing your evaluation. There is plenty of information about the FI-WARE project. However, here it is our recommendation: * Perform steps 1 and 2 of the quick FI-WARE tour at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Quick_FI-WARE_tour * Read text of the third FI-WARE Open Call: http://www.fi-ware.eu/open-call/ * Check published guidelines for applicants to the third FI-WARE Open Call: http://www.fi-ware.eu/wp-content/uploads/2013/02/FI-WARE_Open_Call_Guide_for_applicants-Open-Call-3.docx Despite we believe it would not be strictly necessary for carrying out the evaluation of proposals, you can of course learn more details about FI-WARE by taking a look at the FI-WARE Architecture Description: * FI-WARE Architecture Description: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture Of course, we are happy to respond any question you wish to formulate during your self-training. We offer a virtual training session on the second half of this week (Wednesday 13 - Friday 15). Members of the FI-WARE project team will attend this session and will provide valuable information about the FI-WARE project as well as the specific goals of this Open Call that may help you during the evaluation process. They may also answer any question you may have. Please cast your preferences in the following doodle poll in order to fix a suitable date/time for the confcall+webex. Attendance, of course, is not mandatory but evaluators of previous open calls have found this session extremely useful: http://www.doodle.com/33t55ugt5c62n4rw Evaluation of proposals should close before March 19 EOB. We want to emphasize that the evaluation will be remote (no need to travel) but we expect that you will devote up to 2 full working days for the evaluation of proposals. You will also have to send an evaluation form per each of the proposals being evaluated (4 proposals in total). The evaluation will end up with a consensus virtual meeting that will take place some day between March 20-22. This meeting typically last about 3-4 hours, with some break in between. We will setup a doodle poll in the following days to find the most suitable date and timeslot for this consensus meeting. If you agree with the proposed process and compensation, we ask you to confirm your acceptance no later than March 12th, 12:00pm by sending me a reply to this message cc Javier de Pedro and Carlos Ralli also in copy of this mail. We will also ask you that you attach to your email a signed NDA that will be sent to you. A hard copy of the signed NDA document should also additionally be sent by postal mail to: Jose Luis Pe?a Sedano Distrito Telef?nica Investigaci?n y Desarrollo Edifico Oeste 1, Planta 4 Ronda de la Comunicaci?n S/N 28050 Madrid (Spain) Last but not least, you have to confirm in your response that you don't have any conflict of interest to participate as evaluator in this Open Call. In order to evaluate this, please find enclosed the list of partners involved in the proposals received to 3rd FI-WARE Open Call. We look forward to your response. Kind regards, Juanjo Hierro (on behalf of the FI-WARE Project) ------------- 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: Open Call 3 - Summary of Proposals.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 10004 bytes Desc: not available URL: From mcp at tid.es Mon Mar 11 11:04:45 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 11 Mar 2013 11:04:45 +0100 Subject: [Fiware-wpa] minutes Message-ID: <513DAC3D.2050806@tid.es> https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.un6roxdpg71d -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From thierry.nagellen at orange.com Mon Mar 11 11:08:28 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 11 Mar 2013 10:08:28 +0000 Subject: [Fiware-wpa] [Fiware-wpl] minutes In-Reply-To: <513DAC3D.2050806@tid.es> References: <513DAC3D.2050806@tid.es> Message-ID: <4110_1362996509_513DAD1D_4110_448_7_976A65C5A08ADF49B9A8523F7F81925C0B98B2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Nobody from IoT can attend the meeting because we have a F2F meeting currently. 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 Miguel Carrillo Envoy??: lundi 11 mars 2013 11:05 ??: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet?: [Fiware-wpl] minutes https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.un6roxdpg71d -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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 juan.bareno at atosresearch.eu Mon Mar 11 15:45:13 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Mon, 11 Mar 2013 15:45:13 +0100 Subject: [Fiware-wpa] [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ?? Message-ID: Dear All Please find here enclosed the "Standardization calendar link" to fulfil with your WP contribution (presentation, demo, express FI-WARE support.......) to specific Standards. So, what kind of activity can _your_ Work Package propose ??" https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation "The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification". This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards. Of course changes and delays etc will happen frequently, but it is important to start this. Example: DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it Thanks for your contribution 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-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost Sent: jueves, 28 de febrero de 2013 16:29 To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: Nuria De-Lama Sanchez; 'lorant.farkas at nsn.com'; Ernoe Kovacs; Carmen Perea Escribano Subject: Re: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ?? Dear all, on request of management, because the link is FI-WARE_private and looks "dead" to anyone from the public www, I have moved the location of the link to our private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Main_Page#FI-WARE_Exploitation at the section for FI-WARE Exploitation, saying: Standardization (re-use of specs, contributions to SDOs) has a separate planning tool for coordination: * SDO_Calendar_2013 thank you for any comments about using the tool ... /Lindsay From: fiware-standardization-bounces at lists.fi-ware.eu [mailto:fiware-standardization-bounces at lists.fi-ware.eu] On Behalf Of Lindsay Frost Sent: Donnerstag, 28. Februar 2013 12:34 To: fiware-standardization at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: Nuria De-Lama Sanchez; Ernoe Kovacs; 'Carmen Perea Escribano'; 'lorant.farkas at nsn.com' Subject: [Fiware-standardization] Planning calendar link exists, what kind of activity can _your_ Work Package propose ?? Dear all, with help from Miquel and others, there is now a "protected" link to the xls calendar at: FI-WARE Exploitation . It is downloadable only by FI-WARE members and the EU commission. As a FIRST example of using it, Luca Giacomello has kindly provided a DRAFT "activity" for the date 09.12.2013. You should see it on the "Timeline" worksheet immediately on opening the xlsm link at the text "SDO_Calendar_2013" on the FI-WARE Exploitation area (or at the first hyperlink in this email): DRAFT SCHEDULE "OSGi Cloud proxy" Presentation and/or Demo of WP7 "Interfaces to network" technology at HGI EVENT. Contact = luca.giacomello at telecomitalia.it The idea is to pick SDO meetings where your Work Package _intends_ to make some contribution or presentation or demo or even just "express FI-WARE support for a Work Item or agreed Specification". This will show the EU commission and all FI-WARE partners that FI-WARE is impacting standards. Of course changes and delays etc will happen frequently, but it is important to start this. So, what kind of activity can _your_ Work Package propose ?? Please ask your teams! Please supply one or more simple texts like the example given above. Thank you for replying to all when answering, so we can quickly see what objections or improvements are needed. best wishes Lindsay PS: Apologies to Luca! The old xls on the server does not match the desired message above. I will fix it as soon as somebody has time to help me with some problems (a) my ignorance of proper method, (b) lack of authorization, (c) both PPS: I am happy to add also new SDO events, interesting workshops, national holidays, etc ... it should be useful and interesting for everybody ;-) ... just email me privately and I will update. ------------------------------------------------------------------ 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: From giorgio.parladori at alcatel-lucent.com Mon Mar 11 16:23:02 2013 From: giorgio.parladori at alcatel-lucent.com (PARLADORI, GIORGIO (GIORGIO)) Date: Mon, 11 Mar 2013 15:23:02 +0000 Subject: [Fiware-wpa] Patent and Publication subnitted in 2012 in the context of FI-WARE In-Reply-To: References: Message-ID: As ALU-I we would like to mention: Pasquale Donadio, Giorgio Parladori "Network Virtualization in the Cloud Computing Era" Presented @ Networks 2012, October 15-18 Rome, Italy Regards, Giorgio From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: venerd? 8 marzo 2013 10.26 To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware] Patent and Publication subnitted in 2012 in the context of FI-WARE Dear Colleagues As responsible of exploitation activities, I have to fulfill with the following request form the EC concerning the provision of data about patents and publications that were submitted or published in 2012 for the Monitoring of the FP7 Implementation in the following link http://digital-agenda-data.eu/survey/index.php/survey/index/sid/414196/token/285248/lang/en The survey will be open until 15th March 2013. So please send me the following before 13th March EOB: - FI WARE publications- Title, Author, publication magazine... - Patent applications originate from partners? work done in the context of FI-WARE (Applicant name, Inventor Name, IPC Class..) Thanks for your collaboration Br Juan ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Mar 11 19:07:47 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 11 Mar 2013 19:07:47 +0100 Subject: [Fiware-wpa] FI-WARE / Security Chapter contrib to D2.3.2 ready for peer review Message-ID: <1969_1363025277_513E1D79_1969_20_1_390145e3-a5bb-4e2f-9ad6-6a32eb3da8ab@THSONEA01HUB03P.one.grp> Dear Colleagues, This email just to let you know that Security Chapter contrib. has been uploaded and is ready for peer review. Cockpit has been updated accordingly with the link to the Doc (cf. https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0) Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Mar 11 21:41:10 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 11 Mar 2013 21:41:10 +0100 Subject: [Fiware-wpa] R: [Fiware-wpl] More on the Architecture document In-Reply-To: <5135FE94.20808@tid.es> References: <5135FE94.20808@tid.es> Message-ID: Dear All, Also the draft D2.3.2 doc concerning I2ND chapter is ready for peer review. I have uploaded it on the docman system of the FI-WARE private wiki, the link is available in the shared spreadsheet at link https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 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: marted? 5 marzo 2013 15:18 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: Sandfuchs, Thorsten; Klein, Andreas Oggetto: [Fiware-wpl] More on the Architecture document Dear all, In the message with the guidelines for the Architecture doc (attached) I promised an email elaborating a bit on the work of creating the docx. Let us recapitulate for your convenience and also add some extra info. As you may recall, we need to create a cover with the basic info and a list of links. I created the skeleton of what you need on this page on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.2.3.2.submission_cockpit You just will use the "partial per chapter contributions" table (a line per chapter) for the time being. I have asked SAP to create a fresh version of the generated zip twice a day (12am and 5 pm). We can refresh it under demand as well but please ask for this just when strictly necessary only As usual, you need to: * Update the "Structure of this Document" section with the links * Update other sections as needed (note that they will be merged in the final deliverable unifying all chapters in one doc) * Once the zip is generated, follow the tutorial on https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables - this was made by SAP in the past due to time constraints but we need to learn to do it, it is reasonably simple. But yes, it needs some work on your side. Also, there is a video tutorial on https://forge.fi-ware.eu/docman/view.php/27/1526/FI-WARE_software_deliverable_front_pages.flv. Andreas and Thorsten (in CC) could also help you if you get stuck at some point. There is very good news. SAP have figured out how to produce documents mixing pages on different wikis. So what I said in my previous emails about having all on the same wiki is not an issue anymore. You just have to use the following format: Fiware Public Page :[URL_TO_PUBLIC_WIKI_PAGE NAME_OF_PUBLIC_WIKI_PAGE] Fiware Private Page :[[NAME_OF_PRIVATE_WIKI_PAGE]] Example: Fiware Public Page :[http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision FI-WARE Product Vision] Fiware Private Page :[[Deliverables cockpit]] Please keep in mind that only a new document version in the Frontpage (Changes History - {{DocVersion|}}) will lead to a complete regeneration of the deliverable including an update of all linked pictures. If you don't update the document version already cached pictures will be used for document generation. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Tue Mar 12 12:13:35 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 12 Mar 2013 12:13:35 +0100 Subject: [Fiware-wpa] Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report In-Reply-To: References: Message-ID: <513F0DDF.4010303@tid.es> Dear partners, I forward to you without even reading it yet to avoid any delay. I'll come to this after I read it carefully. 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: FI-WARE 4th Review meeting: Outcome Letter & Review report Date: Tue, 12 Mar 2013 10:43:05 +0000 From: To: CC: , , , , , , , Dear Mr Hierro, Please find attached a scanned copy of the outcome letter and review report of project 285248 FI-WARE. Please acknowledge receipt of this letter. Many thanks in advance Best regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck 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: FI-WARE Review 4 Report.pdf.pdf Type: application/pdf Size: 692696 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outcome FI-WARE review 4 report.pdf.pdf Type: application/pdf Size: 142922 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue Mar 12 16:47:56 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 12 Mar 2013 16:47:56 +0100 Subject: [Fiware-wpa] Architects Week in Madrid Message-ID: <513F4E2C.1090506@eng.it> Dear Juanjo, do you have some update on the status of the preparation for the Architects Week in April? Location, draft agenda ... thank you and Kind Regards, Davide From mcp at tid.es Tue Mar 12 17:46:06 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 12 Mar 2013 17:46:06 +0100 Subject: [Fiware-wpa] Fiware Live Demo list Message-ID: <513F5BCE.1010304@tid.es> Dear WPLs/WPAs, Regarding the "Live application demo" item at https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu, all the WPA/WPLs have been just subscribed by Ferm?n to the fiware-demo list (fiware-demo at lists.fi-ware.eu). Note the following AP on the weekly minutes of meeting to be complete by every WPA/WPL: AP on all WPLs to send email to Miguel cc/ Ferm?n and Juanjo regarding members of their teams they wish to include in the mailing list. There are two ways of actually accomplishing this AP * Send an email to me cc/ Ferm?n and Juanjo with the emails to be subscribed. * Each people that needs subscription does it himself/herself using the fiware-demo interface: https://lists.fi-ware.eu/listinfo/fiware-demo This AP has to be completed before tomorrow Wednesday 12th EoB. Ferm?n will send the "kick-off email" on this date so if we do not get the info by Wednesday, Fermin's email could fail to get to important people and leave them out of the start of the Live Demo evolution. This is fairly straightforward and shouldn't take more that a few minutes so please try to assess internally if you need more people on the list. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Mar 12 18:22:17 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 12 Mar 2013 18:22:17 +0100 Subject: [Fiware-wpa] Moving date of next WPL/WPA follow-up confcall Message-ID: <513F6449.8060600@tid.es> Dear colleagues, Monday March 18th is holiday in Spain. Therefore, we will have our regular joint WPLs/WPAs follow-up confcall on Tuesday, same time for both parts. I understand that this may mean that some of you cannot make it but it would be difficult to find another day that same week. Apologize for the inconvenience. 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 Tue Mar 12 18:21:57 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Tue, 12 Mar 2013 17:21:57 +0000 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall (Part I) Message-ID: <936DECD07EB54B4BAA44E7B823EC894150FE9057@EX10-MB2-MAD.hi.inet> When: Tuesday, March 19, 2013 11:00 AM-12:30 PM. (UTC+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* Joint WPLs/WPAs follow-up confcalls are splitted into two parts. This is the first one and we will always stick to the end time. Topics not addressed in this slot will be treated in the slot of the afternoon. The slot in the afternoon will be used to also address Technical-Architecture issues. 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: 4016 bytes Desc: not available URL: From jhierro at tid.es Tue Mar 12 18:22:16 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Tue, 12 Mar 2013 17:22:16 +0000 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall (Part II) Message-ID: <936DECD07EB54B4BAA44E7B823EC894150FE90DA@EX10-MB2-MAD.hi.inet> When: Tuesday, March 19, 2013 2:30 PM-4:00 PM. (UTC+01:00) Brussels, Copenhagen, Madrid, Paris *~*~*~*~*~*~*~*~*~* Joint WPLs/WPAs follow-up confcalls are splitted into two parts. This is the second one and we will always stick to the end time. Topics not addressed in the first slot will be treated in this slot of the afternoon. This slot will also be used to also address Technical-Architecture issues. 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: 4011 bytes Desc: not available URL: From mcp at tid.es Tue Mar 12 19:46:08 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 12 Mar 2013 19:46:08 +0100 Subject: [Fiware-wpa] SW deliverables in April/June Message-ID: <513F77F0.4000304@tid.es> Dear all, I was checking with Juanjo your question about what we are expecting to deliver with the software and when. Fortunately for all of us, his answer is 100% aligned with what it was said yesterday 1) The roadmap leaves clear what we will have for April (those with something in R2.2 or R2.1) and what will be left for June (R2.3). The vast majority of the GEs should be delivered in April. After a quick scan through the roadmap I see IoT as the only chapter who leaves most of their GEs for R2.3. The rest of the chapters are complying with the general rule of delivering most of the GEs in April. 2) Delivering software without info makes no sense. Delivering is delivering the whole lot, as usual. * We expect the usual pack in April (for those GEs who deliver in April). This means: * Software * Install and admin manual * User and Programmers manual * Unit test plan and report * In June we will deliver everything. * Those GEs with no change (no backlog items in R2.3) could be be delivered unchanged integrated in the final deliverables. Exceptions: * The GE owner may decide to change something for whatever reason. * The requests from the Use Cases may introduce changes * Those GEs delivered in April but with backlog items in R2.3 will possibly need updating * The new deliverables (those who deliver in R2.3 only) will provide all the sw + the aforementioned documentation pack To avoid confusions I attach an excel spreadsheet with my view of R2. I am using your backlog to reflect what is delivered when so this shouldn't be particularly surprising. AP: all WPA/WPL please confirm in private that this excel file reflects correctly what goes for April and what goes for July. This is a formal commitment to deliver. Also, check that the list is correct and there are no GEs missing or extra GEs. As this is not so urgent, an answer by the end of the week (Fri, 15) should be ok. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Delivery_roadmap.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 16293 bytes Desc: not available URL: From mcp at tid.es Wed Mar 13 15:44:53 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 13 Mar 2013 15:44:53 +0100 Subject: [Fiware-wpa] Date for the M24 review - June 12-13 Message-ID: <514090E5.7050609@tid.es> Dear all, As stated during our WPL/WPA confcall on Monday, the PO was a bit puzzled to see a change in the date agreed in the last review (June 12-13). It seems that there were no objections to take these dates(I understood that some of you expressed a preference for the other date we were handling internally but would accept it if necessary) Unless someone replies with a serious objection before the end of tomorrow, we will confirm Arian that we can have the review on the initial dates (June 12-13). We will send this message to him Friday first thing in the morning. Not surprisingly, be ready to have a rehearsal on monday 10 (we will confirm the exact time shortly) and tuesday 11 (full day). Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Thu Mar 14 06:58:38 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 14 Mar 2013 06:58:38 +0100 Subject: [Fiware-wpa] Fwd: Venue for the FI-PPP Phase 2 FI-PPP Architecture Week In-Reply-To: <514166B3.8060703@tid.es> References: <514166B3.8060703@tid.es> Message-ID: <5141670E.1030808@tid.es> FYI. Hope this helps you to close booking of your trip to Madrid for the Architecture Week. Best regards, -- Juanjo -------- Original Message -------- Subject: Venue for the FI-PPP Phase 2 FI-PPP Architecture Week Date: Thu, 14 Mar 2013 06:57:07 +0100 From: Juanjo Hierro To: Lakaniemi Ilkka , Cecchi Maurizio , Sjaak Wolfert , Williams Fiona , Fourdeaux Henri , "rod.franklin at kuehne-nagel.com" , "sergio.gusmeroli at txtgroup.com" , Christoph Thuemmler , Van Der Linden Pieter , Anastasius Gavras CC: Fatelnig Peter , "Arian.ZWEGERS at ec.europa.eu" , "Ragnar.Bergstrom at ec.europa.eu" , "Maria-Concepcion.ANTON-GARCIA at ec.europa.eu" , David Kennedy , "FI-PPP-Phase-2-Contacts at future-internet.eu" , Turkama Petra , Salo Juha , Schaffers Hans , Thomas Michael Bohnert Dear all, This mail is to announce that the FI-PPP Architecture Week for Phase 2 will take place in the following venue: Aula Magna in Building "A" School of Telecommunication Engineering (ETS Ingenieros de Telecomunicacion - ETSIT) Avenida Complutense # 30 University City 28040 Madrid Directions and hotels close to the venue can be found at: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/como-llegar.html%3FL%3Dttqltguphtgolkug&usg=ALkJrhi775kjxa4XFzatOQMya9dkNbh5wg Maps of the buildings associated to the ETSIT: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/etsi-de-telecomunicacion/etsit-edificios.html&usg=ALkJrhi0WiJVR4jcJKDRa0prunRkZbTCig We had received many request to allow more than two people attending on behalf of phase 2 projects to the Architecture Week that will take place in Madrid, during April 2-5, that's why we have been late announcing the venue. Actually, the original venues were at a different location, but the meeting room was limited to 28-30 people maximum. Please note that coffee and lunch breaks will be scheduled during the week, but each attendee has to cover its own expenses. There is a restaurant and coffee bar in the same building of the venue with convenient prices. Note also that it might take a while to go from the University to the Airport, first walking to the metro stop "Ciudad Universitaria" (aprox. 1 Km) and then taking the metro to the Airport (you should take line 6 until "Nuevos Ministerios" and then line 8). You should take this into consideration when arranging the time of your return fligths on Friday. I will come later this week with a more detailed agenda, but the one already sent to you (see mail below) should be enough as far as logistics is concerned. 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 20/02/13 05:01, Lakaniemi Ilkka wrote: Dear all, As indicated yesterday, please find more detailed info about the FI-PPP Architecture Week on 2-5 April in Madrid. For any further details and info, please be in touch with Juanjo, Thomas B and me. The agenda of this meeting (draft): * April 2 (starting at 11:00am): FI-WARE to provide a thorough introduction on FI-WARE scope, goals, basic concepts, methodology, planning, available documentation, resources, tools, etc as well as a detailed description of the way the FI-PPP AB works. * April 3 morning: FI-WARE to provide detailed info about the FI-WARE Second Release, training planning, etc. * April 3 afternoon until April 5 17:00 CET: sequence of half-days workshops per UC Trial projects where UC Trials will present a sketch of their envisioned architecture, their current plans regarding usage of FI-WARE GEs, needs regarding setup of their trials, questions on which they need responses, etc. FI-WARE will provide feedback during these workshops that will help UC projects to program their planning of activities taking the most of FI-WARE. Note from FI-WARE: Technical managers/architects from UC Trial projects that are continuation of Phase 1 UC projects may skip the first day (i.e., people already engaged in phase 1 and part of the FI-PPP AB already). The rest of days will be mandatory for all UC Trial projects as well as FI-WARE and Xifi. People engaged in the FI-PPP for their first time must also attend the first day. It is expected that 2, maximum 3 people per project will attend. They should play a technical role in their project. Ideally, two of them should be the ones being appointed as members of the FI-PPP AB. Kind regards, Ilkka and Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Thu Mar 14 08:18:31 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 14 Mar 2013 07:18:31 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Date for the M24 review - June 12-13 In-Reply-To: <514090E5.7050609@tid.es> References: <514090E5.7050609@tid.es> Message-ID: <20378_1363245513_514179C9_20378_993_2_976A65C5A08ADF49B9A8523F7F81925C0BB37E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Miguel, No pb for me, I booked the date in November. 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 Miguel Carrillo Envoy??: mercredi 13 mars 2013 15:45 ??: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet?: [Fiware-wpl] Date for the M24 review - June 12-13 Dear all, As stated during our WPL/WPA confcall on Monday, the PO was a bit puzzled to see a change in the date agreed in the last review (June 12-13). It seems that there were no objections to take these dates(I understood that some of you expressed a preference for the other date we were handling internally but would accept it if necessary) Unless someone replies with a serious objection before the end of tomorrow, we will confirm Arian that we can have the review on the initial dates (June 12-13). We will send this message to him Friday first thing in the morning. Not surprisingly, be ready to have a rehearsal on monday 10 (we will confirm the exact time shortly) and tuesday 11 (full day). Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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 mcp at tid.es Fri Mar 15 16:34:31 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 15 Mar 2013 16:34:31 +0100 Subject: [Fiware-wpa] Status of Architecture review Message-ID: <51433F87.5090805@tid.es> Dear all, This is how I see the 1st round of reviews: [cid:part1.07040402.01000001 at tid.es] In other words: * Cloud, I2ND, Security & Data - ok, reasonable situation (pending check in private with cloud) * Apps - not very good, quite late * IoT - disastrous Apps seem to be moving and although late I am hopeful that they will finish soon. IoT seems to be in a coma. I did not open the docs but I guess that if there is something particularly worth mentioning you will contact me (only if it is really relevant, please). Best regards Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ifcacgcg.png Type: image/png Size: 15001 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Fri Mar 15 18:48:53 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 15 Mar 2013 18:48:53 +0100 Subject: [Fiware-wpa] TR: FI-WARE / Security Chapter / Security Monitoring GE - Information needed Message-ID: <19083_1363369982_51435FFE_19083_5413_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E4465567@THSONEA01CMS04P.one.grp> Dear All, I'm forwarding you this email for which so far we (Daniel nor I) didn't receive any answer. As such I hope by resending this email this time we will get some answer/feedback to member who registered to that list. As for the rest let's also add it to list of topics we would have to address at our WPL/WPA conference. Best Regards, Pascal De : BISSON Pascal Envoy? : mercredi 6 mars 2013 09:21 ? : fiware-secure-cloud at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; GIDOIN Daniel; BISSON Pascal Objet : FI-WARE / Security Chapter / Security Monitoring GE - Information needed Importance : Haute Dear Colleagues, Find attached to this email an excel file prepared by Daniel & I with help of the team that state the information requested by the Security Monitoring GE to get it up and running. Mainly addressed to Cloud Hosting and the thread of discussion newly created and reflected by the secure-cloud mailing list we wanted to share it also with other chapters being said Security Monitoring would also be aiming at being used in their context to protect against some specific chapter's threats that would have been identified and reported to us (let me here remind as per Rome meeting specific action which was set on this - and which is btw still pending ...). In the attached excel you will see the information requested by each of the major modules of Security Monitoring architecture (the way it has been defined) clearly stating why it is needed (the rationale) and examples of the way it is expected to be passed to us (SecMon GE owner). In order to get us moving regarding integration of the Security Monitoring GE in FI-WARE we'd like to hear how we could gain access to the information we are requested. So hearing first from people from Cloud Chapter enlisted in the secure-cloud mailing list. In the meantime this doesn't prevent other chapters to also report their views and information they could contribute from their side and in complement of information provided by Cloud. Looking forward to reading you soon on this hot topic. Best Regards, Pascal & Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware - Security Risk Analysis - Inputs.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 16163 bytes Desc: FI-Ware - Security Risk Analysis - Inputs.xlsx URL: From thorsten.sandfuchs at sap.com Mon Mar 18 08:49:39 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 18 Mar 2013 07:49:39 +0000 Subject: [Fiware-wpa] Deliverable 10.5.1 rejected (was: FW: Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3158@DEWDFEMB11A.global.corp.sap> Dear WPL/WPA, This is to make you all aware and start the discussion on one of the parts of the Review report concerning the validation topic (10.5.X). Status: - D.10.5.1 (validation report) was rejected (as attached below) and they expect a resolved version of the validation report (and major changes) for M24 (already end of April). - Main point from the reviewers: validation report does not met the expectations set by the DoW. 1. UC requirements are not linked to the validation (Personal assumption: ... as these requirements are not fully recorded in the first place, it is almost impossible to resolve this ) 2. Non-functional capabilities are not part of the presented evaluation approach - This can't be resolved on the testbed-level, we have to start the resolution and discussion on the WPL/WPA level My personal opinion to the matter: - The validation process was aligned between the UC and FI-WARE and was part of an official AB-resolution - The requirement matrix can't be established, as we do not have a concise list of requirements by the UCs - For the non-functional capabilities we need to come up with a new approach currently I don't know have a good idea on how to approach this - do you have any other agile processes where non-functional capabilities are part of the validation? Our (quiet obvious) options for 1. (UC requirement links) are: I. Give in to the reviewers and try to intro a link between the "requirements"/"feature"-list and the UC validation (if we take "FEATURES": I personally won't know who would really be able to judge if a feature is really present in a given GE and given the high amount of "FEATURES" in our wikis, this would be a hard job... ) (if we take "requirements": we would firstly need to consolidate and aggregate a list of requirements - who would be able to input here, as the UC projects in phase 1 are probably not responsive any more and the UC2 are just starting ) II. Convince the reviewers that the AB board decision overrules the DoW (potentially and just-to-be-sure: this should be communicated before the next review and potentially clarified with the PO) (potentially this should be reflected in one upcoming amendment of the DoW) III. ... < your options go here > :) Our (quiet obvious) options for 2. (non-functional capabilities) are: I. Give in to the reviewers and introduce a new process on how to validate non-functional capabilities of GEs or the platform in a whole (Who can contribute here?) II. ... < your options go here > :) Unfortunately I won't be able to join the next WPL/WPA call for long (and iff, only for the first slot) on Tuesday, therefore I would appreciate if you would take the topic in the first slot and make it the first topic. Thanks for any feedback and input and best regards, /Thorsten Attachement: D10.5.1 Report on Validation Process including Validation with Use Case projects This deliverable outlines the designed and recommended validation process for the use cases to follow. Additionally the initial feedback survey, which was initiate and send to the use case projects and the main findings are outlined. The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases. The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. As explained in the document, there is no tight linkage between the defined requirements and the features provided by the GE providers. Hence, the validation and requirements evaluation will not be based on a requirements matrix, but will follow an open questionnaire approach. The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterisation of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. Deliverable D10.5.1 is rejected. No re-submission is required, -- 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 jhierro at tid.es Mon Mar 18 09:31:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 18 Mar 2013 09:31:02 +0100 Subject: [Fiware-wpa] For the avoidance of doubt: our joint WPLs/WPAs confcall this week was moved to tomorrow Message-ID: <5146D0C6.2000708@tid.es> Hi all, For the avoidance of doubt: our joint WPLs/WPAs confcall this week was moved to tomorrow. Same two parts, same time. 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 axel.fasse at sap.com Mon Mar 18 09:55:02 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Mon, 18 Mar 2013 08:55:02 +0000 Subject: [Fiware-wpa] Log-Files Message-ID: Dear Juanjo, so far I did not really understand the concrete need for the additional effort to send out the Log-Files to IBM (and TID). Instead of analyzing the log-files "manually" I would suggest to use an easy to use Open source tool to monitor the GE's (Nagios http://www.nagios.org/ ) that could be used within the TestBed environment to monitor the availability of the GE's and could easily provide some reports in the case of errors or problems. Especially with respect to the OIL it is very important to this kind of information available. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Next Business and Technology SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe, Germany T +49 6227 7-52528 M +4915153858917 E axel.fasse at sap.com 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Mar 18 11:16:58 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 18 Mar 2013 11:16:58 +0100 Subject: [Fiware-wpa] Preparation of material for FI-PPP Architects Week Message-ID: <5146E99A.8000107@tid.es> Dear all, We have to prepare the material for the FI-PPP Architects Week in Madrid that will take place from April 2 (11:00) until April 5th (17:00). While we will discuss this in detail during our joint WPLs/WPAs confcall tomorrow, I would like to start the discussion off-line with this email. As a reminder, the agenda for the FI-PPP Architects Week is organized as follows: * April 2 will be mostly devoted to training of new phase 2 projects * April 3 morning will be devoted to elaborate on the FI-WARE functionality that will be made available to UC projects in the 2nd Release as well as the FI-WARE roadmap * From April 3 afternoon until April 5, we will run workshops with the UC projects so that each elaborate on their envisioned functional and physical architecture Regarding April 2, here it is my take: * TID will prepare and make a presentation elaborating on FI-WARE main concepts, introduction of the FI-WARE chapters, how FI-WARE specifications and APIs look like and will perform a quick FI-WARE Tour through the different FI-WARE resources on the web (FI-WARE wiki, FI-WARE Catalogue, ...) * The FI-WARE Testbed team should prepare a presentation on how to start using the FI-WARE Testbed (how to create a user account, what info they need to register, etc) * TID will prepare and make a presentation announcing the calendar of milestones new phase 2 projects should care about (at least for 2013). We have to agree on this. My current take is that we shall announce: * Calendar of webinars for FI-WARE GEis in the 2nd Release. This means to explain how we will run them and in which months they will take place ... also when the concrete dates for each webinar will be announced. * Calendar of dates at which review of the architecture of UC Trials will take place. * Other ? * closing the day, TID will make a presentation about the FI-PPP AB to new project representatives in the AB (AB mission, how the AB works in practice, etc) Regarding April 3 in the morning, UC Trials have already announced in advance that they wouldn't like to see a presentation on the internal architecture of FI-WARE chapters or specific FI-WARE GEis but rather about the functionality offered to UC projects (to be available in the 2nd Release and lookint into the future). I would suggest leveraging the different presentations on the Live Demo App as much as possible (see details below). Pending on discussion and agreement during our joint WPLs/WPAs follow-up confcall tomorrow, I would propose the following agenda: * Introduction to Live Demo App - 15 mins * Session on FI-WARE Cloud capabilities to be offered (Alex) - 20 mins: * this will mostly a demo of the FI-WARE Cloud available on the Testbed (OIL in the future) * I would propose to run the demo based on a version of the FI-WARE Cloud as closer to what we are going to have for Release 2 as possible, rather than based on what Phase 1 projects are using (FI-WARE Release 1) * Presentation on NGSI (common to IoT and Data chapter) (Juanjo/Thierry/Fermin) - 30-45 mins * Introduction to NGSI from a programming perspective: interfaces and introduction to REST API * Role of NGSI in the FI-WARE Architecture (Data and IoT chapters) * Usage example relying on the Live Demo App * Presentation on rest of FI-WARE GEis in the Data Chapter - 30 mins * Presentation on rest of FI-WARE GEis in the IoT Chapter - 30 mins * Presentation on Identity Management GE and OAuth-based Access Control to APIs (Thales/UPM ?) - 30 mins * I would first elaborate on the Identity Management GE (from a user/developer perspective) * then elaborate on the architecture regarding Access Control, relying on the presentation made by UPM during the WPLs/WPAs confcall (you may take advantage they can attend f2f) * Presentation on composition and mediation GEs (front-end web mashup based on wirecloud, backend service composition, mediation GEs) - 20 mins * regarding wirecloud, I would rely on the Live Demo App * didn't we use also the mediation GE in the Live Demo App, if so, rely on it * for those GEs not used in the live demo, elaborate on interfaces, APIs * Presentation on Bussiness Framework - 20 mins * I would present here the architecture document you have recently discussed within WP3 (you may add some disclaimer explaining it's work in progress) * you may rely on the fact that the UPM team of Javier Soriano can attend f2f * Presentation on I2ND GEs - 30 mins * I would just present those GEs that may relevant from a user/programmers' perspective. Not sure if it is worth elaborating on interfaces to networks that will not be exposed. Maybe just an overview on them * Presentation on Security Monitoring and brief introduction to Optional Security GEs - 20 mins * I would just present those GEs that may relevant from a user/programmers' perspective. Based on feedback from UC projects, going into details about the Security Monitoring Architecture will not be that helpful. Elaborating on what a user can do to setup security rules, or get notice about security breaches will be more useful, I guess. Maybe just overview on those GEs that are not visible through APIs exposed to app programmers. * Presentation on tools - 30 mins * focus on users/programmers' perspective I will try to prepare a draft agenda with the contents above in a google doc spreadsheet to ease our discussion tomorrow. Clearly, we may have an issue with the time ... your ideas on how to deal with the matter or anything regarding the agenda will be welcome. 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 Mar 18 14:27:10 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 18 Mar 2013 13:27:10 +0000 Subject: [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: References: Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [cid:image001.jpg at 01CE0539.CCE50940] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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.jpg Type: image/jpeg Size: 71929 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v3_demo_app.graphml Type: application/octet-stream Size: 63297 bytes Desc: fiware-cross-chapter_v3_demo_app.graphml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v3.graphml Type: application/octet-stream Size: 66307 bytes Desc: fiware-cross-chapter_v3.graphml URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jhierro at tid.es Mon Mar 18 18:25:22 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 18 Mar 2013 18:25:22 +0100 Subject: [Fiware-wpa] Fwd: FI-WARE: possible upcoming requests for speakers In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06D83D87@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06D83D87@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <51474E02.80000@tid.es> For your info. This is a task we should share among all FI-WARE partners, particularly WPLs/WPAs, each taking care of events in its own country. 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: FI-WARE: possible upcoming requests for speakers Date: Sat, 16 Mar 2013 12:10:58 +0000 From: To: CC: Dear Juanjo, Just to pre-warn you that we might ask FI-WARE soon for speakers to participate in phase 3 national workshops. Attached is a draft schedule, which will be on our websites soon (when more details are available). At the moment, the organisation of these workshops is rather chaotic with 2 units and FIF involved, but we are working on that. Best regards, Arian. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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-PPP_Phase3_Workshops.xls Type: application/vnd.ms-excel Size: 39424 bytes Desc: not available URL: From GLIKSON at il.ibm.com Mon Mar 18 20:16:25 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 18 Mar 2013 21:16:25 +0200 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> Message-ID: Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture ?citymap? below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than ?apps?) 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [ mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were ?known? while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking ?your? chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs ? currently this is more like a ?city map? than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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: 71929 bytes Desc: not available URL: From thierry.nagellen at orange.com Tue Mar 19 08:38:03 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 19 Mar 2013 07:38:03 +0000 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> Message-ID: <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [cid:image001.jpg at 01CE247C.F2E101A0] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 71929 bytes Desc: image001.jpg URL: From jhierro at tid.es Tue Mar 19 09:49:12 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 09:49:12 +0100 Subject: [Fiware-wpa] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW Message-ID: <51482688.2070907@tid.es> Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 effort-budget-funding - Amendment 4 v22.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 254498 bytes Desc: not available URL: From thierry.nagellen at orange.com Tue Mar 19 09:50:24 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 19 Mar 2013 08:50:24 +0000 Subject: [Fiware-wpa] Urgent email to EC for new resources distribution Message-ID: <18038_1363683026_514826D2_18038_3510_1_976A65C5A08ADF49B9A8523F7F81925C0BC14C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I cannot attend the meeting this afternoon because I'm flying to Paris for the last General Assembly of Instant Mobility project. I would raise here an urgent issue which was already urgent 3 weeks ago: we have to send an email to EC to validate the last decision of PCC to solve the withdrawal of Ericsson and involve some existing partners to replace them. It is critical for IoT chapter because of ETSI-M2M topic which has a clear impact on the architecture and what we can deliver in release2.2 and 2.3. Till now, I'm not aware of any email under preparation so I think this is now critical for us to have a decision of when new partners could be involved in these activities and we just need a written answer from our PO to do it... In any case it will be very difficult to be aligned with the roadmap if we add new delays for this email. 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 jhierro at tid.es Tue Mar 19 09:57:30 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 09:57:30 +0100 Subject: [Fiware-wpa] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <51482688.2070907@tid.es> References: <51482688.2070907@tid.es> Message-ID: <5148287A.2070708@tid.es> Hi all, Please use the new spreadsheet attached to this email instead of the previous one. We have included a new column we ask you to fill with a date from which reporting of costs should be accepted (you only need to fill the white cells in that column). Please respond back to these email with an email with your confirmation/comments together with a version of the spreadsheet with this info about starting date filled regarding WPs you lead. Apologizes for the inconvenience. 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 19/03/13 09:49, Juanjo Hierro wrote: Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 effort-budget-funding - Amendment 4 v23.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 254926 bytes Desc: not available URL: From jhierro at tid.es Tue Mar 19 10:15:44 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 10:15:44 +0100 Subject: [Fiware-wpa] Shared minutes of today's WPLs/WPAs follow-up confcall Message-ID: <51482CC0.5040206@tid.es> Dear colleagues, Please find the shared pre-minutes of our joint WPLs/WPAs follow-up confcall at: https://docs.google.com/document/d/15UOA2B7ot6FmNDXT1CmU5j_n9KiLl0BMksiymyhuGUQ/edit?usp=sharing We will handle revision of the M18 review report in the first place (this should address the request made by Thorsten). Then we will deal with report on status of the several short-term deliverables. Discussion on preparation of the Architects Week will most probably take place in the slot of the afternoon. 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 axel.fasse at sap.com Tue Mar 19 10:15:57 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Tue, 19 Mar 2013 09:15:57 +0000 Subject: [Fiware-wpa] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <5148287A.2070708@tid.es> References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> Message-ID: Dear Juanjo, Because not all of our partners are WPL/WPA, I would suggest to send out the this list for the approval directly to each of the partners. So they can agree on their changes and you can close the task. Actually I cannot foresee the "partners" that are involved within you current mailing list, this steps seems to be necessary. What do you think about ma Idea. Best regards, Axel 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, 19. M?rz 2013 09:57 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es; fiware-pcc at lists.fi-ware.eu Subject: Re: [Fiware-wpa] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW Hi all, Please use the new spreadsheet attached to this email instead of the previous one. We have included a new column we ask you to fill with a date from which reporting of costs should be accepted (you only need to fill the white cells in that column). Please respond back to these email with an email with your confirmation/comments together with a version of the spreadsheet with this info about starting date filled regarding WPs you lead. Apologizes for the inconvenience. 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 19/03/13 09:49, Juanjo Hierro wrote: Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 thierry.nagellen at orange.com Tue Mar 19 10:25:44 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 19 Mar 2013 09:25:44 +0000 Subject: [Fiware-wpa] [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <5148287A.2070708@tid.es> References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> Message-ID: <22521_1363685147_51482F19_22521_26_1_976A65C5A08ADF49B9A8523F7F81925C0BC1C3@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Here are the changes for WP5 no transfer from Ericsson to FT but to Fraunhofer. I did not change the PM but as the funding model is not the same we should not have 16PM for Fraunhofer. BR Thierry De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 19 mars 2013 09:58 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : subsidies at tid.es; fiware-pcc at lists.fi-ware.eu Objet : Re: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW Hi all, Please use the new spreadsheet attached to this email instead of the previous one. We have included a new column we ask you to fill with a date from which reporting of costs should be accepted (you only need to fill the white cells in that column). Please respond back to these email with an email with your confirmation/comments together with a version of the spreadsheet with this info about starting date filled regarding WPs you lead. Apologizes for the inconvenience. 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 19/03/13 09:49, Juanjo Hierro wrote: Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE effort-budget-funding - Amendment 4 v23 FT.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 256785 bytes Desc: FI-WARE effort-budget-funding - Amendment 4 v23 FT.xlsx URL: From jhierro at tid.es Tue Mar 19 10:31:21 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 10:31:21 +0100 Subject: [Fiware-wpa] Monitoring of log/trace files In-Reply-To: <5135FE2D.3090809@eng.it> References: <5135FE2D.3090809@eng.it> Message-ID: <51483069.8040409@tid.es> Dear Davide, I count you can make us a presentation on this topic during this afternoon session (part II of the joint WPLs/WPAs follow-up confcall) 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/03/13 15:16, Davide Dalle Carbonare wrote: Dear partners, I'd like to remind you one point we've on the minutes: "Monitoring of log/trace files" https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy @Juanjo, can you kindly send a feedback on what's your take on the purpose and technology points reported on the minutes? @WPAs, can you kindly forward to your GEi providers the request to send an example of log/trace files produced by their GE implementations? Please send the logs to Marcel Zalmanovici and to the WPA mailing list. I'm expecting to receive one example per GEi that will be available for release 2. Kind Regards, Davide _______________________________________________ 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 pierangelo.garino at telecomitalia.it Tue Mar 19 10:44:16 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 19 Mar 2013 10:44:16 +0100 Subject: [Fiware-wpa] R: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <5148287A.2070708@tid.es> References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> Message-ID: Hi Juanjo, concerning I2ND chapter, a couple of weeks ago I sent you a mail proposing to allocate a portion of Ericsson's efforts released in I2ND chapter to Uniroma, to cope with the work they would take in charge for adoption of the Android Flow Monitoring GE (including the possible use of one functionality of this GE for CDI own purposes). Moreover, I found that they don't have efforts allocated in the Integration WP, which is rather strange as they contribute to develop and make available components of two GEs of I2ND chapter. I would propose to allocate a (limited) effort on this too. Can we manage this already at this stage, so that effort would be moved directly to Uniroma? BR Pier Da: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: marted? 19 marzo 2013 09:58 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es; fiware-pcc at lists.fi-ware.eu Oggetto: Re: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW Hi all, Please use the new spreadsheet attached to this email instead of the previous one. We have included a new column we ask you to fill with a date from which reporting of costs should be accepted (you only need to fill the white cells in that column). Please respond back to these email with an email with your confirmation/comments together with a version of the spreadsheet with this info about starting date filled regarding WPs you lead. Apologizes for the inconvenience. 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 19/03/13 09:49, Juanjo Hierro wrote: Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 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 Tue Mar 19 11:04:28 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 11:04:28 +0100 Subject: [Fiware-wpa] R: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> Message-ID: <5148382C.2040103@tid.es> This is why we asked for your final confirmation/revision. I don't find any particular issue with your request regarding the I2ND WP. We need to check the implications regarding your request in WP10 with Engineering, leader of that WP. 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 19/03/13 10:44, Garino Pierangelo wrote: Hi Juanjo, concerning I2ND chapter, a couple of weeks ago I sent you a mail proposing to allocate a portion of Ericsson's efforts released in I2ND chapter to Uniroma, to cope with the work they would take in charge for adoption of the Android Flow Monitoring GE (including the possible use of one functionality of this GE for CDI own purposes). Moreover, I found that they don't have efforts allocated in the Integration WP, which is rather strange as they contribute to develop and make available components of two GEs of I2ND chapter. I would propose to allocate a (limited) effort on this too. Can we manage this already at this stage, so that effort would be moved directly to Uniroma? BR Pier Da: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: marted? 19 marzo 2013 09:58 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es; fiware-pcc at lists.fi-ware.eu Oggetto: Re: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW Hi all, Please use the new spreadsheet attached to this email instead of the previous one. We have included a new column we ask you to fill with a date from which reporting of costs should be accepted (you only need to fill the white cells in that column). Please respond back to these email with an email with your confirmation/comments together with a version of the spreadsheet with this info about starting date filled regarding WPs you lead. Apologizes for the inconvenience. 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 19/03/13 09:49, Juanjo Hierro wrote: Hi all, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year !). In order to avoid any issue regarding reporting of costs in the 2nd reporting period (2nd year) we will try to get the amendment 4 ready by end of April if not earlier. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. You should check whether the proposed changes for amendment 4 matches your recollection on pending changes. Changes are summarized in the sheet titled "Changes (amendment 4)". Please also check whether you agree with final picture of PMs allocation among tasks of the WP you lead. We believe that the spreadsheet should make it rather easy for you to double-check everything is fine, so we will ask for your confirmation before tomorrow noon. We will send an email to our PO with this summary spreadsheet right afterwards so that he can formally acknowledge the PMs reallocation, despite the official amendment of the DoW may require more time. 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 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 manieri at eng.it Tue Mar 19 11:10:50 2013 From: manieri at eng.it (Andrea Manieri) Date: Tue, 19 Mar 2013 11:10:50 +0100 Subject: [Fiware-wpa] [Fiware-wpl] R: [Fiware-pcc] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <5148382C.2040103@tid.es> References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> <5148382C.2040103@tid.es> Message-ID: <514839AA.1040102@eng.it> Fine with ENG to add UniRoma effort in WP10. A> Il 19/03/2013 11:04, Juanjo Hierro ha scritto: > > This is why we asked for your final confirmation/revision. I don't > find any particular issue with your request regarding the I2ND WP. > We need to check the implications regarding your request in WP10 with > Engineering, leader of that WP. > > 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 19/03/13 10:44, Garino Pierangelo wrote: >> >> Hi Juanjo, >> >> concerning I2ND chapter, a couple of weeks ago I sent you a mail >> proposing to allocate a portion of Ericsson's efforts released in >> I2ND chapter to Uniroma, to cope with the work they would take in >> charge for adoption of the Android Flow Monitoring GE (including the >> possible use of one functionality of this GE for CDI own purposes). >> Moreover, I found that they don't have efforts allocated in the >> Integration WP, which is rather strange as they contribute to develop >> and make available components of two GEs of I2ND chapter. I would >> propose to allocate a (limited) effort on this too. >> >> Can we manage this already at this stage, so that effort would be >> moved directly to Uniroma? >> >> BR >> >> Pier >> >> *Da:*fiware-pcc-bounces at lists.fi-ware.eu >> [mailto:fiware-pcc-bounces at lists.fi-ware.eu] *Per conto di *Juanjo Hierro >> *Inviato:* marted? 19 marzo 2013 09:58 >> *A:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu >> *Cc:* subsidies at tid.es; fiware-pcc at lists.fi-ware.eu >> *Oggetto:* Re: [Fiware-pcc] URGENT: Adjustment of efforts in next >> Amendment of the FI-WARE DoW >> >> Hi all, >> >> Please use the new spreadsheet attached to this email instead of >> the previous one. We have included a new column we ask you to fill >> with a date from which reporting of costs should be accepted (you >> only need to fill the white cells in that column). Please respond >> back to these email with an email with your confirmation/comments >> together with a version of the spreadsheet with this info about >> starting date filled regarding WPs you lead. >> >> Apologizes for the inconvenience. >> >> 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 19/03/13 09:49, Juanjo Hierro wrote: >> >> Hi all, >> >> Once we have finalized amendment 3 of our DoW, we should open a >> new amendment dealing with fixing all PMs reallocation that were >> pending (some of which pending since July last year !). >> >> In order to avoid any issue regarding reporting of costs in the >> 2nd reporting period (2nd year) we will try to get the amendment >> 4 ready by end of April if not earlier. >> >> Please find enclosed a spreadsheet which summarizes the changes >> already implemented in amendment 3 as well as changes proposed in >> amendment 4. You should check whether the proposed changes for >> amendment 4 matches your recollection on pending changes. >> Changes are summarized in the sheet titled "Changes (amendment >> 4)". Please also check whether you agree with final picture of >> PMs allocation among tasks of the WP you lead. >> >> We believe that the spreadsheet should make it rather easy for >> you to double-check everything is fine, so *we will ask for your >> confirmation before tomorrow noon*. >> >> We will send an email to our PO with this summary spreadsheet >> right afterwards so that he can formally acknowledge the PMs >> reallocation, despite the official amendment of the DoW may >> require more time. >> >> 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 >> >> 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'ambienteRispetta l'ambiente. Non stampare questa mail se >> non ? necessario.* >> > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > 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 davide.dallecarbonare at eng.it Tue Mar 19 12:06:18 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 19 Mar 2013 12:06:18 +0100 Subject: [Fiware-wpa] [Fiware-wpl] Monitoring of log/trace files In-Reply-To: <51483069.8040409@tid.es> References: <5135FE2D.3090809@eng.it> <51483069.8040409@tid.es> Message-ID: <514846AA.4070202@eng.it> Dear Juanjo, I can't prepare any presentation before having the questions on the minutes answered. You can find them under the section "Monitoring of log/trace files" > @Juanjo, can you kindly send a feedback on what's your take on the > purpose and technology points reported on the minutes? Thank you, Davide On 19/03/2013 10:31, Juanjo Hierro wrote: > Dear Davide, > > I count you can make us a presentation on this topic during this > afternoon session (part II of the joint WPLs/WPAs follow-up confcall) > > 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/03/13 15:16, Davide Dalle Carbonare wrote: >> Dear partners, >> I'd like to remind you one point we've on the minutes: >> >> "Monitoring of log/trace files" >> >> https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy >> >> @Juanjo, can you kindly send a feedback on what's your take on the >> purpose and technology points reported on the minutes? >> >> @WPAs, can you kindly forward to your GEi providers the request to >> send an example of log/trace files produced by their GE implementations? >> Please send the logs to Marcel Zalmanovici >> and to the WPA mailing list. >> I'm expecting to receive one example per GEi that will be available >> for release 2. >> >> Kind Regards, >> Davide >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 mcp at tid.es Tue Mar 19 12:22:02 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 19 Mar 2013 12:22:02 +0100 Subject: [Fiware-wpa] SW deliverables in April/June In-Reply-To: <513F7B0C.3060405@tid.es> References: <513F77F0.4000304@tid.es> <513F7B0C.3060405@tid.es> Message-ID: <51484A5A.8060008@tid.es> Dear all, Unless I have missed a message (600 messages in my inbox now!), and after a quick search in case there is something related, this is how I see it: * Apps - failed to answer * Cloud - thanks for the info, Alex * Data - thanks for the info, Sergio * IoT - failed to answer * I2ND - failed to answer * Security - failed to answer Take into account that this is a formal commitment of your chapter ... B.R. Miguel El 12/03/2013 19:46, Miguel Carrillo escribi?: Dear all, I was checking with Juanjo your question about what we are expecting to deliver with the software and when. Fortunately for all of us, his answer is 100% aligned with what it was said yesterday 1) The roadmap leaves clear what we will have for April (those with something in R2.2 or R2.1) and what will be left for June (R2.3). The vast majority of the GEs should be delivered in April. After a quick scan through the roadmap I see IoT as the only chapter who leaves most of their GEs for R2.3. The rest of the chapters are complying with the general rule of delivering most of the GEs in April. 2) Delivering software without info makes no sense. Delivering is delivering the whole lot, as usual. * We expect the usual pack in April (for those GEs who deliver in April). This means: * Software * Install and admin manual * User and Programmers manual * Unit test plan and report * In June we will deliver everything. * Those GEs with no change (no backlog items in R2.3) could be be delivered unchanged integrated in the final deliverables. Exceptions: * The GE owner may decide to change something for whatever reason. * The requests from the Use Cases may introduce changes * Those GEs delivered in April but with backlog items in R2.3 will possibly need updating * The new deliverables (those who deliver in R2.3 only) will provide all the sw + the aforementioned documentation pack To avoid confusions I attach an excel spreadsheet with my view of R2. I am using your backlog to reflect what is delivered when so this shouldn't be particularly surprising. AP: all WPA/WPL please confirm in private that this excel file reflects correctly what goes for April and what goes for July. This is a formal commitment to deliver. Also, check that the list is correct and there are no GEs missing or extra GEs. As this is not so urgent, an answer by the end of the week (Fri, 15) should be ok. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ 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: Delivery_roadmap.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 16293 bytes Desc: not available URL: From jhierro at tid.es Tue Mar 19 15:05:17 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 15:05:17 +0100 Subject: [Fiware-wpa] Information about relationship between the date at which software is delivered and the date at which that is software up and running on the FI-WARE Testbed Message-ID: <5148709D.7000807@tid.es> Hi, Just for you reference, here it goes the page on the wiki page where relationship between the date at which software is delivered (through SVN or alternative approach), and the date at which that software is up and running on the FI-WARE Testbed, is explained: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates There, it is said: PLEASE NOTE that software associated to Minor Releases may be made available on the FI-WARE Testbed after completing that Minor Release, typically by the end of the following month. A revised version of the documentation accompanying software delivered after closing a Minor Release is also typically delivered by end of the following month. Hope the relationship is clear. Please share with your teams just in case. 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 manieri at eng.it Tue Mar 19 15:05:00 2013 From: manieri at eng.it (Andrea Manieri) Date: Tue, 19 Mar 2013 15:05:00 +0100 Subject: [Fiware-wpa] [Fiware-wpl] URGENT: Adjustment of efforts in next Amendment of the FI-WARE DoW In-Reply-To: <5148287A.2070708@tid.es> References: <51482688.2070907@tid.es> <5148287A.2070708@tid.es> Message-ID: <5148708C.2070100@eng.it> Dear Juanjo, could you please explain the rational for the reallocation of the full EAB effort in WP9 to UPM, while an internal agreement discussed with Juan Quemada and agreed by WP9 partners was slight different? Thanks in advance for a prompt and formal reply, A. Il 19/03/2013 09:57, Juanjo Hierro ha scritto: > Hi all, > > Please use the new spreadsheet attached to this email instead of the > previous one. We have included a new column we ask you to fill with > a date from which reporting of costs should be accepted (you only need > to fill the white cells in that column). Please respond back to > these email with an email with your confirmation/comments together > with a version of the spreadsheet with this info about starting date > filled regarding WPs you lead. > > Apologizes for the inconvenience. > > 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 19/03/13 09:49, Juanjo Hierro wrote: >> Hi all, >> >> Once we have finalized amendment 3 of our DoW, we should open a new >> amendment dealing with fixing all PMs reallocation that were pending >> (some of which pending since July last year !). >> >> In order to avoid any issue regarding reporting of costs in the 2nd >> reporting period (2nd year) we will try to get the amendment 4 ready >> by end of April if not earlier. >> >> Please find enclosed a spreadsheet which summarizes the changes >> already implemented in amendment 3 as well as changes proposed in >> amendment 4. You should check whether the proposed changes for >> amendment 4 matches your recollection on pending changes. Changes >> are summarized in the sheet titled "Changes (amendment 4)". Please >> also check whether you agree with final picture of PMs allocation >> among tasks of the WP you lead. >> >> We believe that the spreadsheet should make it rather easy for you >> to double-check everything is fine, so *we will ask for your >> confirmation before tomorrow noon*. >> >> We will send an email to our PO with this summary spreadsheet right >> afterwards so that he can formally acknowledge the PMs reallocation, >> despite the official amendment of the DoW may require more time. >> >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Tue Mar 19 19:12:59 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 19 Mar 2013 18:12:59 +0000 Subject: [Fiware-wpa] Deliverable 10.5.1 rejected (was: FW: Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5A3B@DEWDFEMB11A.global.corp.sap> Hi, There might be a valid third option for case 1 (UC requirements) to cater for UC1 projects only 1.III. Take every "Accpeted for inclusion for FIWARE backlog", "Already part of baseline asset" and "Covered by fi-ware backlog entries" ticket out of the DEPRECATED tracker of feature-requests: https://forge.fi-ware.eu/tracker/?atid=163&group_id=7&func=browse - present this list as one part of the validation to the particular UC or all of them. - As attached that would be around 70 tickets As these fields do not exist in the chapter-specific trackers, this can't be applied to the new UCs right? What do you think? Please let me know if this topic gets into the WPL meeting today and when - I have an all-day event, which I can't Best, /Thorsten From: Sandfuchs, Thorsten Sent: Montag, 18. M?rz 2013 08:50 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-testbed at lists.fi-ware.eu Subject: Deliverable 10.5.1 rejected (was: FW: [Fiware-wpa] Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) Dear WPL/WPA, This is to make you all aware and start the discussion on one of the parts of the Review report concerning the validation topic (10.5.X). Status: - D.10.5.1 (validation report) was rejected (as attached below) and they expect a resolved version of the validation report (and major changes) for M24 (already end of April). - Main point from the reviewers: validation report does not met the expectations set by the DoW. 1. UC requirements are not linked to the validation (Personal assumption: ... as these requirements are not fully recorded in the first place, it is almost impossible to resolve this ) 2. Non-functional capabilities are not part of the presented evaluation approach - This can't be resolved on the testbed-level, we have to start the resolution and discussion on the WPL/WPA level My personal opinion to the matter: - The validation process was aligned between the UC and FI-WARE and was part of an official AB-resolution - The requirement matrix can't be established, as we do not have a concise list of requirements by the UCs - For the non-functional capabilities we need to come up with a new approach currently I don't know have a good idea on how to approach this - do you have any other agile processes where non-functional capabilities are part of the validation? Our (quiet obvious) options for 1. (UC requirement links) are: I. Give in to the reviewers and try to intro a link between the "requirements"/"feature"-list and the UC validation (if we take "FEATURES": I personally won't know who would really be able to judge if a feature is really present in a given GE and given the high amount of "FEATURES" in our wikis, this would be a hard job... ) (if we take "requirements": we would firstly need to consolidate and aggregate a list of requirements - who would be able to input here, as the UC projects in phase 1 are probably not responsive any more and the UC2 are just starting ) II. Convince the reviewers that the AB board decision overrules the DoW (potentially and just-to-be-sure: this should be communicated before the next review and potentially clarified with the PO) (potentially this should be reflected in one upcoming amendment of the DoW) III. ... < your options go here > J Our (quiet obvious) options for 2. (non-functional capabilities) are: I. Give in to the reviewers and introduce a new process on how to validate non-functional capabilities of GEs or the platform in a whole (Who can contribute here?) II. ... < your options go here > J Unfortunately I won't be able to join the next WPL/WPA call for long (and iff, only for the first slot) on Tuesday, therefore I would appreciate if you would take the topic in the first slot and make it the first topic. Thanks for any feedback and input and best regards, /Thorsten Attachement: D10.5.1 Report on Validation Process including Validation with Use Case projects This deliverable outlines the designed and recommended validation process for the use cases to follow. Additionally the initial feedback survey, which was initiate and send to the use case projects and the main findings are outlined. The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases. The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. As explained in the document, there is no tight linkage between the defined requirements and the features provided by the GE providers. Hence, the validation and requirements evaluation will not be based on a requirements matrix, but will follow an open questionnaire approach. The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterisation of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. Deliverable D10.5.1 is rejected. No re-submission is required, -- 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: tracker_report-2013-03-19.csv Type: application/octet-stream Size: 52648 bytes Desc: tracker_report-2013-03-19.csv URL: From thorsten.sandfuchs at sap.com Tue Mar 19 19:24:09 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 19 Mar 2013 18:24:09 +0000 Subject: [Fiware-wpa] [Fiware-testbed] Deliverable 10.5.1 rejected (was: FW: Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5A3B@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5A3B@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5BCD@DEWDFEMB11A.global.corp.sap> Ah nice - just discovered that this email didn't get out this morning and got delivered only "now" - so sorry for the delay - content wise it was mentioned in the WPL/WPA meeting. Comments as always still welcome... Best & sorry again for the "late" submission. /Thorsten From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 19. M?rz 2013 19:13 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-testbed at lists.fi-ware.eu Subject: Re: [Fiware-testbed] Deliverable 10.5.1 rejected (was: FW: [Fiware-wpa] Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) Hi, There might be a valid third option for case 1 (UC requirements) to cater for UC1 projects only 1.III. Take every "Accpeted for inclusion for FIWARE backlog", "Already part of baseline asset" and "Covered by fi-ware backlog entries" ticket out of the DEPRECATED tracker of feature-requests: https://forge.fi-ware.eu/tracker/?atid=163&group_id=7&func=browse - present this list as one part of the validation to the particular UC or all of them. - As attached that would be around 70 tickets As these fields do not exist in the chapter-specific trackers, this can't be applied to the new UCs right? What do you think? Please let me know if this topic gets into the WPL meeting today and when - I have an all-day event, which I can't Best, /Thorsten From: Sandfuchs, Thorsten Sent: Montag, 18. M?rz 2013 08:50 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: fiware-testbed at lists.fi-ware.eu Subject: Deliverable 10.5.1 rejected (was: FW: [Fiware-wpa] Fwd: FI-WARE 4th Review meeting: Outcome Letter & Review report) Dear WPL/WPA, This is to make you all aware and start the discussion on one of the parts of the Review report concerning the validation topic (10.5.X). Status: - D.10.5.1 (validation report) was rejected (as attached below) and they expect a resolved version of the validation report (and major changes) for M24 (already end of April). - Main point from the reviewers: validation report does not met the expectations set by the DoW. 1. UC requirements are not linked to the validation (Personal assumption: ... as these requirements are not fully recorded in the first place, it is almost impossible to resolve this ) 2. Non-functional capabilities are not part of the presented evaluation approach - This can't be resolved on the testbed-level, we have to start the resolution and discussion on the WPL/WPA level My personal opinion to the matter: - The validation process was aligned between the UC and FI-WARE and was part of an official AB-resolution - The requirement matrix can't be established, as we do not have a concise list of requirements by the UCs - For the non-functional capabilities we need to come up with a new approach currently I don't know have a good idea on how to approach this - do you have any other agile processes where non-functional capabilities are part of the validation? Our (quiet obvious) options for 1. (UC requirement links) are: I. Give in to the reviewers and try to intro a link between the "requirements"/"feature"-list and the UC validation (if we take "FEATURES": I personally won't know who would really be able to judge if a feature is really present in a given GE and given the high amount of "FEATURES" in our wikis, this would be a hard job... ) (if we take "requirements": we would firstly need to consolidate and aggregate a list of requirements - who would be able to input here, as the UC projects in phase 1 are probably not responsive any more and the UC2 are just starting ) II. Convince the reviewers that the AB board decision overrules the DoW (potentially and just-to-be-sure: this should be communicated before the next review and potentially clarified with the PO) (potentially this should be reflected in one upcoming amendment of the DoW) III. ... < your options go here > :) Our (quiet obvious) options for 2. (non-functional capabilities) are: I. Give in to the reviewers and introduce a new process on how to validate non-functional capabilities of GEs or the platform in a whole (Who can contribute here?) II. ... < your options go here > :) Unfortunately I won't be able to join the next WPL/WPA call for long (and iff, only for the first slot) on Tuesday, therefore I would appreciate if you would take the topic in the first slot and make it the first topic. Thanks for any feedback and input and best regards, /Thorsten Attachement: D10.5.1 Report on Validation Process including Validation with Use Case projects This deliverable outlines the designed and recommended validation process for the use cases to follow. Additionally the initial feedback survey, which was initiate and send to the use case projects and the main findings are outlined. The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases. The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. As explained in the document, there is no tight linkage between the defined requirements and the features provided by the GE providers. Hence, the validation and requirements evaluation will not be based on a requirements matrix, but will follow an open questionnaire approach. The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterisation of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. Deliverable D10.5.1 is rejected. No re-submission is required, -- 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 thorsten.sandfuchs at sap.com Tue Mar 19 19:31:10 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 19 Mar 2013 18:31:10 +0000 Subject: [Fiware-wpa] proposal to change the moderation of fiware-wpl/wpa lists Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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 jhierro at tid.es Tue Mar 19 20:19:38 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Mar 2013 20:19:38 +0100 Subject: [Fiware-wpa] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: <5148BA4A.8000607@tid.es> Dear Thorsten, Thanks for your proactiveness proposing this enhancement. I actually would go for Option 1 ... and the only reason why we haven't set this up was, honestly, because we were not aware how such rules could be configured in mailman (we cannot be experts in everything and certainly we are not that expert in mailman). The only thing I have seen that it was feasible was to configure filters on topics formulated as regular expressions over the keywords and subject headers of messages. However, it is unclear to me how we can use this for the purpose ... can standard header fiels like the from: header field be treated as keyword ? Can you explain us how this could be configured in mailman ? As I have said, we would be more than happy to go for Option 1. It would rather make our life much easier. 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 19/03/13 19:31, Sandfuchs, Thorsten wrote: Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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 andrea.manieri at gmail.com Tue Mar 19 12:15:03 2013 From: andrea.manieri at gmail.com (andrea.manieri at gmail.com) Date: Tue, 19 Mar 2013 11:15:03 +0000 Subject: [Fiware-wpa] R: Re: [Fiware-wpl] Monitoring of log/trace files In-Reply-To: <514846AA.4070202@eng.it> References: <5135FE2D.3090809@eng.it> <51483069.8040409@tid.es> <514846AA.4070202@eng.it> Message-ID: <699313461-1363691893-cardhu_decombobulator_blackberry.rim.net-207849620-@b15.c6.bise7.blackberry> Dear Juanjo, As discussed during the last call, monitoring of logs is usually a testbed owner related task. More, depending on the purpose different type of logs need to be monitored. Lastly, collecting monitoring logs involve the testbed on the server side but also, and most critical, ALL components (i.e. GEs) running in the infra. Then, please, clarify urgently what are the requirements of such logs (system monitoring, security monitoring, compliance monitoring, etc) and then we (ENG as tools or testbeds leader) can provide concrete solutions and suggestions. Br A Andrea Manieri -----Original Message----- From: Davide Dalle Carbonare Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Tue, 19 Mar 2013 12:06:18 To: Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu; Subject: Re: [Fiware-wpl] [Fiware-wpa] Monitoring of log/trace files _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From depa at eng.it Tue Mar 19 21:06:28 2013 From: depa at eng.it (depa at eng.it) Date: Tue, 19 Mar 2013 20:06:28 +0000 Subject: [Fiware-wpa] R: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: <456203962-1363723493-cardhu_decombobulator_blackberry.rim.net-2013116412-@b14.c14.bise7.blackberry> Dear Thorsten, Being the wpl/wpa more a governing body than a free forum i'd prefer option2, while i'll implement option 1 for all the wps mail list. My two cents, Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: "Sandfuchs, Thorsten" Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Tue, 19 Mar 2013 18:31:10 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From stefano.depanfilis at eng.it Wed Mar 20 03:02:16 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 20 Mar 2013 03:02:16 +0100 Subject: [Fiware-wpa] [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA**** > > We would like come forward with a proposal to change the policy on how > mails to the lists fiware-wpl at lists.fi-ware.eu and > fiware-wpa at lists.fi-ware.eu are currently moderated/filtered.**** > > ** ** > > Please indicate if you support this approach or want to object to it and > what option would be your favorite one. Please respond within the next two > weeks (EOB 29.03.) to hopefully implement the changes starting with the > second week of april (8th of april).**** > > ** ** > > Current situation:**** > > **- **All emails of non-members get in a queue of a moderator**** > > **- **The moderator judges by the relevance for ?general > interest? and is denying or allowing the request (in most cases the request > passes this filter and is posted to the list)**** > > ** ** > > Rationale:**** > > **- **The rationale behind this is to have a tight control on > who is able to post on the list *and* to filter spam**** > > ** ** > > New approach:**** > > Option 1: filter & automatically approve emails based on regular > expressions on company level related to FI-PPP members (e.g. @tid.es @ > ibm.com, ?) **** > > Option 2: filter & automatically approve emails based on members > subscribed to the forge (if members has an account-email address, take this > emailaddress as valid poster to the list)**** > > **- **All non-pre-filtered (option 1 or 2) emails will still be > routed to the moderator as is the current situation**** > > **- **New: the moderator should allow *every* ?human? and > obvious ?non-spam? email to pass to the list**** > > ** ** > > New Rational:**** > > **- **The *sole purpose* of the new filter mechanism is now to > filter out *spam* emails by bots**** > > **- **Responsibility on who is posting to the list lies solely > on the poster. The lists are not governed by a moderator from a content > perspective.**** > > **- **We enable more timely emails to the lists by members and > non-members**** > > ** ** > > The new approach of both options is from a technology perspective quite > easy to implement (given standard mailman functionality).**** > > ** ** > > Our recommendation and preferred option: option 1 as it as well lowers > the administrative overhead for the moderator and is the most ?open > communication? encouraging approach.**** > > ** ** > > This initiative is not really related to a particular case, but the > general notion of having emails delayed is to our opinion a potential risk > for the project success. While the effort of filtering spam is highly > appreciated, as it is lowering our burden to process more mails, we > shouldn?t constraint ourselves to much and allow every (human) voice to be > heart on the lists and encourage and support the communication to be as > open as possible.**** > > ** ** > > Thanks for your support & best regards,**** > > ** ** > > **** > > -- **** > > ** ** > > 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-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 Wed Mar 20 09:50:38 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 20 Mar 2013 09:50:38 +0100 Subject: [Fiware-wpa] R: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: Dear All, I do support the proposal by Stefano, to implement filtering both on wpl/wpa mailing lists and on all the other fiware-nnn mailing lists (as spamming has become rather aggressive in the past two-three weeks). I would vote Option 2 for wpl/wpa lists and Option 1 for all the other lists. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di stefano de panfilis Inviato: mercoled? 20 marzo 2013 03:02 A: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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-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 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 davide.dallecarbonare at eng.it Wed Mar 20 09:53:50 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 20 Mar 2013 09:53:50 +0100 Subject: [Fiware-wpa] [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: <5149791E.6040307@eng.it> Dear Thorsten and all, +1 for Stefano's proposal. cheers, Davide On 20/03/2013 03:02, stefano de panfilis wrote: > Dear Thorsten and all, > > Being the wpl/wpa more a governing body than a free forum for > discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd > implement option 1 for all the wps mail list. > > My two cents, > Stefano > > > 2013/3/19 Sandfuchs, Thorsten > > > Dear WPL/WPA > > We would like come forward with a proposalto change the policy on > how mails to the lists fiware-wpl at lists.fi-ware.eu > and > fiware-wpa at lists.fi-ware.eu > are currently moderated/filtered. > > Please indicate if you support this approach or want to object to > it and what option would be your favorite one. Please respond > within the next two weeks (EOB 29.03.) to hopefully implement the > changes starting with the second week of april (8^th of april). > > Current situation: > > -All emails of non-members get in a queue of a moderator > > -The moderator judges by the relevance for "general interest" and > is denying or allowing the request (in most cases the request > passes this filter and is posted to the list) > > Rationale: > > -The rationale behind this is to have a tight control on who is > able to post on the list *and* to filter spam > > New approach: > > Option 1: filter & automatically approve emails based on regular > expressions on company level related to FI-PPP members (e.g. > @tid.es @ibm.com , ...) > > Option 2: filter & automatically approve emails based on members > subscribed to the forge (if members has an account-email address, > take this emailaddress as valid poster to the list) > > -All non-pre-filtered (option 1 or 2) emails will still be routed > to the moderator as is the current situation > > -New: the moderator should allow *every* "human" and obvious > "non-spam" email to pass to the list > > New Rational: > > -The *sole purpose* of the new filter mechanism is now to filter > out *spam* emails by bots > > -Responsibility on who is posting to the list lies solely on the > poster. The lists are not governed by a moderator from a content > perspective. > > -We enable more timely emails to the lists by members and non-members > > The new approach of both options is from a technology perspective > quite easy to implement (given standard mailman functionality). > > Our recommendationand preferred option: option 1 as it as well > lowers the administrative overhead for the moderator and is the > most "open communication" encouraging approach. > > This initiative is not really related to a particular case, but > the general notion of having emails delayed is to our opinion a > potential risk for the project success. While the effort of > filtering spam is highly appreciated, as it is lowering our burden > to process more mails, we shouldn't constraint ourselves to much > and allow every (human) voice to be heart on the listsand > encourage and support the communication to be as open as possible. > > Thanks for your support & best regards, > > -- > > 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-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 mcp at tid.es Wed Mar 20 10:01:23 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 20 Mar 2013 10:01:23 +0100 Subject: [Fiware-wpa] [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <5149791E.6040307@eng.it> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> <5149791E.6040307@eng.it> Message-ID: <51497AE3.4000802@tid.es> Dear all, As I fully trust Thorsten, I take for granted that Option 1 can be implemented without developement (I should contact our support and check once this is decided but I am optimistic) I wonder if Option 2 available without coding effort. The support we have does not provide development. If Option 2 is chosen and we need some development, I guess that SAP can help doing this? Best regards, Miguel El 20/03/2013 9:53, Davide Dalle Carbonare escribi?: Dear Thorsten and all, +1 for Stefano's proposal. cheers, Davide On 20/03/2013 03:02, stefano de panfilis wrote: Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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-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 _______________________________________________ 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 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Wed Mar 20 10:19:46 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 20 Mar 2013 10:19:46 +0100 Subject: [Fiware-wpa] [Fiware-wpl] Shared minutes of today's WPLs/WPAs follow-up confcall In-Reply-To: <51482CC0.5040206@tid.es> References: <51482CC0.5040206@tid.es> Message-ID: <51497F32.2090304@eng.it> Dear Juanjo, I've updated directly on the minutes (at the end of " FI-WARE webinars") the proposed milestones for the training activities (live and recorded sessions). BR Davide On 19/03/2013 10:15, Juanjo Hierro wrote: > Dear colleagues, > > Please find the shared pre-minutes of our joint WPLs/WPAs follow-up > confcall at: > > https://docs.google.com/document/d/15UOA2B7ot6FmNDXT1CmU5j_n9KiLl0BMksiymyhuGUQ/edit?usp=sharing > > > We will handle revision of the M18 review report in the first place > (this should address the request made by Thorsten). Then we will > deal with report on status of the several short-term deliverables. > Discussion on preparation of the Architects Week will most probably > take place in the slot of the afternoon. > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed Mar 20 10:26:30 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Mar 2013 09:26:30 +0000 Subject: [Fiware-wpa] [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <51497AE3.4000802@tid.es> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> <5149791E.6040307@eng.it> <51497AE3.4000802@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB6411@DEWDFEMB11A.global.corp.sap> Dear colleagues, Concerning the "implementation" parts & questions: For option 1: This should technically possible with the ability to apply "non-member filters" on mailman level. Reference: http://www.gnu.org/software/mailman/mailman-admin/node22.html and further Documentation on https://calmail.berkeley.edu/docs/mailman/regexp.html There is a second, process related thing which might be not "implementable". Identifying which company-regular expression applies to which FI-PPP partner. This could be supported by a wiki page, where partners enter their respective emailadresses or company-regular expressions For option 2: Technology wise this is mearly a "larger" list of people with full-qualified names on the non-member filters. Therefore this has as well nothing to do with "implementation": I see only "process related" thing: once you have successfully "allowed" somebody to your forge-project you should take the mentioned emailaddress in the list of non-members filters. SAP could support in compiling an initial list of subscribers to e.g. fiware-part of the forge (but most probably it's even easier for an admin to compile this list, as it is the aggregation of a table of the forge with all the email-addresses, which most probably is a single column in the forge DB) Please let me know, iff needed. Hope this helped, /Thorsten From: Miguel Carrillo [mailto:mcp at tid.es] Sent: Mittwoch, 20. M?rz 2013 10:01 To: Davide Dalle Carbonare Cc: Sandfuchs, Thorsten; stefano de panfilis; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists Dear all, As I fully trust Thorsten, I take for granted that Option 1 can be implemented without developement (I should contact our support and check once this is decided but I am optimistic) I wonder if Option 2 available without coding effort. The support we have does not provide development. If Option 2 is chosen and we need some development, I guess that SAP can help doing this? Best regards, Miguel El 20/03/2013 9:53, Davide Dalle Carbonare escribi?: Dear Thorsten and all, +1 for Stefano's proposal. cheers, Davide On 20/03/2013 03:02, stefano de panfilis wrote: Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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-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 _______________________________________________ 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 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Mar 20 12:17:06 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 20 Mar 2013 12:17:06 +0100 Subject: [Fiware-wpa] Fwd: RE: More on: Question on acceptance of cost as a result of accepting re-submission of rejected deliverables In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06D848EF@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06D848EF@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <51499AB2.7000006@tid.es> Dear all, As you know, I told you that I formulated a question to Arian regarding how cost reports will be managed when re-submitted deliverables are accepted. Please find below the response by Arian. My understanding is that, unless we report a cost for developing a deliverable that is much more than what was initially planned, the costs will be accepted. Regarding how much cost a deliverable was planned, I guess that the EC should rely on information in NEF ... Therefore, I understand we shouldn't expect any bad surprise. Different story, I guess, has to do with deliverables for which re-submission was rejected ... 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: RE: More on: Question on acceptance of cost as a result of accepting re-submission of rejected deliverables Date: Wed, 20 Mar 2013 10:51:42 +0000 From: To: CC: , , Dear Juanjo, Acceptance / rejection decisions about costs will only be made when financial and effort figures are present, so in this case at M24. Regarding (temporarily) rejected costs in reporting period 1, and associated deliverables accepted in the M18 review report, such costs would under normal circumstances be accepted. Circumstances would not be normal if e.g. 3x the amount of efforts were spent on a deliverable than planned, without proper justification. Again, that will only be assessed at M24. Best regards, Arian. -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Tuesday, March 19, 2013 8:23 AM To: ZWEGERS Arian (CNECT) Cc: subsidies at tid.es; Miguel Carrillo; CNECT-ICT-285248 Subject: More on: Question on acceptance of cost as a result of accepting re-submission of rejected deliverables Dear Arian, Partners also want to know what are the implications, regarding assessment of costs, of the rejection of re-submitted deliverables, overall when no re-submission is requested (e.g., re-submission of deliverable D.2.4.1) Thanks in advance, -- 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 19/03/13 07:34, Juanjo Hierro wrote: > Dear Arian, > > Several partners are asking whether it can be assumed that costs > rejected in the 1st reporting period (M12) review report matching > deliverables that have been re-submitted and accepted in the M18 > review will be then accepted in the 2nd reporting period. > > Could you elaborate on what the official rules of FP7 projects state > in this respect ? > > Thanks in advance, > > -- 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 thierry.nagellen at orange.com Wed Mar 20 22:49:05 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 20 Mar 2013 21:49:05 +0000 Subject: [Fiware-wpa] [Fiware-wpl] R: proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> Message-ID: <16304_1363816147_514A2ED3_16304_12803_1_976A65C5A08ADF49B9A8523F7F81925C0BC7E4@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Maybe I miss a point but till now we do not have so many messages from people who are registered on the forge and not in the mailing-lists. So the 2 options should not really change the situation. I have also at least 3 or 4 spams per day in the IoT list, which is not so much but of course requires some additional work. I'm also not an expert in mailman but is it not possible to apply filters on some keywords in the header of the email? If not I prefer to have the same solution for all mailing-list and prefer option 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mercredi 20 mars 2013 09:51 ? : Sandfuchs, Thorsten; stefano de panfilis Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] R: proposal to change the moderation of fiware-wpl/wpa lists Dear All, I do support the proposal by Stefano, to implement filtering both on wpl/wpa mailing lists and on all the other fiware-nnn mailing lists (as spamming has become rather aggressive in the past two-three weeks). I would vote Option 2 for wpl/wpa lists and Option 1 for all the other lists. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di stefano de panfilis Inviato: mercoled? 20 marzo 2013 03:02 A: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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-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 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From mcp at tid.es Wed Mar 20 23:00:56 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 20 Mar 2013 23:00:56 +0100 Subject: [Fiware-wpa] [Fiware-wpl] R: proposal to change the moderation of fiware-wpl/wpa lists In-Reply-To: <16304_1363816147_514A2ED3_16304_12803_1_976A65C5A08ADF49B9A8523F7F81925C0BC7E4@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB5C3A@DEWDFEMB11A.global.corp.sap> <16304_1363816147_514A2ED3_16304_12803_1_976A65C5A08ADF49B9A8523F7F81925C0BC7E4@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <514A3198.7090203@tid.es> Dear Thierry, dear all, As regards spam. Good news. I've got a feeling that the new solution would not delete spam messages, it would just hold them (as it does now). The difference is that all the messages from "known" people would make it through and not get moderated. The drawback is that anyone in the consortium could break in in any list (but people seem happy with this) I have being discussing the spam problem with our administrator for weeks and he managed to come up with something just today. Thierry complains about one list, I manage tens, so you can imagine how long it takes every day. The good news is that this morning our administrator has included several changes in the configuration of our Postifx mail server in order to reject the wide majority of unwanted incoming "junk email". The changes included add more restrictions that the Postfix SMTP server applies in the context of a client. We are not taking into account the content of the emails yet, we are avoiding mails from servers that misbehave (that don't follow the standard). If the result is not a drastic reduction of spam, the next action is to add applications that parse the content of emails and mark them as SPAM or even drop them. Best regards, Miguel El 20/03/2013 22:49, thierry.nagellen at orange.com escribi?: Dear all, Maybe I miss a point but till now we do not have so many messages from people who are registered on the forge and not in the mailing-lists. So the 2 options should not really change the situation. I have also at least 3 or 4 spams per day in the IoT list, which is not so much but of course requires some additional work. I'm also not an expert in mailman but is it not possible to apply filters on some keywords in the header of the email? If not I prefer to have the same solution for all mailing-list and prefer option 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mercredi 20 mars 2013 09:51 ? : Sandfuchs, Thorsten; stefano de panfilis Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] R: proposal to change the moderation of fiware-wpl/wpa lists Dear All, I do support the proposal by Stefano, to implement filtering both on wpl/wpa mailing lists and on all the other fiware-nnn mailing lists (as spamming has become rather aggressive in the past two-three weeks). I would vote Option 2 for wpl/wpa lists and Option 1 for all the other lists. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di stefano de panfilis Inviato: mercoled? 20 marzo 2013 03:02 A: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] proposal to change the moderation of fiware-wpl/wpa lists Dear Thorsten and all, Being the wpl/wpa more a governing body than a free forum for discussion i'd prefer option 2 for the wpl/wpa mail list, while i'd implement option 1 for all the wps mail list. My two cents, Stefano 2013/3/19 Sandfuchs, Thorsten > Dear WPL/WPA We would like come forward with a proposal to change the policy on how mails to the lists fiware-wpl at lists.fi-ware.eu and fiware-wpa at lists.fi-ware.eu are currently moderated/filtered. Please indicate if you support this approach or want to object to it and what option would be your favorite one. Please respond within the next two weeks (EOB 29.03.) to hopefully implement the changes starting with the second week of april (8th of april). Current situation: - All emails of non-members get in a queue of a moderator - The moderator judges by the relevance for "general interest" and is denying or allowing the request (in most cases the request passes this filter and is posted to the list) Rationale: - The rationale behind this is to have a tight control on who is able to post on the list and to filter spam New approach: Option 1: filter & automatically approve emails based on regular expressions on company level related to FI-PPP members (e.g. @tid.es @ibm.com, ...) Option 2: filter & automatically approve emails based on members subscribed to the forge (if members has an account-email address, take this emailaddress as valid poster to the list) - All non-pre-filtered (option 1 or 2) emails will still be routed to the moderator as is the current situation - New: the moderator should allow every "human" and obvious "non-spam" email to pass to the list New Rational: - The sole purpose of the new filter mechanism is now to filter out spam emails by bots - Responsibility on who is posting to the list lies solely on the poster. The lists are not governed by a moderator from a content perspective. - We enable more timely emails to the lists by members and non-members The new approach of both options is from a technology perspective quite easy to implement (given standard mailman functionality). Our recommendation and preferred option: option 1 as it as well lowers the administrative overhead for the moderator and is the most "open communication" encouraging approach. This initiative is not really related to a particular case, but the general notion of having emails delayed is to our opinion a potential risk for the project success. While the effort of filtering spam is highly appreciated, as it is lowering our burden to process more mails, we shouldn't constraint ourselves to much and allow every (human) voice to be heart on the lists and encourage and support the communication to be as open as possible. Thanks for your support & best regards, -- 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-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 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-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 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Thu Mar 21 07:56:51 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 21 Mar 2013 06:56:51 +0000 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [cid:image001.jpg at 01CE25C3.6B143560] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 71929 bytes Desc: image001.jpg URL: From jhierro at tid.es Thu Mar 21 08:32:28 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 21 Mar 2013 08:32:28 +0100 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> Message-ID: <514AB78C.4030102@tid.es> Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [mailbox:///Users/jhierro/Mail/correo.tid.es/Inbox?number=1257296033&header=quotebody&part=1.1.2&filename=image001.jpg] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. _______________________________________________ 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: 71929 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Thu Mar 21 08:50:35 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 21 Mar 2013 07:50:35 +0000 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <514AB78C.4030102@tid.es> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> <514AB78C.4030102@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FC4609@DEWDFEMB11A.global.corp.sap> Hi Juanjo, thanks for the comments. The initial list of GEs was compiled from the table "FI-WARE testbed planned usage"-Table - back then I can assure you that the listed GEs were part of this table - but our disclaimer was always: please change at your will if we got something wrong :) 1. The backend/local distinction has been tried with the dotted boxes (infrastructure and onpremise) - sorry the "Legend" is not part of the picture I had in the mail: a. Large grey boxes: main chapters b. Large grey boxes (dotted lines): FI-WARE external c. White boxes: GEs provide d. White boxes (dashed lines): components which are not part of FI-WARE, but do interact with GEs (in most cases they are present as chapter-architecture diagrams did reference them) e. Dark grey boxes: GEs of release 2 (as initially known by the "planned usage" matrix In general the components were "roughly" (as good as possible) ordered towards the boxes they interact with. E.g. ProtocolAdapter of IoT interacts with Infrastructure. 2. As back in the matrix I2ND was only present with the "cloud proxy" (which was as well part of "Cloud" and didn't provide another GE, there was not need for a separate "box" and the proxy got part of the cloud box - this holds true for the second release as well obviously - at least if you count this table. 3. "Premise on the level of infrastructure" - We think as well that they are needed in the diagram but where else would you position them? Positioning them :) Best, /Thorsten Reference: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=4 From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 21. M?rz 2013 08:32 To: Sandfuchs, Thorsten Cc: thierry.nagellen at orange.com; Alex Glikson; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [mailbox:///Users/jhierro/Mail/correo.tid.es/Inbox?number=1257296033&header=quotebody&part=1.1.2&filename=image001.jpg] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. _______________________________________________ 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: 71929 bytes Desc: image001.jpg URL: From pierangelo.garino at telecomitalia.it Thu Mar 21 08:57:43 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 21 Mar 2013 08:57:43 +0100 Subject: [Fiware-wpa] R: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <514AB78C.4030102@tid.es> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> <514AB78C.4030102@tid.es> Message-ID: Dear All, I share the opinion by Juanjo concerning the inclusion of I2ND GEs in the diagram: although I was not very active so far on this topic due to absolute lack of time, I started investigating how the GEs of this chapter could be inserted in the overall picture, which is not always easy if the result needs to be 'clear and compact'. The distinction between backend and local GEs, as well as the access devices, would be also an important 'message' to be conveyed through the diagram. I'll try as well to make some proposal with an I2ND update on the diagram, hopefully by today EOB, but most probably tomorrow morning. 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? 21 marzo 2013 08:32 A: Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten [cid:image001.jpg at 01CE2612.268B6720] -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. _______________________________________________ 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 71929 bytes Desc: image001.jpg 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 Thu Mar 21 10:09:41 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 21 Mar 2013 10:09:41 +0100 Subject: [Fiware-wpa] Final check regarding PMs/funding reallocation in FI-WARE to be implemented in amendment 4 of the DoW Message-ID: <514ACE55.10502@tid.es> Hi all, First of all thanks very much for your responses to our request to verify the spreadsheet summarizing the PMs reallocation to be implemented in amendment 4 of the FI-WARE contract. Please find enclosed the final spreadsheet where we believe that, to the best of our knowledge, we have implemented all the comments we have received from you. We will send it to our PO this afternoon, right after our PCC confcall unless objections are raised. Please take your time to make a final 5-minute check that everything is ok. If you reply to this message, please don't forget to add subsidies at tid.es in copy Thanks and 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE effort-budget-funding - Amendment 4 v27.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 257997 bytes Desc: not available URL: From manieri at eng.it Thu Mar 21 11:13:34 2013 From: manieri at eng.it (Andrea Manieri) Date: Thu, 21 Mar 2013 11:13:34 +0100 Subject: [Fiware-wpa] [Fiware] Final check regarding PMs/funding reallocation in FI-WARE to be implemented in amendment 4 of the DoW In-Reply-To: <514ACE55.10502@tid.es> References: <514ACE55.10502@tid.es> Message-ID: <514ADD4E.8040106@eng.it> Dear Juanjo, the reallocation foreseen in the spreedsheet is ok for ENG (either in WP9 and WP10). thanks A. Il 21/03/2013 10:09, Juanjo Hierro ha scritto: > Hi all, > > First of all thanks very much for your responses to our request to > verify the spreadsheet summarizing the PMs reallocation to be > implemented in amendment 4 of the FI-WARE contract. > > Please find enclosed the final spreadsheet where we believe that, to > the best of our knowledge, we have implemented all the comments we have > received from you. > > We will send it to our PO this afternoon, right after our PCC > confcall unless objections are raised. Please take your time to make a > final 5-minute check that everything is ok. > > If you reply to this message, please don't forget to add > subsidies at tid.es in copy > > Thanks and 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 mailing list > Fiware at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu Mar 21 12:11:44 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 21 Mar 2013 12:11:44 +0100 Subject: [Fiware-wpa] Reminder: start of rehearsal on June , 10 ( 11:00 am ) Message-ID: <514AEAF0.8050105@tid.es> Dear all, Although mentioned on the minutes of meeting, it is worth reminding that we will start the review rehearsal on Monday, the 10th of June at 11:00am and will take us 2 days. The venue will be circulated once it is confirmed (we will try to get the usual meeting room) Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail:mcp at tid.es Follow FI-WARE on the net Website:http://www.fi-ware.eu Facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter:http://twitter.com/Fiware LinkedIn:http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Thu Mar 21 23:53:37 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 21 Mar 2013 23:53:37 +0100 Subject: [Fiware-wpa] Fwd: RE: Future Internet PPP Call 2 Negotiations - Common texts/content In-Reply-To: <59812FF1E287AD4497054F3D2B92B26A03917406@S-DC-ESTH04-B.net1.cec.eu.int> References: <59812FF1E287AD4497054F3D2B92B26A03917406@S-DC-ESTH04-B.net1.cec.eu.int> Message-ID: <514B8F71.2000808@tid.es> Version 7 of the new FI-PPP governance model, this time officially from the EC. 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: RE: Future Internet PPP Call 2 Negotiations - Common texts/content Date: Thu, 21 Mar 2013 16:57:19 +0000 From: To: , , , , , CC: , , , , , , , , Dear Project Co-ordinator of a FI-PPP phase II proposal, Further to the revision of the "FI-PPP Management Organisation Model" we hereby confirm that the attached text (version 7) should be included in your DoW, instead of version 6 as indicated in the previous e-mail. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom at ec.europa.eu _____________________________________________ From: BERGSTROM Ragnar (CNECT) Sent: Tuesday, March 12, 2013 5:36 PM To: 'maurizio.cecchi at telecomitalia.it'; 'Anastasius Gavras'; 'pieter.vanderlinden at technicolor.com'; 'fiona.williams at ericsson.com'; 'sjaak.wolfert at wur.nl'; 'sergio.gusmeroli at txtgroup.com' Cc: 'jimenez at tid.es'; 'jhierro at tid.es'; 'Turkama Petra (petra.turkama at aalto.fi)'; ilkka.lakaniemi at aalto.fi; ''Federico Alvarez' (federico.alvarez at upm.es)'; FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT); ANTON GARCIA Maria Concepcion (CNECT); VILLASANTE Jesus (CNECT) Subject: Future Internet PPP Call 2 Negotiations - Common texts/content Dear Project Co-ordinator of a FI-PPP phase II proposal, As confirmed in our e-mail following the "Future Internet PPP Call 2 Negotiation Workshop, Brussels, 4/5 February 2013", here is the additional information regarding common texts/content for inclusion in your Description of Work (DoW). 1) FI-PPP Governance The attached FI-PPP Management Organisation Model text should be included in your DoW. It corresponds to the version 6 of the document that was already circulated to you previously. << File: FI PPP Governance Model_20130312.docx >> 2) Key Performance Indicators (KPIs) CONCORD made a presentation (attached) on the FI-PPP KPI framework at the workshop. << File: Proposed FI PPP-Programme-level KPIs.ppt >> 2a) Project-level: You should include the relevant project-level KPIs from this presentation in your DoW. (NB. It is of course expected that you also include other KPIs that are specific to your project). 2b) Programme-level: Note that CONCORD will establish an evaluation process for the programme-level KPIs and you should therefore ensure that the relevant programme level KPIs and their measuring are foreseen in your DoW, so that your project can contribute accordingly to CONCORD and meet the programme-level objectives. 3) FI-PPP programme communications In addition to your participation in the "Communication and Dissemination Working Group" your DoW's list of dissemination events/activities should include the yearly FI-PPP programme-level event that, as agreed in the workshop, should in principle take place in March 2014 and March 2015. (Venue and exact date will be defined by the working group later). 4) Resources for programme level activities You must explicitly allocate financial and human resources to fulfil your role at the FI-PPP programme level. We request each project to budget for a minimum of 24 person-months per year and 150.000 EURO for the total project duration for FI-PPP programme activities. Finally, when it comes to "Openness and cooperation beyond the FI-PPP" we have already presented this and circulated information about it. We expect this dimension to be fully represented in your DoW. We would like to kindly ask you to implement these actions in your Description of Work and bring the negotiations to a swift close as the formal deadline of 28 February has passed. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom at ec.europa.eu _____________________________________________ From: BERGSTROM Ragnar (CNECT) Sent: Wednesday, February 20, 2013 7:30 PM To: maurizio.cecchi at telecomitalia.it; Anastasius Gavras; pieter.vanderlinden at technicolor.com; fiona.williams at ericsson.com; sjaak.wolfert at wur.nl; sergio.gusmeroli at txtgroup.com Cc: jimenez at tid.es; jhierro at tid.es; Turkama Petra (petra.turkama at aalto.fi); ilkka.lakaniemi at aalto.fi; 'Federico Alvarez' (federico.alvarez at upm.es); FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT); ANTON GARCIA Maria Concepcion (CNECT); VILLASANTE Jesus (CNECT) Subject: Future Internet PPP Call 2 Negotiation Workshop, Brussels, 4/5 February 2013 - Follow-up Dear Project Co-ordinator of FI-PPP phase II proposal, We would like to thank you and all the project representatives for the active contributions during the workshop. During the finalisation of the FI-PPP Call 2 projects' negotiations we are focusing on the commitment towards the FI-PPP Programme success and strong collaboration implemented by the following actions: * New governance structure reflected by a common text in the DoW. * Quantitative KPIs (notably on the usage of the GEs and the trials): not only for Use Case Trial projects (UC) but also for FI-WARE, XIFI and Concord. KPIs on the external view of the PPP (e.g. success stories) should also be included. * Explicit identification of the GEs that UCs will / intend to use + a validation strategy. * Milestones: * M6: discussion of the architecture approaches of the different UCs vis-?-vis FI-WARE and XIFI --> see draft standard text below. * M6 (at the latest): Information from phase 2 projects about what phase 3 projects may use, a full description, and under what conditions (both inside and outside the PPP). * M6: UCs to provide requirements on infrastructure needs, to be consolidated by XIFI in M6. This does not have to be a UC deliverable per se, but at least the commitment to give this input must be stated. * M15: availability of platforms. The UCs should be aligned along a M15 milestone. --> Concord to make a first draft of a PPP wide GANTT chart reflecting this. * Common articulated approach on FI-PPP programme communications. * Openness and cooperation beyond the FI-PPP reflected by a common text in DoW. * All projects must allocate explicitly financial and human resources to fulfil their roles at the FI-PPP programme level: Governance, management, communications, etc. Amounts for the costs, as well as person-months. * There should be clear Terms & Conditions for usage of GEs and specific enablers with specific deliverables at month 6 and month 15 (within and beyond the FI-PPP). * Public deliverables on Commission websites: --> see standard text below. * Kick-off meetings should be announced to EC and include presentation on the FI-PPP Programme dimension (EC to present when possible). FI-WARE should also be invited to present its role within the FI-PPP. * Participation in FI-PPP Phase 2 Architecture Week. Elements of draft standard texts for DoW, in addition to the ones already provided in relation to the workshop: 1. "The project aims to use the Generic Enablers (and Specific Enablers) in the list / picture below. A draft architecture including Generic Enablers and Specific Enablers will be defined at month X (latest: M6). This architecture will be discussed within the Architecture Board with FI-WARE and XIFI, and suggestions by FI-WARE and XIFI architects will be taken into account for the specification of a revised architecture at month Y." 2. "Deliverables marked as ?public (PU)? in the Dissemination Level column in the Deliverable List table above will be made available to the general public via the project?s web site, within a month after their formal approval in a review report. The deliverables will include a copyright notice. Upon request by the Commission, public deliverables will be made available to the Commission for publication on a Commission web site, with a copyright notice as indicated by the consortium. Such deliverables will be made available to the Commission in a publishable format." The European Commission services will provide the common texts on: * The new governance structure, * The programme related KPIs, * Openness and cooperation towards other initiatives. We would like to kindly ask you to implement these actions in your Description of Work. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom 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: FI PPP Governance Model_20130321.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 282459 bytes Desc: not available URL: From jhierro at tid.es Thu Mar 21 23:56:46 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 21 Mar 2013 23:56:46 +0100 Subject: [Fiware-wpa] Fwd: Re: Future Internet PPP Call 2 Negotiations - Common texts/content In-Reply-To: <514B8ED8.5010504@tid.es> References: <514B8ED8.5010504@tid.es> Message-ID: <514B902E.1050109@tid.es> Dear partners, As agreed, we have communicated to the EC that it's ok to include contents of the version 7 of the governance model in a next amendment of the FI-WARE DoW. 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: Re: Future Internet PPP Call 2 Negotiations - Common texts/content Date: Thu, 21 Mar 2013 23:51:04 +0100 From: Juanjo Hierro To: Ragnar.Bergstrom at ec.europa.eu CC: Peter.Fatelnig at ec.europa.eu, Arian.ZWEGERS at ec.europa.eu, Maria-Concepcion.ANTON-GARCIA at ec.europa.eu, Jesus.Villasante at ec.europa.eu, "fiware-pcc at lists.fi-ware.eu" Dear Ragnar and members of the Commission, FI-WARE agrees to incorporate text of version 7 of the FI-PPP Governance Model in a next amendment of the DoW. 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 21/03/13 17:57, Ragnar.Bergstrom at ec.europa.eu wrote: Dear Project Co-ordinator of a FI-PPP phase II proposal, Further to the revision of the "FI-PPP Management Organisation Model" we hereby confirm that the attached text (version 7) should be included in your DoW, instead of version 6 as indicated in the previous e-mail. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom at ec.europa.eu _____________________________________________ From: BERGSTROM Ragnar (CNECT) Sent: Tuesday, March 12, 2013 5:36 PM To: 'maurizio.cecchi at telecomitalia.it'; 'Anastasius Gavras'; 'pieter.vanderlinden at technicolor.com'; 'fiona.williams at ericsson.com'; 'sjaak.wolfert at wur.nl'; 'sergio.gusmeroli at txtgroup.com' Cc: 'jimenez at tid.es'; 'jhierro at tid.es'; 'Turkama Petra (petra.turkama at aalto.fi)'; ilkka.lakaniemi at aalto.fi; ''Federico Alvarez' (federico.alvarez at upm.es)'; FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT); ANTON GARCIA Maria Concepcion (CNECT); VILLASANTE Jesus (CNECT) Subject: Future Internet PPP Call 2 Negotiations - Common texts/content Dear Project Co-ordinator of a FI-PPP phase II proposal, As confirmed in our e-mail following the "Future Internet PPP Call 2 Negotiation Workshop, Brussels, 4/5 February 2013", here is the additional information regarding common texts/content for inclusion in your Description of Work (DoW). 1) FI-PPP Governance The attached FI-PPP Management Organisation Model text should be included in your DoW. It corresponds to the version 6 of the document that was already circulated to you previously. << File: FI PPP Governance Model_20130312.docx >> 2) Key Performance Indicators (KPIs) CONCORD made a presentation (attached) on the FI-PPP KPI framework at the workshop. << File: Proposed FI PPP-Programme-level KPIs.ppt >> 2a) Project-level: You should include the relevant project-level KPIs from this presentation in your DoW. (NB. It is of course expected that you also include other KPIs that are specific to your project). 2b) Programme-level: Note that CONCORD will establish an evaluation process for the programme-level KPIs and you should therefore ensure that the relevant programme level KPIs and their measuring are foreseen in your DoW, so that your project can contribute accordingly to CONCORD and meet the programme-level objectives. 3) FI-PPP programme communications In addition to your participation in the "Communication and Dissemination Working Group" your DoW's list of dissemination events/activities should include the yearly FI-PPP programme-level event that, as agreed in the workshop, should in principle take place in March 2014 and March 2015. (Venue and exact date will be defined by the working group later). 4) Resources for programme level activities You must explicitly allocate financial and human resources to fulfil your role at the FI-PPP programme level. We request each project to budget for a minimum of 24 person-months per year and 150.000 EURO for the total project duration for FI-PPP programme activities. Finally, when it comes to "Openness and cooperation beyond the FI-PPP" we have already presented this and circulated information about it. We expect this dimension to be fully represented in your DoW. We would like to kindly ask you to implement these actions in your Description of Work and bring the negotiations to a swift close as the formal deadline of 28 February has passed. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom at ec.europa.eu _____________________________________________ From: BERGSTROM Ragnar (CNECT) Sent: Wednesday, February 20, 2013 7:30 PM To: maurizio.cecchi at telecomitalia.it; Anastasius Gavras; pieter.vanderlinden at technicolor.com; fiona.williams at ericsson.com; sjaak.wolfert at wur.nl; sergio.gusmeroli at txtgroup.com Cc: jimenez at tid.es; jhierro at tid.es; Turkama Petra (petra.turkama at aalto.fi); ilkka.lakaniemi at aalto.fi; 'Federico Alvarez' (federico.alvarez at upm.es); FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT); ANTON GARCIA Maria Concepcion (CNECT); VILLASANTE Jesus (CNECT) Subject: Future Internet PPP Call 2 Negotiation Workshop, Brussels, 4/5 February 2013 - Follow-up Dear Project Co-ordinator of FI-PPP phase II proposal, We would like to thank you and all the project representatives for the active contributions during the workshop. During the finalisation of the FI-PPP Call 2 projects' negotiations we are focusing on the commitment towards the FI-PPP Programme success and strong collaboration implemented by the following actions: * New governance structure reflected by a common text in the DoW. * Quantitative KPIs (notably on the usage of the GEs and the trials): not only for Use Case Trial projects (UC) but also for FI-WARE, XIFI and Concord. KPIs on the external view of the PPP (e.g. success stories) should also be included. * Explicit identification of the GEs that UCs will / intend to use + a validation strategy. * Milestones: * M6: discussion of the architecture approaches of the different UCs vis-?-vis FI-WARE and XIFI --> see draft standard text below. * M6 (at the latest): Information from phase 2 projects about what phase 3 projects may use, a full description, and under what conditions (both inside and outside the PPP). * M6: UCs to provide requirements on infrastructure needs, to be consolidated by XIFI in M6. This does not have to be a UC deliverable per se, but at least the commitment to give this input must be stated. * M15: availability of platforms. The UCs should be aligned along a M15 milestone. --> Concord to make a first draft of a PPP wide GANTT chart reflecting this. * Common articulated approach on FI-PPP programme communications. * Openness and cooperation beyond the FI-PPP reflected by a common text in DoW. * All projects must allocate explicitly financial and human resources to fulfil their roles at the FI-PPP programme level: Governance, management, communications, etc. Amounts for the costs, as well as person-months. * There should be clear Terms & Conditions for usage of GEs and specific enablers with specific deliverables at month 6 and month 15 (within and beyond the FI-PPP). * Public deliverables on Commission websites: --> see standard text below. * Kick-off meetings should be announced to EC and include presentation on the FI-PPP Programme dimension (EC to present when possible). FI-WARE should also be invited to present its role within the FI-PPP. * Participation in FI-PPP Phase 2 Architecture Week. Elements of draft standard texts for DoW, in addition to the ones already provided in relation to the workshop: 1. "The project aims to use the Generic Enablers (and Specific Enablers) in the list / picture below. A draft architecture including Generic Enablers and Specific Enablers will be defined at month X (latest: M6). This architecture will be discussed within the Architecture Board with FI-WARE and XIFI, and suggestions by FI-WARE and XIFI architects will be taken into account for the specification of a revised architecture at month Y." 2. "Deliverables marked as ?public (PU)? in the Dissemination Level column in the Deliverable List table above will be made available to the general public via the project?s web site, within a month after their formal approval in a review report. The deliverables will include a copyright notice. Upon request by the Commission, public deliverables will be made available to the Commission for publication on a Commission web site, with a copyright notice as indicated by the consortium. Such deliverables will be made available to the Commission in a publishable format." The European Commission services will provide the common texts on: * The new governance structure, * The programme related KPIs, * Openness and cooperation towards other initiatives. We would like to kindly ask you to implement these actions in your Description of Work. Kind regards, On behalf of the EC FI-PPP team, Ragnar Bergstr?m Project Officer __________________________ EUROPEAN COMMISSION DG for Communications Networks, Content and Technology Unit E3 - Net Innovation Office BU25 3/104, B-1049 Bruxelles Tel: +32(0)2.295.64.15 e-mail: ragnar.bergstrom 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: From mcp at tid.es Fri Mar 22 01:01:31 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 22 Mar 2013 01:01:31 +0100 Subject: [Fiware-wpa] Fwd: Submission of deliverable D2.4.2 FI-WARE Technical Roadmap In-Reply-To: <514B9E09.3070008@tid.es> References: <514B9E09.3070008@tid.es> Message-ID: <514B9F5B.1020702@tid.es> FYI Thanks to all contributors! Miguel -------- Mensaje original -------- Asunto: Submission of deliverable D2.4.2 FI-WARE Technical Roadmap Fecha: Fri, 22 Mar 2013 00:55:53 +0100 De: Miguel Carrillo Para: Arian.ZWEGERS at ec.europa.eu , Vanessa.VANHUMBEECK at ec.europa.eu CC: JUAN JOSE HIERRO SUREDA , "INFSO-ICT-285248 at ec.europa.eu" Dear Arian, dear Vanessa, This is the official submission of the following deliverable: * D2.4.2 FI-WARE Technical Roadmap The deliverable is attached to this message and also publicly available on * https://forge.fi-ware.eu/docman/view.php/7/1984/D.2.4.b_FI-WARE+Technical+Roadmap.pdf The deliverable is available on the FI-WARE wiki as well(http://wiki.fi-ware.eu/FI-WARE_Technical_Roadmap) where we keep it constantly updated. If you have any queries we would be pleased to help. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.4.b_FI-WARE Technical Roadmap.pdf Type: application/pdf Size: 2850512 bytes Desc: not available URL: From jhierro at tid.es Fri Mar 22 14:07:11 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 22 Mar 2013 14:07:11 +0100 Subject: [Fiware-wpa] Fwd: Agenda of the FI-PPP Architects Week In-Reply-To: <514C278D.3050306@tid.es> References: <514C278D.3050306@tid.es> Message-ID: <514C577F.5030800@tid.es> FYI, the agenda of the FI-PPP Architects Week. Please take care of the particular parts of the presentations you have to cover during the first two days: * WP10 (Testbed) team: prepare the presentation on "FI-WARE Testbed" planned on April 2, from 14:30 to 15:00 * Be pragmatic, focus on how to get access to the testbed, how to create accounts, gain access, etc * You don't need to go into the details about Cloud capabilities because they will described on April 3 * WP9 (Tools) team: prepare presentation regarding "FI-WARE Training" planned on April 2, from 15:00 to 15:30 * Give a view on how we plan the training sessions (live webinars, recording sessions, etc). I understand we cannot be too precise here, because it is work still under development, but I guess it would be nice to explain the approach and the goals we are looking for * Explain when we plan the live webinars to take place and how we will organize subscription to the webinars. We can discuss this off-line, but I would go for a similar approach to the one followed for the webinars of the 1st Release of FI-WARE. * WP10 (Testbed) team, SAP: prepare the presentation on "FI-WARE validation by UC projects": * Explain the current validation process (including rationale: we agreed in the AB not to make this a heavy-duty process) * Call for feedback from new UC projects about enhancements they may believe would be nice to introduce in the process * All WPLs: I understand that everything is clear regarding assignment of responsibilites for the items in the agenda of the second day. Please also take a look to the notes that were inserted in the minutes of our last WPLs/WPAs confcall where I provided some more details/insights. Hope this all helps to start rolling-out the ball. I will be on holidays next week but will connect from time (although I'll be in NY and therefore there will be 6 hours of difference). Let's keep the discussion open during these days. The regular monday WPLs/WPAs follow-up confcall next monday March 25 will take place and Miguel will chair it. 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: Agenda of the FI-PPP Architects Week Date: Fri, 22 Mar 2013 10:42:37 +0100 From: Juanjo Hierro To: Lakaniemi Ilkka , Cecchi Maurizio , Sjaak Wolfert , Williams Fiona , Fourdeaux Henri , "rod.franklin at kuehne-nagel.com" , "sergio.gusmeroli at txtgroup.com" , Christoph Thuemmler , Van Der Linden Pieter , Anastasius Gavras CC: Fatelnig Peter , "Arian.ZWEGERS at ec.europa.eu" , "Ragnar.Bergstrom at ec.europa.eu" , "Maria-Concepcion.ANTON-GARCIA at ec.europa.eu" , David Kennedy , "FI-PPP-Phase-2-Contacts at future-internet.eu" , Turkama Petra , Salo Juha , Schaffers Hans , Thomas Michael Bohnert , "jhierro >> \"Juan J. Hierro\"" Dear all, You can find a draft agenda of the FI-PPP Architects Week at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdE4teWs4UEpZa29zd0FRUmNTaFdxT2c&usp=sharing Thanks to Thomas M. Bohnert for his feedback and help finalizing it. We would like to hear your input, regarding what is the day where we can co-llocate the workshop dealing with your UC Trial project. Based on an initial request, we have placed cSpace in the workshop colocated in April 3. Please send your proposals to Thomas and me so that we can come with a final proposal. Please take into account that we have to meet a compromise, so we hope you can trust we will make a reasonable proposal. We may come back to you with more details about what info we are asking you to provide in the workshops dedicated to UC projects. We are discussing with Xifi what can be specific requests about info we would love to hear from you. 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 14/03/13 06:57, Juanjo Hierro wrote: Dear all, This mail is to announce that the FI-PPP Architecture Week for Phase 2 will take place in the following venue: Aula Magna in Building "A" School of Telecommunication Engineering (ETS Ingenieros de Telecomunicacion - ETSIT) Avenida Complutense # 30 University City 28040 Madrid Directions and hotels close to the venue can be found at: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/como-llegar.html%3FL%3Dttqltguphtgolkug&usg=ALkJrhi775kjxa4XFzatOQMya9dkNbh5wg Maps of the buildings associated to the ETSIT: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/etsi-de-telecomunicacion/etsit-edificios.html&usg=ALkJrhi0WiJVR4jcJKDRa0prunRkZbTCig We had received many request to allow more than two people attending on behalf of phase 2 projects to the Architecture Week that will take place in Madrid, during April 2-5, that's why we have been late announcing the venue. Actually, the original venues were at a different location, but the meeting room was limited to 28-30 people maximum. Please note that coffee and lunch breaks will be scheduled during the week, but each attendee has to cover its own expenses. There is a restaurant and coffee bar in the same building of the venue with convenient prices. Note also that it might take a while to go from the University to the Airport, first walking to the metro stop "Ciudad Universitaria" (aprox. 1 Km) and then taking the metro to the Airport (you should take line 6 until "Nuevos Ministerios" and then line 8). You should take this into consideration when arranging the time of your return fligths on Friday. I will come later this week with a more detailed agenda, but the one already sent to you (see mail below) should be enough as far as logistics is concerned. 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 20/02/13 05:01, Lakaniemi Ilkka wrote: Dear all, As indicated yesterday, please find more detailed info about the FI-PPP Architecture Week on 2-5 April in Madrid. For any further details and info, please be in touch with Juanjo, Thomas B and me. The agenda of this meeting (draft): * April 2 (starting at 11:00am): FI-WARE to provide a thorough introduction on FI-WARE scope, goals, basic concepts, methodology, planning, available documentation, resources, tools, etc as well as a detailed description of the way the FI-PPP AB works. * April 3 morning: FI-WARE to provide detailed info about the FI-WARE Second Release, training planning, etc. * April 3 afternoon until April 5 17:00 CET: sequence of half-days workshops per UC Trial projects where UC Trials will present a sketch of their envisioned architecture, their current plans regarding usage of FI-WARE GEs, needs regarding setup of their trials, questions on which they need responses, etc. FI-WARE will provide feedback during these workshops that will help UC projects to program their planning of activities taking the most of FI-WARE. Note from FI-WARE: Technical managers/architects from UC Trial projects that are continuation of Phase 1 UC projects may skip the first day (i.e., people already engaged in phase 1 and part of the FI-PPP AB already). The rest of days will be mandatory for all UC Trial projects as well as FI-WARE and Xifi. People engaged in the FI-PPP for their first time must also attend the first day. It is expected that 2, maximum 3 people per project will attend. They should play a technical role in their project. Ideally, two of them should be the ones being appointed as members of the FI-PPP AB. Kind regards, Ilkka and Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Fri Mar 22 14:17:19 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 22 Mar 2013 14:17:19 +0100 Subject: [Fiware-wpa] Fwd: FI-PPP Phase 2 CONCORD in Phase 2 In-Reply-To: <9112BC7A3E903648A78842961080989425CE01@EXMDB04.org.aalto.fi> References: <9112BC7A3E903648A78842961080989425CE01@EXMDB04.org.aalto.fi> Message-ID: <514C59DF.4020909@tid.es> Dear all, FYI. Official announcement about changes in CONCORD which hopefully will improve overall performance of FI-PPP collaboration activities. You may notice that there is a reference to a FI-PPP Programme Week in June. To the best of my knowledge, preparation of this event had never been discussed with us because, among other things, if it had been, I had immediately raised an issue on behalf of FI-WARE because June is definitively not the best dates (overlapping with our 2nd year official review and the delivery of the FI-WARE 2nd Release). I have already raised this to CONCORD representatives and expect a rectification. 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: FI-PPP Phase 2 CONCORD in Phase 2 Date: Wed, 20 Mar 2013 19:17:07 +0000 From: Lakaniemi Ilkka To: ab at fi-ppp.eu , sb at fi-ppp.eu , FI-PPP-Phase-2-Contacts at future-internet.eu CC: concord-consortium at fi-ppp.eu Dear all, As we are all getting ready to launch FI-PPP in Phase 2, I wanted to inform you of the following major changes taking place within CONCORD for Phase 2 activities. If you have any questions, please do not hesitate to get in contact with me on any CONCORD-related matter. The below listed persons can also present further details on the current and coming activities of their related working areas. We are also happy to contribute and present at your coming events I will also be the main contact point for any on-going action points for CONCORD. I will report on their progress in my following messages. * As indicated at the negotiation workshop, CONCORD has revisited its objectives, tools and structures to reflect the Fi-PPP Phase 2 activities. This means an overhaul of the CONCORD consortium and its ways of working to serve the FI-PPP at all levels. * First, CONCORD now consists of five (5) member organizations: Aalto University, Eurescom, Zurcher Hochschule fur Angewandte Wissenschaft (ZHAW), iMinds and European Network of Living Labs (ENOLL). Each of these organizations is now positioned to best perform within CONCORD and for FI-PPP. * Second, the following persons are responsible for managing, leading and facilitating CONCORD tasks for FI-PPP: * FI-PPP Boards: * Steering Board - David Kennedy (Eurescom), * Architecture Board - Thomas Bohnert (ZHAW), * Executive Industry Board - David Kennedy (Eurescom) * Advisory Board - Petra Turkama (Aalto) * FI-PPP Working Groups (WGs): * Communications and Dissemination - Milon Gupta (Eurescom) * Policy - Hans Schaffers (Aalto) * Business Models and Exploitation - Pieter Ballon (iMinds) * Standardisation - Thomas Bohnert (ZHAW) * Third, CONCORD toolbox for FI-PPP, including IT tools, is being reformatted for FI-PPP information continuity purposes, due to some software license changes and to prepare for coming needs. A separate, detailed message will follow tomorrow about the CONCORD toolbox changes. Contact persons for details on IT changes will be: Juha Salo (Aalto: juha.salo at aalto.fi) and Klaas-Pieter Vlieg (Eurescom: vlieg at eurescom.eu). * Fourth, CONCORD is arranging and planning for FI-PPP-wide events, FI-PPP Programme Weeks, to build the community and enable information sharing. The first meeting is being scheduled for 17-20 June in Berlin. I trust that with the above changes gaining speed and momentum, CONCORD will be ideally positioned to fulfill its role for FI-PPP. Do not hesitate to contact me for any details and stay tuned for more information on the above topics. Kind regards, Ilkka Lakaniemi +358 - 50-434 62 65 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Fri Mar 22 14:32:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 22 Mar 2013 14:32:25 +0100 Subject: [Fiware-wpa] Adoption of JIRA as tool to deal with interaction with FI-WARE Users Message-ID: <514C5D69.6000802@tid.es> Dear all, Some of you had already left our joint WPLs/WPAs confcall when we address the matter, but we had the opportunity to discuss the matter about what tracker tool to use to handle the interaction with final users of FI-WARE (i.e., enhancement requests, bug reporting, requests for information). When I refer to users, we should look beyond the current list of UC projects in the FI-PPP but also app developers, particularly SMEs and web entrepreneurs that will become users of the FI-WARE Open Innovation Lab (OIL) and develop app with FI-WARE technologies. After an internal analysis, comparing JIRA and the FusionForge tracker, we believe that the right decision to make is going for JIRA. This proposal was discussed with the representative of WP9/Tools (Davide) during the WPL/WPA confcall and we rather appreciate their positive feedback, not only because their knowledge in both tools but also because we were concerned about potential impact on the work we are doing in FI-CoDE. JIRA is probably nowadays the most widely used and well-scored tool for tickets tracking and backlog management. It is used extensively and probably many of your companies are already using it. It is much better than the FusionForge tracker in terms of usability and, very much important, the ability to generate statistics that may help us to follow-up and report how demands of users are being attended. Both aspects would be essential in deciding what tool to adopt in interaction with users of FI-WARE. Please note that the use of JIRA would be limited to handling the tickets that users/developers of the FI-WARE GEis and FI-WARE Open Innovation Lab may create and we have to handle. A potential issue may have to do with license costs. The first good news is that JIRA comes for free in the case of open source projects. Therefore, JIRA instances used to handle tickets linked to FI-WARE GEis would not have any costs. Regarding FI-WARE GEis that are not open source, the costs is very limited (around 10? per user/month and users who issue tickets do not count, just the users that will manage the workflow of tickets, that is FI-WARE GEi owners or the team that will operate the FI-WARE OIL). Still pending of careful analysis, we believe that FI-WARE has enough budget to cover the costs without this requiring to touch any of the funding from partners. Hope you will feel excited about this decision as we are. Please share with your teams and get back to us if you have any issue and or concern. It is our intention to communicate the adoption of JIRA for managing interaction with FI-WARE users in the upcoming FI-WARE Architects Week beginning of April. 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 Sun Mar 24 13:19:36 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 24 Mar 2013 13:19:36 +0100 Subject: [Fiware-wpa] Fwd: Fwd: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <514C1163.1010808@tid.es> References: <514C1163.1010808@tid.es> Message-ID: <514EEF58.7040708@tid.es> Dear WPLs/WPAs, Find below a copy of the mail sent to Arian regarding amendment 4. I want to remind you that there was an AP on all WPLs about filling the column with the date from which justification of costs associated to new allocated PMs will apply. Despite we have told Arian that "Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities", we have to be prepared in case he asks for a more precise date, case by case. Note that I have attached two spreadsheets to this message. The one named "FI-WARE effort-budget-funding - Amendment 4 summary for the EC.xlsx" is the only one submitted to the EC. The second one named "FI-WARE effort-budget-funding - Amendment 4 v28.xlsx" is the new one in which you have to fill the column "Start date from which PMs are being consumed" (only cells in white). Please note that you have to submit this info before Wednesday 27th, noon. Otherwise, we assume that you agree that PMs will start to be consumed from the first day of the month at which the new amendment will be be approved. I copy the FI-WARE General Assembly so that individual partners to whom PMs will be allocated can follow-up this with the corresponding WPLs. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Fri, 22 Mar 2013 09:06:03 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: FI-WARE project EC mailbox , "subsidies at tid.es" , Miguel Carrillo , Javier de Pedro Sanchez Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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: FI-WARE effort-budget-funding - Amendment 4 summary for the EC.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 257405 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE effort-budget-funding - Amendment 4 v28.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 258170 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Mon Mar 25 10:06:03 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 25 Mar 2013 09:06:03 +0000 Subject: [Fiware-wpa] Feedback by UC projects on your GE: FInest Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FCE2ED@DEWDFEMB11A.global.corp.sap> Dear GE-providers, Please find attached the feedback, gathered from one of the (phase 1) use case projects in relation to your GE provided through the WP10/Testbed workpackage to you. Please forward this information to people I might have forgotten on the list. As you probably know, the UC projects are currently following a validation process, defined within https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-review/index.php/D.10.5.1.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page They expressed their opinion with the help of the attached xls-table and within a PDF document in relation to the questioned asked. No it is your turn - use the feedback to refine your requirements and components or approach the use case projects directly and gather perhaps some quotes or to position your component within the rest of the project lifetime. If you have any questions, don't hesitate to ask. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-03-GE_Validation_FINEST-v1.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 37647 bytes Desc: 2013-03-GE_Validation_FINEST-v1.xlsx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-03-GE_Validation_FINEST-v1.pdf Type: application/pdf Size: 380056 bytes Desc: 2013-03-GE_Validation_FINEST-v1.pdf URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thorsten.sandfuchs at sap.com Mon Mar 25 10:15:46 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 25 Mar 2013 09:15:46 +0000 Subject: [Fiware-wpa] Feedback by UC projects on your GE: SAFECITY Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FCE38E@DEWDFEMB11A.global.corp.sap> Dear GE-providers, Please find attached the feedback, gathered from one of the (phase 1) use case projects in relation to your GE provided through the WP10/Testbed workpackage to you. Please forward this information to people I might have forgotten on the list. As you probably know, the UC projects are currently following a validation process, defined within https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-review/index.php/D.10.5.1.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page They expressed their opinion with the help of the attached xls-table. No it is your turn - use the feedback to refine your requirements and components or approach the use case projects directly and gather perhaps some quotes or to position your component within the rest of the project lifetime. If you have any questions, don't hesitate to ask. As safecity was the project which made real pocs (arlanda and madrid) this questionnaire has an intrinsic extremely high value. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: SAFECITY_FI-WARE Testbed Questionnaire_v6.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 37985 bytes Desc: SAFECITY_FI-WARE Testbed Questionnaire_v6.xlsx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From mcp at tid.es Mon Mar 25 10:36:46 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 25 Mar 2013 10:36:46 +0100 Subject: [Fiware-wpa] Minutes of today's WPL/WPA call Message-ID: <51501AAE.1000707@tid.es> Dear all, We will use this one (I am editing it right now ) * https://docs.google.com/document/d/164XkFpLUYRFRU-6iJpr_3J_nWUXGZX7jSREDjCoyGJs/edit?usp=sharing Today Juanjo is on holidays. There are things where I am not involved but we will try to go through the ones we can dispatch. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Mar 25 12:34:04 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 25 Mar 2013 12:34:04 +0100 Subject: [Fiware-wpa] Fwd: Fwd: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <514EEF58.7040708@tid.es> References: <514C1163.1010808@tid.es> <514EEF58.7040708@tid.es> Message-ID: <5150362C.2050404@tid.es> Hi, Please copy Javier de Pedro Sanchez in your email regarding start date from which justification of costs associated to new allocated PMs will apply. 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/03/13 13:19, Juanjo Hierro wrote: Dear WPLs/WPAs, Find below a copy of the mail sent to Arian regarding amendment 4. I want to remind you that there was an AP on all WPLs about filling the column with the date from which justification of costs associated to new allocated PMs will apply. Despite we have told Arian that "Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities", we have to be prepared in case he asks for a more precise date, case by case. Note that I have attached two spreadsheets to this message. The one named "FI-WARE effort-budget-funding - Amendment 4 summary for the EC.xlsx" is the only one submitted to the EC. The second one named "FI-WARE effort-budget-funding - Amendment 4 v28.xlsx" is the new one in which you have to fill the column "Start date from which PMs are being consumed" (only cells in white). Please note that you have to submit this info before Wednesday 27th, noon. Otherwise, we assume that you agree that PMs will start to be consumed from the first day of the month at which the new amendment will be be approved. I copy the FI-WARE General Assembly so that individual partners to whom PMs will be allocated can follow-up this with the corresponding WPLs. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Fri, 22 Mar 2013 09:06:03 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: FI-WARE project EC mailbox , "subsidies at tid.es" , Miguel Carrillo , Javier de Pedro Sanchez Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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: From jhierro at tid.es Mon Mar 25 12:34:44 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 25 Mar 2013 12:34:44 +0100 Subject: [Fiware-wpa] Fwd: Fwd: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <514EEF58.7040708@tid.es> References: <514C1163.1010808@tid.es> <514EEF58.7040708@tid.es> Message-ID: <51503654.3010805@tid.es> Dear WPLs, Please copy Javier de Pedro Sanchez in your email regarding start date from which justification of costs associated to new allocated PMs will apply. I remind you that deadline is Wednesday March 27th noon. 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 24/03/13 13:19, Juanjo Hierro wrote: Dear WPLs/WPAs, Find below a copy of the mail sent to Arian regarding amendment 4. I want to remind you that there was an AP on all WPLs about filling the column with the date from which justification of costs associated to new allocated PMs will apply. Despite we have told Arian that "Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities", we have to be prepared in case he asks for a more precise date, case by case. Note that I have attached two spreadsheets to this message. The one named "FI-WARE effort-budget-funding - Amendment 4 summary for the EC.xlsx" is the only one submitted to the EC. The second one named "FI-WARE effort-budget-funding - Amendment 4 v28.xlsx" is the new one in which you have to fill the column "Start date from which PMs are being consumed" (only cells in white). Please note that you have to submit this info before Wednesday 27th, noon. Otherwise, we assume that you agree that PMs will start to be consumed from the first day of the month at which the new amendment will be be approved. I copy the FI-WARE General Assembly so that individual partners to whom PMs will be allocated can follow-up this with the corresponding WPLs. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Fri, 22 Mar 2013 09:06:03 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: FI-WARE project EC mailbox , "subsidies at tid.es" , Miguel Carrillo , Javier de Pedro Sanchez Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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: From jhierro at tid.es Tue Mar 26 06:57:08 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 26 Mar 2013 06:57:08 +0100 Subject: [Fiware-wpa] Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <5151381E.7080809@tid.es> References: <5151381E.7080809@tid.es> Message-ID: <515138B4.4010900@tid.es> Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Mar 26 08:49:31 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 26 Mar 2013 07:49:31 +0000 Subject: [Fiware-wpa] [Fiware-wpl] Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <515138B4.4010900@tid.es> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> Message-ID: <28409_1364284173_5151530D_28409_1817_1_976A65C5A08ADF49B9A8523F7F81925C0BE43D@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Juanjo, all, I globally agree with your answer. I think we can emphasize that involving new industrial partners would also take too much time if we expect to have a good contribution before the end of the project. This is right in the special case of ETSI-M2M because the partners who should provide this implementation of this standard were NSN and Ericsson. If we try to find a new industrial partner for that it would take4 or 6 months to involve them, from an administrative point of view, in the project. Choosing Fraunhofer is the best choice we have in flexibility and reactivity. You can also remind EC that Cumulocity GmbH is now a spin-off of NSN (https://www.cumulocity.com/ ) so this part was all except a weird choice. And to close the IoT chapter, we can also communicate that Telefonica is now the WPA for IoT. BR Thierry 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 26 mars 2013 06:57 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdps at tid.es Tue Mar 26 08:59:09 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Tue, 26 Mar 2013 07:59:09 +0000 Subject: [Fiware-wpa] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <515138B4.4010900@tid.es> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> Message-ID: <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: WP4.zip Type: application/x-zip-compressed Size: 100203 bytes Desc: WP4.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP5.zip Type: application/x-zip-compressed Size: 146609 bytes Desc: WP5.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP6.zip Type: application/x-zip-compressed Size: 962781 bytes Desc: WP6.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP7.zip Type: application/x-zip-compressed Size: 130935 bytes Desc: WP7.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP8.zip Type: application/x-zip-compressed Size: 99745 bytes Desc: WP8.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP9.zip Type: application/x-zip-compressed Size: 93471 bytes Desc: WP9.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP10.zip Type: application/x-zip-compressed Size: 97948 bytes Desc: WP10.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP11.zip Type: application/x-zip-compressed Size: 97128 bytes Desc: WP11.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP12.zip Type: application/x-zip-compressed Size: 93141 bytes Desc: WP12.zip URL: From mcp at tid.es Tue Mar 26 13:12:26 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 26 Mar 2013 13:12:26 +0100 Subject: [Fiware-wpa] Architecture doc (update + guidelines) Message-ID: <515190AA.4080908@tid.es> Dear all, As agreed in our confcall yesterday, we will continue using the cockpit and the process will be similar to the previous round: * http://www.google.com/url?q=https%3A%2F%2Fdocs.google.com%2Fspreadsheet%2Fccc%3Fkey%3D0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c%23gid%3D0 Calendar: 1) docx second version of chapters ready for peer review: March 27th * Each chapter will upload their contributions to the private docman and will add the link to column E (as the Data chapter has already done) 2) Comments on second draft due by April 4th * Each chapter will upload their reviews to the private docman and will add the link to column F 3) 3rd Final version: April 12th * Each chapter will upload their 3rd version of the architecture to docman and will add the link to column G This is the new assignment: * Data - reviewed by Apps * Cloud - reviewed by IoT * Apps - reviewed by I2ND * IoT - reviewed by Data * I2ND - reviewed by Security * Security - reviewed by Cloud Could those who have a new version please upload it? Security said that they would have yesterday but I cannot see it on the cockpit, maybe they were waiting for this confirmation. Up to each WPL to do the work on the wiki or on the document directly. But it is compulsory to 100% synch the public wiki after the delivery. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From manieri at eng.it Tue Mar 26 19:42:24 2013 From: manieri at eng.it (Andrea Manieri) Date: Tue, 26 Mar 2013 19:42:24 +0100 Subject: [Fiware-wpa] [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> Message-ID: <5151EC10.9090008@eng.it> Dear Javier, I was in an all day meeting and I spotted this important email only now. Since effort allocation and check of partner task description is a duty of each partner I forwarded to the WP9 and 10 mailing list for their reply. I'll collect the replies and send to you as soon as possible, thanks for your patience, Andrea Il 26/03/2013 08:59, JAVIER DE PEDRO SANCHEZ ha scritto: > > Dear all. > > Please find attached one zip file for each WP. They are an extract > from the current updated DoW of the amendment 4 to be reviewed and > modified if needed by each WPL. > > I really need your prompt reaction in order to integrate all the > changes and send the updated DoW to Officer tomorrow. *Please, each > WPL has to reply with his reviewed DoW today*. > > Please review: > > Effort by task for each partner. (excel file) > > Role for each partner (word file, according with excel file) > > Description of each task. (word file) > > Thank you for understanding and for your contribution. > > BR > > Javier. > > *De:*JUAN JOSE HIERRO SUREDA > *Enviado el:* martes, 26 de marzo de 2013 6:57 > *Para:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > *CC:* JAVIER DE PEDRO SANCHEZ > *Asunto:* Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW > dealing with PMs reallocation > > Hi all, > > A first reaction from Arian to the reallocation of PMs and my > response to him. I decided to respond quickly to avoid justification > of further delays on the side of the Commission. > > If you believe that I should have added something in my response or > you believe I said something wrong, please let me know. > > 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs > reallocation > > *Date: *** > > > > Tue, 26 Mar 2013 06:54:38 +0100 > > *From: *** > > > > Juanjo Hierro > > *To: *** > > > > > > *CC: *** > > > > > , > , , > , "jhierro >> \"Juan J. Hierro\"" > > > Dear Arian, > > Thanks for your quick response. My response between lines of your > message below ... > > > On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu > wrote: > > Dear Juanjo, > > *The overview of changes presented is very well done and clear, > and I don't have any issues with them, except for the points below. * > > I don't care that much about shifting PMs and who gets what. Here > the consortium has apparently bound itself to all kind of weird > pre-existing agreements anyway, not using the flexibility offered > by the grant agreement. > > > I don't know exactly what you mean, but certainly the consortium has > not bound itself to any weird agreement ... I rather see it the other > way around ... the consortium has been flexible and agile to > reallocate efforts and roles of the partners so that each partner has > concentrated its efforts in less things (thus increasing the efforts > in the things they have decided to concentrate on). > > I rather believe this is a positive thing. I would be much more > worried if we had adopted an approach where partners were > participating in many things, with no significant effort in any. > > One of the things that I believe is rather good in the way FI-WARE > is organized is that it is like 7 IPs (one per technical chapter) but > with the big difference that if you look at each of these IPs, there > is a limited number of key partners (4-6). There is also a clear > role of partners within each chapter, each partner typically bound to > the implementation of some GE in the chapter. All of this will help, > imho, in achieveing good results. > > > Having said that, the thing to avoid is that industry withdraws and > academia gets more funding. That is the trend here, with industry > reducing its involvement with 640k and academia/research institutes > increasing with 640k. I understand there is no choice because industry > is not willing/able to do more, but it is against the spirit of the > industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad > on EU industry. > > > The industrial partners has taken the decisions consciously and I > honestly believe that the situation is not as bad as it may be > considered in a very first approach: > > * There were only two GEs for which the implementation has been > transferred to an academia partner: > > o Ericsson was originally planned to contribute the > implementation of the IoT Gateway Device Management GE in the > IoT chapter and, while it was agreed with them that they would > support an ETSI M2M compliant interface, they were only able > to commit to support this interface in their product for the > 3rd Release of FI-WARE. When Ericsson withdrew, we found > here an opportunity to find someone who could contribute an > ETSI M2M implementation already rather than to be able to > develop it from the start. This was Franhoufer. This made > us feel more confident to keep our initial plans to deliver an > Architecture which already considered support to the relevant > ETSI M2M standard. There were not many other options from > any industry partner in Europe so that's why. > o Ericsson was also originally planned to contribute an > implementation of the Store GE in the Apps Chapter (part of > the Business Framework). Here, we decided to go for UPM > basically for two reasons. First because they had an asset > (WireCloud) part of which (WireCloud's catalogue) could evolve > to become the Store we were looking for in reasonable time. > Second because they were committed to contribute their > implementation as open source. Here, we found that elivering > the code of the Store as open source could be something that > would give FI-WARE better chances to make impact: there are > many proprietary commercial stores out there ... but none is > open source so we expect this will call the attention of third > parties. > > * The rest of new PMs allocated to academia partners do not > correspond to transference of the responsibility to implement > FI-WARE GEs: > > o PMs transferred from Ericsson to UPM in WP9 (Tools) correspond > to the implementation of the FI-WARE Catalogue portal: this is > not a FI-WARE GE in itself nor anything that will be used to > setup and operate FI-WARE Instances. It will not be > commercialized standalone so it was a matter of finding who > could make a good job and the UPM had proved they can develop > a good implementation of the FI-WARE Catalogue. The UPM also > committed to implement it as open source and that is also > relevant to ensure sustainability. > o When NSN-Germany withdrew from WP5 (tools) we found out that > finding a replacement for them was not rather critical so that > we may use the corresponding PMs/funding in reinforcing other > tasks in other WPs. We finally decided to transfer the PMs, > initally allocated to NSN-Germany in the IoT chapter, to UPM > because a) it would reinforce the work they were already doing > with the Cloud portal (to be delivered as open source and > contributed to the OpenStack Community), b) it allowed us to > assign the UPM the task of designing and maintaining the > look&feel of FI-WARE web portals (since they were in charge of > the most significant one in FI-WARE, it sounded like it made > sense) and c) it allowed us to assign the UPM to implement > some pieces of the FI-WARE Testbed/OIL portal that were not > initially foreseen as needed. There was unanimity in > considering that the UPM was doing a great job regarding the > Cloud portal so it was like natural to select them. > o Some new PMs were assigned to UniRoma because it was found > that the amount of PMs they had currently assigned was not > enough for them to carry out their assigned tasks. > > > This is just a first quick response to your concern. A more > elaborated response can be provided if needed. > > > Please note that I care more about changes in the DoW wrt > tasks/activities to be carried out. Large changes in efforts without > any change in the task description (e.g. the iMinds addition in WP3) > cannot be correct. > > > We prepared a new description of WP3 as a result of their inclusion > as new beneficiaries in amendment 3 ... Is there anything you are > still missing ? If it was just an example, be sure we understand > that we should provide new description of tasks/WPs where major > changes are incorporated. We are here just anticipating the figures, > so that you can approve them, subject to proper description in an > amendment of the DoW. > > > Then, what is most important is *what happens with the contributions > from the withdrawing partners, NSN-FI and EAB.* > > > Just a clarification: NSN-FI withdraw without having made any > relevant contribution. I believe you refer to NSN-H (Hungary) who > was indeed playing the role of WPA in the IoT chapter and were the > ones that were contributing the Cumulocity product as implementation > of the IoT Backend Device Management GE ... > > > > What happens with Ericsson's Service Composition - Ericsson > Composition Engine (ECE) > > What happens with Ericsson's Gateway Device Management GE - Ericsson > IoT Gateway > > In a previous email (19 Nov 2012), you concluded (for the ECE): "So > the problem here is not about sustainability beyond the FI-PPP (which > Ericsson states would be provided) but inside the FI-PPP ..." > > Will they remain available to FI-WARE? Under what conditions? > > If nothing remains available, what does that mean for their > contribution to FI-WARE? Will these be replaced? > > > Ericsson was contributing the implementation of two GEs in WP3 (Apps > Chapter): the Store GE, part of the Business Framework, and the ECE > GE. The amount of PMs/funding assigned to Ericsson for contributing > these two assets and evolve them was fair because Ericsson was relying > on existing and mature assets. When Ericsson withdrew from WP3, we > couldn't find any partner that may provide an asset for the Store GE > so therefore we had to plan its development. Then we found that the > whole amount of funding assigned to Ericsson was necessary to carry > out that development and we were lucky because we could leverage on > the WireCloud's catalogue for that purpose. Since there were already > other service composition tools already, we concluded that it was not > critical to find a replacement for the ECE. > > > Same questions for NSN-FI. I understand they were in charge of the GE > "Backend Device Management"?? And they contributed an asset called > "Cumulocity". So same questions as above. > > > The IoT Backend Device Management GE will be implemented through the > IDAS DCA product contributed by Telefonica. This product essentially > replaces the Cumulocity product that was planned to be contributed by > NSN. > > > Specific questions: > > 1) What does the underlined text mean in the sentence "Withdrawal of > Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM > until M18, so it transfers 16 PM to FRAUNHOFER because they have to > assume Advanced Connectivity GEs with ETSI-M2M interface and _will be > involeved in the project at the beginning of April 2013!"_ > > > Well, we are simply saying that in the case of Fraunhofer, they will > start working in the IoT chapter since beginning of April 2013 ... > Of course, Franhoufer has been working on the project since its > beginning, but in different WPs. > > > 2) What does the following sentence mean? "TRDF-P finished at > 31-12-2012. People moved to TRDF." TRDP is no longer a third party? > > > I hope Javier de Pedro, in copy, can reply this part since I'm not > so much aware of what third party is involved in each case. For me, > all of them are Thales ... > > > > Finally, are you going to ask an amendment for the *Electronic-only > signature and transmission of Form C *(see attachment)? > > > Again, I would ask Javier de Pedro to answer this part. > > Cheers, > > -- Juanjo > > > > Best regards, > > Arian. > > PS. I am kind-of allergic to statements like your "No early > response...", knowing that the only deadlines I'm bound to are the > ones in the grant agreement?EUR? > > -----Original Message----- > > From: Juanjo Hierro [mailto:jhierro at tid.es] > > Sent: Friday, March 22, 2013 9:06 AM > > To: ZWEGERS Arian (CNECT) > > Cc: CNECT-ICT-285248; subsidies at tid.es ; > Miguel Carrillo; Javier de Pedro Sanchez > > Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with > PMs reallocation > > Dear Arian, > > Once we have finalized amendment 3 of our DoW, we should open a new > > amendment dealing with fixing all PMs reallocation that were pending > > (some of which pending since July last year). As already announced in > > our mail on January 20th this year, the situation is critical regarding > > some of these PMs reallocation, particularly dealing with the ability to > > handle withdrawal of several partners. > > All this PMs reallocation have been agreed among the partners at PCC > > (Project Coordination Committee), WPLs/WPAs and General Assembly level. > > We believe that is is critical to close this amendment 4 before end > > of April as to allow a reporting of costs for the 2nd period that is > > aligned with an approved DoW. > > Please find enclosed a spreadsheet which summarizes the changes > > already implemented in amendment 3 as well as changes proposed in > > amendment 4. Changes being proposed for amendment 4 are summarized in > > the sheet titled "Changes (amendment 4)". There is a final picture of > > PMs allocation to tasks for each WP as well as impact in figures > > (overall funding is kept the same). > > Consumption of allocated PMs have taken place since start of the 2nd > > reporting period and, in the case of partners withdrawing the > > consortium, since a decision was taken regarding what partner was going > > to take over their responsibilities. > > We will soon send you a draft of the DoW that will incorporate the > > changes summarized here. > > We will kindly ask you to send a response to this mail with your > > agreement to the proposed PMs reallocation in advance to approval of the > > DoW amendment itself which may take more time. That would give the > > existing partners, overall those taking the responsibility to take over > > the tasks from withdrawing partners, the necessary security to keep > > their investments they have been making so far. > > No early response will be taken as acknowledge and acceptance of this > > proposed PMs reallocation. > > We will rather appreciate your help in moving this forward. > > 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 > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol??tica de env??o y recepci??n de correo > electr??nico en el enlace situado m??s abajo. > This message is intended exclusively for its 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 thierry.nagellen at orange.com Wed Mar 27 08:17:37 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 27 Mar 2013 07:17:37 +0000 Subject: [Fiware-wpa] [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> Message-ID: <4083_1364368659_51529D12_4083_6598_1_976A65C5A08ADF49B9A8523F7F81925C0C3CE9@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Javier I apologize for the delay but I had to check some emails before to be sure that I did not miss some information regarding UPM. I did not notice previously that UPM would be involved in WP5, especially in WP5 for Data Handling. I clearly do not understand what UPM will provide in this part because they do not have any asset for that so currently I cannot validate this point. For Fraunhofer, as I explained before, this partner does not have the same cost model that Ericsson so I?m sure that the 16PM from Ercisson are not 16PM for Fraunhofer but around 13 or 14PM with the same budget. Could you calculate the right level of PM for Fraunhofer? Thanks and Best regards. Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de JAVIER DE PEDRO SANCHEZ Envoy? : mardi 26 mars 2013 08:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : subsidies at tid.es Objet : Re: [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importance : Haute Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Mar 27 09:34:45 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 27 Mar 2013 09:34:45 +0100 Subject: [Fiware-wpa] Registration for Architects' Week Message-ID: <5152AF25.1090304@tid.es> Dear all, Many of you are speaking at the Architecture Week and yet I do not see any of you on the registration! Will you please express the days that you are going to be there? We need to have the right numbers. The registration is here: * https://docs.google.com/spreadsheet/ccc?key=0AtBbzsh_CGfydFEtLXVfV1E3T21aWVAwc3lfdTNuQ3c#gid=0 If you need to double check what's programmed for each day, you can always see the agenda: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdE4teWs4UEpZa29zd0FRUmNTaFdxT2c#gid=0 Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Mar 27 09:39:40 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 27 Mar 2013 09:39:40 +0100 Subject: [Fiware-wpa] [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> Message-ID: <19196_1364373856_5152B15F_19196_7_3_07fd34d2-e8a0-40b8-82a6-6c842dfaf10f@THSONEA01HUB04P.one.grp> Dear Javier, Sorry but yesterday I was away and could only see your email today. So will try to get it answered asap and by EOB today at the latest. But please consider it is not easy to react with such ?short? deadline. 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 JAVIER DE PEDRO SANCHEZ Envoy? : mardi 26 mars 2013 08:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : subsidies at tid.es Objet : Re: [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importance : Haute Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 jdps at tid.es Wed Mar 27 10:11:26 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 27 Mar 2013 09:11:26 +0000 Subject: [Fiware-wpa] [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <4083_1364368659_51529D12_4083_6598_1_976A65C5A08ADF49B9A8523F7F81925C0C3CE9@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> <77A22C1085494D48B4018F06A40DB2C71C0A8382@EX10-MB2-MAD.hi.inet> <4083_1364368659_51529D12_4083_6598_1_976A65C5A08ADF49B9A8523F7F81925C0C3CE9@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <77A22C1085494D48B4018F06A40DB2C71C0A9B42@EX10-MB2-MAD.hi.inet> Thank you Thierry, please let me explain about the transfer of effort (General idea): PartnerA withdraws from the WPx, so it will transfer its effort to PartnerB. The maximum funding to be transferred (MFT) is calculated with the final funding from the costs of PartnerA. Now, there are two cases: Case 1: If ?MFT of PartnerA? > ?MFT of PartnerB?, the received funding will be calculated with MFT of PartnerB. An adjust must be applied, ?Adjust 2? in order to match with the MFT of Partner A. It would be minimalized with the remaining budget of case 2. (?Adjust 3?) Case 2: If ?MFT of PartnerA? < ?MFT of PartnerB?, the received funding will be calculated with MFT of PartnerA. The remaining funding will be used to minimalize the case 1. (?Adjust 3?) Fraunhofer case: In the explanation above, WPx = WP2 + WP5, PartnerA= EAB and PartnerB = Fraunhofer. [cid:image002.jpg at 01CE2AD3.85AFF390] It is the case 1. It is necessary to make the ?adjust 2? in Fraunhofer budget because its MFT is higher that EAB one. We need to apply -26.740 ? according to have a maximum extra funding of 129.630. And we can minimize this adjust with an ?adjust 3? of 7.739 ? [cid:image006.jpg at 01CE2AD3.85AFF390] So, the modification in Fraunhofer?s funding is as follows: [cid:image007.jpg at 01CE2AD3.85AFF390] I hope this helps. BR Javier. De: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Enviado el: mi?rcoles, 27 de marzo de 2013 8:18 Para: JAVIER DE PEDRO SANCHEZ; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: subsidies at tid.es Asunto: RE: [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi Javier I apologize for the delay but I had to check some emails before to be sure that I did not miss some information regarding UPM. I did not notice previously that UPM would be involved in WP5, especially in WP5 for Data Handling. I clearly do not understand what UPM will provide in this part because they do not have any asset for that so currently I cannot validate this point. For Fraunhofer, as I explained before, this partner does not have the same cost model that Ericsson so I?m sure that the 16PM from Ercisson are not 16PM for Fraunhofer but around 13 or 14PM with the same budget. Could you calculate the right level of PM for Fraunhofer? Thanks and Best regards. Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de JAVIER DE PEDRO SANCHEZ Envoy? : mardi 26 mars 2013 08:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : subsidies at tid.es Objet : Re: [Fiware-wpl] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importance : Haute Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 41863 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 33270 bytes Desc: image006.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 37291 bytes Desc: image007.jpg URL: From jdps at tid.es Wed Mar 27 10:16:26 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 27 Mar 2013 09:16:26 +0000 Subject: [Fiware-wpa] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> Message-ID: <77A22C1085494D48B4018F06A40DB2C71C0A9B9D@EX10-MB2-MAD.hi.inet> Dear all, some of you are telling me that you need more time because you need to contact with the partner involved in your WP. It is reasonable. So, please, provide the update DoW by April 2nd, 2013. Please don?t forget to activate the control change of the document. Thank you very much for your contribution. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 26 de marzo de 2013 9:00 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JUAN JOSE HIERRO SUREDA; subsidies at tid.es Asunto: RE: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importancia: Alta Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 jdps at tid.es Wed Mar 27 11:43:36 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 27 Mar 2013 10:43:36 +0000 Subject: [Fiware-wpa] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> Message-ID: <77A22C1085494D48B4018F06A40DB2C71C0A9E20@EX10-MB2-MAD.hi.inet> Dear all. Updating the DoW, it?s important to take in account that some partners have declared effort in task or WP and they withdraw from them now. So, if a partner has declared effort, it can?t be deleted from the task/WP where it was involved. You?ll need to update its role, but it can be deleted. Please, in case I have deleted EAB in the word file I have sent to you, reject and update it. Please find enclosed by WP, the effort declared by partner I have so far. [cid:image001.png at 01CE2ADF.DDE4B530] [cid:image002.png at 01CE2ADF.DDE4B530] [cid:image003.png at 01CE2ADF.DDE4B530] [cid:image004.png at 01CE2ADF.DDE4B530] [cid:image005.png at 01CE2AE0.30C2B270] [cid:image006.png at 01CE2AE0.30C2B270] [cid:image007.png at 01CE2AE0.30C2B270] [cid:image008.png at 01CE2AE0.30C2B270] [cid:image009.png at 01CE2AE0.30C2B270] [cid:image010.png at 01CE2AE0.30C2B270] BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 27 de marzo de 2013 10:17 Para: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu' CC: JUAN JOSE HIERRO SUREDA; 'subsidies at tid.es' Asunto: RE: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importancia: Alta Dear all, some of you are telling me that you need more time because you need to contact with the partner involved in your WP. It is reasonable. So, please, provide the update DoW by April 2nd, 2013. Please don?t forget to activate the control change of the document. Thank you very much for your contribution. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 26 de marzo de 2013 9:00 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JUAN JOSE HIERRO SUREDA; subsidies at tid.es Asunto: RE: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importancia: Alta Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: 42494 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 32668 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 38556 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 33399 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 43070 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 38777 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 33544 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 47338 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 40355 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 48357 bytes Desc: image010.png URL: From pascal.bisson at thalesgroup.com Wed Mar 27 12:59:23 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 27 Mar 2013 12:59:23 +0100 Subject: [Fiware-wpa] [Fiware-wpl] Architecture doc (update + guidelines) In-Reply-To: <515190AA.4080908@tid.es> References: <515190AA.4080908@tid.es> Message-ID: <25385_1364385829_5152E025_25385_595_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E496BCA8@THSONEA01CMS04P.one.grp> Document has been uploaded for what concerns Security. Apologize for the delay. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 26 mars 2013 13:12 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Architecture doc (update + guidelines) Dear all, As agreed in our confcall yesterday, we will continue using the cockpit and the process will be similar to the previous round: * http://www.google.com/url?q=https%3A%2F%2Fdocs.google.com%2Fspreadsheet%2Fccc%3Fkey%3D0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c%23gid%3D0 Calendar: 1) docx second version of chapters ready for peer review: March 27th * Each chapter will upload their contributions to the private docman and will add the link to column E (as the Data chapter has already done) 2) Comments on second draft due by April 4th * Each chapter will upload their reviews to the private docman and will add the link to column F 3) 3rd Final version: April 12th * Each chapter will upload their 3rd version of the architecture to docman and will add the link to column G This is the new assignment: * Data - reviewed by Apps * Cloud - reviewed by IoT * Apps - reviewed by I2ND * IoT - reviewed by Data * I2ND - reviewed by Security * Security - reviewed by Cloud Could those who have a new version please upload it? Security said that they would have yesterday but I cannot see it on the cockpit, maybe they were waiting for this confirmation. Up to each WPL to do the work on the wiki or on the document directly. But it is compulsory to 100% synch the public wiki after the delivery. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed Mar 27 13:37:14 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 27 Mar 2013 12:37:14 +0000 Subject: [Fiware-wpa] Feedback by UC projects on your GE: FINSENY Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD27B7@DEWDFEMB11A.global.corp.sap> Dear GE-providers, Please find attached the feedback, gathered from one of the (phase 1) use case projects in relation to your GE provided through the WP10/Testbed workpackage to you. Please forward this information to people I might have forgotten on the list. For the GE "(Backend) Device Management GE" I couldn't identify a single contact point within the fi-ware catalogue here the chapter lead should take this and distribute it accordingly. As you probably know, the UC projects are currently following a validation process, defined within https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-review/index.php/D.10.5.1.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page They expressed their opinion with the help of the attached xls-table. No it is your turn - use the feedback to refine your requirements and components or approach the use case projects directly and gather perhaps some quotes or to position your component within the rest of the project lifetime. If you have any questions, don't hesitate to ask. As safecity was the project which made real pocs (arlanda and madrid) this questionnaire has an intrinsic extremely high value. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2013-01-Validation_process_template_for_use_case_projects_v2_FINSENY_final.pdf Type: application/pdf Size: 432443 bytes Desc: 2013-01-Validation_process_template_for_use_case_projects_v2_FINSENY_final.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FINSENY_FI-WARE Testbed Questionnaire_v3_FINSENY_20130327.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 36374 bytes Desc: FINSENY_FI-WARE Testbed Questionnaire_v3_FINSENY_20130327.xlsx URL: From jhierro at tid.es Wed Mar 27 15:05:53 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 27 Mar 2013 15:05:53 +0100 Subject: [Fiware-wpa] IMPORTANT APs on YOU: Fwd: Agenda of the FI-PPP Architects Week In-Reply-To: <514C577F.5030800@tid.es> References: <514C278D.3050306@tid.es> <514C577F.5030800@tid.es> Message-ID: <5152FCC1.6000908@tid.es> Dear WPLs/WPAs, I reminder of the APs on your side regarding the Architects Week next week. I assume all WPLs are dealing with the presentations on the second day that relate to their chapters, according to what was explained in the minutes of the confcall on March 19, subsection "Description of FI-WARE 2nd Release and roadmap in April 3" on section "Architects Week in April": https://docs.google.com/document/d/15UOA2B7ot6FmNDXT1CmU5j_n9KiLl0BMksiymyhuGUQ/edit?usp=sharing There was also instructions regarding the first day, also further detailed in my email on March 22. Cheers, -- Juanjo On 22/03/13 14:07, Juanjo Hierro wrote: FYI, the agenda of the FI-PPP Architects Week. Please take care of the particular parts of the presentations you have to cover during the first two days: * WP10 (Testbed) team: prepare the presentation on "FI-WARE Testbed" planned on April 2, from 14:30 to 15:00 * Be pragmatic, focus on how to get access to the testbed, how to create accounts, gain access, etc * You don't need to go into the details about Cloud capabilities because they will described on April 3 * WP9 (Tools) team: prepare presentation regarding "FI-WARE Training" planned on April 2, from 15:00 to 15:30 * Give a view on how we plan the training sessions (live webinars, recording sessions, etc). I understand we cannot be too precise here, because it is work still under development, but I guess it would be nice to explain the approach and the goals we are looking for * Explain when we plan the live webinars to take place and how we will organize subscription to the webinars. We can discuss this off-line, but I would go for a similar approach to the one followed for the webinars of the 1st Release of FI-WARE. * WP10 (Testbed) team, SAP: prepare the presentation on "FI-WARE validation by UC projects": * Explain the current validation process (including rationale: we agreed in the AB not to make this a heavy-duty process) * Call for feedback from new UC projects about enhancements they may believe would be nice to introduce in the process * All WPLs: I understand that everything is clear regarding assignment of responsibilites for the items in the agenda of the second day. Please also take a look to the notes that were inserted in the minutes of our last WPLs/WPAs confcall where I provided some more details/insights. Hope this all helps to start rolling-out the ball. I will be on holidays next week but will connect from time (although I'll be in NY and therefore there will be 6 hours of difference). Let's keep the discussion open during these days. The regular monday WPLs/WPAs follow-up confcall next monday March 25 will take place and Miguel will chair it. 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: Agenda of the FI-PPP Architects Week Date: Fri, 22 Mar 2013 10:42:37 +0100 From: Juanjo Hierro To: Lakaniemi Ilkka , Cecchi Maurizio , Sjaak Wolfert , Williams Fiona , Fourdeaux Henri , "rod.franklin at kuehne-nagel.com" , "sergio.gusmeroli at txtgroup.com" , Christoph Thuemmler , Van Der Linden Pieter , Anastasius Gavras CC: Fatelnig Peter , "Arian.ZWEGERS at ec.europa.eu" , "Ragnar.Bergstrom at ec.europa.eu" , "Maria-Concepcion.ANTON-GARCIA at ec.europa.eu" , David Kennedy , "FI-PPP-Phase-2-Contacts at future-internet.eu" , Turkama Petra , Salo Juha , Schaffers Hans , Thomas Michael Bohnert , "jhierro >> \"Juan J. Hierro\"" Dear all, You can find a draft agenda of the FI-PPP Architects Week at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdE4teWs4UEpZa29zd0FRUmNTaFdxT2c&usp=sharing Thanks to Thomas M. Bohnert for his feedback and help finalizing it. We would like to hear your input, regarding what is the day where we can co-llocate the workshop dealing with your UC Trial project. Based on an initial request, we have placed cSpace in the workshop colocated in April 3. Please send your proposals to Thomas and me so that we can come with a final proposal. Please take into account that we have to meet a compromise, so we hope you can trust we will make a reasonable proposal. We may come back to you with more details about what info we are asking you to provide in the workshops dedicated to UC projects. We are discussing with Xifi what can be specific requests about info we would love to hear from you. 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 14/03/13 06:57, Juanjo Hierro wrote: Dear all, This mail is to announce that the FI-PPP Architecture Week for Phase 2 will take place in the following venue: Aula Magna in Building "A" School of Telecommunication Engineering (ETS Ingenieros de Telecomunicacion - ETSIT) Avenida Complutense # 30 University City 28040 Madrid Directions and hotels close to the venue can be found at: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/como-llegar.html%3FL%3Dttqltguphtgolkug&usg=ALkJrhi775kjxa4XFzatOQMya9dkNbh5wg Maps of the buildings associated to the ETSIT: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/etsi-de-telecomunicacion/etsit-edificios.html&usg=ALkJrhi0WiJVR4jcJKDRa0prunRkZbTCig We had received many request to allow more than two people attending on behalf of phase 2 projects to the Architecture Week that will take place in Madrid, during April 2-5, that's why we have been late announcing the venue. Actually, the original venues were at a different location, but the meeting room was limited to 28-30 people maximum. Please note that coffee and lunch breaks will be scheduled during the week, but each attendee has to cover its own expenses. There is a restaurant and coffee bar in the same building of the venue with convenient prices. Note also that it might take a while to go from the University to the Airport, first walking to the metro stop "Ciudad Universitaria" (aprox. 1 Km) and then taking the metro to the Airport (you should take line 6 until "Nuevos Ministerios" and then line 8). You should take this into consideration when arranging the time of your return fligths on Friday. I will come later this week with a more detailed agenda, but the one already sent to you (see mail below) should be enough as far as logistics is concerned. 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 20/02/13 05:01, Lakaniemi Ilkka wrote: Dear all, As indicated yesterday, please find more detailed info about the FI-PPP Architecture Week on 2-5 April in Madrid. For any further details and info, please be in touch with Juanjo, Thomas B and me. The agenda of this meeting (draft): * April 2 (starting at 11:00am): FI-WARE to provide a thorough introduction on FI-WARE scope, goals, basic concepts, methodology, planning, available documentation, resources, tools, etc as well as a detailed description of the way the FI-PPP AB works. * April 3 morning: FI-WARE to provide detailed info about the FI-WARE Second Release, training planning, etc. * April 3 afternoon until April 5 17:00 CET: sequence of half-days workshops per UC Trial projects where UC Trials will present a sketch of their envisioned architecture, their current plans regarding usage of FI-WARE GEs, needs regarding setup of their trials, questions on which they need responses, etc. FI-WARE will provide feedback during these workshops that will help UC projects to program their planning of activities taking the most of FI-WARE. Note from FI-WARE: Technical managers/architects from UC Trial projects that are continuation of Phase 1 UC projects may skip the first day (i.e., people already engaged in phase 1 and part of the FI-PPP AB already). The rest of days will be mandatory for all UC Trial projects as well as FI-WARE and Xifi. People engaged in the FI-PPP for their first time must also attend the first day. It is expected that 2, maximum 3 people per project will attend. They should play a technical role in their project. Ideally, two of them should be the ones being appointed as members of the FI-PPP AB. Kind regards, Ilkka and Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Mar 27 16:33:19 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 27 Mar 2013 15:33:19 +0000 Subject: [Fiware-wpa] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B551FAF46@EX10-MB2-MAD.hi.inet> Dear Partners, As you know we are about to finish Sprint 2.2.3 corresponding to M23. This sprint closes Release 2.2 Next 1.April (M24) Sprint 2.3.1 (1st sprint of Release 2.3) is opened. Please, update your backlog items accordingly. 1. Close the tickets you finished along M23 (if not already done) 2. Update tickets under execution not finished to belong to Sprint 2.3.1 3. Open those new tickets you have scheduled/planned for Release 2.3 Sprint 2.3.1 - be aware Release 2.3 is the last release available for the current reporting period. Let me stress agile is obsessed with delivery, so there's need to commit to the backlog content allocated for a sprint (step 3), then few tickets are moved to next sprint (step 2). During this month we have updated the wiki templates for the public backlog items, please, check your content is consistent. Now there're fewer fields than before but still some content is missing or not correct. The templates have categories, please, check your team is using them properly. If anything, please, let me know. 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 thorsten.sandfuchs at sap.com Wed Mar 27 17:06:33 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 27 Mar 2013 16:06:33 +0000 Subject: [Fiware-wpa] IMPORTANT APs on YOU: Fwd: Agenda of the FI-PPP Architects Week In-Reply-To: <5152FCC1.6000908@tid.es> References: <514C278D.3050306@tid.es> <514C577F.5030800@tid.es> <5152FCC1.6000908@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD2F27@DEWDFEMB11A.global.corp.sap> Hi, Is there a share or something where we collect the needed slides? Or is there a common review process? Otherwise I would just bring them with me to the event... Best regards, /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: Mittwoch, 27. M?rz 2013 15:06 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT APs on YOU: Fwd: Agenda of the FI-PPP Architects Week Dear WPLs/WPAs, I reminder of the APs on your side regarding the Architects Week next week. I assume all WPLs are dealing with the presentations on the second day that relate to their chapters, according to what was explained in the minutes of the confcall on March 19, subsection "Description of FI-WARE 2nd Release and roadmap in April 3" on section "Architects Week in April": https://docs.google.com/document/d/15UOA2B7ot6FmNDXT1CmU5j_n9KiLl0BMksiymyhuGUQ/edit?usp=sharing There was also instructions regarding the first day, also further detailed in my email on March 22. Cheers, -- Juanjo On 22/03/13 14:07, Juanjo Hierro wrote: FYI, the agenda of the FI-PPP Architects Week. Please take care of the particular parts of the presentations you have to cover during the first two days: * WP10 (Testbed) team: prepare the presentation on "FI-WARE Testbed" planned on April 2, from 14:30 to 15:00 * Be pragmatic, focus on how to get access to the testbed, how to create accounts, gain access, etc * You don't need to go into the details about Cloud capabilities because they will described on April 3 * WP9 (Tools) team: prepare presentation regarding "FI-WARE Training" planned on April 2, from 15:00 to 15:30 * Give a view on how we plan the training sessions (live webinars, recording sessions, etc). I understand we cannot be too precise here, because it is work still under development, but I guess it would be nice to explain the approach and the goals we are looking for * Explain when we plan the live webinars to take place and how we will organize subscription to the webinars. We can discuss this off-line, but I would go for a similar approach to the one followed for the webinars of the 1st Release of FI-WARE. * WP10 (Testbed) team, SAP: prepare the presentation on "FI-WARE validation by UC projects": * Explain the current validation process (including rationale: we agreed in the AB not to make this a heavy-duty process) * Call for feedback from new UC projects about enhancements they may believe would be nice to introduce in the process * All WPLs: I understand that everything is clear regarding assignment of responsibilites for the items in the agenda of the second day. Please also take a look to the notes that were inserted in the minutes of our last WPLs/WPAs confcall where I provided some more details/insights. Hope this all helps to start rolling-out the ball. I will be on holidays next week but will connect from time (although I'll be in NY and therefore there will be 6 hours of difference). Let's keep the discussion open during these days. The regular monday WPLs/WPAs follow-up confcall next monday March 25 will take place and Miguel will chair it. 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: Agenda of the FI-PPP Architects Week Date: Fri, 22 Mar 2013 10:42:37 +0100 From: Juanjo Hierro To: Lakaniemi Ilkka , Cecchi Maurizio , Sjaak Wolfert , Williams Fiona , Fourdeaux Henri , "rod.franklin at kuehne-nagel.com" , "sergio.gusmeroli at txtgroup.com" , Christoph Thuemmler , Van Der Linden Pieter , Anastasius Gavras CC: Fatelnig Peter , "Arian.ZWEGERS at ec.europa.eu" , "Ragnar.Bergstrom at ec.europa.eu" , "Maria-Concepcion.ANTON-GARCIA at ec.europa.eu" , David Kennedy , "FI-PPP-Phase-2-Contacts at future-internet.eu" , Turkama Petra , Salo Juha , Schaffers Hans , Thomas Michael Bohnert , "jhierro >> \"Juan J. Hierro\"" Dear all, You can find a draft agenda of the FI-PPP Architects Week at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdE4teWs4UEpZa29zd0FRUmNTaFdxT2c&usp=sharing Thanks to Thomas M. Bohnert for his feedback and help finalizing it. We would like to hear your input, regarding what is the day where we can co-llocate the workshop dealing with your UC Trial project. Based on an initial request, we have placed cSpace in the workshop colocated in April 3. Please send your proposals to Thomas and me so that we can come with a final proposal. Please take into account that we have to meet a compromise, so we hope you can trust we will make a reasonable proposal. We may come back to you with more details about what info we are asking you to provide in the workshops dedicated to UC projects. We are discussing with Xifi what can be specific requests about info we would love to hear from you. 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 14/03/13 06:57, Juanjo Hierro wrote: Dear all, This mail is to announce that the FI-PPP Architecture Week for Phase 2 will take place in the following venue: Aula Magna in Building "A" School of Telecommunication Engineering (ETS Ingenieros de Telecomunicacion - ETSIT) Avenida Complutense # 30 University City 28040 Madrid Directions and hotels close to the venue can be found at: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/como-llegar.html%3FL%3Dttqltguphtgolkug&usg=ALkJrhi775kjxa4XFzatOQMya9dkNbh5wg Maps of the buildings associated to the ETSIT: http://translate.googleusercontent.com/translate_c?client=tmpg&depth=1&hl=en&langpair=es%7Cen&rurl=translate.google.com&u=http://www.etsit.upm.es/la-escuela/etsi-de-telecomunicacion/etsit-edificios.html&usg=ALkJrhi0WiJVR4jcJKDRa0prunRkZbTCig We had received many request to allow more than two people attending on behalf of phase 2 projects to the Architecture Week that will take place in Madrid, during April 2-5, that's why we have been late announcing the venue. Actually, the original venues were at a different location, but the meeting room was limited to 28-30 people maximum. Please note that coffee and lunch breaks will be scheduled during the week, but each attendee has to cover its own expenses. There is a restaurant and coffee bar in the same building of the venue with convenient prices. Note also that it might take a while to go from the University to the Airport, first walking to the metro stop "Ciudad Universitaria" (aprox. 1 Km) and then taking the metro to the Airport (you should take line 6 until "Nuevos Ministerios" and then line 8). You should take this into consideration when arranging the time of your return fligths on Friday. I will come later this week with a more detailed agenda, but the one already sent to you (see mail below) should be enough as far as logistics is concerned. 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 20/02/13 05:01, Lakaniemi Ilkka wrote: Dear all, As indicated yesterday, please find more detailed info about the FI-PPP Architecture Week on 2-5 April in Madrid. For any further details and info, please be in touch with Juanjo, Thomas B and me. The agenda of this meeting (draft): * April 2 (starting at 11:00am): FI-WARE to provide a thorough introduction on FI-WARE scope, goals, basic concepts, methodology, planning, available documentation, resources, tools, etc as well as a detailed description of the way the FI-PPP AB works. * April 3 morning: FI-WARE to provide detailed info about the FI-WARE Second Release, training planning, etc. * April 3 afternoon until April 5 17:00 CET: sequence of half-days workshops per UC Trial projects where UC Trials will present a sketch of their envisioned architecture, their current plans regarding usage of FI-WARE GEs, needs regarding setup of their trials, questions on which they need responses, etc. FI-WARE will provide feedback during these workshops that will help UC projects to program their planning of activities taking the most of FI-WARE. Note from FI-WARE: Technical managers/architects from UC Trial projects that are continuation of Phase 1 UC projects may skip the first day (i.e., people already engaged in phase 1 and part of the FI-PPP AB already). The rest of days will be mandatory for all UC Trial projects as well as FI-WARE and Xifi. People engaged in the FI-PPP for their first time must also attend the first day. It is expected that 2, maximum 3 people per project will attend. They should play a technical role in their project. Ideally, two of them should be the ones being appointed as members of the FI-PPP AB. Kind regards, Ilkka and Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Wed Mar 27 18:24:58 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 27 Mar 2013 17:24:58 +0000 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> <514AB78C.4030102@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD31DF@DEWDFEMB11A.global.corp.sap> Dear colleagues, I updated the new "FI-WARE citymap" as good as I could with relevant GEs, that I could gather from all over the places (quite a hassle to get them together). Please find the yEd files attached and a screenshot down below. Please update your content if I made some mistakes by yourself. I as well integrated the I2ND chapter, hopefully as envisioned. Any more comments? Now it should be ready to be uploaded to the fi-ware architecture page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture I think we should try to improve this page respectively - my proposal is: - Take some of the role descriptions (basically covering the roles on the diagram) out of the 3rd party innovation guide and copy & paste them to the architecture page https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf - Have at least one decent paragraph covering every chapter and this together with "short"-version on how it _really_ interrelates to other chapters (referencing the boxes on this city map) I know this information is partially "there" in the product vision, but there it is quite old and does not cover the things that we currently "see" evolving - so I think it is our "duty" to open the eyes of others :)) What do you think? Best, /Thorsten [cid:image002.png at 01CE2B18.30049820] From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Donnerstag, 21. M?rz 2013 08:58 To: Juanjo Hierro; Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: R: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear All, I share the opinion by Juanjo concerning the inclusion of I2ND GEs in the diagram: although I was not very active so far on this topic due to absolute lack of time, I started investigating how the GEs of this chapter could be inserted in the overall picture, which is not always easy if the result needs to be 'clear and compact'. The distinction between backend and local GEs, as well as the access devices, would be also an important 'message' to be conveyed through the diagram. I'll try as well to make some proposal with an I2ND update on the diagram, hopefully by today EOB, but most probably tomorrow morning. 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? 21 marzo 2013 08:32 A: Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. _______________________________________________ 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 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: image002.png Type: image/png Size: 119048 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v4.graphml Type: application/octet-stream Size: 83961 bytes Desc: fiware-cross-chapter_v4.graphml URL: From jhierro at tid.es Thu Mar 28 07:50:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 28 Mar 2013 07:50:50 +0100 Subject: [Fiware-wpa] Fwd: Invitation to the cSpace KOM - 08/03 and 09/03 - The Hague In-Reply-To: <2487F45015E27044B15ECEC170A407F00115A41E@INTMAIL03.es.int.atosorigin.com> References: <2487F45015E27044B15ECEC170A407F00115A41E@INTMAIL03.es.int.atosorigin.com> Message-ID: <5153E84A.4050601@tid.es> Hi all, Is there anyone who may be in the cSpace kick-off meeting in The Hague on behalf of FI-WARE ? 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: Invitation to the cSpace KOM - 08/03 and 09/03 - The Hague Date: Wed, 27 Mar 2013 17:54:44 +0100 From: Carlos Maestre Terol To: CC: , , , , , Dear Stefano, On behalf of the cSpace project I would like to invite you to our Kick-Off meeting (KOM) the 8th and 9th of April in The Hague, being the venue the headquarter of our coordinator, LEI-DLO, Wageningen UR. Attached you may find a final draft of the agenda, where point 5 is a short introduction to FI-WARE and the FI-PPP. We would be glad if you could give the presentation. Apologies for sending you the invitation so late, but we sent it to FI-WARE some time ago, asking for someone to join us, and got no answer. Have a nice week and Easter holidays, Carlos PS: As I will be next days on holidays, please, contact directly our coordinator, Sjaak (as CC), if you need further information about the event. Carlos Maestre Technical coordinator Manufacturing & Retail MRS Market Research & Innovation [cid:image002.gif at 01CCBF17.DE01E180] T +34 912065562 carlos.maestre at atosresearch.eu Albarrac?n 25 28037 Madrid Spain ------------------------------------------------------------------ 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. ------------------------------------------------------------------ ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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/gif Size: 78 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 816 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cSpace Kick-off meeting 2013-01-30-31-Agenda-v003.docx Type: application/octet-stream Size: 836432 bytes Desc: not available URL: From stefano.depanfilis at eng.it Thu Mar 28 10:52:22 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Thu, 28 Mar 2013 10:52:22 +0100 Subject: [Fiware-wpa] [Fiware-wpl] Fwd: Invitation to the cSpace KOM - 08/03 and 09/03 - The Hague In-Reply-To: <5153E84A.4050601@tid.es> References: <2487F45015E27044B15ECEC170A407F00115A41E@INTMAIL03.es.int.atosorigin.com> <5153E84A.4050601@tid.es> Message-ID: dear juanjo and all, i already did the presentation at finesce (20th march) and confirmed to give those at fitman (10th april) and fi-star (11th april). it would be great if this will be taken by somebody else ... :-) thank you in advance for your understanding. of course i can provide you the presentation i'm using. ciao, stefano 2013/3/28 Juanjo Hierro > Hi all, > > Is there anyone who may be in the cSpace kick-off meeting in The Hague > on behalf of FI-WARE ? > > 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: Invitation to the cSpace KOM > - 08/03 and 09/03 - The Hague Date: Wed, 27 Mar 2013 17:54:44 +0100 From: > Carlos Maestre Terol To: > CC: > , > , > , > , > , > > > Dear Stefano, > > > > On behalf of the cSpace project I would like to invite you to our Kick-Off > meeting (KOM) the 8th and 9th of April in The Hague, being the venue the > headquarter of our coordinator, LEI-DLO, Wageningen UR. > > > > Attached you may find a final draft of the agenda, where point 5 is a > short introduction to FI-WARE and the FI-PPP. We would be glad if you could > give the presentation. Apologies for sending you the invitation so late, > but we sent it to FI-WARE some time ago, asking for someone to join us, and > got no answer. > > > > Have a nice week and Easter holidays, > > Carlos > > > > PS: As I will be next days on holidays, please, contact directly our > coordinator, Sjaak (as CC), if you need further information about the event. > > [image: cid:image001.gif at 01CCBF17.DE01E180] > > *Carlos Maestre* > > > > Technical coordinator > > Manufacturing & Retail > > MRS Market > > > > Research & Innovation > > > > [image: cid:image002.gif at 01CCBF17.DE01E180] > > > > > > T +34 912065562 > > carlos.maestre at atosresearch.eu > > > > Albarrac?n 25 > > 28037 Madrid > > Spain > > > > ------------------------------------------------------------------ > 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. > ------------------------------------------------------------------ > > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its 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/gif Size: 78 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 816 bytes Desc: not available URL: From axel.fasse at sap.com Thu Mar 28 16:07:24 2013 From: axel.fasse at sap.com (Fasse, Axel) Date: Thu, 28 Mar 2013 15:07:24 +0000 Subject: [Fiware-wpa] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation In-Reply-To: <77A22C1085494D48B4018F06A40DB2C71C0A9E20@EX10-MB2-MAD.hi.inet> References: <5151381E.7080809@tid.es> <515138B4.4010900@tid.es> <77A22C1085494D48B4018F06A40DB2C71C0A9E20@EX10-MB2-MAD.hi.inet> Message-ID: Dear Javier, if you have not made any changes in the DoW of WP3, EAB ist included with a new role description in our WP3. Because of this, the Description of the Role, the Efforts, ? should be consistent. If you have any question or comments, please let me know. I will be on vacation for the next days and because of that I am not able to read my mails. In urgent cases, please contact Thorsten Sandfuchs. Best regards, Axel From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of JAVIER DE PEDRO SANCHEZ Sent: Mittwoch, 27. M?rz 2013 11:44 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: subsidies at tid.es Subject: Re: [Fiware-wpa] VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importance: High Dear all. Updating the DoW, it?s important to take in account that some partners have declared effort in task or WP and they withdraw from them now. So, if a partner has declared effort, it can?t be deleted from the task/WP where it was involved. You?ll need to update its role, but it can be deleted. Please, in case I have deleted EAB in the word file I have sent to you, reject and update it. Please find enclosed by WP, the effort declared by partner I have so far. [cid:image001.png at 01CE2BCE.4E5713F0] [cid:image002.png at 01CE2BCE.4E5713F0] [cid:image003.png at 01CE2BCE.4E5713F0] [cid:image004.png at 01CE2BCE.4E5713F0] [cid:image005.png at 01CE2BCE.4E5713F0] [cid:image006.png at 01CE2BCE.4E5713F0] [cid:image007.png at 01CE2BCE.4E5713F0] [cid:image008.png at 01CE2BCE.4E5713F0] [cid:image009.png at 01CE2BCE.4E5713F0] [cid:image010.png at 01CE2BCE.4E5713F0] BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 27 de marzo de 2013 10:17 Para: 'fiware-wpl at lists.fi-ware.eu'; 'fiware-wpa at lists.fi-ware.eu' CC: JUAN JOSE HIERRO SUREDA; 'subsidies at tid.es' Asunto: RE: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importancia: Alta Dear all, some of you are telling me that you need more time because you need to contact with the partner involved in your WP. It is reasonable. So, please, provide the update DoW by April 2nd, 2013. Please don?t forget to activate the control change of the document. Thank you very much for your contribution. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 26 de marzo de 2013 9:00 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JUAN JOSE HIERRO SUREDA; subsidies at tid.es Asunto: RE: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Importancia: Alta Dear all. Please find attached one zip file for each WP. They are an extract from the current updated DoW of the amendment 4 to be reviewed and modified if needed by each WPL. I really need your prompt reaction in order to integrate all the changes and send the updated DoW to Officer tomorrow. Please, each WPL has to reply with his reviewed DoW today. Please review: Effort by task for each partner. (excel file) Role for each partner (word file, according with excel file) Description of each task. (word file) Thank you for understanding and for your contribution. BR Javier. De: JUAN JOSE HIERRO SUREDA Enviado el: martes, 26 de marzo de 2013 6:57 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: JAVIER DE PEDRO SANCHEZ Asunto: Fwd: Re: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Hi all, A first reaction from Arian to the reallocation of PMs and my response to him. I decided to respond quickly to avoid justification of further delays on the side of the Commission. If you believe that I should have added something in my response or you believe I said something wrong, please let me know. 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: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Date: Tue, 26 Mar 2013 06:54:38 +0100 From: Juanjo Hierro To: CC: , , , , "jhierro >> \"Juan J. Hierro\"" Dear Arian, Thanks for your quick response. My response between lines of your message below ... On 25/03/13 19:26, Arian.ZWEGERS at ec.europa.eu wrote: Dear Juanjo, The overview of changes presented is very well done and clear, and I don't have any issues with them, except for the points below. I don't care that much about shifting PMs and who gets what. Here the consortium has apparently bound itself to all kind of weird pre-existing agreements anyway, not using the flexibility offered by the grant agreement. I don't know exactly what you mean, but certainly the consortium has not bound itself to any weird agreement ... I rather see it the other way around ... the consortium has been flexible and agile to reallocate efforts and roles of the partners so that each partner has concentrated its efforts in less things (thus increasing the efforts in the things they have decided to concentrate on). I rather believe this is a positive thing. I would be much more worried if we had adopted an approach where partners were participating in many things, with no significant effort in any. One of the things that I believe is rather good in the way FI-WARE is organized is that it is like 7 IPs (one per technical chapter) but with the big difference that if you look at each of these IPs, there is a limited number of key partners (4-6). There is also a clear role of partners within each chapter, each partner typically bound to the implementation of some GE in the chapter. All of this will help, imho, in achieveing good results. Having said that, the thing to avoid is that industry withdraws and academia gets more funding. That is the trend here, with industry reducing its involvement with 640k and academia/research institutes increasing with 640k. I understand there is no choice because industry is not willing/able to do more, but it is against the spirit of the industry leadership in FI-WARE/FI-PPP. And frankly, it looks very bad on EU industry. The industrial partners has taken the decisions consciously and I honestly believe that the situation is not as bad as it may be considered in a very first approach: * There were only two GEs for which the implementation has been transferred to an academia partner: * Ericsson was originally planned to contribute the implementation of the IoT Gateway Device Management GE in the IoT chapter and, while it was agreed with them that they would support an ETSI M2M compliant interface, they were only able to commit to support this interface in their product for the 3rd Release of FI-WARE. When Ericsson withdrew, we found here an opportunity to find someone who could contribute an ETSI M2M implementation already rather than to be able to develop it from the start. This was Franhoufer. This made us feel more confident to keep our initial plans to deliver an Architecture which already considered support to the relevant ETSI M2M standard. There were not many other options from any industry partner in Europe so that's why. * Ericsson was also originally planned to contribute an implementation of the Store GE in the Apps Chapter (part of the Business Framework). Here, we decided to go for UPM basically for two reasons. First because they had an asset (WireCloud) part of which (WireCloud's catalogue) could evolve to become the Store we were looking for in reasonable time. Second because they were committed to contribute their implementation as open source. Here, we found that elivering the code of the Store as open source could be something that would give FI-WARE better chances to make impact: there are many proprietary commercial stores out there ... but none is open source so we expect this will call the attention of third parties. * The rest of new PMs allocated to academia partners do not correspond to transference of the responsibility to implement FI-WARE GEs: * PMs transferred from Ericsson to UPM in WP9 (Tools) correspond to the implementation of the FI-WARE Catalogue portal: this is not a FI-WARE GE in itself nor anything that will be used to setup and operate FI-WARE Instances. It will not be commercialized standalone so it was a matter of finding who could make a good job and the UPM had proved they can develop a good implementation of the FI-WARE Catalogue. The UPM also committed to implement it as open source and that is also relevant to ensure sustainability. * When NSN-Germany withdrew from WP5 (tools) we found out that finding a replacement for them was not rather critical so that we may use the corresponding PMs/funding in reinforcing other tasks in other WPs. We finally decided to transfer the PMs, initally allocated to NSN-Germany in the IoT chapter, to UPM because a) it would reinforce the work they were already doing with the Cloud portal (to be delivered as open source and contributed to the OpenStack Community), b) it allowed us to assign the UPM the task of designing and maintaining the look&feel of FI-WARE web portals (since they were in charge of the most significant one in FI-WARE, it sounded like it made sense) and c) it allowed us to assign the UPM to implement some pieces of the FI-WARE Testbed/OIL portal that were not initially foreseen as needed. There was unanimity in considering that the UPM was doing a great job regarding the Cloud portal so it was like natural to select them. * Some new PMs were assigned to UniRoma because it was found that the amount of PMs they had currently assigned was not enough for them to carry out their assigned tasks. This is just a first quick response to your concern. A more elaborated response can be provided if needed. Please note that I care more about changes in the DoW wrt tasks/activities to be carried out. Large changes in efforts without any change in the task description (e.g. the iMinds addition in WP3) cannot be correct. We prepared a new description of WP3 as a result of their inclusion as new beneficiaries in amendment 3 ... Is there anything you are still missing ? If it was just an example, be sure we understand that we should provide new description of tasks/WPs where major changes are incorporated. We are here just anticipating the figures, so that you can approve them, subject to proper description in an amendment of the DoW. Then, what is most important is what happens with the contributions from the withdrawing partners, NSN-FI and EAB. Just a clarification: NSN-FI withdraw without having made any relevant contribution. I believe you refer to NSN-H (Hungary) who was indeed playing the role of WPA in the IoT chapter and were the ones that were contributing the Cumulocity product as implementation of the IoT Backend Device Management GE ... What happens with Ericsson's Service Composition - Ericsson Composition Engine (ECE) What happens with Ericsson's Gateway Device Management GE - Ericsson IoT Gateway In a previous email (19 Nov 2012), you concluded (for the ECE): "So the problem here is not about sustainability beyond the FI-PPP (which Ericsson states would be provided) but inside the FI-PPP ..." Will they remain available to FI-WARE? Under what conditions? If nothing remains available, what does that mean for their contribution to FI-WARE? Will these be replaced? Ericsson was contributing the implementation of two GEs in WP3 (Apps Chapter): the Store GE, part of the Business Framework, and the ECE GE. The amount of PMs/funding assigned to Ericsson for contributing these two assets and evolve them was fair because Ericsson was relying on existing and mature assets. When Ericsson withdrew from WP3, we couldn't find any partner that may provide an asset for the Store GE so therefore we had to plan its development. Then we found that the whole amount of funding assigned to Ericsson was necessary to carry out that development and we were lucky because we could leverage on the WireCloud's catalogue for that purpose. Since there were already other service composition tools already, we concluded that it was not critical to find a replacement for the ECE. Same questions for NSN-FI. I understand they were in charge of the GE "Backend Device Management"?? And they contributed an asset called "Cumulocity". So same questions as above. The IoT Backend Device Management GE will be implemented through the IDAS DCA product contributed by Telefonica. This product essentially replaces the Cumulocity product that was planned to be contributed by NSN. Specific questions: 1) What does the underlined text mean in the sentence "Withdrawal of Ericsson from WP5. EAB has 20 PM in DoW and it has declared 3,34 PM until M18, so it transfers 16 PM to FRAUNHOFER because they have to assume Advanced Connectivity GEs with ETSI-M2M interface and will be involeved in the project at the beginning of April 2013!" Well, we are simply saying that in the case of Fraunhofer, they will start working in the IoT chapter since beginning of April 2013 ... Of course, Franhoufer has been working on the project since its beginning, but in different WPs. 2) What does the following sentence mean? "TRDF-P finished at 31-12-2012. People moved to TRDF." TRDP is no longer a third party? I hope Javier de Pedro, in copy, can reply this part since I'm not so much aware of what third party is involved in each case. For me, all of them are Thales ... Finally, are you going to ask an amendment for the Electronic-only signature and transmission of Form C (see attachment)? Again, I would ask Javier de Pedro to answer this part. Cheers, -- Juanjo Best regards, Arian. PS. I am kind-of allergic to statements like your "No early response...", knowing that the only deadlines I'm bound to are the ones in the grant agreement? -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, March 22, 2013 9:06 AM To: ZWEGERS Arian (CNECT) Cc: CNECT-ICT-285248; subsidies at tid.es; Miguel Carrillo; Javier de Pedro Sanchez Subject: VERY IMPORTANT: amendment 4 of the FI-WARE DoW dealing with PMs reallocation Dear Arian, Once we have finalized amendment 3 of our DoW, we should open a new amendment dealing with fixing all PMs reallocation that were pending (some of which pending since July last year). As already announced in our mail on January 20th this year, the situation is critical regarding some of these PMs reallocation, particularly dealing with the ability to handle withdrawal of several partners. All this PMs reallocation have been agreed among the partners at PCC (Project Coordination Committee), WPLs/WPAs and General Assembly level. We believe that is is critical to close this amendment 4 before end of April as to allow a reporting of costs for the 2nd period that is aligned with an approved DoW. Please find enclosed a spreadsheet which summarizes the changes already implemented in amendment 3 as well as changes proposed in amendment 4. Changes being proposed for amendment 4 are summarized in the sheet titled "Changes (amendment 4)". There is a final picture of PMs allocation to tasks for each WP as well as impact in figures (overall funding is kept the same). Consumption of allocated PMs have taken place since start of the 2nd reporting period and, in the case of partners withdrawing the consortium, since a decision was taken regarding what partner was going to take over their responsibilities. We will soon send you a draft of the DoW that will incorporate the changes summarized here. We will kindly ask you to send a response to this mail with your agreement to the proposed PMs reallocation in advance to approval of the DoW amendment itself which may take more time. That would give the existing partners, overall those taking the responsibility to take over the tasks from withdrawing partners, the necessary security to keep their investments they have been making so far. No early response will be taken as acknowledge and acceptance of this proposed PMs reallocation. We will rather appreciate your help in moving this forward. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: 42494 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 32668 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 38556 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 33399 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 43070 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 38777 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 33544 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 47338 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 40355 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 48357 bytes Desc: image010.png URL: From thorsten.sandfuchs at sap.com Thu Mar 28 21:32:48 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 28 Mar 2013 20:32:48 +0000 Subject: [Fiware-wpa] [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD31DF@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> <514AB78C.4030102@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD66460FD31DF@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD5292@DEWDFEMB11A.global.corp.sap> Dear colleagues thanks all your input - I integrated everything in a v5 (attached) and stored it as fiware-citymap.jpg (93% quality) and uploaded it to the wiki. Now it comes to the foreseen changes, which I thought I prepare them on a "V2"-version of the Architecture prior to "release". Find them on: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture_V2 Please review the text I put on your chapter on this page - I basically compiled it out of your texts on your chapter-specific pages, but there might be errors now or you would subsume your chapter differently? I guess we move the page from "V2" to the main page within the next week. Happy Easter holidays, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 27. M?rz 2013 18:25 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: RE: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear colleagues, I updated the new "FI-WARE citymap" as good as I could with relevant GEs, that I could gather from all over the places (quite a hassle to get them together). Please find the yEd files attached and a screenshot down below. Please update your content if I made some mistakes by yourself. I as well integrated the I2ND chapter, hopefully as envisioned. Any more comments? Now it should be ready to be uploaded to the fi-ware architecture page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture I think we should try to improve this page respectively - my proposal is: - Take some of the role descriptions (basically covering the roles on the diagram) out of the 3rd party innovation guide and copy & paste them to the architecture page https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf - Have at least one decent paragraph covering every chapter and this together with "short"-version on how it _really_ interrelates to other chapters (referencing the boxes on this city map) I know this information is partially "there" in the product vision, but there it is quite old and does not cover the things that we currently "see" evolving - so I think it is our "duty" to open the eyes of others :)) What do you think? Best, /Thorsten [cid:image001.png at 01CE2BFB.01518B30] From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Donnerstag, 21. M?rz 2013 08:58 To: Juanjo Hierro; Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: R: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear All, I share the opinion by Juanjo concerning the inclusion of I2ND GEs in the diagram: although I was not very active so far on this topic due to absolute lack of time, I started investigating how the GEs of this chapter could be inserted in the overall picture, which is not always easy if the result needs to be 'clear and compact'. The distinction between backend and local GEs, as well as the access devices, would be also an important 'message' to be conveyed through the diagram. I'll try as well to make some proposal with an I2ND update on the diagram, hopefully by today EOB, but most probably tomorrow morning. 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? 21 marzo 2013 08:32 A: Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. 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-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology 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! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ 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. _______________________________________________ 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 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.png Type: image/png Size: 119048 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v5.graphml Type: application/octet-stream Size: 76812 bytes Desc: fiware-cross-chapter_v5.graphml URL: From jhierro at tid.es Sun Mar 31 23:24:51 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 31 Mar 2013 23:24:51 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs confcall on April 1st - Cancelled Message-ID: <5158A9A3.80906@tid.es> Hi all, For the avoidance of doubt, our joint WPLs/WPAs confcall tomorrow (April 1st) will be cancelled due to holidays in many countries. Regarding the presentations you are preparing for the morning of April 3, don't hesitate to drop an email to solve any doubt. 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 Sun Mar 31 23:29:35 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Sun, 31 Mar 2013 21:29:35 +0000 Subject: [Fiware-wpa] Canceled: Joint WPLs/WPAs follow-up confcall (Part I) Message-ID: <936DECD07EB54B4BAA44E7B823EC894150FF34F2@EX10-MB2-MAD.hi.inet> Joint WPLs/WPAs follow-up confcalls are splitted into two parts. This is the first one and we will always stick to the end time. Topics not addressed in this slot will be treated in the slot of the afternoon. The slot in the afternoon will be used to also address Technical-Architecture issues. 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: 3795 bytes Desc: not available URL: From jhierro at tid.es Sun Mar 31 23:29:39 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Sun, 31 Mar 2013 21:29:39 +0000 Subject: [Fiware-wpa] Canceled: Joint WPLs/WPAs follow-up confcall (Part II) Message-ID: <936DECD07EB54B4BAA44E7B823EC894150FF352D@EX10-MB2-MAD.hi.inet> Joint WPLs/WPAs follow-up confcalls are splitted into two parts. This is the second one and we will always stick to the end time. Topics not addressed in the first slot will be treated in this slot of the afternoon. This slot will also be used to also address Technical-Architecture issues. 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: 3792 bytes Desc: not available URL: