From jhierro at tid.es Fri Nov 1 12:16:50 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 01 Nov 2013 12:16:50 +0100 Subject: [Fiware-wpl] Dates for the month 30 review and rehearsal Message-ID: <52738DA2.5080008@tid.es> Hi all, Looking at the results of the doodle poll, I will propose the following: * 1 full-day review meeting: Wednesday December 18th, starting at 09:00am * Start of reharsal meeting: Monday December 16th, starting at 13:00 * End of rehearsal meeting: Tuesday December 17th (who knows when :-) Unless I see any objection, I will send the official email to Arian end of today. 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 FI-PPP Architecture Board chairman 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 depa at eng.it Fri Nov 1 13:40:29 2013 From: depa at eng.it (depa at eng.it) Date: Fri, 1 Nov 2013 12:40:29 +0000 Subject: [Fiware-wpl] R: Dates for the month 30 review and rehearsal In-Reply-To: <52738DA2.5080008@tid.es> References: <52738DA2.5080008@tid.es> Message-ID: <1376646162-1383309608-cardhu_decombobulator_blackberry.rim.net-755589364-@b3.c14.bise7.blackberry> Dear Juanjo, Perhaps we should try to start the rehearsal as earlier as possible on monday .... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Fri, 01 Nov 2013 12:16:50 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Dates for the month 30 review and rehearsal _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From jhierro at tid.es Fri Nov 1 14:01:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 01 Nov 2013 14:01:02 +0100 Subject: [Fiware-wpl] R: Dates for the month 30 review and rehearsal In-Reply-To: <1376646162-1383309608-cardhu_decombobulator_blackberry.rim.net-755589364-@b3.c14.bise7.blackberry> References: <52738DA2.5080008@tid.es> <1376646162-1383309608-cardhu_decombobulator_blackberry.rim.net-755589364-@b3.c14.bise7.blackberry> Message-ID: <5273A60E.5060109@tid.es> 13:00 is just the mandatory time. I'll try to be there (at whatever office) at 11:30 ... this is the earliest I can arrive travelling that day. BTW, I'll try to book Telefonica's office for the reharsal. 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 FI-PPP Architecture Board chairman 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 01/11/13 13:40, depa at eng.it wrote: Dear Juanjo, Perhaps we should try to start the rehearsal as earlier as possible on monday .... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-wpl-bounces at lists.fi-ware.eu Date: Fri, 01 Nov 2013 12:16:50 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Dates for the month 30 review and rehearsal _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 4 11:06:46 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 04 Nov 2013 11:06:46 +0100 Subject: [Fiware-wpl] Link for today Message-ID: <527771B6.6000603@tid.es> https://docs.google.com/document/d/1AeeIb7kUvevbYPCGHq0nPInyOC26YiZZcVlPlr9zF5M/edit?pli=1# -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Nov 4 11:59:16 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Nov 2013 11:59:16 +0100 Subject: [Fiware-wpl] Fwd: FI-WARE Project extension In-Reply-To: <5274F26A.8050200@tid.es> References: <5274F26A.8050200@tid.es> Message-ID: <52777E04.6030001@tid.es> Hi, This is the email with questions about FI-WARE project extension that I sent to Arian. Cheers, -- Juanjo -------- Original Message -------- Subject: FI-WARE Project extension Date: Sat, 02 Nov 2013 13:39:06 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: jhierro >> "Juan J. Hierro" Dear Arian, As already commented to Jesus and you, we have opened a thread of discussion within FI-WARE about an extension of 4 months to the project in line with the recommendation given in the last review report. In order to give a definitive answer, some partners are asking for some elaborated answer to the following questions: 1. What kind of activities are foreseen during the extended period ? Would they only be related to support, dissemination and training ? 2. Will a given FI-WARE GEi owner be able to chose between a) closing its contribution to FI-WARE GE Open Specifications and its FI-WARE GEi development activities as already planned in the DoW (i.e., delivering updated GE Open Specifications as well as GEi software, testing plans and related documentation in month 33, that is end of January) or b) delay them to be in month 36 ? Ability to choose would be certainly useful, because some GEi owners can adapt to the extension provided that a delay in deliverables is approved, while others can live with the extension but provided that they can close their activities in the dates originally planned in the DoW. Telefonica, as coordinator, doesn't see any problem allowing a partner to close its activities as planned in the DoW. Just to avoid any burden we most probably would submit all the mentioned deliverables in month 36 (despite some partners would submit them internally at month 33) 3. Could month 36 be preserved as the date for submission of deliverables in WP11 (exploitation) ? 4. Could month 40 be defined as the date for submission of deliverables linked to WP12 (communication, collaboration and dissemination) ? 5. Can partners assuming a WPL or WPA role discontinue that role in month 36 if another partner is ready to take over their role until the end of the project ? Could you please answer these questions ? This and any other information that may be helpful to understand what the extension will mean in terms of workload would be certainly helpful to reach an agreement within the consortia as we would love to during this upcoming week. 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 FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 4 12:06:19 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 04 Nov 2013 12:06:19 +0100 Subject: [Fiware-wpl] Fwd: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE In-Reply-To: <50406C77.6030600@tid.es> References: <50406C77.6030600@tid.es> Message-ID: <52777FAB.20204@tid.es> Dear all, As requested in the ongoing meeting, I resend you the submission of the "3rd Party innovation" document that we created and delivered last year. Of course, this is on the submission cockpit (scroll down!) as always * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit Best regards, Miguel -------- Mensaje original -------- Asunto: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE Fecha: Fri, 31 Aug 2012 09:49:11 +0200 De: JUAN JOSE HIERRO SUREDA Para: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , renaud.difrancesco at eu.sony.com , irena.pavlova at isoft-technology.com CC: MIGUEL CARRILLO PACHECO , JOSE JIMENEZ DELGADO , JUAN JOSE HIERRO SUREDA Dear Arian, dear reviewers, This is the official submission of the following deliverable, publicly available from at: https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf * D2.5.1 Third party innovation enablement in FI-WARE Both documents are on our documentation repository (see previous links). Should you have any comments or suggestions, do not hesitate to contact us. Kind 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) 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 Richard.Egan at uk.thalesgroup.com Mon Nov 4 11:59:11 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Mon, 4 Nov 2013 10:59:11 +0000 Subject: [Fiware-wpl] FI-WARE Progress Report - THALES input (to your WP Progress Report) References: Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA99A12F31E@THSONEP02CMB01P.one-02-priv.grp> ..and now with the attachment Richard From: EGAN Richard Sent: 31 October 2013 11:03 To: BISSON Pascal; fiware-wpl at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; SIEUX Corinne; CHALLAMEL Remi; CHATEL Pierre; BESSON Lionel; LOPEZ RAMOS Mario; Juanjo Hierro; JAVIER DE PEDRO SANCHEZ; Stefano.depanfilis at eng.it; GASPARD Lucie Subject: RE: FI-WARE Progress Report - THALES input (to your WP Progress Report) Dear WP Leads (especially WP10, 11 & 12) I have attached an updated version of the Thales contribution with some more details. Tracked changes were used so the updates are visible. Richard Richard Egan Technical Manager, Research & Technology Thales UK Worton Drive, Reading, Berkshire, RG2 0SB www.thalesgroup.com/uk Tel: +44 (0)118 923 8375. Mob: +44 (0)79 71 32 99 28. Fax: +44 (0) 118 923 8399. e-mail: richard.egan at uk.thalesgroup.com From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: 26 October 2013 10:45 To: fiware-wpl at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; SIEUX Corinne; CHALLAMEL Remi; EGAN Richard; CHATEL Pierre; BESSON Lionel; LOPEZ RAMOS Mario; Juanjo Hierro; JAVIER DE PEDRO SANCHEZ; Stefano.depanfilis at eng.it; GASPARD Lucie Subject: FI-WARE Progress Report - THALES input (to your WP Progress Report) Importance: High Dear WP Lead colleagues, Please find attached to this email the Thales wide input - as per today - to Progress Report M25-M30. This in order for you to use and take out of it what needs to go for Thales at the level of the Progress Report of the WP you lead. FYI I would be on vacation next week but Daniel (in cc) would replace me. As for the missing contrib. at WP4 and WP3 level I count on Lionel/Mario and Pierre as participants to these WPs to send them to WP4 Lead (Alex) and WP3 Lead (Markus) asap and cc me/Daniel/Corinne. Best Regards, Pascal PS: I put Thales colleagues involved in your WP in cc of that email for their information also records.s -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - M25-M30 Rreporting per WP THALES 2013-10-24-update1.doc Type: application/msword Size: 271360 bytes Desc: FI-WARE - M25-M30 Rreporting per WP THALES 2013-10-24-update1.doc URL: From mev at tid.es Mon Nov 4 16:44:53 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 04 Nov 2013 15:44:53 +0000 Subject: [Fiware-wpl] Agile: Sprint planning for S3.2.2; Backlog: hot topics (URGENT AND IMPORTANT) Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890EA4BA@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you that we're on sprint planning time for S3.2.2 until day 7, when this activity will be finished. Please, proceed to create or update functional and work items for this sprint. Items not finished last sprint are now moved to the current sprint, if needed, or re-scheduled. Please, be aware of the hot topics which need you to create/update the necessary Functional or Work Items to be addressed properly. 1. Work items for the catalogue. The keyword in the reference for this topic will be Catalogue. 2. Work items for the training material. The keyword in the reference for this topic will be TrainingMaterial. 3. Functional or Work items to deal with Lutz Report. These items will not have keyword on the reference but a label in the description: Source = Lutz Schubert Report Please, be aware I'll be generating activity reports on these topics soon with the purpose to provide needed evidence and support for our management team attending the review meeting next month in Brussels. As you had already imagined, I'll search for the keywords or labels previously pointed out to create the activity reports Regarding the Sprint 3.2.1 closing, the dashboard show the burn down diagrams, which give perspective on how the different chapters did. I'll be analysing deeper with the corresponding WP Leader why some chapters are not doing well yet. In general, let me remind you that it's very important that reducing the errors to zero as well as we get the agile dynamic as soon as possible. Dashboards: https://forge.fi-ware.eu/docman/view.php/27/2992/FIWARE.backlog.apps.dashboard.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2993/FIWARE.backlog.cloud.dashboard.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2996/FIWARE.backlog.iot.dashboard.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2994/FIWARE.backlog.data.dashboard.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2995/FIWARE.backlog.i2nd.dashboard.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2997/FIWARE.backlog.security.dashboard.20131031.xlsx Reviews: https://forge.fi-ware.eu/docman/view.php/27/2998/FIWARE.backlog.apps.review.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/2999/FIWARE.backlog.cloud.review.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/3002/FIWARE.backlog.iot.review.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/3000/FIWARE.backlog.data.review.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/3001/FIWARE.backlog.i2nd.review.20131031.xlsx https://forge.fi-ware.eu/docman/view.php/27/3003/FIWARE.backlog.security.review.20131031.xlsx If you wish to see how backlog are evolving, have a look at the link bellow: https://forge.fi-ware.eu/docman/view.php/27/2857/Backlog-Improvement-monitoring.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Nov 4 18:42:06 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 04 Nov 2013 18:42:06 +0100 Subject: [Fiware-wpl] Fwd: RE: Date for FI-WARE month 30 review In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D076F755F@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D076F755F@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <5277DC6E.1030207@tid.es> FYI, -- 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 FI-PPP Architecture Board chairman 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: Date for FI-WARE month 30 review Date: Mon, 4 Nov 2013 17:26:38 +0000 From: To: Dear Juanjo, Wed Dec 18 is hereby confirmed. It's a full day meeting, start 9.00 hours with the reviewers, 9.30 hours with the consortium, closing at 17.00 hours (incl informal feedback). Best regards, Arian From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Saturday, November 02, 2013 12:08 PM To: ZWEGERS Arian (CNECT) Cc: jhierro >> "Juan J. Hierro" Subject: Date for FI-WARE month 30 review Hi Arian, This is to confirm that, after consultation with the WPLs, the best date for the month 30 review would be Wednesday December 18th. This would allow us to plan for a reharsal the previous two days. Please confirm whether this date would also work for you so that partners can arrange the flights, etc. We assume the review meeting will take place in Brussels. I managed to get a special approval for attending this meeting. We assume, based on emails previously exchanged with you, that this will be a full day review meeting. Please let us know what would be the more suitable time for you to start and close the review meeting. Thanks in advance 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 FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Wed Nov 6 12:56:45 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 06 Nov 2013 11:56:45 +0000 Subject: [Fiware-wpl] Agile dynamic: Sprint Planning 3.2.2- current status - deadline tomorrow Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890EA9E9@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you that the sprint planning will be finished tomorrow. In order to know its current state, find below the dashboard snapshost. Please, be aware, there's need to deliver the backlog deliverable to the EC. So you'll find the dashboards improved. Let me some comments: Apps: 60 items scheduled - Good; All enablers have backlog with content. There are some inconsistent or outdated status; they are marked in red. I'd appreciate they all would be fixed. Cloud: 57 items scheduled - Good but missing content But there are some enablers: ObjectStorage, ScalabilityMgr and ServiceManager whose backlogs are empty. There are some inconsistent or outdated status; they are marked in red. I'd appreciate they all would be fixed. IoT: 13 items scheduled - missing content Most enablers don't have any content yet: BackendDeviceManagement, GatewayProtocolAdapter, GatewaySecurity, IoTDiscovery, ProtocolAdapterCOAP, ProtocolAdapterEPC, ProtocolAdapterZPA Once the previous comment is addressed, I'd also appreciate outdated states and inconsistencies were fixed. Data: 105 items scheduled - Very Good; All enablers have backlog with content. There are some inconsistent or outdated status; they are marked in red. I'd appreciate they all would be fixed. I2ND: 82 items scheduled - Very Good (considering there're only 4 enablers) All enablers have backlogs with content There are inconsistent or outdated status; they are marked in red. I'd appreciate they all would be fixed. Special call to CDI enabler to fix the many items in red. Security: 31 items scheduled - missing content There are enablers with empty backlogs: DataHandling, DigitalSelf, One-IDM, There are inconsistent or outdated status; they are marked in red. I'd appreciate they all would be fixed I'd appreciate cooperation to fix the issues identified. Please Alex, Thierry and Pascal, I think your chapters require more attention, specially IoT. Apps: https://forge.fi-ware.eu/docman/view.php/27/3006/FIWARE.backlog.apps.dashboard.20131106.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3007/FIWARE.backlog.cloud.dashboard.20131106.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3010/FIWARE.backlog.iot.dashboard.20131106.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3008/FIWARE.backlog.data.dashboard.20131106.xlsx I2nd: https://forge.fi-ware.eu/docman/view.php/27/3009/FIWARE.backlog.i2nd.dashboard.20131106.xlsx Security: https://forge.fi-ware.eu/docman/view.php/27/3011/FIWARE.backlog.security.dashboard.20131106.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.bareno at atos.net Wed Nov 6 18:47:43 2013 From: juan.bareno at atos.net (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Wed, 6 Nov 2013 18:47:43 +0100 Subject: [Fiware-wpl] EXPLOITATION: Status of the New Confidential Exploitation Plans delivered so far Message-ID: Dear Colleagues Please find here enclosed below the status of the New Confidential Exploitation Plans delivered so far Be aware that the deadline has expired, and we have just this week to deliver all, please inform about the status of the missing ones before to confirm with our PO that all the new version sent has been effectively received Best Regards Juan o TID- New version Sent o SAP- No update o IBM- New version Sent o FT- ?? o DT- ?? o TI- New version Sent o THALES- New version Sent o ENG- ?? o INTEL- New version Sent o Atos- New version Sent o SIEMENS- New version Sent o NOKIA SIEMENS NETWORKS- New version Sent o ALCATEL (ALU-D)- New version Sent o TECHNICOLOR- ?? o NEC- New version o INRIA- New version Sent 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 IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Juan Bare?o Guerenabarrena Sent: mi?rcoles, 30 de octubre de 2013 18:19 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); fiware-standardization at lists.fi-ware.eu; 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu); ESTANISLAO MA FERNANDEZ GONZALEZ-COLA?O (emfgc at tid.es); Amon, Peter (p.amon at siemens.com); laura pucci (laura.pucci at eng.it); Andrea Manieri (Andrea.Manieri at eng.it); 'Davide Dalle Carbonare' (davide.dallecarbonare at eng.it); Bettina.Lehmann at telekom.de; Hans.Einsiedler at telekom.de; Alex Glikson (GLIKSON at il.ibm.com); Yaron Wolfsthal (WOLFSTAL at il.ibm.com); 'thierry.nagellen at orange.com' (thierry.nagellen at orange.com); pierangelo.garino at telecomitalia.it; Banniza, Thomas-Rolf (Thomas-Rolf) (thomas-rolf.banniza at alcatel-lucent.com); Wuenstel, Klaus (Klaus) (klaus.wuenstel at alcatel-lucent.com); BISSON Pascal (pascal.bisson at thalesgroup.com); GIDOIN Daniel (daniel.gidoin at thalesgroup.com); Seidl, Robert (NSN - DE/Munich) (robert.seidl at nsn.com); Heijnen Henk (henk.heijnen at technicolor.com); 'Varga, Jozsef (NSN - HU/Budapest)'; Ernoe.Kovacs at neclab.eu; 'Kennedy, John M'; 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; 'koen.casier at intec.ugent.be' Cc: Nuria De-Lama Sanchez (nuria.delama at atos.net); Lindsay Frost (Lindsay.Frost at neclab.eu); Javier de Vicente (javier.devicente at futuranetworks.com); Miguel Carrillo (mcp at tid.es); JAVIER DE PEDRO SANCHEZ (jdps at tid.es) Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Exploitation Dear Colleagues Please find enclosed the current version of the periodic report for your review. Each partner should fulfill its participation in each Task 1. 11.1 Market Analysis- nothing new since the last M24 Deliverable 2. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 and the Terms and Conditions fixing 3. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings 4. 11.4 Standardization- Completed by Lindsay 5. 11.5 Community Building- Completed by Javier I miss more inputs on the 11.2 Exploitation plan regarding our new confidential exploitation plan and the fixing of Terms and conditions, as for example Thales and TI define I kindly ask the you to send me any feedback and/or comments no later than tomorrow, Thursday 31st, at 16:00 CET, thanks. Br Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: Juan Bare?o Guerenabarrena Sent: jueves, 17 de octubre de 2013 16:41 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); fiware-standardization at lists.fi-ware.eu; 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: Nuria De-Lama Sanchez (nuria.delama at atos.net); Lindsay Frost (Lindsay.Frost at neclab.eu); Javier de Vicente (javier.devicente at futuranetworks.com); Miguel Carrillo (mcp at tid.es); JAVIER DE PEDRO SANCHEZ (jdps at tid.es) Subject: FW: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Dear Exploitation Colleagues 1. Progress report: request for contributions 2. Periodic Report M30 starts on May 2013 (M25) and ends on October 2013 (M30). 3. Each partner fulfill its participation in each Task a. 11.1 Market Analysis- nothing new since the last M24 Deliverable b. 11.2 Exploitation- The Individual Confidential Exploitation Plans after the review and the ones requested for M30 c. 11.3 Regulatory- nothing new since the last M24 Deliverable. Maybe the CONCORD meetings d. 11.4 Standardization- Lindsay?? e. 11.5 Community Building- Javier?? 4. Deadline next Friday 25th October Thanks for your support 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 IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address juan.bareno at atos.net .The former @atosresearch.eu address will be cancelled soon From: JAVIER DE PEDRO SANCHEZ [mailto:jdps at tid.es] Sent: martes, 15 de octubre de 2013 15:56 To: Juan Bare?o Guerenabarrena Cc: subsidies at tid.es Subject: RE: FI-WARE: Periodic Report M30 (D.1.2.5) - WP11 Importance: High Hola Juan Te remito la plantilla del WP11. Cada socio debe ser evaluado por a nivel de tarea. Por favor, conf?rmame que te ha llegado ?ste correo. Gracias mil. Salu2. Javier. De: subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: martes, 15 de octubre de 2013 15:40 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: [Subsidies] FI-WARE: Periodic Report M30 (D.1.2.5) Importancia: Alta Dear all, as WPL, I need your contribution to deliver the Periodic Report of M30. We have updated the template due to the following remark of the Commission: So, It is very important that the report shows the contribution of each involved partner at task level. We kindly ask you to follow the template where the first section is about the WP as a team, and each task is evaluated by partner. I'm going to send in a particularized e-mail with the template of your WP to you. Please ask to each involved partner their information. As soon as I have the consumption of PM of each partner, I'll send it to you. Note: xxx= Missing information in the document. Deadline: November 30th 2013. It is probably that we'll need a new iteration after this deadline with the effort of each partner, where we'll need you to evaluate each declaration of effort. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 45089 bytes Desc: image003.jpg URL: From nuria.delama at atos.net Thu Nov 7 10:49:50 2013 From: nuria.delama at atos.net (Nuria De-Lama Sanchez) Date: Thu, 7 Nov 2013 10:49:50 +0100 Subject: [Fiware-wpl] FW: Smart City Expo_FI-LAB presence through joint stand FIWARE-XIFI Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A02AE10E4@INTMAIL03.es.int.atosorigin.com> Hi all, See below the e-mail I have just shared with the Dissemination WG of the FI PPP about the presence of FI-LAB in the Smart City Expo. Use it for your own awareness and inform the colleagues of your chapters so that everyone in the project knows about the visibility of FI-WARE. I take advantage of this e-mail to warn you about the need to start working in the design of the stand as well as other related preparations. Best regards, Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address nuria.delama at atos.net The former @atosresearch.eu address will be cancelled soon From: Nuria De-Lama Sanchez Sent: jueves, 07 de noviembre de 2013 10:04 To: dwg at fi-ppp.eu Subject: Smart City Expo_FI-LAB presence through joint stand FIWARE-XIFI Hi all, I am glad to confirm that the FI PPP will be well represented in the Smart City expo at the end of November in Barcelona. You can check information about the event in http://www.smartcityexpo.com/. The information circulated so far within the group was related to the XIFI participation, but we have been discussing about the brand we want to show and the result is that FI-WARE and XIFI will jointly work on that by using the FI-LAB brand. We will share a stand of 30 square meters where we will focus on the product/services offered by us (i.e. avoiding a message based on projects and fully exploiting the "commercial" offering towards Smart Cities). FI-LAB will also be present in the Conference Programme. Find below some info about the session: * GE 2 - EU Smart Cities and Communities Date: 20/11/2013 Time: 12:30 Brief: EU initiatives aimed at identifying and spreading relevant information on technology solutions and needs, as well as providing information for policy support in the framework of a European Innovation Partnership on Smart Cities and Communities. This partnership is bringing the energy, transport and ICT industries together with the cities. Confirmed Speakers: Colette Maloney - Smart Cities and Sustainability Head of Unit - European Commission - Brussels - Belgium If you have any question, please, let me know. We will also share the material gathered during the event. Best regards, Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address nuria.delama at atos.net The former @atosresearch.eu address will be cancelled soon ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From mev at tid.es Thu Nov 7 15:57:57 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 07 Nov 2013 14:57:57 +0000 Subject: [Fiware-wpl] Backlog Content - HOT TOPICS - Request for cooperation Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B891136E9@EX10-MB2-MAD.hi.inet> Dear Partners, Please, find linked some basic reports for each of the hot topics. Lutz Report: 9 items https://forge.fi-ware.eu/docman/view.php/27/3019/FIWARE.backlog.hotTopic-LutzReport.20131107.xlsx Apps (9) ?tems - very appreciated Cloud, IoT, Data, I2nd, Security (0) items TrainingMaterial: 8 items https://forge.fi-ware.eu/docman/view.php/27/3020/FIWARE.backlog.hotTopic-TrainingMaterial.20131107.xlsx Apps(3) - Data(1) - IoT (2) - Security (2) Items Cloud and I2nd (0) items Catalogue: 50 items https://forge.fi-ware.eu/docman/view.php/27/3018/FIWARE.backlog.hotTopic-Catalogue.20131107.xlsx Apps(14) - Cloud(20) - IoT(2) - Data(4) - I2nd(5) - Security(5) All chapters contributed: good at first sight. I need to go deep at GEI level. However, I'd appreciate quick cooperation to have the backlog populated with work items addressing these hot issues. Thanks in advance 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 mev at tid.es Thu Nov 7 17:47:40 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 07 Nov 2013 16:47:40 +0000 Subject: [Fiware-wpl] Lutz Report Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B891137EC@EX10-MB2-MAD.hi.inet> Dear Partners, Please, let me share with you the report by Lutz Schubert since some GE Owners inform not knowing it. It's important to know its content in order to identify corrective actions. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FiWare_PPP_Evaluation v02 by Lutz Schubert.pdf Type: application/pdf Size: 985876 bytes Desc: FiWare_PPP_Evaluation v02 by Lutz Schubert.pdf URL: From jhierro at tid.es Fri Nov 8 08:28:28 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 08 Nov 2013 08:28:28 +0100 Subject: [Fiware-wpl] First 2 big FI-WARE challenges launched ! Please help us to spread the word In-Reply-To: References: Message-ID: <527C929C.8030008@tid.es> Dear FI-WARE partners, As some of you already know, last Thursday we invited developers worldwide to run for two FI-WARE challenges, namely: * a challenge for best application targeted to Smart Cities * a challenge for best application targeted to Smart Businesses/Industries Each of these challenges will be run until Campus Party Brazil and will devote 200 KEUR in prizes ! You can check at the details at http://www.campus-labs.com/webapp/reto/ver/FIWARECHALLENGES?lang=en Don Tapscott, the reputed business guru, has publish a post on twitter on the matter (see below) We would rather appreciate if you can help us to spread the word and reach as many developers as possible. If you use your account on Twitter, please don't forget to add @FIware #FILab @campusparty #FIWAREChallenges Cheers, -- Juanjo Hierro [https://pbs.twimg.com/profile_images/3537430988/3e73c93dcb49b79e2c2257196ed48eef_normal.jpeg] Don Tapscott (@dtapscott) 07/11/13 22:30 Wow. @campusparty and the European Commission launch open challenges with 400K Euros in prize money ow.ly/26ORKy ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 8 10:04:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 08 Nov 2013 09:04:03 +0000 Subject: [Fiware-wpl] Agile dynamic - sprint 3.2.2 planning closed - available dashboards Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89113A0C@EX10-MB2-MAD.hi.inet> Dear Partners, The sprint planning period has finished. Please, find below the corresponding dashboards. Most chapters (Apps, Cloud, Data, I2nd) had good reaction. Congratulations!! IoT and Security had much less items scheduled. I need to understand the reasons preventing better cooperation. I'm using this snapshot for the corresponding backlog deliverable to the EC. However, next time we'll use the one resulting from closing the release 3.2. Now it comes the time to focus on the scheduled work and to progress it. I'll be sharing updated dashboards on days: 14, 21 and 28 (reminding to close the sprint). We need to keep working on the hot topics. Thanks again for the good work!! Kind regards, Manuel Dashboards: https://forge.fi-ware.eu/docman/view.php/27/3025/FIWARE.backlog.apps.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3026/FIWARE.backlog.cloud.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3029/FIWARE.backlog.iot.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3027/FIWARE.backlog.data.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3028/FIWARE.backlog.i2nd.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3030/FIWARE.backlog.security.dashboard.20131108.xlsx ---------------------------- 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 Fri Nov 8 18:15:59 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 8 Nov 2013 17:15:59 +0000 Subject: [Fiware-wpl] D.10.5.2b - validation analysis - current status Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486090D39@DEWDFEMB11A.global.corp.sap> Dear colleagues, please find attached the most current version with updated content in almost all chapters - thanks for every contribution done so far - I think the quality of the deliverable actually improved a lot over the last days - we are on a very good track - but still we need some content and overall a lot of "judgement" or "rationals" and/or "implemented measures", which can be only inputted from the project management team (juanjo/stefano?!). Overivew of missing content (AFAIT): 1. use case specific Clara -> Envirofi Stefano -> OUTSMART 2. Overview FI-WARE project management judgements in chapter "FI-WARE level analysis" (WPL or Juanjo/stefano) Additionally I would like to invite for review of the content as attached - please provide your feedback - even in "comments" where you think we hit the spot of the reviewers or where we still need to improve. The mitigation strategy for non-existing content currently would be: - Tuesday the latest I finalize the text & delete every missing contribution - Wednesday -> Thursday - final review - Next Friday - I can have the latest additions and feedback from the review of the commin weeks (the sooner you review, the better for me!!) - Next Friday: submission to EC as planned Any comments or additions, highly welcome. Wish everybody a nice weekend. /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: Donnerstag, 31. Oktober 2013 13:15 To: fiware-testbed at lists.fi-ware.eu Subject: [Fiware-testbed] D.10.5.2b - use case specific analysis as discussion on the last Phc Dear colleagues, let me shortly summarize the status and tasks in relation to finalizing the validation-analysis content wrt the use case project analysis. We will jointly write the use case scenario analysis based on the free-text format, provided by use cases in phase one. We will work on the wiki page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Use_Case_scenario_analysis For FINEST I started already the summary their answers to the validation context / scenario questionnaire as an example. The main dimensions I took were the following (already in wiki, syntax for you to copy, see below): scenario overview, GE specific questions, use case specific quotes In the Phc we distributed the work like this: John -> smart agrifood Clara -> Envirofi Tarek & Salvatore -> FINSENY Thorsten -> FINEST Pier -> Instant Mobility Stefano -> OUTSMART FI-CONTENT - currently not assigned (!) If you find relevant information, which deem relevant for the "upper"-sections of this page - namely "Main inhibitors identified by the use case projects" and "overall confidence and tension of tone" - please just not only fill them in "your" chapter specific parts, but as well in these subchapters. As you can see in my analysis of FINEST, I really concentrated on the most relevant parts - there is still room for improving the surrounding text, but I can't work on this part currently, therefore open for suggestions in your subchapters. The relevant questionnaire answers is part of the wiki page and linked from there - therefore I think it's easy to start. Timeline: * analysis should be provided ASAP, but not later than 5th of November. * There will be the need to comment on the findings as well in these sections or in one overall section from FI-WARE management. * Overall submission envisioned for the 15th November of number the latest (currently not confirmed by European commission, stefano or Juanjo !!!) * 1st review to start on the 6th of November * still many open contributions missing for the other chapters Thanks for all of your constant support, /Thorsten Here is the blueprint for the section headings already in wiki-syntax (as well open for suggestions on how to improve the heading-text, welcome :)): == Scenario overview == {{Remark|shortly describe the validated scenario and what/who/where/when the validation took place}} == GE specific questions == {{Remark|Question VC.5 and VC.6 (GE cover requirements of the prototype) and (positive/negative comments/feedback) on the GE-level }} == GE specific question and provided answers == ; Lows : something ; High : something == Comments by FI-WARE Management == {{Remark|Here fi-ware management (WPL/WPA or other content personel) should comment: * was the usage as anticipated * are we happy with the results/validation * what did we do in order to tackle identified obstacles * what would we do again (as being rated high) }} Related wiki page (again :)): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Use_Case_scenario_analysis -- 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: D1052b_WP10_v4_generated.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1825492 bytes Desc: D1052b_WP10_v4_generated.docx URL: From markus.heller at sap.com Mon Nov 11 09:57:08 2013 From: markus.heller at sap.com (Heller, Markus) Date: Mon, 11 Nov 2013 08:57:08 +0000 Subject: [Fiware-wpl] [Fiware-ge-owners] Agile dynamic - sprint 3.2.2 planning closed - available dashboards In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B89113A0C@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89113A0C@EX10-MB2-MAD.hi.inet> Message-ID: <393554EDCF801348BC53C7813C6CB73B1A743AE4@DEWDFEMB14A.global.corp.sap> Hi all, I now had a look into this XLS template, it has improved since the last version very much (thanks go to Manuel from me). One Idea: Can't we have two XLS report versions: - one with our internal/ongoing working version with this layout - a second projection that goes to EC with some extra explanation added to it and some details left out ? > I'm using this snapshot for the corresponding backlog deliverable to the EC. However, next time we'll use the one resulting from closing the release 3.2. The current Layout has improved (see above) in my opinion, thx, and I recommend the following improvements on the report layout: I propose the following missing features to be included: 1. one "comment part" in the top for each GE where GE owner can write some own text to explain things he deems important.... Numbers alone ..... Choose another color code (no RED for minor stuff): In my opinion, so much red for minor inconsistencies etc. is highly unfortunate: The EC-facing report one does not need to have the "red" colour code which seems a bit bad since the marked "errors" are mostly minor more than major. For example, our SAP Repository GE is well on track, stuff scheduled etc. But in the report, RED marking indicate that "something is deadly wrong", here the bug was "We have scheduled work (good) but only have forgotten to set state to "scheduled". I consider this very very minor...needed, but minor (only state play) since the real important part is done: We have planned our work thoroughly. I think that might be the case for some more GE's. --> A reviewer can get quickly a very bad impression on GE's if he scans only quickly - and they surely will spend only seconds until the stop at ... red entries.... --> Therefore I propose that we should change these suggestions from "RED" to "light green / blue or whatever better". --> Can be done within seconds and is potentially a big win for GE owners. 2. I propose to suppress _all_ internal flags ("GE = Repository, GE Impl = Default Impl: Status = Waiting GE = Repository, GE Impl = None: Status = Waiting") in the EC-facing report: My reasoning for this, here along the example of the strictly-internal "Status" flagging: a. The flag was meant (at least from me) to signal during WPL/Manuel Telcos what not to discuss again and again for some reasons, not to report to EC that a GE that reports work is deemed as "waiting." b. This flag will raise questions, I guess. Either we do not explain it to EC in a legend (bad) or we explain it (even worse). Therefore I propose to delete this one and for our internal reasons add a new one "skip in WPL/Manuel telcos" or so,. The current way is a bit misfortunate at least for me. Best wishes Markus From: fiware-ge-owners-bounces at lists.fi-ware.eu [mailto:fiware-ge-owners-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Freitag, 8. November 2013 10:04 To: fiware-ge-owners at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-ge-owners] Agile dynamic - sprint 3.2.2 planning closed - available dashboards Dear Partners, The sprint planning period has finished. Please, find below the corresponding dashboards. Most chapters (Apps, Cloud, Data, I2nd) had good reaction. Congratulations!! IoT and Security had much less items scheduled. I need to understand the reasons preventing better cooperation. I'm using this snapshot for the corresponding backlog deliverable to the EC. However, next time we'll use the one resulting from closing the release 3.2. Now it comes the time to focus on the scheduled work and to progress it. I'll be sharing updated dashboards on days: 14, 21 and 28 (reminding to close the sprint). We need to keep working on the hot topics. Thanks again for the good work!! Kind regards, Manuel Dashboards: https://forge.fi-ware.eu/docman/view.php/27/3025/FIWARE.backlog.apps.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3026/FIWARE.backlog.cloud.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3029/FIWARE.backlog.iot.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3027/FIWARE.backlog.data.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3028/FIWARE.backlog.i2nd.dashboard.20131108.xlsx https://forge.fi-ware.eu/docman/view.php/27/3030/FIWARE.backlog.security.dashboard.20131108.xlsx ---------------------------- 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 Mon Nov 11 10:37:35 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 11 Nov 2013 09:37:35 +0000 Subject: [Fiware-wpl] Backlog content - Items name's patterns Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B891173B5@EX10-MB2-MAD.hi.inet> Dear Partners, As we advance in the use of the backlog, it emerges the need to use common patterns for the different topics. These patterns will allow searching items across the different work packages, and work effectively on the topics. These last days I've written in a couple of emails the keywords for the specific hot topics. In order to have a more stable support for them, we are providing them in a page placed at the private wiki. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns We'll need to enrich these patterns. So please, feel free to propose them when there're specific needs to cover. Thanks in advance. Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 11 10:51:10 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 11 Nov 2013 10:51:10 +0100 Subject: [Fiware-wpl] Minutes for today Message-ID: <5280A88E.5080804@tid.es> Dear all, This is the link: * https://docs.google.com/document/d/1liLAOI1-89CLaMhl-2VlavVoYPdRNKgsKqrlbOxbcDI/edit# As usual, ongoing work! See you in a bit, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Nov 11 11:46:52 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 11 Nov 2013 11:46:52 +0100 Subject: [Fiware-wpl] Third Party Innovation Enablement deliverable in word format Message-ID: <5280B59C.9020101@tid.es> Attached -- 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 FI-PPP Architecture Board chairman 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: Third Party Innovation Enablement in FI-WARE 12-08-30.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 505986 bytes Desc: not available URL: From mev at tid.es Mon Nov 11 11:48:25 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 11 Nov 2013 10:48:25 +0000 Subject: [Fiware-wpl] Backlog - Snapshot to be delivered -> last deadline 13.Nov - 12:00 AM Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B891174C6@EX10-MB2-MAD.hi.inet> Dear Partners, Attending the request received during the management board, a final effort is allowed to improve content and to fix inconsistencies in the backlog - dashboard views. It would be much appreciated your taking action to fix ALL items marked red. Please, if you had any doubt on the reason why a specific items is marked red, let me know. It is also an opportunity for the IoT and Security chapters to better improve their backlogs, their current sprint planning level goes to 25% of the other chapters. Thanks again 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 mcp at tid.es Mon Nov 11 14:58:47 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 11 Nov 2013 14:58:47 +0100 Subject: [Fiware-wpl] D2.5 Third party innovation enablement in FI-WARE Message-ID: <5280E297.8030502@tid.es> Dear all, One of the topics that remain open and that were raised today in the call. We were waiting for the contributions to the 3rd party innovation deliverable and none has arrived. Please send them to asap. As a reminder, I copy this from the review report from the review in November/2012 (assessing M13-M18) "This is the first version of this key deliverable that must describe how third party innovation will be enabled and promoted beyond FI-WARE and the FI-PPP. This initial version is a reasonable first step with a useful introduction to relevant stakeholders. However, a significant number of critical issues are not yet addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" From a practical standpoint more detail is required relating to access, licensing and utilisation rights. Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. In addition, the review team expect the next version to address the full scope (including the individual topics) of the deliverable as defined in the DoW." In relation with the last sentence, this is what the DoW says (try to provide something in line with this!): "Third party innovation enablement in FI-WARE.: During the design of FI-WARE, the FI-WARE project will make choices that will affect the way FI-WARE can be used by third parties. Some of these choices will allow and some will limit the possibilities that third parties will get to innovate on top of the platform. It is expected that such choices relate to architectural design and/or to the business model of FI-WARE. This deliverable will document the key choices made and will analyse their effect on future third party innovation. As such, it will provide a justification of these choices against the ultimate objective of enabling third party innovation. It is expected that the deliverable will address topics such as architecture and innovation; neutrality issues; openness; lock-in; data portability; interoperability; patents; standards; specifications; access rights; open source and licensing; and so on." Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 11 16:16:20 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 11 Nov 2013 16:16:20 +0100 Subject: [Fiware-wpl] Thing to consider from today's call Message-ID: <5280F4C4.5050006@tid.es> Dear all, Minutes of meeting: https://docs.google.com/document/d/1liLAOI1-89CLaMhl-2VlavVoYPdRNKgsKqrlbOxbcDI/edit A number of things to take into account: * Third party innovation is still awaiting your inputs (this goes in detail in a separate email today) * IoT and Security backlogs are in a bad shape * The links for the delivery of R3 have to be created by the WPL, not the partners. I see that WP4, WP5, WP8 and (possibly) WP13 look bad. Are any partners editing the manuals in this WPs? Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergg at tid.es Mon Nov 11 16:31:36 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 11 Nov 2013 15:31:36 +0000 Subject: [Fiware-wpl] D2.5 Third party innovation enablement in FI-WARE In-Reply-To: <5280E297.8030502@tid.es> References: <5280E297.8030502@tid.es> Message-ID: <03BE306058976141B4883174DF62D54DCA52124C@EX10-MB2-MAD.hi.inet> Dear all, I send you herewith my changes. The most important proposal is to add the application sponsor as an important FI-WARE stakeholder, so that the deliverable is aligned with the latest leaflet. Check the description in section 2 and the benefits for this new role in the conclusions. I have also added changes and updates to WP6 text. More than that, I would suggest to add additional material from FI-LAB and catalogue descriptions Best Regards, Sergio. From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Monday, November 11, 2013 2:59 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] D2.5 Third party innovation enablement in FI-WARE Dear all, One of the topics that remain open and that were raised today in the call. We were waiting for the contributions to the 3rd party innovation deliverable and none has arrived. Please send them to asap. As a reminder, I copy this from the review report from the review in November/2012 (assessing M13-M18) "This is the first version of this key deliverable that must describe how third party innovation will be enabled and promoted beyond FI-WARE and the FI-PPP. This initial version is a reasonable first step with a useful introduction to relevant stakeholders. However, a significant number of critical issues are not yet addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" From a practical standpoint more detail is required relating to access, licensing and utilisation rights. Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. In addition, the review team expect the next version to address the full scope (including the individual topics) of the deliverable as defined in the DoW." In relation with the last sentence, this is what the DoW says (try to provide something in line with this!): "Third party innovation enablement in FI-WARE.: During the design of FI-WARE, the FI-WARE project will make choices that will affect the way FI-WARE can be used by third parties. Some of these choices will allow and some will limit the possibilities that third parties will get to innovate on top of the platform. It is expected that such choices relate to architectural design and/or to the business model of FI-WARE. This deliverable will document the key choices made and will analyse their effect on future third party innovation. As such, it will provide a justification of these choices against the ultimate objective of enabling third party innovation. It is expected that the deliverable will address topics such as architecture and innovation; neutrality issues; openness; lock-in; data portability; interoperability; patents; standards; specifications; access rights; open source and licensing; and so on." Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: Third Party Innovation Enablement in FI-WARE 11-11-13-WP6.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 512323 bytes Desc: Third Party Innovation Enablement in FI-WARE 11-11-13-WP6.docx URL: From mcp at tid.es Mon Nov 11 17:36:25 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 11 Nov 2013 17:36:25 +0100 Subject: [Fiware-wpl] Lutz present at the review Message-ID: <52810789.4070905@tid.es> Dear all, This is just to let you know that Arian has just replied. It looks like Lutz is going to attend the forthcoming M30 review. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From pascal.bisson at thalesgroup.com Tue Nov 12 10:55:29 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 12 Nov 2013 10:55:29 +0100 Subject: [Fiware-wpl] Lutz present at the review In-Reply-To: <52810789.4070905@tid.es> References: <52810789.4070905@tid.es> Message-ID: <22230_1384250130_5281FB12_22230_14789_1_CBBCD6C304123F4AB23FAAE3055C8C0E0208201FCC78@THSONEA01CMS04P.one.grp> Dear Miguel, Thanks to share with us. >From my side this is something I was guessing also why I did raise the question. Now confirmed. Regards Pascal -----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 novembre 2013 17:36 ??: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet?: [Fiware-wpl] Lutz present at the review Dear all, This is just to let you know that Arian has just replied. It looks like Lutz is going to attend the forthcoming M30 review. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From mev at tid.es Tue Nov 12 10:57:44 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 12 Nov 2013 09:57:44 +0000 Subject: [Fiware-wpl] Backlog content: Training Material work items - update -> deadline 15.Nov Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89117955@EX10-MB2-MAD.hi.inet> Dear Partners, After some cooperative thinking with Davide, we decided to simplify the scheme to create the corresponding work items. You can find relevant info at the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Training_Material There's a description for each step, and links give additional details to follow the process. We want to have all work items created on Friday. I would appreciate each GE Owner creating its own entries. If you couldn't do it, please, let me know, I'll create them for you. There's a list of GE-GEImp already available in the FI-LAB, which need to react quickly to have their training material available as soon as possible. As long as I know they are: Store, WireCloud, IdM, orion, bigdata and cloud (paas manager, sdc, drcm and portal) If anything, please, don't hesitate to contact me, or Davide. 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 mev at tid.es Tue Nov 12 17:22:00 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 12 Nov 2013 16:22:00 +0000 Subject: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89119B00@EX10-MB2-MAD.hi.inet> Dear Partners, As you know we keep working on this hot topic as well. After some cooperative thinking with my workmate Santi (cc'd), and considering the structure of the spreadsheet maintained by Stefano, we've updated the template for the work items to be created for this hot topic. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Catalogue In order to speed up the creation process, Santi is about to start creating those work items with your permission. If you had any objection, please, let us know. The work items will be left as open so that you can schedule them, and will be assigned to your work package leader, who will reassign them appropriately. I hope you find it all acceptable. We think this way can be more effective. Obviously, if you had any objection, please, let me know. Thanks for your 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 stefano.depanfilis at eng.it Tue Nov 12 19:29:11 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 12 Nov 2013 19:29:11 +0100 Subject: [Fiware-wpl] catalogue status as for today Message-ID: ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed-V2_catalogue_publication_status.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 49761 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Tue Nov 12 20:57:34 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 12 Nov 2013 20:57:34 +0100 Subject: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B89119B00@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89119B00@EX10-MB2-MAD.hi.inet> Message-ID: Dear Manuel, I appreciate a lot your effort and support (also by Santi) to complete the set of items that are currently necessary, however I believe that at least for what concerns I2ND, creating all the work items you list in the template page is not completely meaningful, as for many GEis the instance creation and their inclusion in the catalogue is not necessary. This would therefore result in a number of tickets wich are unnecessary. I suggest the following: tomorrow I'll discuss this point with my Gianmario, who's taking care of the I2ND item issues, and we'll agree with you and Santi what is the set of work items which needs to be created in the I2ND backlog. Does this work for you? BR Pier ________________________________________ From: fiware-wpl-bounces at lists.fi-ware.eu [fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE [mev at tid.es] Sent: Tuesday, November 12, 2013 5:22 PM To: fiware-ge-owners at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: SANTIAGO MARTINEZ GARCIA; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov Dear Partners, As you know we keep working on this hot topic as well. After some cooperative thinking with my workmate Santi (cc?d), and considering the structure of the spreadsheet maintained by Stefano, we?ve updated the template for the work items to be created for this hot topic. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Catalogue In order to speed up the creation process, Santi is about to start creating those work items with your permission. If you had any objection, please, let us know. The work items will be left as open so that you can schedule them, and will be assigned to your work package leader, who will reassign them appropriately. I hope you find it all acceptable. We think this way can be more effective. Obviously, if you had any objection, please, let me know. Thanks for your 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From mev at tid.es Wed Nov 13 12:47:06 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 13 Nov 2013 11:47:06 +0000 Subject: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89119B00@EX10-MB2-MAD.hi.inet> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911A394@EX10-MB2-MAD.hi.inet> Dear Pier, Perhaps I didn't explain it well. The idea is to create the needed entries. The template offers a set of them to be used according to the specific need and status of each enabler. It's been refined to that level so as to have the same visibility and management level as Stefano had. Yes, let's do it that way! Thanks. Manuel -----Original Message----- From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: martes, 12 de noviembre de 2013 20:58 To: MANUEL ESCRICHE VICENTE Cc: SANTIAGO MARTINEZ GARCIA; fiware-wpa at lists.fi-ware.eu; Bollano Gianmario; fiware-ge-owners at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: RE: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov Dear Manuel, I appreciate a lot your effort and support (also by Santi) to complete the set of items that are currently necessary, however I believe that at least for what concerns I2ND, creating all the work items you list in the template page is not completely meaningful, as for many GEis the instance creation and their inclusion in the catalogue is not necessary. This would therefore result in a number of tickets wich are unnecessary. I suggest the following: tomorrow I'll discuss this point with my Gianmario, who's taking care of the I2ND item issues, and we'll agree with you and Santi what is the set of work items which needs to be created in the I2ND backlog. Does this work for you? BR Pier ________________________________________ From: fiware-wpl-bounces at lists.fi-ware.eu [fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE [mev at tid.es] Sent: Tuesday, November 12, 2013 5:22 PM To: fiware-ge-owners at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: SANTIAGO MARTINEZ GARCIA; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Backlog content - Catalogue work items - update -> deadline 15.Nov Dear Partners, As you know we keep working on this hot topic as well. After some cooperative thinking with my workmate Santi (cc'd), and considering the structure of the spreadsheet maintained by Stefano, we've updated the template for the work items to be created for this hot topic. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Catalogue In order to speed up the creation process, Santi is about to start creating those work items with your permission. If you had any objection, please, let us know. The work items will be left as open so that you can schedule them, and will be assigned to your work package leader, who will reassign them appropriately. I hope you find it all acceptable. We think this way can be more effective. Obviously, if you had any objection, please, let me know. Thanks for your 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mev at tid.es Wed Nov 13 13:25:05 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 13 Nov 2013 12:25:05 +0000 Subject: [Fiware-wpl] Backlog content: Dashboard and Review's update Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911A3F6@EX10-MB2-MAD.hi.inet> Dear Partners, Please, find linked dashboards and reviews updated. They have been beautified. Reviews have now new different graphs focused on the issues - stats graphs are left for the last page WC4. Dashboards -> for activity management Apps: https://forge.fi-ware.eu/docman/view.php/27/3060/FIWARE.backlog.apps.dashboard.20131113.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3061/FIWARE.backlog.cloud.dashboard.20131113.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3064/FIWARE.backlog.iot.dashboard.20131113.xlsx Data:https://forge.fi-ware.eu/docman/view.php/27/3062/FIWARE.backlog.data.dashboard.20131113.xlsx I2nd:https://forge.fi-ware.eu/docman/view.php/27/3063/FIWARE.backlog.i2nd.dashboard.20131113.xlsx Sec: https://forge.fi-ware.eu/docman/view.php/27/3065/FIWARE.backlog.security.dashboard.20131113.xlsx Reviews -> for fixing issues on the tracker and wiki Apps: https://forge.fi-ware.eu/docman/view.php/27/3054/FIWARE.backlog.apps.review.20131113.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3055/FIWARE.backlog.cloud.review.20131113.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3058/FIWARE.backlog.iot.review.20131113.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3056/FIWARE.backlog.data.review.20131113.xlsx I2nd: https://forge.fi-ware.eu/docman/view.php/27/3057/FIWARE.backlog.i2nd.review.20131113.xlsx Sec: https://forge.fi-ware.eu/docman/view.php/27/3059/FIWARE.backlog.security.review.20131113.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Wed Nov 13 14:05:03 2013 From: markus.heller at sap.com (Heller, Markus) Date: Wed, 13 Nov 2013 13:05:03 +0000 Subject: [Fiware-wpl] Backlog-Deliverable to EC: People's names in Backlog content deliverables Message-ID: <393554EDCF801348BC53C7813C6CB73B1A745D62@DEWDFEMB14A.global.corp.sap> Hi Manuel, all, I also have a new question about people names in the deliverable version of the backlog: What would you think, should we delete the columns with the developer names in the backlogs or other way round, are they necessary (since they represent some form of personal information which is not needed at this reporting level maybe)? Maybe the individual contributor info provides no real value to the reader? Alternative: We could replace employee names with company names instead, so that individual contributors do not need to be reported. I ask because I guess that this information usually is not reported since personal information about the employees direct work is reported. But if I am right, backlog deliverable is a public deliverable (I think maybe not finally decided yet..), so that the employee's names might be blacked out or so as usual? I am not sure about this, what is your opinion? How do other EU-projects handle this? Best wishes Markus From mev at tid.es Wed Nov 13 14:22:04 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 13 Nov 2013 13:22:04 +0000 Subject: [Fiware-wpl] Backlog-Deliverable to EC: People's names in Backlog content deliverables In-Reply-To: <393554EDCF801348BC53C7813C6CB73B1A745D62@DEWDFEMB14A.global.corp.sap> References: <393554EDCF801348BC53C7813C6CB73B1A745D62@DEWDFEMB14A.global.corp.sap> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911A661@EX10-MB2-MAD.hi.inet> Hi Markus, Person's name will be removed in the deliverable! Kind regards, Manuel -----Original Message----- From: Heller, Markus [mailto:markus.heller at sap.com] Sent: mi?rcoles, 13 de noviembre de 2013 14:05 To: MANUEL ESCRICHE VICENTE Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Backlog-Deliverable to EC: People's names in Backlog content deliverables Hi Manuel, all, I also have a new question about people names in the deliverable version of the backlog: What would you think, should we delete the columns with the developer names in the backlogs or other way round, are they necessary (since they represent some form of personal information which is not needed at this reporting level maybe)? Maybe the individual contributor info provides no real value to the reader? Alternative: We could replace employee names with company names instead, so that individual contributors do not need to be reported. I ask because I guess that this information usually is not reported since personal information about the employees direct work is reported. But if I am right, backlog deliverable is a public deliverable (I think maybe not finally decided yet..), so that the employee's names might be blacked out or so as usual? I am not sure about this, what is your opinion? How do other EU-projects handle this? Best wishes Markus ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 mev at tid.es Wed Nov 13 15:40:07 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 13 Nov 2013 14:40:07 +0000 Subject: [Fiware-wpl] Backlog Content - patterns for documentation and software Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911A732@EX10-MB2-MAD.hi.inet> Dear Partners, After some cooperative thinking with Miguel, we have identified the following patterns for Documentation and Software. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Documentation These patterns want to be only a help. Perhaps you have useful proposals of objects or actions suitable for them. So if you had other suggestions or proposals, please, let me know. Kind regards, Manuel [cid:image001.png at 01CEE086.9FB26070] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 35273 bytes Desc: image001.png URL: From nuria.delama at atos.net Wed Nov 13 16:19:39 2013 From: nuria.delama at atos.net (Nuria De-Lama Sanchez) Date: Wed, 13 Nov 2013 16:19:39 +0100 Subject: [Fiware-wpl] SMART CITY EXPO_ATTENDEES FOR FI-WARE (FREE PASSES TO THE EXPO) Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A02B4E63E@INTMAIL03.es.int.atosorigin.com> Dear colleagues, Let me inform you that FI-WARE is finally coming to an end in the preparations of our presence in Smart City Expo next week in Barcelona. Let me summarize a bit the current situation for the sake of coordination and awareness. I highlight in yellow the aspects that could be of your interest and for which I need an urgent reaction from PCC members and WPL/WPA. ? Smart City Expo: one of the most important international events around the topic of Smart Cities. Place: Barcelona; Dates: 19-21 November. Further info in http://www.smartcityexpo.com/. ? FI-WARE will attend Smart City Expo together with XIFI. We will not promote projects, but commercial brands, since this event has nothing to do with research. It will be an offering for Smart Cities. The main label will be FI-LAB. ? FI-WARE/FI-LAB will be visible in Smart City Expo through the following activities o Joint stand of 30 square meters. People from Ogilvy are taking care of decoration and branding and we expect to have high visibility, thanks also to the good location of the stand (I attach the maps for your convenience). o FI-LAB speech in the Conference Program o Additional activities such as possible press conference and presence in mass media (ongoing) ? Then, let me call you for your interest in attending this event (we are sorry about the late announcement even if most of you knew about the event already) o Our contract includes 30 passes to the expo (few of them already reserved for Ogilvy people + Juanjo) o We need some people from FI-WARE with good knowledge on the messages to be in the stand and take care of our visitors. We do not have to forget that this is a marketing activity, and therefore, a good analysis of competitors and good marketing to attract potential customers have to be put in place. If a great stand is not accompanied by great people (human resources) to do the work, then, it will be almost useless. o I ask all PCC members, WPL/WPA to send me a list of people interested in attending the expo (not the congress as such; this requires separate tickets, like in Mobile World Congress). Send the list as soon as possible and NOT LATER THAN TOMORROW EOB. o I need name of the person and organization. I will compile all the info and will send that to the organizers. Thanks in advance and let's maximize a new "commercial opportunity" for FI-WARE, in this case targeting the major exploitation channel pointed out in front of the EC. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address nuria.delama at atos.net The former @atosresearch.eu address will be cancelled soon ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Smart City expo_location1.pdf Type: application/octet-stream Size: 198958 bytes Desc: Smart City expo_location1.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Smart City expo_location2.pdf Type: application/octet-stream Size: 1414782 bytes Desc: Smart City expo_location2.pdf URL: From thorsten.sandfuchs at sap.com Wed Nov 13 19:46:32 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 13 Nov 2013 18:46:32 +0000 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report ready for review within the next business day Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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: D1052b_WP10_v5_THS.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1999278 bytes Desc: D1052b_WP10_v5_THS.docx URL: From jdps at tid.es Wed Nov 13 23:22:10 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 13 Nov 2013 22:22:10 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Message-ID: <77A22C1085494D48B4018F06A40DB2C730010D7F@EX10-MB2-MAD.hi.inet> Dear all, First of all, thank you very much for your contribution. Please find attached the first draft version of the Periodic Report M30 where we have integrated all the received contributions so far. I kindly ask you to use this one as basis in order to provide a new version of the report of your WP. Please check it, and complete where ?xxx? is still written. Don?t hesitate to share it with your involved partners. Note: We?ll only accept changes in a WP from its own WPL. Deadline, November 20th, 2013, EOB. Please confirm the reception of this important e-mail. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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.1.2.5 - Periodic Report M30 (DRAFT v1).docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1425878 bytes Desc: D.1.2.5 - Periodic Report M30 (DRAFT v1).docx URL: From thorsten.sandfuchs at sap.com Thu Nov 14 09:03:22 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 14 Nov 2013 08:03:22 +0000 Subject: [Fiware-wpl] testbed planned usage - phase two projects & counting of "functionalities" in the totals & how to handle this for the other chapters Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486097767@DEWDFEMB11A.global.corp.sap> Dear colleagues, there were some mismatches and not counted lines in the "Testbed planned usage" matrix we all use https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 I tried to fix it - but actually with the last "fix" I don't know how to proceed. Cloud chapter introduced "functionalities" and not GEs in line 9-15 The question is now: should we count their "D"/"U"/"E" in the totals or not? Currently they are NOT counted (btw I had to fix for some of the sums the uniformity - e.g. that the sum reaches the cell down below like 95 and not stops prior to WP13): So my question is: do we count the "functionalities" as "GE"-ratings or not? Second question: what would happen if any of the other chapters introduced these kind of functionalities? Where to layout them? I know that at least in one chapter we would have the requirement to introduce this as well. Thanks for letting me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19645 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 14871 bytes Desc: image002.jpg URL: From nuria.delama at atos.net Thu Nov 14 12:08:26 2013 From: nuria.delama at atos.net (Nuria De-Lama Sanchez) Date: Thu, 14 Nov 2013 12:08:26 +0100 Subject: [Fiware-wpl] Reminder for attendees to Smart City Expo Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A02B4E80D@INTMAIL03.es.int.atosorigin.com> Dear colleagues, Let me remind you about the availability of passes for the Smart City Expo that will be held next week in Barcelona (19-21 November). We also have a strong need of colleagues from the project to represent FI-LAB at the stand so that we can take proper care of the visitors interested in FI-WARE, FI-LAPS and FI-OPS. I encourage you to contact me if you need further information. Share this with all the members in your WPs and come back to me by today EOB with the list of people (& organizations) that want to be there and get a free pass. Best regards, Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address nuria.delama at atos.net The former @atosresearch.eu address will be cancelled soon ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From pierangelo.garino at telecomitalia.it Thu Nov 14 23:16:00 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 14 Nov 2013 23:16:00 +0100 Subject: [Fiware-wpl] R: [Fiware-testbed] D.10.5.2b validation analysis and report ready for review within the next business day In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> Message-ID: Dear Thorsten, here is a version of the document with few minor comments and adjustments from my side (I accepted all changes before introducing mine). Overall the document looks good, considering that the main concern is due to the limited amount of feedback received (i.e. few enablers actually validated); in my view better results couldn't be obtained with such a limited material to manage. I didn't provide answers to the main questions you raise in the doc, as I don't feel to have sufficient elements to draw specific conclusions. I wonder if there's the need to mention somewhere in the doc that I2ND GEs were not validated (except Cloud Proxy in conjunction with Cloud) as they were planned for R2 only. BR Pier Da: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: mercoled? 13 novembre 2013 19:47 A: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-testbed] D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! 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: D1052b_WP10_v5_THS_PG.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1886114 bytes Desc: D1052b_WP10_v5_THS_PG.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From thierry.nagellen at orange.com Fri Nov 15 07:59:08 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 15 Nov 2013 06:59:08 +0000 Subject: [Fiware-wpl] URGENT: LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III Message-ID: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I do not know if you have heard about this FITMAN webinar. Going quickly through the short description of each module it seems that as FI-Ware we must attend some of them because they propose some Specific Enablers which are close to some Generic Enablers: typically for my part (IoT) the ShopFloor DATA Collection could be replace by some IoT GEs but we could be also interested by the one working on Semantic interface. Juanjo, Stefano (as member of the Architecture Board because I could not attend the last meeting): do we have some clear architecture picture from FITMAN explaining how their Specific Enablers would interact/use some Generic Enablers? BR Thierry De : Celine Vergne [mailto:celine.vergne at interop-vlab.eu] Envoy? : jeudi 14 novembre 2013 14:58 ? : dissemination at interop-vlab.eu Objet : LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III ------------------------------------------------------------------------------------------------------------------------------------------------------- ------ Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son carnet d'adresses. Vous pouvez le faire en utilisant ce modele d'email. Merci Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? You can use this email template if you like. Thanks ------------------------------------------------------------------------------------------------------------------------------------------------------- ------ INTEROP-VLab Communication (partner of the FITMAN project) [cid:image002.png at 01CEE13F.8B37EB10] Invitation to the FITMAN FI-PPP Phase III Webinar (Nov. 19TH, 2013) And to Specific Enablers Webinars (see schedule below) Free online webinars We would like to invite you to join the FITMAN Phase III webinar on Tuesday 19 November 2013 at 12pm CET. The webinar is for FI-PPP Phase III participants who wish to build on FITMAN work and/or address ICT in manufacturing. It will provide information about FITMAN deliverables, methodologies for SME and web entrepreneur engagement, and other Phase III related information. For a detailed agenda, please click here For registration link, click here For more information on the FITMAN Specific Enablers benefits and functionalities, you are invited to join the series of webinars scheduled over the coming days (see programme below). Programme of FITMAN Specific Enablers webinars Tittle Presenter/contact Date/time Secure Event Management Salvatore Piccione (TXT E-Solutions) 15-11-2013 - 11h CET Unstructured and Social Data Analytics Fenareti Lampathaki (National Technical University of Athens) 25-11-2013- 11h CET Data Interoperability Platform Services Michele Sesana (TXT E-Solutions) 19-11-2013- 11h CET Collaborative Business Process Management Mauro Isaja (Engineering) 21-11-2013- 11h CET Metadata and Ontologies Semantic Matching Sotiris Kousouris (National Technical University of Athens) 22-11-2013- 11h CET Supply Chain & Business Ecosystem Apps Michele Sesana (TXT E-Solutions) 22-11-2013 - 15h CET Shopfloor Data Collection Sudeep Ghimire (UNINOVA) 27-11-2013- 11h CET Collaborative Assets Management Mauro Isaja (Engineering) 05-12-2013- 11h CET Click on the title to view the full description and registration link. If you are interested in engaging with Phase III in the area of ICT for Manufacturing, please book that date on your calendar and participate in the FITMAN Phase III webinar! You can send any question about the FITMAN Phase III webinar to: fitman-phase-iii-info at txtgroup.com Best regards, Cathy LIEU, INTEROP-VLab Assistant Manager in charge of the communication www.interop-vlab.eu [logo1sansfond7pct] This email is sent by the INTEROP-VLab Management. If you do not wish to receive message from INTEROP-VLab, please write to cathy.lieu at interop-vlab.eu to be unsubscribed of the mailing list. _________________________________________________________________________________________________________________________ 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, 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, 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: image002.png Type: image/png Size: 10766 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 2153 bytes Desc: image003.gif URL: From thomas.bohnert at zhaw.ch Fri Nov 15 08:08:59 2013 From: thomas.bohnert at zhaw.ch (Thomas Michael Bohnert) Date: Fri, 15 Nov 2013 08:08:59 +0100 Subject: [Fiware-wpl] URGENT: LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III In-Reply-To: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <1384499339.2977.0.camel@Hjalmar> Thierry, We'll make this an action item for the next AB meeting. Cheers, Thomas -- Thomas Michael Bohnert www: www.cloudcomp.ch www: http://tmb.nginet.de twitter: tmbohnert On Fri, 2013-11-15 at 06:59 +0000, thierry.nagellen at orange.com wrote: > Dear all, > > I do not know if you have heard about this FITMAN webinar. Going quickly through the short description of each module it seems that as FI-Ware we must attend some of them because they propose some Specific Enablers which are close to some Generic Enablers: typically for my part (IoT) the ShopFloor DATA Collection could be replace by some IoT GEs but we could be also interested by the one working on Semantic interface. > > Juanjo, Stefano (as member of the Architecture Board because I could not attend the last meeting): do we have some clear architecture picture from FITMAN explaining how their Specific Enablers would interact/use some Generic Enablers? > > BR > Thierry > > De : Celine Vergne [mailto:celine.vergne at interop-vlab.eu] > Envoy? : jeudi 14 novembre 2013 14:58 > ? : dissemination at interop-vlab.eu > Objet : LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III > > > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > ------ > > > > Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son > > carnet d'adresses. Vous pouvez le faire en utilisant ce modele d'email. Merci > > > > > > Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? > > You can use this email template if you like. Thanks > > > > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > ------ > > > > INTEROP-VLab Communication (partner of the FITMAN project) > > [cid:image002.png at 01CEE13F.8B37EB10] > > Invitation to the FITMAN FI-PPP Phase III Webinar (Nov. 19TH, 2013) > And to Specific Enablers Webinars (see schedule below) > Free online webinars > > We would like to invite you to join the FITMAN Phase III webinar on Tuesday 19 November 2013 at 12pm CET. The webinar is for FI-PPP Phase III participants who wish to build on FITMAN work and/or address ICT in manufacturing. It will provide information about FITMAN deliverables, methodologies for SME and web entrepreneur engagement, and other Phase III related information. > For a detailed agenda, please click here > For registration link, click here > > For more information on the FITMAN Specific Enablers benefits and functionalities, you are invited to join the series of webinars scheduled over the coming days (see programme below). > > Programme of FITMAN Specific Enablers webinars > > Tittle > > Presenter/contact > > Date/time > > Secure Event Management > > Salvatore Piccione (TXT E-Solutions) > > 15-11-2013 - 11h CET > > Unstructured and Social Data Analytics > > Fenareti Lampathaki (National Technical University of Athens) > > 25-11-2013- 11h CET > > Data Interoperability Platform Services > > Michele Sesana (TXT E-Solutions) > > 19-11-2013- 11h CET > > Collaborative Business Process Management > > Mauro Isaja (Engineering) > > 21-11-2013- 11h CET > > Metadata and Ontologies Semantic Matching > > Sotiris Kousouris (National Technical University of Athens) > > 22-11-2013- 11h CET > > Supply Chain & Business Ecosystem Apps > > Michele Sesana (TXT E-Solutions) > > 22-11-2013 - 15h CET > > Shopfloor Data Collection > > Sudeep Ghimire (UNINOVA) > > 27-11-2013- 11h CET > > Collaborative Assets Management > > Mauro Isaja (Engineering) > > 05-12-2013- 11h CET > > > Click on the title to view the full description and registration link. > > If you are interested in engaging with Phase III in the area of ICT for Manufacturing, please book that date on your calendar and participate in the FITMAN Phase III webinar! > You can send any question about the FITMAN Phase III webinar to: fitman-phase-iii-info at txtgroup.com > > Best regards, > > Cathy LIEU, INTEROP-VLab > Assistant Manager > in charge of the communication > www.interop-vlab.eu > [logo1sansfond7pct] > This email is sent by the INTEROP-VLab Management. If you do not wish to receive message from INTEROP-VLab, please write to cathy.lieu at interop-vlab.eu to be unsubscribed of the mailing list. > > > _________________________________________________________________________________________________________________________ > > 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, > 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, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl From thierry.nagellen at orange.com Fri Nov 15 09:57:05 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 15 Nov 2013 08:57:05 +0000 Subject: [Fiware-wpl] [Fiware-testbed] R: D.10.5.2b validation analysis and report ready for review within the next business day In-Reply-To: References: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> Message-ID: <27266_1384505829_5285E1E4_27266_8023_1_976A65C5A08ADF49B9A8523F7F81925C1490E5@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is my review. More comments up to you to integrate some changes and some small changes in the text. What about the Outsmart evaluation? If it is required I can do it but only during the week end :(. BR Thierry De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : jeudi 14 novembre 2013 23:16 ? : Sandfuchs, Thorsten Cc : Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-testbed] R: D.10.5.2b validation analysis and report ready for review within the next business day Dear Thorsten, here is a version of the document with few minor comments and adjustments from my side (I accepted all changes before introducing mine). Overall the document looks good, considering that the main concern is due to the limited amount of feedback received (i.e. few enablers actually validated); in my view better results couldn't be obtained with such a limited material to manage. I didn't provide answers to the main questions you raise in the doc, as I don't feel to have sufficient elements to draw specific conclusions. I wonder if there's the need to mention somewhere in the doc that I2ND GEs were not validated (except Cloud Proxy in conjunction with Cloud) as they were planned for R2 only. BR Pier Da: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: mercoled? 13 novembre 2013 19:47 A: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-testbed] D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! 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, 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, 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: D1052b_WP10_v5_TNA.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 2015868 bytes Desc: D1052b_WP10_v5_TNA.docx URL: From depa at eng.it Fri Nov 15 10:22:24 2013 From: depa at eng.it (depa at eng.it) Date: Fri, 15 Nov 2013 09:22:24 +0000 Subject: [Fiware-wpl] R: Re: [Fiware-testbed] R: D.10.5.2b validation analysis and report ready for review within the next business day In-Reply-To: <27266_1384505829_5285E1E4_27266_8023_1_976A65C5A08ADF49B9A8523F7F81925C1490E5@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> <27266_1384505829_5285E1E4_27266_8023_1_976A65C5A08ADF49B9A8523F7F81925C1490E5@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2094620448-1384507346-cardhu_decombobulator_blackberry.rim.net-1737432390-@b2.c14.bise7.blackberry> I'm doing it at the moment. Thank you for your kind offer. Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: thierry.nagellen at orange.com Sender: fiware-testbed-bounces at lists.fi-ware.eu Date: Fri, 15 Nov 2013 08:57:05 To: Garino Pierangelo; Sandfuchs, Thorsten Cc: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: Re: [Fiware-testbed] R: D.10.5.2b validation analysis and report ready for review within the next business day _______________________________________________ Fiware-testbed mailing list Fiware-testbed at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-testbed From stefano.depanfilis at eng.it Fri Nov 15 11:33:28 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Fri, 15 Nov 2013 11:33:28 +0100 Subject: [Fiware-wpl] [Fiware-testbed] R: Re: R: D.10.5.2b validation analysis and report ready for review within the next business day In-Reply-To: <2094620448-1384507346-cardhu_decombobulator_blackberry.rim.net-1737432390-@b2.c14.bise7.blackberry> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486097396@DEWDFEMB11A.global.corp.sap> <27266_1384505829_5285E1E4_27266_8023_1_976A65C5A08ADF49B9A8523F7F81925C1490E5@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2094620448-1384507346-cardhu_decombobulator_blackberry.rim.net-1737432390-@b2.c14.bise7.blackberry> Message-ID: dear thorsten, outsmart done! it is rather poor, but it is what we do have ..... ciao, stefano 2013/11/15 : > I'm doing it at the moment. > Thank you for your kind offer. > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: thierry.nagellen at orange.com > Sender: fiware-testbed-bounces at lists.fi-ware.eu > Date: Fri, 15 Nov 2013 08:57:05 > To: Garino Pierangelo; Sandfuchs, Thorsten > Cc: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu > Subject: Re: [Fiware-testbed] R: D.10.5.2b validation analysis and report ready > for review within the next business day > > _______________________________________________ > Fiware-testbed mailing list > Fiware-testbed at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-testbed > > _______________________________________________ > Fiware-testbed mailing list > Fiware-testbed at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-testbed > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 From mev at tid.es Fri Nov 15 13:43:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 15 Nov 2013 12:43:03 +0000 Subject: [Fiware-wpl] BacklogContent.hotTopics.Update ;-) Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B3D1@EX10-MB2-MAD.hi.inet> Dear Partners, Let me update you on entries about hot topics. TraningMaterial: App:22; Cloud:7; Data:7; I2nd:4; IoT:11; Sec:11 = 62 items https://forge.fi-ware.eu/docman/view.php/27/3081/FIWARE.backlog.hotTopic-TrainingMaterial.20131115.xlsx Catalogue: Apps: 27; Cloud: 19; Data:11; I2nd: 21; Sec: 3 = 96 items https://forge.fi-ware.eu/docman/view.php/27/3079/FIWARE.backlog.hotTopic-Catalogue.20131115.xlsx Lutz Report: Apps: 9; Cloud: 0; Data: 4; I2nd: 2; IoT:1, Sec: 0 = 16 Items https://forge.fi-ware.eu/docman/view.php/27/3080/FIWARE.backlog.hotTopic-LutzReport.20131115.xlsx Thanks for the effort!! There's been clear improvement on TrainingMaterial and Catalogue. We need a more intense effort on the LutzReport. 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 thorsten.sandfuchs at sap.com Fri Nov 15 16:58:19 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 15 Nov 2013 15:58:19 +0000 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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: D1052b_WP10_v7_generated.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 2040093 bytes Desc: D1052b_WP10_v7_generated.docx URL: From jhierro at tid.es Mon Nov 18 07:43:10 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 18 Nov 2013 07:43:10 +0100 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> Message-ID: <5289B6FE.4030603@tid.es> Dear Thorsten, Thanks for your I have planed to review this deliverable before tomorrow, but if you want to deliver it today by all means, I won't object. After all, I quickly checked the yellow boxes where you asked for input and I understood they were not just for me but for all WPLs and WPAs (referred collectively as management since indeed architecture chapter WPs are managed through the direct involvement of WPLs and WPAs). Indeed, while I can provide comments in most of the cases, they shouldn't be so much different from those that can be provided by the WPLs/WPAs because most of the comments by UC projects, or data extracted from the questionnaires they have filled, go into details about usage of the GEis linked to the several chapters. I can carry out, though, a final review before tomorrow as I have just said. As you wish. But let me know so that I don't work in vain. If there is any particular section where my concrete input would relevant, please let me know. BTW, I found a couple of editorial issues when I quickly perform a first reading of the contents of the version you distributed last week ... have you fixed those in this version ? If you don't recall having fixed any editorial ... then I would suggest to carefully review the writing ... 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 FI-PPP Architecture Board chairman 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 15/11/13 16:58, Sandfuchs, Thorsten wrote: Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 18 08:41:39 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 18 Nov 2013 07:41:39 +0000 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) In-Reply-To: <5289B6FE.4030603@tid.es> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> <5289B6FE.4030603@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7DDE6@DEWDFEMB11B.global.corp.sap> Dear colleagues, as I was not involved in the interaction with the EC to postpone this deliverable, I honestly can't judge if this can be postponed again. I would assume as it in general is not more "major" than other deliverables, it might be able to wait another day... but in the end this decision has to come from the management level & the people interacting with timing of deliverables towards the EC. Since the last version (with or without "yellow boxes") there have been no major changes concerning editorial - OUTSMART as a chapter emerged and some sentences were rephrased. The final text and the diff is traceable in the wiki - the wiki is the single source of truth. https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php?title=D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page (links via "Structure"-section). I didn't check the front page again, there might be errors - other errors (editorial or formal) I as well might be overlooking them as I read the text already a number of times - please mark them or comment them and I can fix them. My proposal: wait for your review, integrate all changes and then submit. But again: I was not involved in the EC communication, so I can't judge the "urgency" of the deliverable really. Concerning needed input: although "possible" and as you outlined, the FI-WARE level analysis was only edited and commented very little by anybody. In the end I even deleted the chapter "Comments by FI-WARE management" because there was actually zero content. Now it "looks" as no sections has been planned, but as a reviewer I would immediately ask the question (especially after the section about the identified "main-inhibitors") if all of them were duly addressed by the consortium. Just ending the section there without any comment (as currently) is a bit harsh and we will have to comment on this on the review. If we already would know that all of the inhibitors were taking care of, why not write this and - at least for some - give proper examples of reactions of the UC projects. Unfortunately I can't provide this text - therefore I would kindly ask for contributions by anybody. If you input here - please make a introduce a separate section "Comments by FI-WARE management/leadership" or something similar. Section in question: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_level_analysis#Results_from_.22validation_context.22_dimension_questions As always: you can work on wiki/doc (but please use TRACK CHANGES) or any other format and I will integrate this in the final wiki-based deliverable if needed. Best regards, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 18. November 2013 07:43 To: Sandfuchs, Thorsten; stefano de panfilis; fiware-testbed at lists.fi-ware.eu Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear Thorsten, Thanks for your I have planed to review this deliverable before tomorrow, but if you want to deliver it today by all means, I won't object. After all, I quickly checked the yellow boxes where you asked for input and I understood they were not just for me but for all WPLs and WPAs (referred collectively as management since indeed architecture chapter WPs are managed through the direct involvement of WPLs and WPAs). Indeed, while I can provide comments in most of the cases, they shouldn't be so much different from those that can be provided by the WPLs/WPAs because most of the comments by UC projects, or data extracted from the questionnaires they have filled, go into details about usage of the GEis linked to the several chapters. I can carry out, though, a final review before tomorrow as I have just said. As you wish. But let me know so that I don't work in vain. If there is any particular section where my concrete input would relevant, please let me know. BTW, I found a couple of editorial issues when I quickly perform a first reading of the contents of the version you distributed last week ... have you fixed those in this version ? If you don't recall having fixed any editorial ... then I would suggest to carefully review the writing ... 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 FI-PPP Architecture Board chairman 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 15/11/13 16:58, Sandfuchs, Thorsten wrote: Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! _____ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Mon Nov 18 10:46:43 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 18 Nov 2013 09:46:43 +0000 Subject: [Fiware-wpl] Backlog: Dashboard, Review and hotTopics -> updated Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B817@EX10-MB2-MAD.hi.inet> Dear Partners, Please, find below the links to updated views: Dashboards: Apps: https://forge.fi-ware.eu/docman/view.php/27/3083/FIWARE.backlog.apps.dashboard.20131118.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3084/FIWARE.backlog.cloud.dashboard.20131118.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3087/FIWARE.backlog.iot.dashboard.20131118.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3085/FIWARE.backlog.data.dashboard.20131118.xlsx I2nd: https://forge.fi-ware.eu/docman/view.php/27/3086/FIWARE.backlog.i2nd.dashboard.20131118.xlsx Sec: https://forge.fi-ware.eu/docman/view.php/27/3088/FIWARE.backlog.security.dashboard.20131118.xlsx Please, notice the flow chart has now an additional curve. Review: Apps: https://forge.fi-ware.eu/docman/view.php/27/3089/FIWARE.backlog.apps.review.20131118.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3090/FIWARE.backlog.cloud.review.20131118.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3093/FIWARE.backlog.iot.review.20131118.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3091/FIWARE.backlog.data.review.20131118.xlsx I2nd: https://forge.fi-ware.eu/docman/view.php/27/3092/FIWARE.backlog.i2nd.review.20131118.xlsx Sec: https://forge.fi-ware.eu/docman/view.php/27/3094/FIWARE.backlog.security.review.20131118.xlsx Hot Topics: Catalogue: https://forge.fi-ware.eu/docman/view.php/27/3095/FIWARE.backlog.hotTopic-Catalogue.20131118.xlsx TrainingMaterial: https://forge.fi-ware.eu/docman/view.php/27/3097/FIWARE.backlog.hotTopic-TrainingMaterial.20131118.xlsx LutzReport: https://forge.fi-ware.eu/docman/view.php/27/3096/FIWARE.backlog.hotTopic-LutzReport.20131118.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 18 11:04:40 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 18 Nov 2013 11:04:40 +0100 Subject: [Fiware-wpl] Link for today's call Message-ID: <5289E638.3010305@tid.es> https://docs.google.com/document/d/1z-NXeT1DsXfESy2jQ5OtuWNmEzDYZuaLEfBBLzKNQAA/edit?pli=1# -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From stefano.depanfilis at eng.it Mon Nov 18 11:33:01 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 18 Nov 2013 11:33:01 +0100 Subject: [Fiware-wpl] URGENT: integration report status and documentation status Message-ID: dear colleagues, please find attached the status of the integration test. we had already to deliver this, but the situation is that only wp3 and wp6 are fine (well wp6 simply becouse there aro no dependencies to test). the worstto say is that despite the offer to provide support no support has been provided (except wp3, thank you thortsen) thus no integration test was possible at all. our position is to deliver this deliverable as standing, of course this will affect also the effort accounted to wp10 that i'm going unilaterlay to reduce.... in addition you have also the situation of our check over the documentation. again as this table was sent end of september no actions have been taken. this is not part of the deliverable itself (we have to discuss where to put it), but of course affects the answers to lutz .... ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed-Release_2.3_StatusReport.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 47591 bytes Desc: not available URL: From markus.heller at sap.com Mon Nov 18 11:43:42 2013 From: markus.heller at sap.com (Heller, Markus) Date: Mon, 18 Nov 2013 10:43:42 +0000 Subject: [Fiware-wpl] Deliverable "3rd Party Enablement" - Proposal for TOC / content Message-ID: <393554EDCF801348BC53C7813C6CB73B1A7499E7@DEWDFEMB14A.global.corp.sap> Hi all, as discussed in today WPL/WPA telco, I propose the following ideas for inclusion (might be interesting for a reader). meant for WP3 - Contents / but maybe relevant for all WPs: 1. Architecture Changes: Description of changes in Architecture during reporting period that helped somehow the uptake/enablement of 3rd parties. 2. Licenses/T&C Status: Diagram/Table showing overview of all WP3 license software assets and T+C info open specs (like in M24 review) and text explaining this 3. FI-WARE Catalog & FI-LAB / Testbedas Status: Diagram/Table showing current state of availability in FI-WARE Catalog and FI-LAB (BUT: Two columns, one is "submitted for approval / available for publication", the other column "approved and published" --> because current pipeline status would otherwise work against WP3 interests :)) 4. Software Releases Status: Exec Summary-like short overview of Software Releases 2 and 3 (as in the reporting period). 5. Example success stories: how the WP3 e.g. for some UC enabled them to work...(optional, or leave out here and refer to reports on UC successes reported somewhere in other deliverables?). Templates for Tables needed: For all, we need templates to have them aligned in the chapter section, give a good overall document impression IMHO and simplifies work for all. The texts explaining these template tables could then be more individual, while I personally also here would recommend some structural text templeates that then more or less is simply filled with text by chapter teams: My opinion: Most of these topics are interesting IMHO for each chapter. I recommend to leave them inside the chapter sections and _not_ move them into a general section in the document, because otherwise no real interesting content would remain to be reported in the chapter sections... And the work can be better distributed. Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Nov 19 09:05:26 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 19 Nov 2013 09:05:26 +0100 Subject: [Fiware-wpl] Fwd: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 In-Reply-To: References: Message-ID: <528B1BC6.1090200@tid.es> Dear all, I just wanted to share with you the official invitation for the review as we get it. Best regards, Miguel -------- Mensaje original -------- Asunto: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 Fecha: Tue, 19 Nov 2013 07:55:46 +0000 De: Para: , CC: , , , , , , , Dear Mr. Hierro, In accordance with Article II.23 of the contract, and as agreed with you recently, I hereby inform you of the Commission's intention to hold a review meeting of the project FP7-ICT-285248 FI-WARE in Brussels, Belgium on 18th December 2013. The meeting will take place in the premises of the European Commission in avenue de Beaulieu, 1160 Brussels Meeting rooms: 18th December 2013, avenue de Beaulieu BU25 0/S2 As agreed with you, the Commission will be assisted by the following independent experts: - Mr Renaud Di Fancesco - Mr Dominic Greenwood - Mrs Man-Sze Li - Mrs Irena Pavlova - Mr Lutz Schubert The objectives of the review are, in particular, to establish: * the degree of fulfillment of the project work plan for the relevant period and of the related deliverables; * the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; * the resources planned and utilized in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; * the management procedures and methods of the project; * the beneficiaries' contributions and integration within the project; * the expected potential impact in scientific, technologic, economic, competitive and social terms (where relevant), and the plans for the use and dissemination of results. If you have not sent the deliverables for this review period (months 25 to 30) to the European Commission yet, please do so as soon as possible and put the experts (see cc) in copy. Please send us the draft agenda of this meeting before Wednesday 4th December 2013. Please send me the names of the people attending the review Wednesday 11th December 2013. Should you have any questions before the meeting, please do not hesitate to contact me. Thank you for your co-operation. 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: From thierry.nagellen at orange.com Tue Nov 19 09:57:53 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 19 Nov 2013 08:57:53 +0000 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7DDE6@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> <5289B6FE.4030603@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD66486A7DDE6@DEWDFEMB11B.global.corp.sap> Message-ID: <4071_1384851474_528B2812_4071_19210_1_976A65C5A08ADF49B9A8523F7F81925C149A5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Based on mailing lists concerns I'm not sure that everyone receive this email I sent yesterday. Apologize if you receive it twice. BR Thierry -------------------------- Dear all, I've added some comments very quickly regarding main inhibitors. Please take time to read them and improve them. This is not a chapter view but a more general approach explaining how we did our best to improve the relationships with UC projects. https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_level_analysis#Main_inhibitors_identified_by_the_use_case_projects BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Sandfuchs, Thorsten Envoy? : lundi 18 novembre 2013 08:42 ? : Juanjo Hierro; stefano de panfilis Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear colleagues, as I was not involved in the interaction with the EC to postpone this deliverable, I honestly can't judge if this can be postponed again. I would assume as it in general is not more "major" than other deliverables, it might be able to wait another day... but in the end this decision has to come from the management level & the people interacting with timing of deliverables towards the EC. Since the last version (with or without "yellow boxes") there have been no major changes concerning editorial - OUTSMART as a chapter emerged and some sentences were rephrased. The final text and the diff is traceable in the wiki - the wiki is the single source of truth. https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php?title=D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page (links via "Structure"-section). I didn't check the front page again, there might be errors - other errors (editorial or formal) I as well might be overlooking them as I read the text already a number of times - please mark them or comment them and I can fix them. My proposal: wait for your review, integrate all changes and then submit. But again: I was not involved in the EC communication, so I can't judge the "urgency" of the deliverable really. Concerning needed input: although "possible" and as you outlined, the FI-WARE level analysis was only edited and commented very little by anybody. In the end I even deleted the chapter "Comments by FI-WARE management" because there was actually zero content. Now it "looks" as no sections has been planned, but as a reviewer I would immediately ask the question (especially after the section about the identified "main-inhibitors") if all of them were duly addressed by the consortium. Just ending the section there without any comment (as currently) is a bit harsh and we will have to comment on this on the review. If we already would know that all of the inhibitors were taking care of, why not write this and - at least for some - give proper examples of reactions of the UC projects. Unfortunately I can't provide this text - therefore I would kindly ask for contributions by anybody. If you input here - please make a introduce a separate section "Comments by FI-WARE management/leadership" or something similar. Section in question: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_level_analysis#Results_from_.22validation_context.22_dimension_questions As always: you can work on wiki/doc (but please use TRACK CHANGES) or any other format and I will integrate this in the final wiki-based deliverable if needed. Best regards, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 18. November 2013 07:43 To: Sandfuchs, Thorsten; stefano de panfilis; fiware-testbed at lists.fi-ware.eu Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear Thorsten, Thanks for your I have planed to review this deliverable before tomorrow, but if you want to deliver it today by all means, I won't object. After all, I quickly checked the yellow boxes where you asked for input and I understood they were not just for me but for all WPLs and WPAs (referred collectively as management since indeed architecture chapter WPs are managed through the direct involvement of WPLs and WPAs). Indeed, while I can provide comments in most of the cases, they shouldn't be so much different from those that can be provided by the WPLs/WPAs because most of the comments by UC projects, or data extracted from the questionnaires they have filled, go into details about usage of the GEis linked to the several chapters. I can carry out, though, a final review before tomorrow as I have just said. As you wish. But let me know so that I don't work in vain. If there is any particular section where my concrete input would relevant, please let me know. BTW, I found a couple of editorial issues when I quickly perform a first reading of the contents of the version you distributed last week ... have you fixed those in this version ? If you don't recall having fixed any editorial ... then I would suggest to carefully review the writing ... 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 FI-PPP Architecture Board chairman 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 15/11/13 16:58, Sandfuchs, Thorsten wrote: Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Tue Nov 19 09:59:37 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 19 Nov 2013 08:59:37 +0000 Subject: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) In-Reply-To: <4071_1384851474_528B2812_4071_19210_1_976A65C5A08ADF49B9A8523F7F81925C149A5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> <5289B6FE.4030603@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD66486A7DDE6@DEWDFEMB11B.global.corp.sap> <4071_1384851474_528B2812_4071_19210_1_976A65C5A08ADF49B9A8523F7F81925C149A5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7F047@DEWDFEMB11B.global.corp.sap> Very valuable input - thanks! Will be part of the final deliverable. Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. November 2013 09:58 To: Sandfuchs, Thorsten; Juanjo Hierro; stefano de panfilis Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) Based on mailing lists concerns I'm not sure that everyone receive this email I sent yesterday. Apologize if you receive it twice. BR Thierry -------------------------- Dear all, I've added some comments very quickly regarding main inhibitors. Please take time to read them and improve them. This is not a chapter view but a more general approach explaining how we did our best to improve the relationships with UC projects. https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_level_analysis#Main_inhibitors_identified_by_the_use_case_projects BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Sandfuchs, Thorsten Envoy? : lundi 18 novembre 2013 08:42 ? : Juanjo Hierro; stefano de panfilis Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear colleagues, as I was not involved in the interaction with the EC to postpone this deliverable, I honestly can't judge if this can be postponed again. I would assume as it in general is not more "major" than other deliverables, it might be able to wait another day... but in the end this decision has to come from the management level & the people interacting with timing of deliverables towards the EC. Since the last version (with or without "yellow boxes") there have been no major changes concerning editorial - OUTSMART as a chapter emerged and some sentences were rephrased. The final text and the diff is traceable in the wiki - the wiki is the single source of truth. https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php?title=D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page (links via "Structure"-section). I didn't check the front page again, there might be errors - other errors (editorial or formal) I as well might be overlooking them as I read the text already a number of times - please mark them or comment them and I can fix them. My proposal: wait for your review, integrate all changes and then submit. But again: I was not involved in the EC communication, so I can't judge the "urgency" of the deliverable really. Concerning needed input: although "possible" and as you outlined, the FI-WARE level analysis was only edited and commented very little by anybody. In the end I even deleted the chapter "Comments by FI-WARE management" because there was actually zero content. Now it "looks" as no sections has been planned, but as a reviewer I would immediately ask the question (especially after the section about the identified "main-inhibitors") if all of them were duly addressed by the consortium. Just ending the section there without any comment (as currently) is a bit harsh and we will have to comment on this on the review. If we already would know that all of the inhibitors were taking care of, why not write this and - at least for some - give proper examples of reactions of the UC projects. Unfortunately I can't provide this text - therefore I would kindly ask for contributions by anybody. If you input here - please make a introduce a separate section "Comments by FI-WARE management/leadership" or something similar. Section in question: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_level_analysis#Results_from_.22validation_context.22_dimension_questions As always: you can work on wiki/doc (but please use TRACK CHANGES) or any other format and I will integrate this in the final wiki-based deliverable if needed. Best regards, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Montag, 18. November 2013 07:43 To: Sandfuchs, Thorsten; stefano de panfilis; fiware-testbed at lists.fi-ware.eu Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear Thorsten, Thanks for your I have planed to review this deliverable before tomorrow, but if you want to deliver it today by all means, I won't object. After all, I quickly checked the yellow boxes where you asked for input and I understood they were not just for me but for all WPLs and WPAs (referred collectively as management since indeed architecture chapter WPs are managed through the direct involvement of WPLs and WPAs). Indeed, while I can provide comments in most of the cases, they shouldn't be so much different from those that can be provided by the WPLs/WPAs because most of the comments by UC projects, or data extracted from the questionnaires they have filled, go into details about usage of the GEis linked to the several chapters. I can carry out, though, a final review before tomorrow as I have just said. As you wish. But let me know so that I don't work in vain. If there is any particular section where my concrete input would relevant, please let me know. BTW, I found a couple of editorial issues when I quickly perform a first reading of the contents of the version you distributed last week ... have you fixed those in this version ? If you don't recall having fixed any editorial ... then I would suggest to carefully review the writing ... 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 FI-PPP Architecture Board chairman 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 15/11/13 16:58, Sandfuchs, Thorsten wrote: Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Nov 19 10:23:09 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 19 Nov 2013 10:23:09 +0100 Subject: [Fiware-wpl] D8.1.2 Resubmission - Need urgently your final review (IdM GE Open Specs) Message-ID: <30493_1384852997_528B2E05_30493_12026_2_6e5ffae9-31f5-4696-b8b3-3219548b3f7c@THSONEA01HUB06P.one.grp> Dear Juanjo, This email just to let you know that we are still awaiting for your review of IdM GE Open Specifications which has been redrafted by IdM GE owners to address reviewers comments also yours. Being said we called for your final review by end of October/early November I would appreciate if you could deliver it to us asap being said I don't want to delay re-submission of D8.1.2. Hope you can share with me on this. So counting on you to receive it asap (and obviously the sooner the better). Hearing from you. Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Nov 19 11:11:47 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Nov 2013 11:11:47 +0100 Subject: [Fiware-wpl] D8.1.2 Resubmission - Need urgently your final review (IdM GE Open Specs) In-Reply-To: <30493_1384852997_528B2E05_30493_12026_2_6e5ffae9-31f5-4696-b8b3-3219548b3f7c@THSONEA01HUB06P.one.grp> References: <30493_1384852997_528B2E05_30493_12026_2_6e5ffae9-31f5-4696-b8b3-3219548b3f7c@THSONEA01HUB06P.one.grp> Message-ID: <528B3963.1070908@tid.es> Question is that I identified some issues I believe should be fixed ... so I'm trying to provide detailed comments ... hopefully along today. 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 FI-PPP Architecture Board chairman 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/11/13 10:23, BISSON Pascal wrote: Dear Juanjo, This email just to let you know that we are still awaiting for your review of IdM GE Open Specifications which has been redrafted by IdM GE owners to address reviewers comments also yours. Being said we called for your final review by end of October/early November I would appreciate if you could deliver it to us asap being said I don't want to delay re-submission of D8.1.2. Hope you can share with me on this. So counting on you to receive it asap (and obviously the sooner the better). Hearing from you. Regards, Pascal ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 19 11:13:05 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 19 Nov 2013 11:13:05 +0100 Subject: [Fiware-wpl] Fwd: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 In-Reply-To: References: Message-ID: <528B39B1.4070501@tid.es> Hi, Distributed as convenient. 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 FI-PPP Architecture Board chairman 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: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 Date: Tue, 19 Nov 2013 07:55:46 +0000 From: To: , CC: , , , , , , , Dear Mr. Hierro, In accordance with Article II.23 of the contract, and as agreed with you recently, I hereby inform you of the Commission's intention to hold a review meeting of the project FP7-ICT-285248 FI-WARE in Brussels, Belgium on 18th December 2013. The meeting will take place in the premises of the European Commission in avenue de Beaulieu, 1160 Brussels Meeting rooms: 18th December 2013, avenue de Beaulieu BU25 0/S2 As agreed with you, the Commission will be assisted by the following independent experts: - Mr Renaud Di Fancesco - Mr Dominic Greenwood - Mrs Man-Sze Li - Mrs Irena Pavlova - Mr Lutz Schubert The objectives of the review are, in particular, to establish: * the degree of fulfillment of the project work plan for the relevant period and of the related deliverables; * the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; * the resources planned and utilized in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; * the management procedures and methods of the project; * the beneficiaries' contributions and integration within the project; * the expected potential impact in scientific, technologic, economic, competitive and social terms (where relevant), and the plans for the use and dissemination of results. If you have not sent the deliverables for this review period (months 25 to 30) to the European Commission yet, please do so as soon as possible and put the experts (see cc) in copy. Please send us the draft agenda of this meeting before Wednesday 4th December 2013. Please send me the names of the people attending the review Wednesday 11th December 2013. Should you have any questions before the meeting, please do not hesitate to contact me. Thank you for your co-operation. 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: From markus.heller at sap.com Tue Nov 19 11:24:53 2013 From: markus.heller at sap.com (Heller, Markus) Date: Tue, 19 Nov 2013 10:24:53 +0000 Subject: [Fiware-wpl] Fwd: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 In-Reply-To: <528B39B1.4070501@tid.es> References: <528B39B1.4070501@tid.es> Message-ID: <393554EDCF801348BC53C7813C6CB73B1A74A411@DEWDFEMB14A.global.corp.sap> Hi, When reading the "objectives of the review" section: - What would we all see if there are really new noteworthy objectives in here, what do you mean? - For example, will the review be more as usual or will there really be this (earlier indicated) "per GE" / "per Partner" focus for which we are preparing ourselves at the moment.? Lutz Schubert will attend, so at least this is a sign of a more GE/partner focus maybe, (any received agenda hints by Arian maybe)? What do you mean? Best wishes Markus From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Dienstag, 19. November 2013 11:13 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 Hi, Distributed as convenient. 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 FI-PPP Architecture Board chairman 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: FP7-ICT - 285248 FI-WARE - Official Invitation to Review Meeting - Brussels, 18th December 2013 Date: Tue, 19 Nov 2013 07:55:46 +0000 From: To: , CC: , , , , , , , Dear Mr. Hierro, In accordance with Article II.23 of the contract, and as agreed with you recently, I hereby inform you of the Commission's intention to hold a review meeting of the project FP7-ICT-285248 FI-WARE in Brussels, Belgium on 18th December 2013. The meeting will take place in the premises of the European Commission in avenue de Beaulieu, 1160 Brussels Meeting rooms: 18th December 2013, avenue de Beaulieu BU25 0/S2 As agreed with you, the Commission will be assisted by the following independent experts: - Mr Renaud Di Fancesco - Mr Dominic Greenwood - Mrs Man-Sze Li - Mrs Irena Pavlova - Mr Lutz Schubert The objectives of the review are, in particular, to establish: ? the degree of fulfillment of the project work plan for the relevant period and of the related deliverables; ? the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; ? the resources planned and utilized in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; ? the management procedures and methods of the project; ? the beneficiaries' contributions and integration within the project; ? the expected potential impact in scientific, technologic, economic, competitive and social terms (where relevant), and the plans for the use and dissemination of results. If you have not sent the deliverables for this review period (months 25 to 30) to the European Commission yet, please do so as soon as possible and put the experts (see cc) in copy. Please send us the draft agenda of this meeting before Wednesday 4th December 2013. Please send me the names of the people attending the review Wednesday 11th December 2013. Should you have any questions before the meeting, please do not hesitate to contact me. Thank you for your co-operation. 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: From pierangelo.garino at telecomitalia.it Tue Nov 19 17:46:52 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 19 Nov 2013 17:46:52 +0100 Subject: [Fiware-wpl] R: [Fiware-testbed] D.10.5.2b validation analysis and report final version (submission postponed to monday) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7CE3F@DEWDFEMB11B.global.corp.sap> Message-ID: Dear Thorsten, as defined in WP10 call today, I have added some comment in section 11 Validation methodology analysis. I activated the track changes so it should be easy identifying them, please review them and incorporate in the wiki if acceptable (maybe other WPLs can comment on them). BR Pier Da: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: venerd? 15 novembre 2013 16:58 A: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; Juanjo Hierro Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-testbed] D.10.5.2b validation analysis and report final version (submission postponed to monday) Dear colleagues, as juanjo seems to be busy and not in spain, there seems to be the weekend left for last fixes. If you can find any problems in the attached version of the deliverable, please let me know. Please use TRACK CHANGES if you change something in the file. This version is still not released to the final wiki (accessible to all use case projects and EC) - so it is NOT the real final one, but if no changes are there in the text any more, I would release it. I now deleted every "yellow" box in this version, still I would presume that the reviewers would find that FI-ware management did not comment a lot on the "findings" we unearthed, but that most probably will be the risk that we will face here. I as well compiled a possible "executive summary". Please carefully re-read the deliverable and I will do the move to the review-wiki on Monday morning, submission then on Monday EOB the latest. Thanks for everybodies dedication and support in this topic! Best, /Thorsten From: Sandfuchs, Thorsten Sent: Mittwoch, 13. November 2013 19:47 To: stefano de panfilis; fiware-testbed at lists.fi-ware.eu; 'Juanjo Hierro' Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: D.10.5.2b validation analysis and report ready for review within the next business day Dear colleagues, please find the current version of the D.10.5.2b deliverable for your consideration and review (you have one business day). The latest changes I introduced are yet to be dully synced with the wiki, but this I will do tomorrow prior to final compilation. Of the deliverable on Friday. Please provide your feedback, comments or direct changes (please use the track-changes functionality!!) in the word version directly and send it back to me. What is open? - Especially for FI-WARE project management some more verbose information is highly needed e.g. in chapter FI-WARE level analysis (chapter 3.3). What did we draw out of the validation in this respect and how do we address the identified challenges? What was perceived good by fi-ware? - OUTSMART use case analysis is still missing - I will add some further and more details on the chapter 11 "validation methodology" - Review by all of the interested parties Additionally we need a fresh minded review of the deliverable and judgment whether we present the FI-WARE project "good enough" and actually to the high level, that we actually reached so far. Please take this seriously as I would imagine that this report might be considered for the next review as well in relation to GO or NO-GO decisions of your Generic Enablers! To ease up readability you might consider activating the "final markup"-view in word or, prior to the introduction of new changes, just accept all pending changes that the team did before. Thanks for any support & 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! 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: D1052b_WP10_v7_generated-PG.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 2043233 bytes Desc: D1052b_WP10_v7_generated-PG.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From thorsten.sandfuchs at sap.com Wed Nov 20 10:25:10 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Nov 2013 09:25:10 +0000 Subject: [Fiware-wpl] Final version of D.10.5.2.b validation analysis & recommendation for submission to EC Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FBA7@DEWDFEMB11B.global.corp.sap> Dear colleagues, I hereby attach the final version of the deliverable "D.10.5.2b Report on Validation Process including Validation with Use Case projects" as docx. There is one last thing missing & it is commented in the doc: a link to a file, which I can't upload to the fi-ware-review forge. This is the last AP which is open: @Miguel: please upload the file (https://forge.fi-ware.eu/docman/view.php/27/3107/2013-10-07-validation-answers-to-validation-questionnaire-phase-one_updated_september.xlsx) and link it in the final doc. @all: please do a quick check if you find any blocking issues, which I overlook during compilation. @all: thanks again a lot for your very valuable contributions & the support given. Other than that I would recommend submission of this deliverable to the EC ASAP and not later than today, 14:00 (please send any veto until then to Miguel, Juanjo and me). Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.10.5.2b Report on Validation Process including Validation with Use Case projects.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 2036252 bytes Desc: D.10.5.2b Report on Validation Process including Validation with Use Case projects.docx URL: From mev at tid.es Wed Nov 20 11:39:16 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 20 Nov 2013 10:39:16 +0000 Subject: [Fiware-wpl] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. 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 Nov 20 13:20:18 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Nov 2013 12:20:18 +0000 Subject: [Fiware-wpl] [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE10@DEWDFEMB11B.global.corp.sap> Hi Manuel, please let me emphasize that from the conversation we had on Monday, we clearly need to find a resolution to the initial "challenge" before you send out the graph below: [cid:image003.jpg at 01CEE5F3.3FBE8FF0] As anticipated already to you the "89%" is not acceptable for the WP3 chapter and was never accepted before. You calculated for apps the numbers not taking into account that involved partners followed all related guidance in the time they actually were in place as long as their components were "actively" maintained in the tracker. There have been new guidelines AFTER the partners left the project or the GEs were being actively "tracked" and governed. Only items that were actively worked on must be relevant for calculating the "hierarchy" view of the backlog items. As WP3 started to question the calculation of the metric from the beginning on and you actually in many telephone conferences anticipated that this would be resolved and we shouldn't care too much about it or we wouldn't find this in any EC related conversation, we actually accepted your reports so far - it seems now that this has changed & that "apps" now has a _reported_ "bad" rating from you and is drawn in front of the reviewers. "worst initial hierarchy"... Please update the graph as I propose the resolution as shown below - I think the resolution does not pose much effort on your side & would greatly improve the situation and allow the submission of the deliverable in time. Alternatively you could consider skipping this graph completely in your reporting for this reporting period until we can resolve this on management board level. 1. Given our internal calculations at least 32 of your 123 tracker items, are related to components which are not going to change and nobody can force other partners from introducing hierarchies to components, which they are not responsible for (e.g. ECE CompositionEditor) or which are no longer tracked in the backlog actively (e.g. USDL). As the related partner followed the related guidance always as far as they were valid, these items MUST not be counted in a "bad" sense on the chapters watch. ? Please delete the following 32 items for all of your related checkpoints in the above graph, starting with the 20/06/2013 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 2. The clear resolution that we reached in our telco was: we are focusing with our backlog-improvement work on the "current" (active) tracked items and in a number of telcos you promised, that we will be not counted on the closed items, which actually put a hard burden on us to maintain in the miss-performing forge-system and are considered not as relevant for the current activities. ? Therefore please delete from your 123 items, that you counted so fart - the following 113 lines, which actually do targed stories that are considered closed in the above graph, starting with the 20/06/2013 3205 Apps.ApplicationMashup.AddWidgetToWorkspace F=[] Story - Closed 4181 Apps.ApplicationMashup.ApplicationMashupRESTAPI F=[] Story - Closed 4491 Apps.ApplicationMashup.CommunicateBackendWithApplicationMashupThrougPubSub F=[] Story - Closed 3202 Apps.ApplicationMashup.CreateWiringAndPipingOfAMashup F=[] Story - Closed 3462 Apps.ApplicationMashup.DevelopAWidgetUsingOAuth2 F=[] Story - Closed 3460 Apps.ApplicationMashup.DevelopAWidgetUsingObjectStorage F=[] Story - Closed 3458 Apps.ApplicationMashup.DevelopAWidgetUsingPubSub F=[] Story - Closed 1828 Apps.ApplicationMashup.GEsIntegration F=[] Story - Closed 3206 Apps.ApplicationMashup.InstallOperator F=[] Story - Closed 3456 Apps.ApplicationMashup.IntegrationWithDataChapterGEs.DevelopAWidgetUsingAQueryBroker F=['3441'] Story - Closed 4605 Apps.ApplicationMashup.IntegrationWithExternalCatalogues F=[] Story - Closed 3203 Apps.ApplicationMashup.InteractionWithCatalogue F=[] Story - Closed 3204 Apps.ApplicationMashup.InteractionWithMarketplace F=[] Story - Closed 4094 Apps.ApplicationMashup.OAuth2APIAuthentication F=[] Story - Closed 3199 Apps.ApplicationMashup.PublishAMashupInASharedCatalogue F=[] Story - Closed 3198 Apps.ApplicationMashup.PublishAMashupInLocalCatalogue F=[] Story - Closed 3200 Apps.ApplicationMashup.PublishAMashupInMarketplace F=[] Story - Closed 1829 Apps.ApplicationMashup.SupportForLinkedUSDL F=[] Story - Closed 3463 Apps.ApplicationMashup.SupportForOAuth2Login F=[] Story - Closed 897 Apps.ApplicationMashup.SupportPushDrivenWidgets F=[] Story - Closed 3201 Apps.ApplicationMashup.UploadComponentInLocalCatalogue F=[] Story - Closed 1039 Apps.CompositionEditor.AnnotateServiceComposition F=[] Story - Closed 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 3407 Apps.LightSemanticComposition.DeployUndeployCompositionModel F=[] Story - Closed 3411 Apps.LightSemanticComposition.EnableDisableCompositionModel F=[] Story - Closed 3397 Apps.LightSemanticComposition.GenerateExecutableBPMNModel F=[] Story - Closed 3401 Apps.LightSemanticComposition.ProcessEngineIntegration F=[] Story - Closed 1399 Apps.LightSemanticComposition.SemanticDataMediation F=[] Story - Closed 3394 Apps.LightSemanticComposition.ValidateBPMNModel F=[] Story - Closed 625 Apps.Marketplace.ManageStoresAndOffers.OfferingAPI F=['620'] Story - Closed 626 Apps.Marketplace.ManageStoresAndOffers.StoreAPI F=['620'] Story - Closed 3658 Apps.Marketplace.PricingDecisionSupport.ComparePriceLevels F=[] Story - Closed 3655 Apps.Marketplace.PricingDecisionSupport.CreateMarketScenario F=[] Story - Closed 3661 Apps.Marketplace.PricingDecisionSupport.SimulatePriceLevels F=[] Story - Closed 628 Apps.Marketplace.RatingAndFeedback.RatingAPI F=['622'] Story - Closed 4898 Apps.Marketplace.RatingAndFeedback.Recommendation F=['622'] Story - Closed 629 Apps.Marketplace.RatingAndFeedback.ReviewAPI F=['622'] Story - Closed 4897 Apps.Marketplace.RatingAndFeedback.ReviewAndRating F=['622'] Story - Closed 632 Apps.Marketplace.ServiceComparison.ComparisonAPI F=['623'] Story - Closed 631 Apps.Marketplace.ServiceDiscovery.DiscoveryAPI F=['624'] Story - Closed 630 Apps.Marketplace.ServiceDiscovery.SearchAPI F=['624'] Story - Closed 1384 Apps.Mediation.BPMNManager F=[] Story - Closed 2077 Apps.Mediation.CreateBPMN20 F=[] Story - Closed 1811 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.GenericTransformation F=[] Story - Closed 1806 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.SMSServiceTransformation F=[] Story - Closed 1802 Apps.Mediation.ProtocolMediation.Security.REST.BasicAuthentication F=[] Story - Closed 1804 Apps.Mediation.ProtocolMediation.Security.SOAP.WSSecurity F=[] Story - Closed 1385 Apps.Mediation.TaskIOMapping F=[] Story - Closed 5507 Apps.Registry.CheckLicenseInformation F=[] Story - Closed 612 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.ListServiceDescriptions F=[] Story - Closed 611 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.RetrieveServiceDescription F=[] Story - Closed 610 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.UploadServiceDescription F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 933 Apps.ServiceMashup.SetupComposerExecutionEngine F=[] Story - Closed 3676 Apps.Store.AccessOfferingResources F=[] Story - Closed 4163 Apps.Store.BuyAServiceWithCreditCard F=[] Story - Closed 4164 Apps.Store.BuyAServiceWithPayPalAccount F=[] Story - Closed 4155 Apps.Store.ChargePeriodicPayments F=[] Story - Closed 4154 Apps.Store.ChargeSinglePayments F=[] Story - Closed 4158 Apps.Store.ChargeUseBasedPayments F=[] Story - Closed 3659 Apps.Store.CommentOfferings F=[] Story - Closed 3636 Apps.Store.CreateANewOffering F=[] Story - Closed 3678 Apps.Store.DeleteAnOffering F=[] Story - Closed 3646 Apps.Store.DeleteAnOfferingFromMarketplace F=[] Story - Closed 4162 Apps.Store.DownloadInvoice F=[] Story - Closed 4152 Apps.Store.FeedRSSWithCDR F=[] Story - Closed 4161 Apps.Store.FeedWithAccountingInfo F=[] Story - Closed 3652 Apps.Store.PerformAdministrationTasks F=[] Story - Closed 3642 Apps.Store.PublishAnOffering F=[] Story - Closed 3660 Apps.Store.RateOfferings F=[] Story - Closed 3637 Apps.Store.RegisterNewResource F=[] Story - Closed 3649 Apps.Store.RegisterRepository F=[] Story - Closed 3639 Apps.Store.RegisterStoreOnAMarketplace F=[] Story - Closed 4157 Apps.Store.RenovateSubscriptions F=[] Story - Closed 3638 Apps.Store.RetrieveOfferingInformation F=[] Story - Closed 3677 Apps.Store.SearchForOfferings F=[] Story - Closed 3656 Apps.Store.ShowOfferingsInformation F=[] Story - Closed 3654 Apps.Store.ShowPublishedOfferings F=[] Story - Closed 3653 Apps.Store.ShowUserOfferings F=[] Story - Closed 4156 Apps.Store.SubscribeService F=[] Story - Closed 3651 Apps.Store.UnregisterRepository F=[] Story - Closed 3640 Apps.Store.UnregisterStoreFromAMarketplace F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 4151 Apps.Store.NotifyRSSNewOffering F=[] Story - Dismissed Overall this would hopefully help you to demonstrate that actually the apps chapter is not any more on the "worst" part of the initial graph and you would be able to kindly change the sentence subsuming the performance of the apps chapter. Overall we would expect that we reach in the end 10 tracker items where the hierarchy is (still) not fixed by our partners (despite your initial number of 123). Thanks in advance for your support on this and best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Mittwoch, 20. November 2013 11:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. Thanks for cooperation! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 18380 bytes Desc: image003.jpg URL: From thorsten.sandfuchs at sap.com Wed Nov 20 13:48:12 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Nov 2013 12:48:12 +0000 Subject: [Fiware-wpl] [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE89@DEWDFEMB11B.global.corp.sap> Dear Manuel, Sort of the similar thing already mention for graph 3 in the previous mail, there are similar implications on your numbers in relation to the following graphs as outlined below. We would be very happy if we find a good consensus which "better" reflects the actual situation, before submission of these graphs to the EC. [cid:image003.jpg at 01CEE5F7.2657BC90] In the apps chapter we have on the tracker part 260 items which we clearly communicated and you clearly agreed that a resolution (non-automated) should not be accounted for further reporting - in particular the case was: fixing for the 260 items in tracker AND the wiki a mere caps-conversation (STORY => Story, FEATURE => Feature, ...) and so on must not be rated "badly" for the chapter. We accepted your figures as long as we knew they were not reported - now this changes and we like to emphasize that our agreement was to not report them. It was just not reasonable to fix this manually as it would impose days if not weeks of work for the people involved, where development efforts or other _real_ content work of FI-WARE would be not possible, just to fix this. Therefore: please delete in all of your reporting lines (starting with the 20/06/2013) and recalculate the tracker performance of the apps chapter WITHOUT the 260 "failed" tracker items. We would expect to degenerate the percentage (73%, 71%, 70%, ...) significantly. Additionally and with the the previous mail applied we would end up with ~492 instead of 865 failed tracker items e.g. for 2013-10-28 report. Thanks for your understanding and dedication to make this happen! /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Mittwoch, 20. November 2013 11:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. Thanks for cooperation! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 45579 bytes Desc: image003.jpg URL: From mev at tid.es Wed Nov 20 14:27:25 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 20 Nov 2013 13:27:25 +0000 Subject: [Fiware-wpl] [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE10@DEWDFEMB11B.global.corp.sap> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE10@DEWDFEMB11B.global.corp.sap> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CE7E@EX10-MB2-MAD.hi.inet> Hi Thorsten, The guideline governing the hierarchy of names was not changed in the resolution taken by the management board, so I don't agree with your comment on this point. As it's evident from having a look at the other chapters' hierarchy, which are in fairly good shape compared to Apps. Otherwise, all chapter's hierarchies would have similar profile. It's evident it's a particular circumstance happening in Apps chapter. I disagree on the way you're exposing this. The main directive I've sent to this chapter for several months have been: focus on fixing the hierarchy, and forget other mistakes. It's quite amazing you're now stating I've said "you shouldn't care too much". The evolution of this chapter compared to others clearly shows lack of reaction until end of September. However, The graphs shows you have improved it by almost 40% in the last 2 months, which is much appreciated. It shows you're taking now interest on fixing it. Thorsten, by the end of next month, there will be another delivery, so I see no point in delaying this any longer. I suggest Apps chapter focus on the new target and keep taking the problem seriously. On Monday I agree on Apps chapter rising the issue to the management board, but obviously it could have been done since June, in any management board meeting. Therefore, I don't agree on stopping the delivery for this reason. I don't see all this that dramatic. I think the main and most important message from this graph is that we are improving. And most important I'd like to report in the next delivery due by the end on December, all our KPI are close to 0% level, having then a reliable backlog. Kind regards, Manuel From: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Sent: mi?rcoles, 20 de noviembre de 2013 13:20 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Manuel, please let me emphasize that from the conversation we had on Monday, we clearly need to find a resolution to the initial "challenge" before you send out the graph below: [cid:image001.jpg at 01CEE5F9.0FBE7300] As anticipated already to you the "89%" is not acceptable for the WP3 chapter and was never accepted before. You calculated for apps the numbers not taking into account that involved partners followed all related guidance in the time they actually were in place as long as their components were "actively" maintained in the tracker. There have been new guidelines AFTER the partners left the project or the GEs were being actively "tracked" and governed. Only items that were actively worked on must be relevant for calculating the "hierarchy" view of the backlog items. As WP3 started to question the calculation of the metric from the beginning on and you actually in many telephone conferences anticipated that this would be resolved and we shouldn't care too much about it or we wouldn't find this in any EC related conversation, we actually accepted your reports so far - it seems now that this has changed & that "apps" now has a _reported_ "bad" rating from you and is drawn in front of the reviewers. "worst initial hierarchy"... Please update the graph as I propose the resolution as shown below - I think the resolution does not pose much effort on your side & would greatly improve the situation and allow the submission of the deliverable in time. Alternatively you could consider skipping this graph completely in your reporting for this reporting period until we can resolve this on management board level. 1. Given our internal calculations at least 32 of your 123 tracker items, are related to components which are not going to change and nobody can force other partners from introducing hierarchies to components, which they are not responsible for (e.g. ECE CompositionEditor) or which are no longer tracked in the backlog actively (e.g. USDL). As the related partner followed the related guidance always as far as they were valid, these items MUST not be counted in a "bad" sense on the chapters watch. ? Please delete the following 32 items for all of your related checkpoints in the above graph, starting with the 20/06/2013 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 2. The clear resolution that we reached in our telco was: we are focusing with our backlog-improvement work on the "current" (active) tracked items and in a number of telcos you promised, that we will be not counted on the closed items, which actually put a hard burden on us to maintain in the miss-performing forge-system and are considered not as relevant for the current activities. ? Therefore please delete from your 123 items, that you counted so fart - the following 113 lines, which actually do targed stories that are considered closed in the above graph, starting with the 20/06/2013 3205 Apps.ApplicationMashup.AddWidgetToWorkspace F=[] Story - Closed 4181 Apps.ApplicationMashup.ApplicationMashupRESTAPI F=[] Story - Closed 4491 Apps.ApplicationMashup.CommunicateBackendWithApplicationMashupThrougPubSub F=[] Story - Closed 3202 Apps.ApplicationMashup.CreateWiringAndPipingOfAMashup F=[] Story - Closed 3462 Apps.ApplicationMashup.DevelopAWidgetUsingOAuth2 F=[] Story - Closed 3460 Apps.ApplicationMashup.DevelopAWidgetUsingObjectStorage F=[] Story - Closed 3458 Apps.ApplicationMashup.DevelopAWidgetUsingPubSub F=[] Story - Closed 1828 Apps.ApplicationMashup.GEsIntegration F=[] Story - Closed 3206 Apps.ApplicationMashup.InstallOperator F=[] Story - Closed 3456 Apps.ApplicationMashup.IntegrationWithDataChapterGEs.DevelopAWidgetUsingAQueryBroker F=['3441'] Story - Closed 4605 Apps.ApplicationMashup.IntegrationWithExternalCatalogues F=[] Story - Closed 3203 Apps.ApplicationMashup.InteractionWithCatalogue F=[] Story - Closed 3204 Apps.ApplicationMashup.InteractionWithMarketplace F=[] Story - Closed 4094 Apps.ApplicationMashup.OAuth2APIAuthentication F=[] Story - Closed 3199 Apps.ApplicationMashup.PublishAMashupInASharedCatalogue F=[] Story - Closed 3198 Apps.ApplicationMashup.PublishAMashupInLocalCatalogue F=[] Story - Closed 3200 Apps.ApplicationMashup.PublishAMashupInMarketplace F=[] Story - Closed 1829 Apps.ApplicationMashup.SupportForLinkedUSDL F=[] Story - Closed 3463 Apps.ApplicationMashup.SupportForOAuth2Login F=[] Story - Closed 897 Apps.ApplicationMashup.SupportPushDrivenWidgets F=[] Story - Closed 3201 Apps.ApplicationMashup.UploadComponentInLocalCatalogue F=[] Story - Closed 1039 Apps.CompositionEditor.AnnotateServiceComposition F=[] Story - Closed 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 3407 Apps.LightSemanticComposition.DeployUndeployCompositionModel F=[] Story - Closed 3411 Apps.LightSemanticComposition.EnableDisableCompositionModel F=[] Story - Closed 3397 Apps.LightSemanticComposition.GenerateExecutableBPMNModel F=[] Story - Closed 3401 Apps.LightSemanticComposition.ProcessEngineIntegration F=[] Story - Closed 1399 Apps.LightSemanticComposition.SemanticDataMediation F=[] Story - Closed 3394 Apps.LightSemanticComposition.ValidateBPMNModel F=[] Story - Closed 625 Apps.Marketplace.ManageStoresAndOffers.OfferingAPI F=['620'] Story - Closed 626 Apps.Marketplace.ManageStoresAndOffers.StoreAPI F=['620'] Story - Closed 3658 Apps.Marketplace.PricingDecisionSupport.ComparePriceLevels F=[] Story - Closed 3655 Apps.Marketplace.PricingDecisionSupport.CreateMarketScenario F=[] Story - Closed 3661 Apps.Marketplace.PricingDecisionSupport.SimulatePriceLevels F=[] Story - Closed 628 Apps.Marketplace.RatingAndFeedback.RatingAPI F=['622'] Story - Closed 4898 Apps.Marketplace.RatingAndFeedback.Recommendation F=['622'] Story - Closed 629 Apps.Marketplace.RatingAndFeedback.ReviewAPI F=['622'] Story - Closed 4897 Apps.Marketplace.RatingAndFeedback.ReviewAndRating F=['622'] Story - Closed 632 Apps.Marketplace.ServiceComparison.ComparisonAPI F=['623'] Story - Closed 631 Apps.Marketplace.ServiceDiscovery.DiscoveryAPI F=['624'] Story - Closed 630 Apps.Marketplace.ServiceDiscovery.SearchAPI F=['624'] Story - Closed 1384 Apps.Mediation.BPMNManager F=[] Story - Closed 2077 Apps.Mediation.CreateBPMN20 F=[] Story - Closed 1811 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.GenericTransformation F=[] Story - Closed 1806 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.SMSServiceTransformation F=[] Story - Closed 1802 Apps.Mediation.ProtocolMediation.Security.REST.BasicAuthentication F=[] Story - Closed 1804 Apps.Mediation.ProtocolMediation.Security.SOAP.WSSecurity F=[] Story - Closed 1385 Apps.Mediation.TaskIOMapping F=[] Story - Closed 5507 Apps.Registry.CheckLicenseInformation F=[] Story - Closed 612 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.ListServiceDescriptions F=[] Story - Closed 611 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.RetrieveServiceDescription F=[] Story - Closed 610 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.UploadServiceDescription F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 933 Apps.ServiceMashup.SetupComposerExecutionEngine F=[] Story - Closed 3676 Apps.Store.AccessOfferingResources F=[] Story - Closed 4163 Apps.Store.BuyAServiceWithCreditCard F=[] Story - Closed 4164 Apps.Store.BuyAServiceWithPayPalAccount F=[] Story - Closed 4155 Apps.Store.ChargePeriodicPayments F=[] Story - Closed 4154 Apps.Store.ChargeSinglePayments F=[] Story - Closed 4158 Apps.Store.ChargeUseBasedPayments F=[] Story - Closed 3659 Apps.Store.CommentOfferings F=[] Story - Closed 3636 Apps.Store.CreateANewOffering F=[] Story - Closed 3678 Apps.Store.DeleteAnOffering F=[] Story - Closed 3646 Apps.Store.DeleteAnOfferingFromMarketplace F=[] Story - Closed 4162 Apps.Store.DownloadInvoice F=[] Story - Closed 4152 Apps.Store.FeedRSSWithCDR F=[] Story - Closed 4161 Apps.Store.FeedWithAccountingInfo F=[] Story - Closed 3652 Apps.Store.PerformAdministrationTasks F=[] Story - Closed 3642 Apps.Store.PublishAnOffering F=[] Story - Closed 3660 Apps.Store.RateOfferings F=[] Story - Closed 3637 Apps.Store.RegisterNewResource F=[] Story - Closed 3649 Apps.Store.RegisterRepository F=[] Story - Closed 3639 Apps.Store.RegisterStoreOnAMarketplace F=[] Story - Closed 4157 Apps.Store.RenovateSubscriptions F=[] Story - Closed 3638 Apps.Store.RetrieveOfferingInformation F=[] Story - Closed 3677 Apps.Store.SearchForOfferings F=[] Story - Closed 3656 Apps.Store.ShowOfferingsInformation F=[] Story - Closed 3654 Apps.Store.ShowPublishedOfferings F=[] Story - Closed 3653 Apps.Store.ShowUserOfferings F=[] Story - Closed 4156 Apps.Store.SubscribeService F=[] Story - Closed 3651 Apps.Store.UnregisterRepository F=[] Story - Closed 3640 Apps.Store.UnregisterStoreFromAMarketplace F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 4151 Apps.Store.NotifyRSSNewOffering F=[] Story - Dismissed Overall this would hopefully help you to demonstrate that actually the apps chapter is not any more on the "worst" part of the initial graph and you would be able to kindly change the sentence subsuming the performance of the apps chapter. Overall we would expect that we reach in the end 10 tracker items where the hierarchy is (still) not fixed by our partners (despite your initial number of 123). Thanks in advance for your support on this and best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Mittwoch, 20. November 2013 11:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: 18380 bytes Desc: image001.jpg URL: From thorsten.sandfuchs at sap.com Wed Nov 20 14:38:48 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Nov 2013 13:38:48 +0000 Subject: [Fiware-wpl] [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CE7E@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE10@DEWDFEMB11B.global.corp.sap> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CE7E@EX10-MB2-MAD.hi.inet> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8007D@DEWDFEMB11B.global.corp.sap> Hi Manuel, I think it's evident that the reaction in some parts of the reporting and backlog has nothing to do with accepted and agreed upon "non-reaction" in other parts - therefore I can only emphasize that it has been agreed together with you already in the beginning of your work that we are focusing our efforts on non-closed items and as outlined below. All of this with the clear background information about not reporting this to the EC, therefore not overstressing you in your startup period. The hierarchy and how it was finally computed out of the summary-names actually WAS implemented _after_ you started - before then there was not clear guidance and no tracking, nor the existed implementation was of any concern. Therefore the comment would still apply: the involved partners were action in everybodies best interest and this can't and must not degenerate the performance of the overall chapter. The proposal of me is not to diminish the fact that the apps chapter might have started to improve the situation in September, but the leveling of the overall thing. We merely started with a much lower level, as explainted below and this is what I want to have reflected. As in particular this is the first time this kind of reporting is in place, it is actually quite vital to be rightfully (and as agreed) reflected in this first delivery. The resubmission of this deliverable in the future is not relevant in this respect. Thanks for you understanding, /Thorsten From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: Mittwoch, 20. November 2013 14:27 To: Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Thorsten, The guideline governing the hierarchy of names was not changed in the resolution taken by the management board, so I don't agree with your comment on this point. As it's evident from having a look at the other chapters' hierarchy, which are in fairly good shape compared to Apps. Otherwise, all chapter's hierarchies would have similar profile. It's evident it's a particular circumstance happening in Apps chapter. I disagree on the way you're exposing this. The main directive I've sent to this chapter for several months have been: focus on fixing the hierarchy, and forget other mistakes. It's quite amazing you're now stating I've said "you shouldn't care too much". The evolution of this chapter compared to others clearly shows lack of reaction until end of September. However, The graphs shows you have improved it by almost 40% in the last 2 months, which is much appreciated. It shows you're taking now interest on fixing it. Thorsten, by the end of next month, there will be another delivery, so I see no point in delaying this any longer. I suggest Apps chapter focus on the new target and keep taking the problem seriously. On Monday I agree on Apps chapter rising the issue to the management board, but obviously it could have been done since June, in any management board meeting. Therefore, I don't agree on stopping the delivery for this reason. I don't see all this that dramatic. I think the main and most important message from this graph is that we are improving. And most important I'd like to report in the next delivery due by the end on December, all our KPI are close to 0% level, having then a reliable backlog. Kind regards, Manuel From: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Sent: mi?rcoles, 20 de noviembre de 2013 13:20 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Manuel, please let me emphasize that from the conversation we had on Monday, we clearly need to find a resolution to the initial "challenge" before you send out the graph below: [cid:image001.jpg at 01CEE5FE.38757A00] As anticipated already to you the "89%" is not acceptable for the WP3 chapter and was never accepted before. You calculated for apps the numbers not taking into account that involved partners followed all related guidance in the time they actually were in place as long as their components were "actively" maintained in the tracker. There have been new guidelines AFTER the partners left the project or the GEs were being actively "tracked" and governed. Only items that were actively worked on must be relevant for calculating the "hierarchy" view of the backlog items. As WP3 started to question the calculation of the metric from the beginning on and you actually in many telephone conferences anticipated that this would be resolved and we shouldn't care too much about it or we wouldn't find this in any EC related conversation, we actually accepted your reports so far - it seems now that this has changed & that "apps" now has a _reported_ "bad" rating from you and is drawn in front of the reviewers. "worst initial hierarchy"... Please update the graph as I propose the resolution as shown below - I think the resolution does not pose much effort on your side & would greatly improve the situation and allow the submission of the deliverable in time. Alternatively you could consider skipping this graph completely in your reporting for this reporting period until we can resolve this on management board level. 1. Given our internal calculations at least 32 of your 123 tracker items, are related to components which are not going to change and nobody can force other partners from introducing hierarchies to components, which they are not responsible for (e.g. ECE CompositionEditor) or which are no longer tracked in the backlog actively (e.g. USDL). As the related partner followed the related guidance always as far as they were valid, these items MUST not be counted in a "bad" sense on the chapters watch. => Please delete the following 32 items for all of your related checkpoints in the above graph, starting with the 20/06/2013 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 2. The clear resolution that we reached in our telco was: we are focusing with our backlog-improvement work on the "current" (active) tracked items and in a number of telcos you promised, that we will be not counted on the closed items, which actually put a hard burden on us to maintain in the miss-performing forge-system and are considered not as relevant for the current activities. => Therefore please delete from your 123 items, that you counted so fart - the following 113 lines, which actually do targed stories that are considered closed in the above graph, starting with the 20/06/2013 3205 Apps.ApplicationMashup.AddWidgetToWorkspace F=[] Story - Closed 4181 Apps.ApplicationMashup.ApplicationMashupRESTAPI F=[] Story - Closed 4491 Apps.ApplicationMashup.CommunicateBackendWithApplicationMashupThrougPubSub F=[] Story - Closed 3202 Apps.ApplicationMashup.CreateWiringAndPipingOfAMashup F=[] Story - Closed 3462 Apps.ApplicationMashup.DevelopAWidgetUsingOAuth2 F=[] Story - Closed 3460 Apps.ApplicationMashup.DevelopAWidgetUsingObjectStorage F=[] Story - Closed 3458 Apps.ApplicationMashup.DevelopAWidgetUsingPubSub F=[] Story - Closed 1828 Apps.ApplicationMashup.GEsIntegration F=[] Story - Closed 3206 Apps.ApplicationMashup.InstallOperator F=[] Story - Closed 3456 Apps.ApplicationMashup.IntegrationWithDataChapterGEs.DevelopAWidgetUsingAQueryBroker F=['3441'] Story - Closed 4605 Apps.ApplicationMashup.IntegrationWithExternalCatalogues F=[] Story - Closed 3203 Apps.ApplicationMashup.InteractionWithCatalogue F=[] Story - Closed 3204 Apps.ApplicationMashup.InteractionWithMarketplace F=[] Story - Closed 4094 Apps.ApplicationMashup.OAuth2APIAuthentication F=[] Story - Closed 3199 Apps.ApplicationMashup.PublishAMashupInASharedCatalogue F=[] Story - Closed 3198 Apps.ApplicationMashup.PublishAMashupInLocalCatalogue F=[] Story - Closed 3200 Apps.ApplicationMashup.PublishAMashupInMarketplace F=[] Story - Closed 1829 Apps.ApplicationMashup.SupportForLinkedUSDL F=[] Story - Closed 3463 Apps.ApplicationMashup.SupportForOAuth2Login F=[] Story - Closed 897 Apps.ApplicationMashup.SupportPushDrivenWidgets F=[] Story - Closed 3201 Apps.ApplicationMashup.UploadComponentInLocalCatalogue F=[] Story - Closed 1039 Apps.CompositionEditor.AnnotateServiceComposition F=[] Story - Closed 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 3407 Apps.LightSemanticComposition.DeployUndeployCompositionModel F=[] Story - Closed 3411 Apps.LightSemanticComposition.EnableDisableCompositionModel F=[] Story - Closed 3397 Apps.LightSemanticComposition.GenerateExecutableBPMNModel F=[] Story - Closed 3401 Apps.LightSemanticComposition.ProcessEngineIntegration F=[] Story - Closed 1399 Apps.LightSemanticComposition.SemanticDataMediation F=[] Story - Closed 3394 Apps.LightSemanticComposition.ValidateBPMNModel F=[] Story - Closed 625 Apps.Marketplace.ManageStoresAndOffers.OfferingAPI F=['620'] Story - Closed 626 Apps.Marketplace.ManageStoresAndOffers.StoreAPI F=['620'] Story - Closed 3658 Apps.Marketplace.PricingDecisionSupport.ComparePriceLevels F=[] Story - Closed 3655 Apps.Marketplace.PricingDecisionSupport.CreateMarketScenario F=[] Story - Closed 3661 Apps.Marketplace.PricingDecisionSupport.SimulatePriceLevels F=[] Story - Closed 628 Apps.Marketplace.RatingAndFeedback.RatingAPI F=['622'] Story - Closed 4898 Apps.Marketplace.RatingAndFeedback.Recommendation F=['622'] Story - Closed 629 Apps.Marketplace.RatingAndFeedback.ReviewAPI F=['622'] Story - Closed 4897 Apps.Marketplace.RatingAndFeedback.ReviewAndRating F=['622'] Story - Closed 632 Apps.Marketplace.ServiceComparison.ComparisonAPI F=['623'] Story - Closed 631 Apps.Marketplace.ServiceDiscovery.DiscoveryAPI F=['624'] Story - Closed 630 Apps.Marketplace.ServiceDiscovery.SearchAPI F=['624'] Story - Closed 1384 Apps.Mediation.BPMNManager F=[] Story - Closed 2077 Apps.Mediation.CreateBPMN20 F=[] Story - Closed 1811 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.GenericTransformation F=[] Story - Closed 1806 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.SMSServiceTransformation F=[] Story - Closed 1802 Apps.Mediation.ProtocolMediation.Security.REST.BasicAuthentication F=[] Story - Closed 1804 Apps.Mediation.ProtocolMediation.Security.SOAP.WSSecurity F=[] Story - Closed 1385 Apps.Mediation.TaskIOMapping F=[] Story - Closed 5507 Apps.Registry.CheckLicenseInformation F=[] Story - Closed 612 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.ListServiceDescriptions F=[] Story - Closed 611 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.RetrieveServiceDescription F=[] Story - Closed 610 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.UploadServiceDescription F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 933 Apps.ServiceMashup.SetupComposerExecutionEngine F=[] Story - Closed 3676 Apps.Store.AccessOfferingResources F=[] Story - Closed 4163 Apps.Store.BuyAServiceWithCreditCard F=[] Story - Closed 4164 Apps.Store.BuyAServiceWithPayPalAccount F=[] Story - Closed 4155 Apps.Store.ChargePeriodicPayments F=[] Story - Closed 4154 Apps.Store.ChargeSinglePayments F=[] Story - Closed 4158 Apps.Store.ChargeUseBasedPayments F=[] Story - Closed 3659 Apps.Store.CommentOfferings F=[] Story - Closed 3636 Apps.Store.CreateANewOffering F=[] Story - Closed 3678 Apps.Store.DeleteAnOffering F=[] Story - Closed 3646 Apps.Store.DeleteAnOfferingFromMarketplace F=[] Story - Closed 4162 Apps.Store.DownloadInvoice F=[] Story - Closed 4152 Apps.Store.FeedRSSWithCDR F=[] Story - Closed 4161 Apps.Store.FeedWithAccountingInfo F=[] Story - Closed 3652 Apps.Store.PerformAdministrationTasks F=[] Story - Closed 3642 Apps.Store.PublishAnOffering F=[] Story - Closed 3660 Apps.Store.RateOfferings F=[] Story - Closed 3637 Apps.Store.RegisterNewResource F=[] Story - Closed 3649 Apps.Store.RegisterRepository F=[] Story - Closed 3639 Apps.Store.RegisterStoreOnAMarketplace F=[] Story - Closed 4157 Apps.Store.RenovateSubscriptions F=[] Story - Closed 3638 Apps.Store.RetrieveOfferingInformation F=[] Story - Closed 3677 Apps.Store.SearchForOfferings F=[] Story - Closed 3656 Apps.Store.ShowOfferingsInformation F=[] Story - Closed 3654 Apps.Store.ShowPublishedOfferings F=[] Story - Closed 3653 Apps.Store.ShowUserOfferings F=[] Story - Closed 4156 Apps.Store.SubscribeService F=[] Story - Closed 3651 Apps.Store.UnregisterRepository F=[] Story - Closed 3640 Apps.Store.UnregisterStoreFromAMarketplace F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 4151 Apps.Store.NotifyRSSNewOffering F=[] Story - Dismissed Overall this would hopefully help you to demonstrate that actually the apps chapter is not any more on the "worst" part of the initial graph and you would be able to kindly change the sentence subsuming the performance of the apps chapter. Overall we would expect that we reach in the end 10 tracker items where the hierarchy is (still) not fixed by our partners (despite your initial number of 123). Thanks in advance for your support on this and best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Mittwoch, 20. November 2013 11:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: 18380 bytes Desc: image001.jpg URL: From jdps at tid.es Wed Nov 20 14:50:55 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 20 Nov 2013 13:50:55 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Message-ID: <77A22C1085494D48B4018F06A40DB2C73001DA7F@EX10-MB2-MAD.hi.inet> Dear all, in case there is missing information from a partner because they don't answer you, please change the label "xxx" on the report by "No input from partner. As far as the WPL knows, the contribution of the partner is ....." Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 13 de noviembre de 2013 23:21 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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Importancia: Alta Dear all, First of all, thank you very much for your contribution. Please find attached the first draft version of the Periodic Report M30 where we have integrated all the received contributions so far. I kindly ask you to use this one as basis in order to provide a new version of the report of your WP. Please check it, and complete where "xxx" is still written. Don't hesitate to share it with your involved partners. Note: We'll only accept changes in a WP from its own WPL. Deadline, November 20th, 2013, EOB. Please confirm the reception of this important e-mail. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 20 15:19:49 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 20 Nov 2013 14:19:49 +0000 Subject: [Fiware-wpl] [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8007D@DEWDFEMB11B.global.corp.sap> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CD7F@EX10-MB2-MAD.hi.inet> <2981E9D6242FCF47ADC9B5DBA5DFD66486A7FE10@DEWDFEMB11B.global.corp.sap> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CE7E@EX10-MB2-MAD.hi.inet> <2981E9D6242FCF47ADC9B5DBA5DFD66486A8007D@DEWDFEMB11B.global.corp.sap> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911CEE2@EX10-MB2-MAD.hi.inet> Hi Thorsten, Yes, how can I oppose to your internal strategy to focus first on active items? It's seem quite sensible to me. The reviews reports aren't reported - just the monitoring. I have to show progress. Otherwise, it's meaningless. It reads like you haven't started working until the end of September not to overstress me. Kidding!? The hierarchy was taken seriously by other chapters before my arrival -so it was right fairly well when monitoring started. The guidelines were clearly written by Juanjo. Small updated were done to simplify it - only minor amount of items needed to be modified for this change. So it's not an argument to be exposed. The Data chapter was in the worst situation 95%, they took the problem seriously and started working in June, and were able to get down to 26%. So I don't share your comments. I think the deliverable is right. And it's relevant the existence of new deliveries each term until the end of the project since it gives opportunities to show diligence in our work, excluding the dramatic approach all-nothing you're given, which is not real. Kind regards, Manuel From: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Sent: mi?rcoles, 20 de noviembre de 2013 14:39 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Manuel, I think it's evident that the reaction in some parts of the reporting and backlog has nothing to do with accepted and agreed upon "non-reaction" in other parts - therefore I can only emphasize that it has been agreed together with you already in the beginning of your work that we are focusing our efforts on non-closed items and as outlined below. All of this with the clear background information about not reporting this to the EC, therefore not overstressing you in your startup period. The hierarchy and how it was finally computed out of the summary-names actually WAS implemented _after_ you started - before then there was not clear guidance and no tracking, nor the existed implementation was of any concern. Therefore the comment would still apply: the involved partners were action in everybodies best interest and this can't and must not degenerate the performance of the overall chapter. The proposal of me is not to diminish the fact that the apps chapter might have started to improve the situation in September, but the leveling of the overall thing. We merely started with a much lower level, as explainted below and this is what I want to have reflected. As in particular this is the first time this kind of reporting is in place, it is actually quite vital to be rightfully (and as agreed) reflected in this first delivery. The resubmission of this deliverable in the future is not relevant in this respect. Thanks for you understanding, /Thorsten From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: Mittwoch, 20. November 2013 14:27 To: Sandfuchs, Thorsten; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Thorsten, The guideline governing the hierarchy of names was not changed in the resolution taken by the management board, so I don't agree with your comment on this point. As it's evident from having a look at the other chapters' hierarchy, which are in fairly good shape compared to Apps. Otherwise, all chapter's hierarchies would have similar profile. It's evident it's a particular circumstance happening in Apps chapter. I disagree on the way you're exposing this. The main directive I've sent to this chapter for several months have been: focus on fixing the hierarchy, and forget other mistakes. It's quite amazing you're now stating I've said "you shouldn't care too much". The evolution of this chapter compared to others clearly shows lack of reaction until end of September. However, The graphs shows you have improved it by almost 40% in the last 2 months, which is much appreciated. It shows you're taking now interest on fixing it. Thorsten, by the end of next month, there will be another delivery, so I see no point in delaying this any longer. I suggest Apps chapter focus on the new target and keep taking the problem seriously. On Monday I agree on Apps chapter rising the issue to the management board, but obviously it could have been done since June, in any management board meeting. Therefore, I don't agree on stopping the delivery for this reason. I don't see all this that dramatic. I think the main and most important message from this graph is that we are improving. And most important I'd like to report in the next delivery due by the end on December, all our KPI are close to 0% level, having then a reliable backlog. Kind regards, Manuel From: Sandfuchs, Thorsten [mailto:thorsten.sandfuchs at sap.com] Sent: mi?rcoles, 20 de noviembre de 2013 13:20 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Hi Manuel, please let me emphasize that from the conversation we had on Monday, we clearly need to find a resolution to the initial "challenge" before you send out the graph below: [cid:image001.jpg at 01CEE602.76F8C120] As anticipated already to you the "89%" is not acceptable for the WP3 chapter and was never accepted before. You calculated for apps the numbers not taking into account that involved partners followed all related guidance in the time they actually were in place as long as their components were "actively" maintained in the tracker. There have been new guidelines AFTER the partners left the project or the GEs were being actively "tracked" and governed. Only items that were actively worked on must be relevant for calculating the "hierarchy" view of the backlog items. As WP3 started to question the calculation of the metric from the beginning on and you actually in many telephone conferences anticipated that this would be resolved and we shouldn't care too much about it or we wouldn't find this in any EC related conversation, we actually accepted your reports so far - it seems now that this has changed & that "apps" now has a _reported_ "bad" rating from you and is drawn in front of the reviewers. "worst initial hierarchy"... Please update the graph as I propose the resolution as shown below - I think the resolution does not pose much effort on your side & would greatly improve the situation and allow the submission of the deliverable in time. Alternatively you could consider skipping this graph completely in your reporting for this reporting period until we can resolve this on management board level. 1. Given our internal calculations at least 32 of your 123 tracker items, are related to components which are not going to change and nobody can force other partners from introducing hierarchies to components, which they are not responsible for (e.g. ECE CompositionEditor) or which are no longer tracked in the backlog actively (e.g. USDL). As the related partner followed the related guidance always as far as they were valid, these items MUST not be counted in a "bad" sense on the chapters watch. => Please delete the following 32 items for all of your related checkpoints in the above graph, starting with the 20/06/2013 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 2. The clear resolution that we reached in our telco was: we are focusing with our backlog-improvement work on the "current" (active) tracked items and in a number of telcos you promised, that we will be not counted on the closed items, which actually put a hard burden on us to maintain in the miss-performing forge-system and are considered not as relevant for the current activities. => Therefore please delete from your 123 items, that you counted so fart - the following 113 lines, which actually do targed stories that are considered closed in the above graph, starting with the 20/06/2013 3205 Apps.ApplicationMashup.AddWidgetToWorkspace F=[] Story - Closed 4181 Apps.ApplicationMashup.ApplicationMashupRESTAPI F=[] Story - Closed 4491 Apps.ApplicationMashup.CommunicateBackendWithApplicationMashupThrougPubSub F=[] Story - Closed 3202 Apps.ApplicationMashup.CreateWiringAndPipingOfAMashup F=[] Story - Closed 3462 Apps.ApplicationMashup.DevelopAWidgetUsingOAuth2 F=[] Story - Closed 3460 Apps.ApplicationMashup.DevelopAWidgetUsingObjectStorage F=[] Story - Closed 3458 Apps.ApplicationMashup.DevelopAWidgetUsingPubSub F=[] Story - Closed 1828 Apps.ApplicationMashup.GEsIntegration F=[] Story - Closed 3206 Apps.ApplicationMashup.InstallOperator F=[] Story - Closed 3456 Apps.ApplicationMashup.IntegrationWithDataChapterGEs.DevelopAWidgetUsingAQueryBroker F=['3441'] Story - Closed 4605 Apps.ApplicationMashup.IntegrationWithExternalCatalogues F=[] Story - Closed 3203 Apps.ApplicationMashup.InteractionWithCatalogue F=[] Story - Closed 3204 Apps.ApplicationMashup.InteractionWithMarketplace F=[] Story - Closed 4094 Apps.ApplicationMashup.OAuth2APIAuthentication F=[] Story - Closed 3199 Apps.ApplicationMashup.PublishAMashupInASharedCatalogue F=[] Story - Closed 3198 Apps.ApplicationMashup.PublishAMashupInLocalCatalogue F=[] Story - Closed 3200 Apps.ApplicationMashup.PublishAMashupInMarketplace F=[] Story - Closed 1829 Apps.ApplicationMashup.SupportForLinkedUSDL F=[] Story - Closed 3463 Apps.ApplicationMashup.SupportForOAuth2Login F=[] Story - Closed 897 Apps.ApplicationMashup.SupportPushDrivenWidgets F=[] Story - Closed 3201 Apps.ApplicationMashup.UploadComponentInLocalCatalogue F=[] Story - Closed 1039 Apps.CompositionEditor.AnnotateServiceComposition F=[] Story - Closed 2078 Apps.CompositionEditor.CompositionDesigner F=[] Story - Closed 899 Apps.CompositionEditor.CreateMashupFromCatalog F=[] Story - Closed 1914 Apps.CompositionEditor.ECE-ExportToRepository F=[] Story - Closed 1915 Apps.CompositionEditor.ECE-ImportFromRepository F=[] Story - Closed 900 Apps.CompositionEditor.ExportMashupDefinition F=[] Story - Closed 2079 Apps.CompositionEditor.ImportExportBPMN20Models F=[] Story - Closed 901 Apps.CompositionEditor.ImportMashup F=[] Story - Closed 2130 Apps.CompositionEditor.MediatorIntegration F=[] Story - Closed 1380 Apps.CompositionEditor.OntologyBrowser F=[] Story - Closed 1378 Apps.CompositionEditor.SemanticComposerIntegration F=[] Story - Closed 1382 Apps.CompositionEditor.Service-ProcessSemanticDescriptionWidget F=[] Story - Closed 934 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1207 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 1209 Apps.CompositionEditor.SetupServiceComposer F=[] Story - Closed 2131 Apps.CompositionEditor.StoreDescriptionToUSDLRepository F=[] Story - Closed 1383 Apps.CompositionEditor.TaskBinding F=[] Story - Closed 1208 Apps.CompositionEditor.USDLInterfaceAdaption F=[] Story - Closed 882 Apps.ExecutionEngine.C3CreateLoadBalancedExecution F=[] Story - Closed 3407 Apps.LightSemanticComposition.DeployUndeployCompositionModel F=[] Story - Closed 3411 Apps.LightSemanticComposition.EnableDisableCompositionModel F=[] Story - Closed 3397 Apps.LightSemanticComposition.GenerateExecutableBPMNModel F=[] Story - Closed 3401 Apps.LightSemanticComposition.ProcessEngineIntegration F=[] Story - Closed 1399 Apps.LightSemanticComposition.SemanticDataMediation F=[] Story - Closed 3394 Apps.LightSemanticComposition.ValidateBPMNModel F=[] Story - Closed 625 Apps.Marketplace.ManageStoresAndOffers.OfferingAPI F=['620'] Story - Closed 626 Apps.Marketplace.ManageStoresAndOffers.StoreAPI F=['620'] Story - Closed 3658 Apps.Marketplace.PricingDecisionSupport.ComparePriceLevels F=[] Story - Closed 3655 Apps.Marketplace.PricingDecisionSupport.CreateMarketScenario F=[] Story - Closed 3661 Apps.Marketplace.PricingDecisionSupport.SimulatePriceLevels F=[] Story - Closed 628 Apps.Marketplace.RatingAndFeedback.RatingAPI F=['622'] Story - Closed 4898 Apps.Marketplace.RatingAndFeedback.Recommendation F=['622'] Story - Closed 629 Apps.Marketplace.RatingAndFeedback.ReviewAPI F=['622'] Story - Closed 4897 Apps.Marketplace.RatingAndFeedback.ReviewAndRating F=['622'] Story - Closed 632 Apps.Marketplace.ServiceComparison.ComparisonAPI F=['623'] Story - Closed 631 Apps.Marketplace.ServiceDiscovery.DiscoveryAPI F=['624'] Story - Closed 630 Apps.Marketplace.ServiceDiscovery.SearchAPI F=['624'] Story - Closed 1384 Apps.Mediation.BPMNManager F=[] Story - Closed 2077 Apps.Mediation.CreateBPMN20 F=[] Story - Closed 1811 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.GenericTransformation F=[] Story - Closed 1806 Apps.Mediation.ProtocolMediation.SOAP2REST.XSLT.SMSServiceTransformation F=[] Story - Closed 1802 Apps.Mediation.ProtocolMediation.Security.REST.BasicAuthentication F=[] Story - Closed 1804 Apps.Mediation.ProtocolMediation.Security.SOAP.WSSecurity F=[] Story - Closed 1385 Apps.Mediation.TaskIOMapping F=[] Story - Closed 5507 Apps.Registry.CheckLicenseInformation F=[] Story - Closed 612 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.ListServiceDescriptions F=[] Story - Closed 611 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.RetrieveServiceDescription F=[] Story - Closed 610 Apps.Repository.ManageStoresAndOffers.MaintainServiceDescription.UploadServiceDescription F=[] Story - Closed 881 Apps.ServiceComposition.C3IdentifyandParseUSDL F=[] Story - Closed 1900 Apps.ServiceComposition.ECE-ComposedServiceFormatInRepository F=[] Story - Closed 1926 Apps.ServiceComposition.ECE-CreateUSDLDescriptionForComposedServices F=[] Story - Closed 1931 Apps.ServiceComposition.ECE-ExposeServiceToMarketplace F=[] Story - Closed 1930 Apps.ServiceComposition.ECE-SearchInMarketplace F=[] Story - Closed 1899 Apps.ServiceComposition.ECE-ServiceFormatInRepository F=[] Story - Closed 933 Apps.ServiceMashup.SetupComposerExecutionEngine F=[] Story - Closed 3676 Apps.Store.AccessOfferingResources F=[] Story - Closed 4163 Apps.Store.BuyAServiceWithCreditCard F=[] Story - Closed 4164 Apps.Store.BuyAServiceWithPayPalAccount F=[] Story - Closed 4155 Apps.Store.ChargePeriodicPayments F=[] Story - Closed 4154 Apps.Store.ChargeSinglePayments F=[] Story - Closed 4158 Apps.Store.ChargeUseBasedPayments F=[] Story - Closed 3659 Apps.Store.CommentOfferings F=[] Story - Closed 3636 Apps.Store.CreateANewOffering F=[] Story - Closed 3678 Apps.Store.DeleteAnOffering F=[] Story - Closed 3646 Apps.Store.DeleteAnOfferingFromMarketplace F=[] Story - Closed 4162 Apps.Store.DownloadInvoice F=[] Story - Closed 4152 Apps.Store.FeedRSSWithCDR F=[] Story - Closed 4161 Apps.Store.FeedWithAccountingInfo F=[] Story - Closed 3652 Apps.Store.PerformAdministrationTasks F=[] Story - Closed 3642 Apps.Store.PublishAnOffering F=[] Story - Closed 3660 Apps.Store.RateOfferings F=[] Story - Closed 3637 Apps.Store.RegisterNewResource F=[] Story - Closed 3649 Apps.Store.RegisterRepository F=[] Story - Closed 3639 Apps.Store.RegisterStoreOnAMarketplace F=[] Story - Closed 4157 Apps.Store.RenovateSubscriptions F=[] Story - Closed 3638 Apps.Store.RetrieveOfferingInformation F=[] Story - Closed 3677 Apps.Store.SearchForOfferings F=[] Story - Closed 3656 Apps.Store.ShowOfferingsInformation F=[] Story - Closed 3654 Apps.Store.ShowPublishedOfferings F=[] Story - Closed 3653 Apps.Store.ShowUserOfferings F=[] Story - Closed 4156 Apps.Store.SubscribeService F=[] Story - Closed 3651 Apps.Store.UnregisterRepository F=[] Story - Closed 3640 Apps.Store.UnregisterStoreFromAMarketplace F=[] Story - Closed 601 Apps.USDL.LDCoreSpecification F=[] Story - Closed 606 Apps.USDL.LDIPRSpecification F=[] Story - Closed 602 Apps.USDL.LDIoTSpecification F=[] Story - Closed 607 Apps.USDL.LDLegalSpecification F=[] Story - Closed 605 Apps.USDL.LDPricingSpecification F=[] Story - Closed 603 Apps.USDL.LDSECSpecification F=[] Story - Closed 604 Apps.USDL.LDSLASpecification F=[] Story - Closed 708 Apps.USDL.Pricing.Requirements F=[] Story - Closed 4151 Apps.Store.NotifyRSSNewOffering F=[] Story - Dismissed Overall this would hopefully help you to demonstrate that actually the apps chapter is not any more on the "worst" part of the initial graph and you would be able to kindly change the sentence subsuming the performance of the apps chapter. Overall we would expect that we reach in the end 10 tracker items where the hierarchy is (still) not fixed by our partners (despite your initial number of 123). Thanks in advance for your support on this and best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Mittwoch, 20. November 2013 11:39 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] D2.1.6-M30 Requirements Backlog open for comments - delivery tomorrow 21.Nov 11:00 AM Dear Partners, Please, find D2.1.6-M30 Requirements Backlog open for comments. https://forge.fi-ware.eu/docman/view.php/27/3110/D2.1.6-M30+Requirements+Backlog.zip Please, send me your feedback today. I intend to deliver it tomorrow 21.Nov at 11:00 AM I hope you don't have many strong objections. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 18380 bytes Desc: image001.jpg URL: From jdps at tid.es Wed Nov 20 15:27:13 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 20 Nov 2013 14:27:13 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Message-ID: <77A22C1085494D48B4018F06A40DB2C73001DB3A@EX10-MB2-MAD.hi.inet> Hi again, We have received comments and another option could be: "No input from partner. As far as the WPL knows, there is no contribution of this partner on the reported period M25-M30". Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 20 de noviembre de 2013 14:50 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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Dear all, in case there is missing information from a partner because they don't answer you, please change the label "xxx" on the report by "No input from partner. As far as the WPL knows, the contribution of the partner is ....." Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 13 de noviembre de 2013 23:21 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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Importancia: Alta Dear all, First of all, thank you very much for your contribution. Please find attached the first draft version of the Periodic Report M30 where we have integrated all the received contributions so far. I kindly ask you to use this one as basis in order to provide a new version of the report of your WP. Please check it, and complete where "xxx" is still written. Don't hesitate to share it with your involved partners. Note: We'll only accept changes in a WP from its own WPL. Deadline, November 20th, 2013, EOB. Please confirm the reception of this important e-mail. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 20 16:14:48 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 20 Nov 2013 16:14:48 +0100 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration In-Reply-To: <77A22C1085494D48B4018F06A40DB2C73001DB3A@EX10-MB2-MAD.hi.inet> References: <77A22C1085494D48B4018F06A40DB2C73001DB3A@EX10-MB2-MAD.hi.inet> Message-ID: <528CD1E8.4020704@eng.it> Dear Javier, thank you for your indication in the case of missing contribution for the activities of the partner. In case of missing justification for over/underspending the reported sentence will be "no justification provided". PLS let me know whether this is fine for you. BR Davide On 20/11/2013 15:27, JAVIER DE PEDRO SANCHEZ wrote: > > Hi again, > > We have received comments and another option could be: "No input from > partner. As far as the WPL knows, there is no contribution of this > partner on the reported period M25-M30". > > Thank you. > > BR > > Javier. > > *De:*JAVIER DE PEDRO SANCHEZ > *Enviado el:* mi?rcoles, 20 de noviembre de 2013 14:50 > *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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration > > Dear all, in case there is missing information from a partner because > they don't answer you, please change the label "xxx" on the report by > "No input from partner. As far as the WPL knows, the contribution of > the partner is ....." > > Thank you. > > BR > > Javier. > > *De:*JAVIER DE PEDRO SANCHEZ > *Enviado el:* mi?rcoles, 13 de noviembre de 2013 23:21 > *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:* FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration > *Importancia:* Alta > > Dear all, > > First of all, thank you very much for your contribution. > > Please find attached the first draft version of the Periodic Report > M30 where we have integrated all the received contributions so far. > > I kindly ask you to use this one as basis in order to provide a new > version of the report of your WP. > > Please check it, and complete where "xxx" is still written. Don't > hesitate to share it with your involved partners. > > Note: We'll only accept changes in a WP from its own WPL. > > *Deadline, November 20^th , 2013, EOB.* > > Please confirm the reception of this important e-mail. > > Thank you in advance. > > BR > > Javier. > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its 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 jdps at tid.es Wed Nov 20 16:27:40 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Wed, 20 Nov 2013 15:27:40 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration In-Reply-To: <528CD1E8.4020704@eng.it> References: <77A22C1085494D48B4018F06A40DB2C73001DB3A@EX10-MB2-MAD.hi.inet> <528CD1E8.4020704@eng.it> Message-ID: <77A22C1085494D48B4018F06A40DB2C73001DC5A@EX10-MB2-MAD.hi.inet> Hi Davide, I agree with you, "No justification has been provided by the partner." is a good sentence. Thanks. BR Javier. De: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Enviado el: mi?rcoles, 20 de noviembre de 2013 16:15 Para: JAVIER DE PEDRO SANCHEZ CC: 'fiware-wpl at lists.fi-ware.eu'; fiware-wpa at lists.fi-ware.eu; subsidies at tid.es Asunto: Re: [Fiware-wpl] FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Dear Javier, thank you for your indication in the case of missing contribution for the activities of the partner. In case of missing justification for over/underspending the reported sentence will be "no justification provided". PLS let me know whether this is fine for you. BR Davide On 20/11/2013 15:27, JAVIER DE PEDRO SANCHEZ wrote: Hi again, We have received comments and another option could be: "No input from partner. As far as the WPL knows, there is no contribution of this partner on the reported period M25-M30". Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 20 de noviembre de 2013 14:50 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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Dear all, in case there is missing information from a partner because they don't answer you, please change the label "xxx" on the report by "No input from partner. As far as the WPL knows, the contribution of the partner is ....." Thank you. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: mi?rcoles, 13 de noviembre de 2013 23:21 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: FI-WARE: Periodic Report M30 (D.1.2.5) - Second iteration Importancia: Alta Dear all, First of all, thank you very much for your contribution. Please find attached the first draft version of the Periodic Report M30 where we have integrated all the received contributions so far. I kindly ask you to use this one as basis in order to provide a new version of the report of your WP. Please check it, and complete where "xxx" is still written. Don't hesitate to share it with your involved partners. Note: We'll only accept changes in a WP from its own WPL. Deadline, November 20th, 2013, EOB. Please confirm the reception of this important e-mail. Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed Nov 20 18:06:14 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 20 Nov 2013 17:06:14 +0000 Subject: [Fiware-wpl] backlog management of "your" chapter for recurring tasks on "Tracker"-items Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A80604@DEWDFEMB11B.global.corp.sap> Dear colleagues, as SAP I can offer you support on your particular backlog-tasks and efforts which might be automatable. Eg. for the apps chapter we migrated a lot of issues (860 issues going down to ~420 issues) with very limited manual effort. I tried to summarize in the table below what might be effected by this automatism, I won't check your reviews proactively, if you think it might be relevant for your tracker/backlog improvements please check the list below. Please let me know what you think could be automated and I can consider implementing this - although I can't promise resolutions in all cases! Your task would be to focus on the "larger" portions that need to be fixed (as it requires still some manual work on my side to customize the scripts) and saves more time. If you would have in C1 e.g. only 2 items, then I would kindly refrain from investing time into it J Best, /Thorsten Things that MIGHT be automated: C1 - sprint and release fields --> consistency of features != open with release and sprint --> consistency of epics with release and sprint >>>>> Scheduled Stories need to have release and sprint >>>>> Scheduled Features need to have release, sprint is not needed >>>>> Scheduled Epics don't need to have either release or sprint ? I can delete arbitrary fields, if Manuel thinks they are not needed any more and implies this as error C2 - backlog reference (summary) consistency with its fields --> items' reference with inconsistent entry type >>>>> Items whose entry type field is not consistent with the entry slot of the reference ? I can change e.g. STORY to Story or similar transitions on field level C5 - Items' descriptions --> backlog items (Story, WorkItem, Bug) with no description on the tracker --> backlog items (Epic, Feature) whose description is provided on the wiki >>>>> Descriptions of Epic and Feature are provided in the wiki, so duplicated here. >>>>> These descriptions can be removed ? I can delete arbitrary fields automatically Things that are hard or NOT possible to automate C3 - backlog hierarchy C4 - Tracker link to the Wiki --> links not needed: Story, WorkItem and Bug on tracker --> links non existing or inconsistent with their reference in tracker --> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing) --> consistent urls but a connection try failed ... and all other things that are NOT listed before J -- 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 mev at tid.es Thu Nov 21 12:30:02 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 21 Nov 2013 11:30:02 +0000 Subject: [Fiware-wpl] D2.1.6-M30 - Just Delivered!! Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8912C7F1@EX10-MB1-MAD.hi.inet> Dear Partners, Let me inform you that D2.1.6-M30 has just been delivered. https://forge.fi-ware.eu/docman/view.php/7/3113/D2.1.6-M30+Requirements+Backlog.zip Thanks all 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 Thu Nov 21 13:18:28 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 21 Nov 2013 12:18:28 +0000 Subject: [Fiware-wpl] Proposal to change hirarchy metric on tracker backlog calculations Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8157D@DEWDFEMB11B.global.corp.sap> Dear colleagues, So far I agreed with Manuel on some improvements of the tracker calculations, which actually didn't make it across to his final numbers. These final numbers are now the ones that are finally reported to the EC, I think it would help that the WPL/WPA board is taking some decisions in order to significantly improve the situation and get to a much better "backlog" performance with as little as possible manual work for us. Please take the proposal below as initial try to come up with new metrics and improve the existing performance and please support this proposal itself. If you think this needs to be further discussed in the Monday morning meeting, I'm happy to comment on this as well. Other than that I would think that it would be sufficient for Manuel that all chapters would agree to a certain case and he would go forward with this. You probably followed the discussion of Manuel and the some colleagues out of the apps chapter on the metric which is related to "hierarchy" of backlog items. As the apps chapter colleagues already communicated in a number of 1:1-telcos and consistently, we think the focus of having a consistent hierarchy is acceptable for ongoing and upcoming features and might be entitled for this kind of tracking. But as the rules on how the hierarchy was finally computed actually is quite "new" in relation to the overall FI-WARE project timeframe, I would propose to keep the focus on relevant (upcoming) things and not lose the focus in tedious renaming of items, which proof little value to the outside. This consensus to act in this way was initially reached on Telco level (at least this is what my opinion is and Manuel might disagree) - I did not insist to reflect this in the numbers, as this poses more effort on Manuel than on us to just "ignore" these numbers. Now and as the numbers are getting reported to the EC as "errors", we need to bring this up again and would seek for your opinion and support on how to go forward with this: Proposal: ignore all "old" tracker-items (closed and dismissed) in the backlog-hierarchy computation in order to focus our work the relevant state-of-play and upcoming tasks. This applies to T-C3: Concept = stories with no feature father >>>>> Stories need a Feature father to exist Implications for chapters => leading to X% of resolution - Security: 2 out of 2 => 100% resolution - Data: 37 out of 55 => 67% resolution - I2ND: 1 out of 2 => 50% resolution - Cloud: 16 out of 38 => 42% resolution - Apps: 111 out of 123 => 90% resolution It is evident that apps has the most "effort" here, but you can clearly see that this metric with the new "rule" would greatly provide a "better" rating across the board of more than 50% (despite cloud with 42%) for each of the chapters. Can you please vote if you would support this proposal or give an indication on how you want to discuss this further. Please note: I have as well other proposals on how to improve the current metrics of backlog calculation which are not related to this and will be further distributed subsequently (additionally I'm reemphasizing that I can change a lot in your backlogs automatically now, hopefully closing this sooner and with less manual work for all of us). Thank you and best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu Nov 21 14:34:56 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 21 Nov 2013 13:34:56 +0000 Subject: [Fiware-wpl] Backlog calculation proposal for "hidden" backlog items in order to not expose unsupported features/epics Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8171A@DEWDFEMB11B.global.corp.sap> Dear colleagues, for 54 items in at least our metric we have things where we have backlog items, which are NOT reflected in the public wiki. Actually in 12 cases the script of Manuel just is not able to parse the name correctly, I would hope this is fixed rather sooner than later. In 10 cases this relates to components of Ericson who apparently left the project. Exposing these 10 Epics in the current setup of the Materializing would in my view "harm" more than doing good - as a user who is browsing the Materializing page would find Features, which later are found as "not supported any more". The easiest solution I see is the following proposal: Proposal 1: exclude components which are no longer maintain from forcing external representation of their features/epics in public facing channels (e.g. the fi-ware wiki) and within the internal metrics. This would as well apply for components (defined by the WPL) and no longer being maintained for e.g. hierarchy-checks, backlog-item-namings, consistency of release and sprints for entries etc pp. Additionally we see down below some ApplicationMashup "Features" which I would as well not support to be exposed on the wiki as features of a software. Therefore the second proposal would be: Proposal 2: Allow a set of items in the backlog which is governed by the WPL and is NOT checked against external representations (in particularly not counted as errors towards the EC). I would be happy if you support proposal 1 and 2 Best, /Thorsten >>>>> Active Epics and Features need to have its external representation in the public wiki, referenced in materializing >>>>> This list contains items with external representation but not found in the chapter materializing page Directory : http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Applications/Services_Ecosystem_and_Delivery_Framework_in_FI-WARE 3446 Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInContainerApp Feature - Scheduled FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInContainerApp 3447 Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInWebBasedSystem Feature - Scheduled FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInWebBasedSystem 3443 Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForOpenSocial Feature - Scheduled FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForOpenSocial 3445 Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForW3CWidgets Feature - Scheduled FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForW3CWidgets 5264 Apps.ApplicationMashup.DevSupport Epic - Open FIWARE.Epic.Apps.ApplicationMashup.DevSupport 4707 Apps.ApplicationMashup.DevSupport.GUITutorials Feature - Closed FIWARE.Feature.Apps.ApplicationMashup.DevSupport.GUITutorials 4706 Apps.ApplicationMashup.DevSupport.SupportMACDescriptionConversion Feature - Closed FIWARE.Feature.Apps.ApplicationMashup.DevSupport.SupportMACDescriptionConversion 2296 Apps.ApplicationMashup.DevSupport.WidgetOperatorDevelopmentEnvironment Feature - Under execution FIWARE.Feature.Apps.ApplicationMashup.DevSupport.WidgetOperatorDevelopmentEnvironment 3197 Apps.ApplicationMashup.IdManagementSupport.IntegrationWithIDManagementSystem Feature - Closed FIWARE.Feature.Apps.ApplicationMashup.IdManagementSupport.IntegrationWithIDManagementSystem 5183 Apps.BEMES.BusinessCalculator.CalculatorHub Feature - Scheduled FIWARE.Feature.Apps.BEMES.BusinessCalculator.CalculatorHub 879 Apps.CompositionEditor.C3BasicSearchUSDLService Feature - Closed FIWARE.Feature.Apps.CompositionEditor.C3BasicSearchUSDLService 2082 Apps.CompositionEditor.CreateComposition Feature - Closed FIWARE.Feature.Apps.CompositionEditor.CreateComposition 2081 Apps.CompositionEditor.ExportImportBPMN20Models Feature - Closed FIWARE.Feature.Apps.CompositionEditor.ExportImportBPMN20Models 3486 Apps.CompositionEditor.GatewayFlowSemanticAnnotation Epic - Closed FIWARE.Epic.Apps.CompositionEditor.GatewayFlowSemanticAnnotation 2272 Apps.CompositionEditor.GeoLocationSearch Feature - Closed FIWARE.Feature.Apps.CompositionEditor.GeoLocationSearch 937 Apps.CompositionEditor.MFBasicSearchUSDLService Feature - Closed FIWARE.Feature.Apps.CompositionEditor.MFBasicSearchUSDLService 2133 Apps.CompositionEditor.PublishMashupDescription Feature - Closed FIWARE.Feature.Apps.CompositionEditor.PublishMashupDescription 2132 Apps.CompositionEditor.SOAP2REST_SMS Feature - Closed FIWARE.Feature.Apps.CompositionEditor.SOAP2REST_SMS 2080 Apps.CompositionEditor.SemanticFeatured Feature - Closed FIWARE.Feature.Apps.CompositionEditor.SemanticFeatured 1400 Apps.CompositionEditor.TaskSemanticAnnotation Feature - Closed FIWARE.Feature.Apps.CompositionEditor.TaskSemanticAnnotation 880 Apps.ExecutionEngine.C3MakeExecutionEngineCloudReady Feature - Closed FIWARE.Feature.Apps.ExecutionEngine.C3MakeExecutionEngineCloudReady 3534 Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithMarketplace Feature - Scheduled FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithMarketplace 3533 Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithRepository Feature - Scheduled FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithRepository 3532 Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithUSDLEditor Feature - Scheduled FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithUSDLEditor 3535 Apps.LightSemanticComposition.IntegrationWithGEs.SupportForIdManagement Feature - Scheduled FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.SupportForIdManagement 621 Apps.Marketplace.PricingDescisionSupport Epic - Closed FIWARE.Epic.Apps.Marketplace.PricingDescisionSupport 2313 Apps.Mediator.BuildServicePayload Feature - Open FIWARE.Feature.Apps.Mediator.BuildServicePayload 2314 Apps.Mediator.DynamicMediation Feature - Open FIWARE.Feature.Apps.Mediator.DynamicMediation 2312 Apps.Mediator.SemanticInvocation Feature - Open FIWARE.Feature.Apps.Mediator.SemanticInvocation 3904 Apps.Registry.GetProviderAndStoreInfo.DeleteEntry Feature - Closed FIWARE.Feature.Apps.Registry.GetProviderAndStoreInfo.DeleteEntry 3348 Apps.Registry.GetProviderAndStoreInfo.GetProviderAndStoreInfo Feature - Closed FIWARE.Feature.Apps.Registry.GetProviderAndStoreInfo.GetProviderAndStoreInfo 3902 Apps.Registry.GetProviderAndStoreInfo.ModifyEntry Feature - Closed FIWARE.Feature.Apps.Registry.GetProviderAndStoreInfo.ModifyEntry 4727 Apps.Registry.IDManagementSupport Epic - Scheduled FIWARE.Epic.Apps.Registry.IDManagementSupport 3349 Apps.Registry.RegisterProviderAndStore.RegisterProviderAndStore Feature - Closed FIWARE.Feature.Apps.Registry.RegisterProviderAndStore.RegisterProviderAndStore 5086 Apps.Store.ComplexPricing Epic - Scheduled FIWARE.Epic.Apps.Store.ComplexPricing 4574 Apps.Store.ComplexPricing.SupportForDeveloperPricePlans Feature - Scheduled FIWARE.Feature.Apps.Store.ComplexPricing.SupportForDeveloperPricePlans 5087 Apps.Store.ComplexPricing.SupportForPriceFunctions Feature - Scheduled FIWARE.Feature.Apps.Store.ComplexPricing.SupportForPriceFunctions 5088 Apps.Store.ComplexPricing.SupportForUpdatesPricePlans Feature - Scheduled FIWARE.Feature.Apps.Store.ComplexPricing.SupportForUpdatesPricePlans 4697 Apps.Store.Contracting.SupportForMultipleOrganizations Feature - Closed FIWARE.Feature.Apps.Store.Contracting.SupportForMultipleOrganizations 4559 Apps.Store.IdManagementSupport.IntegrationWithIdM Feature - Closed FIWARE.Feature.Apps.Store.IdManagementSupport.IntegrationWithIdM 3313 FIWARE.EPIC.Apps.Store.UserCentric&SocialFeatures Epic - Scheduled FIWARE.EPIC.Apps.Store.UserCentric&SocialFeatures 4573 FIWARE.FEATURE.Apps.Store.UserCentric&SocialFeatures.SupportForUsersOpinion Feature - Closed FIWARE.FEATURE.Apps.Store.UserCentric&SocialFeatures.SupportForUsersOpinion 5361 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BMBCIntegrationPOC Feature - Scheduled FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BMBCIntegrationPOC 5302 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendMediator Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendMediator 5303 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendRESTservice Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendRESTservice 5300 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.CanvasViewEnhancements Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.CanvasViewEnhancements 5296 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ModelCreation Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ModelCreation 5362 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ParameterConfiguration Feature - Scheduled FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ParameterConfiguration 5360 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.RefactorDomainTier Feature - Under execution FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.RefactorDomainTier 5363 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.RemodelGraphVisualization Feature - Under execution FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.RemodelGraphVisualization 5298 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.StorageAndRetrieval Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.StorageAndRetrieval 5301 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UndoAndRedo Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UndoAndRedo 5299 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UnitTestFrameworkChange Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UnitTestFrameworkChange 5297 FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.XMLParsing Feature - Closed FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.XMLParsing -- 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 jdps at tid.es Thu Nov 21 15:26:48 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Thu, 21 Nov 2013 14:26:48 +0000 Subject: [Fiware-wpl] FI-WARE: Third submission on NEF of the FORM-C-2 Message-ID: <77A22C1085494D48B4018F06A40DB2C730030686@EX10-MB2-MAD.hi.inet> Dear all, This e-mail is to inform you that we?ve just submitted the FORM-C-2 again. Thank you very much for the received contributions to the Commission?s remarks. The updated Periodic Report M24 is here: https://forge.fi-ware.eu/docman/view.php/27/3114/D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v12+%28clean%29.pdf BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Nov 25 09:46:46 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 25 Nov 2013 09:46:46 +0100 Subject: [Fiware-wpl] VERY IMPORTANT: Criteria for deployment of GEis on FI-Lab Message-ID: <52930E76.9050600@tid.es> Dear partners and GEi owners in particular, This mail is to elaborate on the criteria that is being followed to decide when a given GEi can be deployed on FI-Lab and made available to third parties. FI-WARE GEis can be available to UC projects on the FI-PPP Testbed (http://testbed.fi-ware.eu) but not yet on FI-Lab due to the fact they haven't yet fulfilled the listed criteria: * Documentation linked to the GEi has to pass the internal review (Miguel carrillo in charge). Note that the fact we have submitted this documents as deliverable to the EC, or they have even been accepted by reviewers, doesn't mean that you have passed this internal review. Our review is considering whether the documentation reaches a minimum level as to be shared with third parties. We are referring here to the following documentation: * Installation and Administration guides * User and Programmers guides * Completeness of information in the FI-WARE Catalogue. Here, special attention will be made to info about licenses and External Availability. Overall, we will also check whether description of the GEi is complete and well-written. We will also check that all necessary links to documentation, architecture and API specifications and, when apropriate, source code are published. * Availability of tools for automated creation of instances. It should be feasible to deploy the GEi using virtual pre-configured images, recipes and blueprints. All this information should be documented in the "Creating instances" tab linked to the GEi in the FI-WARE Catalogue. Besides those that don't need to be deployed on FI-Lab because of their nature (e.g., GEis linked to IoT gateways, the Cloud proxy GEi, the CDI GEi or the advanced middleware GEi, to mention some examples), the following GEis are excluded and don't need to follow this rule (the rule has to be fulfilled for all the rest): * WireCloud GEi in the Apps chapter * Business Framework related GEis in the Apps chapter * GEis in the Cloud Hosting chapter * GEis in the Security chapter * GEis in the I2ND chapter * Training material. There should be enough and complete training material for the GEi uploaded in the "Help&Info" webpage of FI-Lab or the FI-WARE eLearning platform. The need to fulfill these requirements are no new, but we wanted to stress that we have decided to prevent that GEis not fulfilling the above criteria are made available to third parties on FI-Lab. Any GEi that fails to cover this criteria will not deployed on FI-Lab. Those GEis already deployed on FI-Lab should work hard to ensure that the above criteria is fulfilled before end of the year. Whenever you believe that you have fulfilled all these criteria, please inform Stefano de Panfilis (stefano.depanfilis at eng.it) and Miguel Carrillo (mcp at tid.es) so that they can confirm. Please keep me on copy. Once fulfillment of the requirements is confirmed, Stefano and Miguel will coordinate the necessary steps to make your GEi available on FI-Lab. Don't hesitate to formulate any question you may have. 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 FI-PPP Architecture Board chairman 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 Nov 25 10:13:07 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 25 Nov 2013 10:13:07 +0100 Subject: [Fiware-wpl] Info about Smart City World Expo and IMPORTANT update about branding material In-Reply-To: <5291EE01.8040707@tid.es> References: <5291EE01.8040707@tid.es> Message-ID: <529314A3.8030903@tid.es> Dear partners, As many of you should know, FI-WARE and FI-LAB were present in the Smart City World Expo last week. This event is the largets event dealing with Smart Cities worldwide. Please find here a summary of most relevant info about our present in the event. * We manage to arrange a nice stand of 30 sqm. Costs and attendance were shared between the XiFi project and us. After several discussions, we agreed with the XiFi project that we should arrive with messages centered on products/brands rather than projects. Some pictures can be downloaded from the following link in dropbox: * https://www.dropbox.com/sh/3ndve6fy46tqzu5/eO9CDL2FfO * The exercise we had to perform previous to the event regarding messages to deliver was extremely useful and we agreed that, from now on, the two projects will focus their dissemination around three products/results, with their corresponding branding (all aligned) and messages/material will be coordinated through a Task Force involving key partners from the two projects. The three brands that we now have are: * FI-WARE refers to the technology that application developers can use to build Future Internet applications (i.e., target audience of FI-WARE are application developers) * FI-Ops refers to the tools that FI-WARE Instance providers can use to operate FI-WARE Instances (i.e., target audience of FI-Ops are Platform Providers) * FI-Lab is the cornerstone element of the open innovation ecosystem that we aim to build. It is the meeting point that allow application developers (with special attention to entrepreneurs) to meet application sponsors (those who wanna invest on applications or acquire them to run their business or offer those applications to their customers) and viceversa. It is a FI-WARE Instance deployed over a number of datacenter nodes distributed and federated across Europe. As such, is an example where FI-WARE and FI-Ops are put at work: * FI-WARE technologies are made available to application developers in FI-LAB for experimentation/testing/trialing * FI-Ops tools are being used by the organizations operating FI-LAB nodes in order to run their operations effectively * Both projects will have the right to use these brands as far as they respect the above descriptions. We modified the flyer we had produced for the event in Santander so that it nows incorporates description of the three brands. See flyer design attached. The logo for FI-Ops will use a different color because different target audience (Platform providers) but will overall align with the other two (FI-WARE and FI-Lab). A link to info about FI-Ops has been added to the home page of FI-Lab at http://lab.fi-ware.eu * It was indeed agreed that main goals of the XiFi project can be stated as: * Expanding FI-LAB across a network of datacenter nodes distributed across Europe. * Come up with a complete set of tools that conform the FI-Ops suite that will ease operations in each of the datacenter nodes supporting FI-Lab as well as operation of any FI-WARE instance * help existing experimental facilities to extend FI-LAB * Aligned with the above, we agreed to deliver the following messages to smart cities during the Smart City World Expo: * FI-WARE and FI-OPS together bring the core enablers and operation support tools of a target Smart City platform. * FI-WARE technologies will ease development of: * innovative solutions helping cities to manage their services more efficiently (e.g., garbage collection, furniture maintenance, etc) * innovative application/services that can be delivered to citizens (e.g., application that ease car driving or usage of public transport in the city) * portals/platform for publication of Open APIs and Open Data that developers can use to develop applications * The FI-OPS suite of tools will ease operation of a Smart City platform based on FI-WARE technologies * Cities can connect to FI-LAB putting their open data at work within that space: * Entrepreneurs can use the open data available in FI-LAB to build innovation solutions and application/services they can showcase to cities * Cities can make a deal with entrepreneurs showcasing the most interesting solutions or application/services * By connecting to FI-LAB, cities can benefit from the visibility and promotion (marketing campaigns, success stories) planned for that space. Besides, solutions trialed on FI-Lab can be easily ported to FI-WARE instances in production (the Smart City platforms). * There is no open innovation ecosystem a single city can build on their own: FI-LAB offers cities the opportunity to join forces and gain the necessary scale and level of awareness among the wide community of developers * The messages we delivered are summarized in the presentation I made which you can download from the following dropbox link. I officially announced during it that Trento and Torino has officially joined FI-Lab: * https://www.dropbox.com/s/czy66znhd884ajr/FI-PPP%20and%20FI-WARE%20for%20Smart%20Cities%20Short%20Overview%2013-11-20.pptx * You can download a summary of the specific marketing material that Ogilvy produced for the stand. I would highlight the two infographics produced as well as the flyer: * logos for the three brands: https://www.dropbox.com/s/6yb1aek72gsm0b6/FI-family_logos.pdf * Infographic about FI-LAB for Smart Cities: http://www.slideshare.net/FI-WARE/hq-fiware-and-filab-in-a-nutshell-infographic * Infographic about FI-WARE and FI-LAB: http://www.slideshare.net/FI-WARE/filab-for-smart * XiFi produced some additional material they adapted in "fast-track" mode prior to the conference. I will ask for a copy of them that I can forward to you: * I had the opportunity to chat with Colette Maloney and clarify her that FI-WARE/FI-LAB should not be taken as regular "EU FP7 research" projects but indeed something much closer to the market. I put the example that cities are already considering its adoption in some countries (currently Spain and Italy but looking for further extensions). We asked her to have a more formal meeting as soon as possible. * We made contacts with several cities that looked interested in what we were doing and for which further opportunities about connection to FI-Lab will be explored. Overall, I believe it was a rather positive experience and another sign that this is the kind of events we have to attend rather that the "business as usual" kind of events we are used to in EU funded projects. Sure we may have a rather significant presence next year since we will be able to provide some more concrete results. The information above has been shared with the EC. I would like to take this opportunity to thank Ogilvy for their support in producing all the material for the event. They made this in record time, just few days before the event actually took place. Don't hesitate to ask any questions you may have. 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 FI-PPP Architecture Board chairman 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-Lab FI-WARE FI-Ops flyer.pdf Type: application/pdf Size: 1954280 bytes Desc: not available URL: From mev at tid.es Mon Nov 25 10:45:29 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 25 Nov 2013 09:45:29 +0000 Subject: [Fiware-wpl] Backlog Content -> dashboards, reviews, hotTopics -> updates Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89135388@EX10-MB1-MAD.hi.inet> Dear Partners, Find below links to backlog-related reports: Hot Topics: Catalogue:https://forge.fi-ware.eu/docman/view.php/27/3138/FIWARE.backlog.hotTopic-Catalogue.20131125.xlsx Lutz Report:https://forge.fi-ware.eu/docman/view.php/27/3142/FIWARE.backlog.hotTopic-LutzReport.20131125.xlsx Training Material: https://forge.fi-ware.eu/docman/view.php/27/3143/FIWARE.backlog.hotTopic-TrainingMaterial.20131125.xlsx Dashboards: Apps: https://forge.fi-ware.eu/docman/view.php/27/3120/FIWARE.backlog.apps.dashboard.20131125.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3121/FIWARE.backlog.cloud.dashboard.20131125.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3124/FIWARE.backlog.iot.dashboard.20131125.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3122/FIWARE.backlog.data.dashboard.20131125.xlsx I2ND: https://forge.fi-ware.eu/docman/view.php/27/3123/FIWARE.backlog.i2nd.dashboard.20131125.xlsx Security: https://forge.fi-ware.eu/docman/view.php/27/3125/FIWARE.backlog.security.dashboard.20131125.xlsx Review: Apps: https://forge.fi-ware.eu/docman/view.php/27/3126/FIWARE.backlog.apps.review.20131125.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3127/FIWARE.backlog.cloud.review.20131125.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3130/FIWARE.backlog.iot.review.20131125.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3128/FIWARE.backlog.data.review.20131125.xlsx I2ND: https://forge.fi-ware.eu/docman/view.php/27/3129/FIWARE.backlog.i2nd.review.20131125.xlsx Security: https://forge.fi-ware.eu/docman/view.php/27/3131/FIWARE.backlog.security.review.20131125.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 25 10:48:09 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 25 Nov 2013 10:48:09 +0100 Subject: [Fiware-wpl] Link for today Message-ID: <52931CD9.4080900@tid.es> Dear all, As usual, here it is: * https://docs.google.com/document/d/1Uv4xv73K5OPJ6-wAWvnIRrIhTYb7VIJUGKMmYcYjQME/edit?pli=1# Speak to you in a sec Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.heller at sap.com Mon Nov 25 10:50:06 2013 From: markus.heller at sap.com (Heller, Markus) Date: Mon, 25 Nov 2013 09:50:06 +0000 Subject: [Fiware-wpl] Info about Smart City World Expo and IMPORTANT update about branding material In-Reply-To: <529314A3.8030903@tid.es> References: <5291EE01.8040707@tid.es> <529314A3.8030903@tid.es> Message-ID: <393554EDCF801348BC53C7813C6CB73B1A74E8CA@DEWDFEMB14A.global.corp.sap> Dear Juanjo, Thank you for the flyer, please note that there seems to be an error in the title of the Apps chapter (see screenshot) It should be "Application and Services Ecosystem and Delivery Framework", the part "architecture of" is not correct and misleading since Apps foremost delivers real software as all others (besides some really nice architecture)... Can you please ask Ogilvy / or the flyer producers to correct this in the online / PDF locations and correct it in future printed/paper flyer versions? Best wishes Markus [cid:image001.png at 01CEE9CB.594F3880] From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 25. November 2013 10:13 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Info about Smart City World Expo and IMPORTANT update about branding material Dear partners, As many of you should know, FI-WARE and FI-LAB were present in the Smart City World Expo last week. This event is the largets event dealing with Smart Cities worldwide. Please find here a summary of most relevant info about our present in the event. * We manage to arrange a nice stand of 30 sqm. Costs and attendance were shared between the XiFi project and us. After several discussions, we agreed with the XiFi project that we should arrive with messages centered on products/brands rather than projects. Some pictures can be downloaded from the following link in dropbox: * https://www.dropbox.com/sh/3ndve6fy46tqzu5/eO9CDL2FfO * The exercise we had to perform previous to the event regarding messages to deliver was extremely useful and we agreed that, from now on, the two projects will focus their dissemination around three products/results, with their corresponding branding (all aligned) and messages/material will be coordinated through a Task Force involving key partners from the two projects. The three brands that we now have are: * FI-WARE refers to the technology that application developers can use to build Future Internet applications (i.e., target audience of FI-WARE are application developers) * FI-Ops refers to the tools that FI-WARE Instance providers can use to operate FI-WARE Instances (i.e., target audience of FI-Ops are Platform Providers) * FI-Lab is the cornerstone element of the open innovation ecosystem that we aim to build. It is the meeting point that allow application developers (with special attention to entrepreneurs) to meet application sponsors (those who wanna invest on applications or acquire them to run their business or offer those applications to their customers) and viceversa. It is a FI-WARE Instance deployed over a number of datacenter nodes distributed and federated across Europe. As such, is an example where FI-WARE and FI-Ops are put at work: * FI-WARE technologies are made available to application developers in FI-LAB for experimentation/testing/trialing * FI-Ops tools are being used by the organizations operating FI-LAB nodes in order to run their operations effectively * Both projects will have the right to use these brands as far as they respect the above descriptions. We modified the flyer we had produced for the event in Santander so that it nows incorporates description of the three brands. See flyer design attached. The logo for FI-Ops will use a different color because different target audience (Platform providers) but will overall align with the other two (FI-WARE and FI-Lab). A link to info about FI-Ops has been added to the home page of FI-Lab at http://lab.fi-ware.eu * It was indeed agreed that main goals of the XiFi project can be stated as: * Expanding FI-LAB across a network of datacenter nodes distributed across Europe. * Come up with a complete set of tools that conform the FI-Ops suite that will ease operations in each of the datacenter nodes supporting FI-Lab as well as operation of any FI-WARE instance * help existing experimental facilities to extend FI-LAB * Aligned with the above, we agreed to deliver the following messages to smart cities during the Smart City World Expo: * FI-WARE and FI-OPS together bring the core enablers and operation support tools of a target Smart City platform. * FI-WARE technologies will ease development of: * innovative solutions helping cities to manage their services more efficiently (e.g., garbage collection, furniture maintenance, etc) * innovative application/services that can be delivered to citizens (e.g., application that ease car driving or usage of public transport in the city) * portals/platform for publication of Open APIs and Open Data that developers can use to develop applications * The FI-OPS suite of tools will ease operation of a Smart City platform based on FI-WARE technologies * Cities can connect to FI-LAB putting their open data at work within that space: * Entrepreneurs can use the open data available in FI-LAB to build innovation solutions and application/services they can showcase to cities * Cities can make a deal with entrepreneurs showcasing the most interesting solutions or application/services * By connecting to FI-LAB, cities can benefit from the visibility and promotion (marketing campaigns, success stories) planned for that space. Besides, solutions trialed on FI-Lab can be easily ported to FI-WARE instances in production (the Smart City platforms). * There is no open innovation ecosystem a single city can build on their own: FI-LAB offers cities the opportunity to join forces and gain the necessary scale and level of awareness among the wide community of developers * The messages we delivered are summarized in the presentation I made which you can download from the following dropbox link. I officially announced during it that Trento and Torino has officially joined FI-Lab: * https://www.dropbox.com/s/czy66znhd884ajr/FI-PPP%20and%20FI-WARE%20for%20Smart%20Cities%20Short%20Overview%2013-11-20.pptx * You can download a summary of the specific marketing material that Ogilvy produced for the stand. I would highlight the two infographics produced as well as the flyer: * logos for the three brands: https://www.dropbox.com/s/6yb1aek72gsm0b6/FI-family_logos.pdf * Infographic about FI-LAB for Smart Cities: http://www.slideshare.net/FI-WARE/hq-fiware-and-filab-in-a-nutshell-infographic * Infographic about FI-WARE and FI-LAB: http://www.slideshare.net/FI-WARE/filab-for-smart * XiFi produced some additional material they adapted in "fast-track" mode prior to the conference. I will ask for a copy of them that I can forward to you: * I had the opportunity to chat with Colette Maloney and clarify her that FI-WARE/FI-LAB should not be taken as regular "EU FP7 research" projects but indeed something much closer to the market. I put the example that cities are already considering its adoption in some countries (currently Spain and Italy but looking for further extensions). We asked her to have a more formal meeting as soon as possible. * We made contacts with several cities that looked interested in what we were doing and for which further opportunities about connection to FI-Lab will be explored. Overall, I believe it was a rather positive experience and another sign that this is the kind of events we have to attend rather that the "business as usual" kind of events we are used to in EU funded projects. Sure we may have a rather significant presence next year since we will be able to provide some more concrete results. The information above has been shared with the EC. I would like to take this opportunity to thank Ogilvy for their support in producing all the material for the event. They made this in record time, just few days before the event actually took place. Don't hesitate to ask any questions you may have. 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 FI-PPP Architecture Board chairman 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: image001.png Type: image/png Size: 92467 bytes Desc: image001.png URL: From mev at tid.es Mon Nov 25 12:34:47 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 25 Nov 2013 11:34:47 +0000 Subject: [Fiware-wpl] Agile Dynamic: Sprint Closing -> S3.2.2 to be closed this week. Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89135408@EX10-MB1-MAD.hi.inet> Dear Partners, Please, let me make you aware of being in a sprint closing week. Please, remember closing the backlog items (epics, features, stories, bugs and work items) you finished during the month. Please, remember NOT to move any backlog item's timeframes (sprint or release). We'll do it next week during the sprint planning week. The closing snapshot will be taken on Friday 29 afternoon, unless anybody request doing it on Saturday 30th Nov. Please, find below the dashboards to help the closing procedure. Dashboards: Apps: https://forge.fi-ware.eu/docman/view.php/27/3120/FIWARE.backlog.apps.dashboard.20131125.xlsx Cloud: https://forge.fi-ware.eu/docman/view.php/27/3121/FIWARE.backlog.cloud.dashboard.20131125.xlsx IoT: https://forge.fi-ware.eu/docman/view.php/27/3124/FIWARE.backlog.iot.dashboard.20131125.xlsx Data: https://forge.fi-ware.eu/docman/view.php/27/3122/FIWARE.backlog.data.dashboard.20131125.xlsx I2ND: https://forge.fi-ware.eu/docman/view.php/27/3123/FIWARE.backlog.i2nd.dashboard.20131125.xlsx Security: https://forge.fi-ware.eu/docman/view.php/27/3125/FIWARE.backlog.security.dashboard.20131125.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Nov 25 14:45:48 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 25 Nov 2013 14:45:48 +0100 Subject: [Fiware-wpl] Interest of UCs on our GEs Message-ID: <5293548C.1070707@tid.es> As mentioned in the call. Will add the link to the minutes. https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From thorsten.sandfuchs at sap.com Mon Nov 25 17:41:41 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 25 Nov 2013 16:41:41 +0000 Subject: [Fiware-wpl] extracting the catalog to a printed version - PoC Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A861B9@DEWDFEMB11B.global.corp.sap> Dear colleagues, This is for the discussion on how to make a "printable" version of the catalogue to be submitted either prior to the review or during the review: As first proof-point and just to emphasize that we might manage to compile this kind of information "within this week", I precompiled the "Terms and conditions" and the "overview" tab out of the current cataloge-system automatically. See attachment... There are obvious "problems" but as a PoC this works quite well and reuses the wiki as intermediary (I took for testing the apps wiki, but can have this everywhere...) - Images are not printed and not copied (e.g. Cloud Edge) - Layout can be improved - More fields might be relevant for extraction - Chapter level headings are missing (currently I ordered the list in relation to the chapters) Any comments appreciated. Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D2013112531531_WPX_generated.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 166573 bytes Desc: D2013112531531_WPX_generated.docx URL: From thorsten.sandfuchs at sap.com Tue Nov 26 10:30:02 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 26 Nov 2013 09:30:02 +0000 Subject: [Fiware-wpl] extracting the catalog to a printed version - PoC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A861B9@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A861B9@DEWDFEMB11B.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86703@DEWDFEMB11B.global.corp.sap> e.g. one might imagine that we layout it with a bit of the new design flavor as shown below. With 2-colum layout where all GE have a page-break before their paragraph.... for some this would be ready for 1-page documents if the font sizes are decreased a bit... I'm not a word-designer, but just to give you some food for thought... Anybody some ideas on the open points or what to change? - Some more of the fields to be exposed here? Contact? Something else? - Should images be supported? I think it's CloudEdge, QueryBroker, IoT-gateway which are using this. - Layout can be improved further improved (whoever is a word guru...) - Chapter level headings are missing (currently I ordered the list in relation to the chapters) - (Automatic) Parsing of the "Availability" and then adding e.g. some icons to visualize better the availability modus: "open source", "FI-PPP", ... - Different table comuns/names/content? - ... Best, /Thorsten [cid:image002.jpg at 01CEEA92.76144DD0] From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Montag, 25. November 2013 17:42 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; Juanjo Hierro Subject: [Fiware-wpl] extracting the catalog to a printed version - PoC Dear colleagues, This is for the discussion on how to make a "printable" version of the catalogue to be submitted either prior to the review or during the review: As first proof-point and just to emphasize that we might manage to compile this kind of information "within this week", I precompiled the "Terms and conditions" and the "overview" tab out of the current cataloge-system automatically. See attachment... There are obvious "problems" but as a PoC this works quite well and reuses the wiki as intermediary (I took for testing the apps wiki, but can have this everywhere...) - Images are not printed and not copied (e.g. Cloud Edge) - Layout can be improved - More fields might be relevant for extraction - Chapter level headings are missing (currently I ordered the list in relation to the chapters) Any comments appreciated. Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 63413 bytes Desc: image002.jpg URL: From thorsten.sandfuchs at sap.com Tue Nov 26 12:32:09 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 26 Nov 2013 11:32:09 +0000 Subject: [Fiware-wpl] [Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A80604@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A80604@DEWDFEMB11B.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86969@DEWDFEMB11B.global.corp.sap> I anyway did a small review of the current set of provided "issues" by manuel (despite that I didn't plan this in the mail before). Status of analysis: 2013-11-25 Here are the things that are most likely to be automated in "your" chapter. Apps TC1 - sprint and release fields 4 --> consistency of story, workitem and bug != open with release and sprint 0 --> consistency of features != open with release and sprint 35 --> consistency of epics with release and sprint 39 Total Data 9 --> consistency of story, workitem and bug != open with release and sprint 45 --> consistency of features != open with release and sprint 24 --> consistency of epics with release and sprint 78 Total C4 - Tracker link to the Wiki 73 --> links not needed: Story, WorkItem and Bug on tracker 47 --> links non existing or inconsistent with their reference in tracker 40 --> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing) 0 --> consistent urls but a connection try failed 160 Total I2ND C5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 112 --> backlog items (Epic, Feature) whose description is provided on the wiki 112 Total Security C5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 66 --> backlog items (Epic, Feature) whose description is provided on the wiki 66 Total IoT TC5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 162 --> backlog items (Epic, Feature) whose description is provided on the wiki 162 Total Der is an additional amount of ~150 "issues" where actually the script of Manuel has a parser error - as the script is not supporting the "&" signs in tracker/wiki-items, although all the rest of the tool do support this, the wiki does not hold any information that would force the GE providers to NOT use the "&" sign and there is no action planned by Manuel to circumvent this on his level. I would call these "issues" as blocked, unless we find a solution how to migrate this high amount of "issues"... So automating at least the items that are listed above is only a click away, but I don't want to force anybody :) Best, /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: Mittwoch, 20. November 2013 18:06 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items Dear colleagues, as SAP I can offer you support on your particular backlog-tasks and efforts which might be automatable. Eg. for the apps chapter we migrated a lot of issues (860 issues going down to ~420 issues) with very limited manual effort. I tried to summarize in the table below what might be effected by this automatism, I won't check your reviews proactively, if you think it might be relevant for your tracker/backlog improvements please check the list below. Please let me know what you think could be automated and I can consider implementing this - although I can't promise resolutions in all cases! Your task would be to focus on the "larger" portions that need to be fixed (as it requires still some manual work on my side to customize the scripts) and saves more time. If you would have in C1 e.g. only 2 items, then I would kindly refrain from investing time into it :) Best, /Thorsten Things that MIGHT be automated: C1 - sprint and release fields --> consistency of features != open with release and sprint --> consistency of epics with release and sprint >>>>> Scheduled Stories need to have release and sprint >>>>> Scheduled Features need to have release, sprint is not needed >>>>> Scheduled Epics don't need to have either release or sprint ? I can delete arbitrary fields, if Manuel thinks they are not needed any more and implies this as error C2 - backlog reference (summary) consistency with its fields --> items' reference with inconsistent entry type >>>>> Items whose entry type field is not consistent with the entry slot of the reference ? I can change e.g. STORY to Story or similar transitions on field level C5 - Items' descriptions --> backlog items (Story, WorkItem, Bug) with no description on the tracker --> backlog items (Epic, Feature) whose description is provided on the wiki >>>>> Descriptions of Epic and Feature are provided in the wiki, so duplicated here. >>>>> These descriptions can be removed ? I can delete arbitrary fields automatically Things that are hard or NOT possible to automate C3 - backlog hierarchy C4 - Tracker link to the Wiki --> links not needed: Story, WorkItem and Bug on tracker --> links non existing or inconsistent with their reference in tracker --> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing) --> consistent urls but a connection try failed ... and all other things that are NOT listed before :) -- 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 pierangelo.garino at telecomitalia.it Tue Nov 26 12:52:24 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 26 Nov 2013 12:52:24 +0100 Subject: [Fiware-wpl] R: [Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86969@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A80604@DEWDFEMB11B.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66486A86969@DEWDFEMB11B.global.corp.sap> Message-ID: Hi Thorsten and All, The use of '&' is indeed an issue for I2ND items, as it contributes to approx 25% of our 'errors' (another approx. 25% comes from using blanks ' '), so treating them automatically would be highly appreciated. I suggested to Manuel during a mail exchange I had with him a couple of weeks ago, to consider these issues as non-errors, same as you do now with your 'blocked' proposal. In I2ND we are currently removing the blanks from our items, which is 'only' time consuming and usually involves old tickets. However doing the same for '&' would be a nightmare because this is used everywhere not only in the tickets, but primarily in the name of I2ND wiki pages, up to the catalogue. I really believe that accepting the character in the parsing procedure would be much more efficient. Another proposal would be to remove from statistics the issues related to tickets closed *and* older than a specified date (e.g. older than the introduction of the new process). BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: marted? 26 novembre 2013 12:32 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items I anyway did a small review of the current set of provided "issues" by manuel (despite that I didn't plan this in the mail before). Status of analysis: 2013-11-25 Here are the things that are most likely to be automated in "your" chapter. Apps TC1 - sprint and release fields 4 --> consistency of story, workitem and bug != open with release and sprint 0 --> consistency of features != open with release and sprint 35 --> consistency of epics with release and sprint 39 Total Data 9 --> consistency of story, workitem and bug != open with release and sprint 45 --> consistency of features != open with release and sprint 24 --> consistency of epics with release and sprint 78 Total C4 - Tracker link to the Wiki 73 --> links not needed: Story, WorkItem and Bug on tracker 47 --> links non existing or inconsistent with their reference in tracker 40 --> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing) 0 --> consistent urls but a connection try failed 160 Total I2ND C5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 112 --> backlog items (Epic, Feature) whose description is provided on the wiki 112 Total Security C5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 66 --> backlog items (Epic, Feature) whose description is provided on the wiki 66 Total IoT TC5 - Items' descriptions 0 --> backlog items (Story, WorkItem, Bug) with no description on the tracker 162 --> backlog items (Epic, Feature) whose description is provided on the wiki 162 Total Der is an additional amount of ~150 "issues" where actually the script of Manuel has a parser error - as the script is not supporting the "&" signs in tracker/wiki-items, although all the rest of the tool do support this, the wiki does not hold any information that would force the GE providers to NOT use the "&" sign and there is no action planned by Manuel to circumvent this on his level. I would call these "issues" as blocked, unless we find a solution how to migrate this high amount of "issues"... So automating at least the items that are listed above is only a click away, but I don't want to force anybody :) Best, /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: Mittwoch, 20. November 2013 18:06 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items Dear colleagues, as SAP I can offer you support on your particular backlog-tasks and efforts which might be automatable. Eg. for the apps chapter we migrated a lot of issues (860 issues going down to ~420 issues) with very limited manual effort. I tried to summarize in the table below what might be effected by this automatism, I won't check your reviews proactively, if you think it might be relevant for your tracker/backlog improvements please check the list below. Please let me know what you think could be automated and I can consider implementing this - although I can't promise resolutions in all cases! Your task would be to focus on the "larger" portions that need to be fixed (as it requires still some manual work on my side to customize the scripts) and saves more time. If you would have in C1 e.g. only 2 items, then I would kindly refrain from investing time into it :) Best, /Thorsten Things that MIGHT be automated: C1 - sprint and release fields --> consistency of features != open with release and sprint --> consistency of epics with release and sprint >>>>> Scheduled Stories need to have release and sprint >>>>> Scheduled Features need to have release, sprint is not needed >>>>> Scheduled Epics don't need to have either release or sprint ? I can delete arbitrary fields, if Manuel thinks they are not needed any more and implies this as error C2 - backlog reference (summary) consistency with its fields --> items' reference with inconsistent entry type >>>>> Items whose entry type field is not consistent with the entry slot of the reference ? I can change e.g. STORY to Story or similar transitions on field level C5 - Items' descriptions --> backlog items (Story, WorkItem, Bug) with no description on the tracker --> backlog items (Epic, Feature) whose description is provided on the wiki >>>>> Descriptions of Epic and Feature are provided in the wiki, so duplicated here. >>>>> These descriptions can be removed ? I can delete arbitrary fields automatically Things that are hard or NOT possible to automate C3 - backlog hierarchy C4 - Tracker link to the Wiki --> links not needed: Story, WorkItem and Bug on tracker --> links non existing or inconsistent with their reference in tracker --> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing) --> consistent urls but a connection try failed ... and all other things that are NOT listed before :) -- 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! 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: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From thorsten.sandfuchs at sap.com Tue Nov 26 14:41:47 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Tue, 26 Nov 2013 13:41:47 +0000 Subject: [Fiware-wpl] [Fiware-wpa] extracting the catalog to a printed version - PoC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86703@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A861B9@DEWDFEMB11B.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66486A86703@DEWDFEMB11B.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86E72@DEWDFEMB11B.global.corp.sap> Another "btw" (most probably minor?!): $ grep -i "open innovation lab" | wc -l 156 ? There are 156 terms where "open innovation lab" is used in the "current" snapshot of the catalogue as of yesterday. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Dienstag, 26. November 2013 10:30 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; Juanjo Hierro Subject: Re: [Fiware-wpa] extracting the catalog to a printed version - PoC e.g. one might imagine that we layout it with a bit of the new design flavor as shown below. With 2-colum layout where all GE have a page-break before their paragraph.... for some this would be ready for 1-page documents if the font sizes are decreased a bit... I'm not a word-designer, but just to give you some food for thought... Anybody some ideas on the open points or what to change? - Some more of the fields to be exposed here? Contact? Something else? - Should images be supported? I think it's CloudEdge, QueryBroker, IoT-gateway which are using this. - Layout can be improved further improved (whoever is a word guru...) - Chapter level headings are missing (currently I ordered the list in relation to the chapters) - (Automatic) Parsing of the "Availability" and then adding e.g. some icons to visualize better the availability modus: "open source", "FI-PPP", ... - Different table comuns/names/content? - ... Best, /Thorsten [cid:image001.jpg at 01CEEAB5.A1442160] From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Montag, 25. November 2013 17:42 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; Juanjo Hierro Subject: [Fiware-wpl] extracting the catalog to a printed version - PoC Dear colleagues, This is for the discussion on how to make a "printable" version of the catalogue to be submitted either prior to the review or during the review: As first proof-point and just to emphasize that we might manage to compile this kind of information "within this week", I precompiled the "Terms and conditions" and the "overview" tab out of the current cataloge-system automatically. See attachment... There are obvious "problems" but as a PoC this works quite well and reuses the wiki as intermediary (I took for testing the apps wiki, but can have this everywhere...) - Images are not printed and not copied (e.g. Cloud Edge) - Layout can be improved - More fields might be relevant for extraction - Chapter level headings are missing (currently I ordered the list in relation to the chapters) Any comments appreciated. Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 63413 bytes Desc: image001.jpg URL: From mcp at tid.es Tue Nov 26 18:24:23 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 26 Nov 2013 18:24:23 +0100 Subject: [Fiware-wpl] Fwd: [Fiware] Delivery of GEs In-Reply-To: <5294D2CC.8090409@tid.es> References: <5294D2CC.8090409@tid.es> Message-ID: <5294D947.2080301@tid.es> Dear all, I just sent this, as agreed yesterday in the call. Note that as in R2, I expect you to perform internal reviews of the manuals + software before coming to me. Then I will review it myself but if the review by the WPL or WPA is done well I should not find too many issues. This applies to all the R3 deliverables, delivered before or on 15/Dec. Best regards, Miguel -------- Mensaje original -------- Asunto: [Fiware] Delivery of GEs Fecha: Tue, 26 Nov 2013 17:56:44 +0100 De: Miguel Carrillo Para: fiware at lists.fi-ware.eu Dear all, A clarification that was asked yesterday in the course of the last WPL/WPA call We fixed a deadline to deliver R3 and the associated manuals by the 15th of December. But of course nothing precludes an early delivery. If someone wants to coordinate with their WPL and release before that, we can simply perform the review of the manuals of a given GE on the private wiki (same procedure as usual) and publish it in advance once approved, before the bulk of R3. Once all this is approved, a given GE could also be added early to the catalogue. As we follow an agile methodology, delivering at the end of each time frame(mapped to calendar months here) is always an option . But a delivery has to be consistent, this means that: * We need a consistent delivery: manuals & sw must be synchronised (if we have the R3 software and the wiki has the R2 manuals, this is a problem!) * We need to have the internal reviews as usual: we cannot take things to the public wiki without prior approval * Same about the catalogue: once the software and manuals are ready, the entry on the catalogue will have to be updated and will undergo reviews as well. Please centralise this with your WPL who, as usual, should provide his feedback and internal review. Once internally cleared, he will let us know that there is a given GE in their chapter delivering early. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware From jhierro at tid.es Tue Nov 26 22:02:25 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 26 Nov 2013 22:02:25 +0100 Subject: [Fiware-wpl] Fwd: RE: FI-WARE Project extension In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D07713571@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D07713571@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <52950C61.6010508@tid.es> Nicely, Arian finally answered the questions we made regarding extension of the project. I will then organize the doodle poll to go for a decision. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: FI-WARE Project extension Date: Tue, 26 Nov 2013 16:46:50 +0000 From: To: CC: Dear Juanjo, 1) This will depend largely on the outcome of the Dec 18 review. The whole purpose is to direct efforts to parts which will/do contribute to the ultimate success of the PPP, and to move FI-WARE into FI-PPP phase 3 mode. I'm not a fortune teller, but ? based on the previous review report and other indications ? I could imagine the following: ? Support, dissemination, and training will indeed be essential, as well as cooperation with XIFI, expansion, sustainability, and hand-over to the TFE project. ? Certain GEi developments will be stopped. Some of them might be started again, but in a different fashion and with a different owner, or using a competition approach. ? GERIs/GEis should be properly packaged and made publicly available, including documentation, manuals, videos, tutorials, etc. Focus on supportive materials, focus on making GE implementations usable. ? GE REFERENCE implementations, and not just GEis, should be developed. We need to move towards true reference implementations of open specifications. Appropriate processes need to be put in place for third parties to comment on and influence the specifications, and for third parties to cross-reference a GERI and its GE specification. The GERIs should document how the specification was interpreted via implementation decisions. ? Related to the point above, GE validation, including redress, by third parties (incl phase 2 projects) need proper processes and mechanisms (see page 4, review report). ? In addition, mechanisms need to be put in place for truly OPEN (and not just public) specifications (see page 5 review report) ? Prioritisation of GEs (see review report page 5) and consequences. This should be presented at the review meeting on Dec 18. ? Clarity on status: cockpit, Catalogue Testbed, FI-LAB, GE + GEi status and planning was and is still unclear. The cockpit is not up-to-date, partners start developing "components", "optional extensions" (what are those?), etc. It is impossible to get a good overview. ? Continuation of exploitation activities including clarification of T&Cs. ? Increased focus in year 3 on dissemination, contests, Startup Weekends, etc. This should be presented in the review meeting. ? Expansion towards smart cities and internationally: what is planned and what can be achieved at the end of the project? Also to be presented at the review meeting. ? Increasing support to phase 2 projects and third parties, where needed 2) For the majority of the work in a specific GE, yes. But I understand GE specifications and implementations are living artefacts. Therefore, it would seem logical to me that support, modifications based on feedback, etc continue until the end of the project. It cannot be that feedback from use case projects is ignored because it came at month 34. 3) That does not make sense to me. It should be month 40. Of course, if partners think they can have their contribution at month 36, they can obviously send it to the WP leader at month 36. 4) Yes 5) Yes Best regards, Arian. From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Saturday, November 02, 2013 1:39 PM To: ZWEGERS Arian (CNECT) Cc: jhierro >> "Juan J. Hierro" Subject: FI-WARE Project extension Dear Arian, As already commented to Jesus and you, we have opened a thread of discussion within FI-WARE about an extension of 4 months to the project in line with the recommendation given in the last review report. In order to give a definitive answer, some partners are asking for some elaborated answer to the following questions: 1. What kind of activities are foreseen during the extended period ? Would they only be related to support, dissemination and training ? 2. Will a given FI-WARE GEi owner be able to chose between a) closing its contribution to FI-WARE GE Open Specifications and its FI-WARE GEi development activities as already planned in the DoW (i.e., delivering updated GE Open Specifications as well as GEi software, testing plans and related documentation in month 33, that is end of January) or b) delay them to be in month 36 ? Ability to choose would be certainly useful, because some GEi owners can adapt to the extension provided that a delay in deliverables is approved, while others can live with the extension but provided that they can close their activities in the dates originally planned in the DoW. Telefonica, as coordinator, doesn't see any problem allowing a partner to close its activities as planned in the DoW. Just to avoid any burden we most probably would submit all the mentioned deliverables in month 36 (despite some partners would submit them internally at month 33) 3. Could month 36 be preserved as the date for submission of deliverables in WP11 (exploitation) ? 4. Could month 40 be defined as the date for submission of deliverables linked to WP12 (communication, collaboration and dissemination) ? 5. Can partners assuming a WPL or WPA role discontinue that role in month 36 if another partner is ready to take over their role until the end of the project ? Could you please answer these questions ? This and any other information that may be helpful to understand what the extension will mean in terms of workload would be certainly helpful to reach an agreement within the consortia as we would love to during this upcoming week. 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 FI-PPP Architecture Board chairman 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 nuria.delama at atos.net Wed Nov 27 03:36:16 2013 From: nuria.delama at atos.net (Nuria De-Lama Sanchez) Date: Wed, 27 Nov 2013 03:36:16 +0100 Subject: [Fiware-wpl] Fwd: RE: FI-WARE Project extension In-Reply-To: <52950C61.6010508@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D07713571@S-DC-ESTF03-B.net1.cec.eu.int> <52950C61.6010508@tid.es> Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A02BB7380@INTMAIL03.es.int.atosorigin.com> Thanks for the e-mail, which clarifies a lot of things. Some of these points are very logical but some others seem to me like a lot of additional work. Since September of this year I have received the comment by Arian that specifications are not fully OPEN in the sense that there was no mechanism in place to ensure that they could be modified based on the feedback from people. ? Starting a process like this at Xmas time (in reality that would mean January) means setting up a process, having someone monitoring that and ensuring that modifications are implemented when needed by GE owners. This is not feasible in 4 months IMHO, but extending it till September requires more work than the originally planned (unless no feedback from externals) Do not underestimate the effort related to dissemination, collaboration and expansion to smart cities and internationally (when did we promise this?). Part of the plan depends on the availability of resources from Ogilvy and partners from the third open call, but every time something serious has to be organized, it requires a lot of work. Bear in mind that the agenda is quite full: ? FIA in March ? The Future Internet event organized by the FI PPP in Brussels (beginning of April); ? Events that will come from the EC, like URBAN forum in February ? Plus the FI-WARE selected events like startup weekends, etc, etc Count on one event per month at least. The extension of the project will come with extension of work. Finally, activities towards real exploitation require an intense follow up. When you want to sell a solution to a customer you present your offering once, but then, convincing the customer means that you have to work continuously until your solution is agreed. So, going to an event is the beginning of something much harder (for example, convincing people from the EIP Smart Cities to bet on FI-WARE will require a lot of effort and resources; of course, convincing real customers is not even thought to be included here...). My two cents. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atos.net Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net IMPORTANT - MAIL ADDRESS CHANGE - From now on, please use only mail address nuria.delama at atos.net The former @atosresearch.eu address will be cancelled soon From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: martes, 26 de noviembre de 2013 22:02 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Fwd: RE: FI-WARE Project extension Nicely, Arian finally answered the questions we made regarding extension of the project. I will then organize the doodle poll to go for a decision. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: FI-WARE Project extension Date: Tue, 26 Nov 2013 16:46:50 +0000 From: To: CC: Dear Juanjo, 1) This will depend largely on the outcome of the Dec 18 review. The whole purpose is to direct efforts to parts which will/do contribute to the ultimate success of the PPP, and to move FI-WARE into FI-PPP phase 3 mode. I'm not a fortune teller, but - based on the previous review report and other indications - I could imagine the following: ? Support, dissemination, and training will indeed be essential, as well as cooperation with XIFI, expansion, sustainability, and hand-over to the TFE project. ? Certain GEi developments will be stopped. Some of them might be started again, but in a different fashion and with a different owner, or using a competition approach. ? GERIs/GEis should be properly packaged and made publicly available, including documentation, manuals, videos, tutorials, etc. Focus on supportive materials, focus on making GE implementations usable. ? GE REFERENCE implementations, and not just GEis, should be developed. We need to move towards true reference implementations of open specifications. Appropriate processes need to be put in place for third parties to comment on and influence the specifications, and for third parties to cross-reference a GERI and its GE specification. The GERIs should document how the specification was interpreted via implementation decisions. ? Related to the point above, GE validation, including redress, by third parties (incl phase 2 projects) need proper processes and mechanisms (see page 4, review report). ? In addition, mechanisms need to be put in place for truly OPEN (and not just public) specifications (see page 5 review report) ? Prioritisation of GEs (see review report page 5) and consequences. This should be presented at the review meeting on Dec 18. ? Clarity on status: cockpit, Catalogue Testbed, FI-LAB, GE + GEi status and planning was and is still unclear. The cockpit is not up-to-date, partners start developing "components", "optional extensions" (what are those?), etc. It is impossible to get a good overview. ? Continuation of exploitation activities including clarification of T&Cs. ? Increased focus in year 3 on dissemination, contests, Startup Weekends, etc. This should be presented in the review meeting. ? Expansion towards smart cities and internationally: what is planned and what can be achieved at the end of the project? Also to be presented at the review meeting. ? Increasing support to phase 2 projects and third parties, where needed 2) For the majority of the work in a specific GE, yes. But I understand GE specifications and implementations are living artefacts. Therefore, it would seem logical to me that support, modifications based on feedback, etc continue until the end of the project. It cannot be that feedback from use case projects is ignored because it came at month 34. 3) That does not make sense to me. It should be month 40. Of course, if partners think they can have their contribution at month 36, they can obviously send it to the WP leader at month 36. 4) Yes 5) Yes Best regards, Arian. From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Saturday, November 02, 2013 1:39 PM To: ZWEGERS Arian (CNECT) Cc: jhierro >> "Juan J. Hierro" Subject: FI-WARE Project extension Dear Arian, As already commented to Jesus and you, we have opened a thread of discussion within FI-WARE about an extension of 4 months to the project in line with the recommendation given in the last review report. In order to give a definitive answer, some partners are asking for some elaborated answer to the following questions: 1. What kind of activities are foreseen during the extended period ? Would they only be related to support, dissemination and training ? 2. Will a given FI-WARE GEi owner be able to chose between a) closing its contribution to FI-WARE GE Open Specifications and its FI-WARE GEi development activities as already planned in the DoW (i.e., delivering updated GE Open Specifications as well as GEi software, testing plans and related documentation in month 33, that is end of January) or b) delay them to be in month 36 ? Ability to choose would be certainly useful, because some GEi owners can adapt to the extension provided that a delay in deliverables is approved, while others can live with the extension but provided that they can close their activities in the dates originally planned in the DoW. Telefonica, as coordinator, doesn't see any problem allowing a partner to close its activities as planned in the DoW. Just to avoid any burden we most probably would submit all the mentioned deliverables in month 36 (despite some partners would submit them internally at month 33) 3. Could month 36 be preserved as the date for submission of deliverables in WP11 (exploitation) ? 4. Could month 40 be defined as the date for submission of deliverables linked to WP12 (communication, collaboration and dissemination) ? 5. Can partners assuming a WPL or WPA role discontinue that role in month 36 if another partner is ready to take over their role until the end of the project ? Could you please answer these questions ? This and any other information that may be helpful to understand what the extension will mean in terms of workload would be certainly helpful to reach an agreement within the consortia as we would love to during this upcoming week. 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 FI-PPP Architecture Board chairman 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 78 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 816 bytes Desc: image002.gif URL: From jhierro at tid.es Wed Nov 27 07:03:02 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 27 Nov 2013 07:03:02 +0100 Subject: [Fiware-wpl] IMPORTANT: Deadline for updating the FI-WARE Catalogue Message-ID: <52958B16.7020809@tid.es> Hi all and particularly FI-WARE GEi owners, This is a reminder for you to update the entries for your GEis in the FI-WARE Catalogue, particularly with respect to the new sections and the section on External Availability under the "Terms and Conditions" tab. Please be aware that this info will play a key role in the assesment of GEis that the EC and reviewers are carrying out. In this respect, the EC has informally communicated us that the review of info available in the FI-WARE Catalogue will start December 1st, so you have end of November as deadline for updating the necessary info you wish to be there. I would rather advice that you disclose any plans you may have for making your GEi available under an open source license if you haven't yet done so but it's planned during Release 3. Note that you should specify what concrete open source license you will adopt and, in the event it is a GPL-like license, you should state that it will not have a viral effect on software packaged together with it (check the Consortium or Collaboration Agreement for reference in this respect). You should also provide useful contact points for third parties who wish to explore usage of the GEis beyond the FI-PPP. I mean, placing there a generic email or web site (e.g., pointing to a generic company home website or stuff like that) won't work. This is info that reviewers are paying special attention to. 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 FI-PPP Architecture Board chairman 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 Wed Nov 27 08:39:17 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 27 Nov 2013 07:39:17 +0000 Subject: [Fiware-wpl] open Spec (implcit/essential) legal notice - status for consortium & call to action Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88954@DEWDFEMB11B.global.corp.sap> Dear colleagues, Let me make you aware of a task that we send around in apps chapter, but most probably is relevant for "your" chapter as well (see arian email). Although it says "details on how to link will be provided", I think we can't wait any longer for this - and in some sense the task is a) easy and b) clear. ? 135 pages link still to either the one or the other old open specification legal notice ? For 66 pages there was a transition to the "new" open specification legal notice Frankly: the status & ratio is alarming. :) Related overview pages to ease up click-through & fixing this: NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 It is really easy: 1. Click on both of the link in "OLD" - check if your component still linking wrongly legal notice 2. Change the link as appropriate to one or the other existing (if you don't know which one to link, as you legal contact, this has been agreed on FI-WARE level!) Judging by the email send around by arian, they will look into this & we should not have this 135:66 ratio! Best, /Thorsten (Note: the 135:66 ratio is computed out of the pure links mentioned above - there are some links e.g. the page itself, which might be counted and does not make sense to count - therefore in the end it will not be 135:66 rather 130:63 or something, but excuse this small impreciseness, I think these plus-minus-one is not the point :)) From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Heller, Markus Sent: Montag, 18. November 2013 19:13 To: 'fiware-apps at lists.fi-ware.eu' Subject: [Fiware-apps] WP3: Check your License open Spec (implcit/essential) correct.....open spec legal notice usage in fi-ware wiki Hi all, please make sure that you have your license correctly written in the WIKI, this was a reviewer request. You have chosen implicit or essential license, please update then (most often "interim License" is used in your GEs in WP3). For SAP GEs we have corrected this, feel inspired. See what we wrote for Marketplace as an example (we chose essential ...) --> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Apps.Marketplace You can check your license with these related overview pages to ease up click-through & fixing this: Who used new license "essential" or "implicit": NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 Who uses the outdated licenses: OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 What to do: Go to "License" are on top of WIKI page for your GE(s) and update license statement with a text. Attention, this is not really free text as you know, it is sort of standardized...So better just replace old link to "Interrim license "with link to your license. You have received mails on this from TID. So, If you find yourself in "OLD" then cross the water and join us in the "NEW" section... Best wishes Markus --- Below one old mail on this open task. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 23. Juni 2013 17:03 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] ToDos from now and the following months Dear colleagues, I would like to highlight a number of points that we have to deal with, and we have to concentrate our efforts on, during the following weeks. All these points will be followed up regularly at our joint WPLs/WPAs follow-up confcalls. Staty tuned regarding further clarifications that will come from your WPLs/WPAs or us in the following days. If someone believes there are additional points to add which require a close follow-up, please don't hesitate to comment. Now the list: * FI-WARE Catalogue: * Entries have to comply with the guidelines provided at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * A reference example can be found at: http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud * Entries which do not comply with the guidelines or whose contents are considered weak will not be made visible and corresponding FI-WARE GEis will therefore not be made available as part of the FI-WARE OIL and Testbed, with potential implications in rejection of costs * Don't forget that FI-WARE GEi have to make public their terms of availability beyond the FI-PPP ("External availability" in "Terms and Conditions") * FI-WARE Legal Notice: * All FI-WARE specifications have to be updated (if not already) to make a reference to any of the two final Legal Notices that have been finally approved: * with implicit patents license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) * with explicit license on essential patents: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) * Detailed instructions about how to update the corresponding sections will be provided * Detailed revision of FI-WARE GEi software and accompanying documentation: * A more in-depth and demanding revision will be carried out from now until end of July, targeted to avoid publication of FI-WARE GEis that we may foresee can receive criticism by developers beyond the research community. * This revision will be carried by programmers from Telefonica and Engineering, other volunteers are welcome. * Note that FI-WARE GEis that have been allowed to be part of FI-WARE r2.2 in our recent submission to the EC may be rejected to be made available in OIL. * In-depth revision of the Architecture and FI-WARE Open Specifications on the wiki * FI-WARE OIL, Testbed and internal Cloud environments setup * The teams in WP10 will have to work hard in order to setup three different FI-WARE Clouds for: * internal developments within FI-WARE (testing of patches, development of new releases) * the FI-WARE Testbed offered to UC projects * the FI-WARE OIL, dealing with quotas * Proper security mechanisms have to be put in place * The deliverables that had to do with Integration Plan and Report will have to be submitted * FI-WARE OIL: recipes for automated deployment of FI-WARE GEi dedicated instances * some FI-WARE GEis may be deployed as a global instance, accessible "as a Service" so that functions can be invoked through well-defined Service End Points and APIs * however, it is highly desirable that some FI-WARE GEis can also be instantiated by application developers on top of the virtual infrastructure they will setup to run their application (Dedicated instances). For this, it is highly recommended that FI-WARE GEi owners support one or several of the following options: * virtual machine images with the FI-WARE GEi properly installed and configured * deployment "recipes" that can be used together with the FI-WARE Cloud tools enabling automated deployment of software on individual VMs * deployment "recipes" that can be used together with the FI-WARE Cloud Blueprint management tools * webinars training on how to build "recipes" have to be organized and run * FI-WARE OIL/Testbed and GEis Support * A JIRA environment will be setup per FI-WARE GEi and for each of the three environments defined above (internal, FI-WARE Testbed and FI-WARE OIL) * A workflow will be defined regarding how tickets can be issued, monitored and resolved. * Access to the corresponding JIRA should be made available from the FI-WARE Catalogue * Generation of training material * WP9 will provide an eLearning and webinar platform which will be adopted as main vehicle for providing training contents * FI-WARE GEi owners will be requested to prepare training material targeted to developers. At least one recorded webinar should be made available per FI-WARE GEi * Organization of Campus Party * There will be a 1-hour session at the main starge of the Campus Party, either on Monday afternoon or Tuesday (most likely this second), where the FI-WARE OIL will be announced. Tentatively, the structure of this session might be (not necessarily in this order): * 15' of someone from the Kroes cabinet that will elaborate on the FI-PPP and will announce launch of the FI-WARE OIL * 15' of keynote speech from some reputed person in the Developers' Community endorsing the initiative (and helping to attract audience :-) * 30' of some sort of panel involving executives from some of the major industry partners (maybe they seating in sofas at the stage and someone acting as chairing/interviewer) * A number of workshops should be programmed, targeted to architects and developers and trying to cover programming practices/exercises that enable attendees to make "hands on" the technology: * Currently we have secured 4 2-hours slot workshops in the workshop area of the Campus Party booked for us. We had initially asked for 6 but seems to be not feasible and I'm trying to negotiate for 5. * Following are the workshops that we have currently identified as suitable for the audience of the Campus Party (programmers), we may decide which to go because there may not be enough number of workshop slots: * Cloud (every function provided through the portal, from deployment of Object Storage and individual VMs, through automated deployment of software on top of available VM instances up to the definition and deployment of blueprints) * Context/Data Management platform (combining a comprehensive review of the Context Broker, CEP and BigData GEs) * IoT, focused on how to connect sensors and make measured data available on the FI-WARE OIL * WireCloud * Identity Management and OAuth2-based Access Control to APIs (potentially to be merged with Cloud) * Advanced Middleware * Media-related GEis (subject to availability of GEis coming from FI-INMEDIA) * Advanced 3D and augmented reality (subject to availability of a first version of GEis coming from WeX) * There will be 2 1-hour sessions where we will be able to introduce the FI-PPP, FI-WARE, explain the ambition, main results, etc as well as announce the different challenges. There will be a space for the UC projects to announce their open calls * There will be a booth we will need to agree how to attend so that we can answer people who may come with questions. * We are negotiating a room for FI-WARE internal meetings for about 10 people, with whiteboard and projector. Our intention is that the different chapters may book slots during the Campus Party for them to meet there, therefore having a f2f meeting there. This way, attendance to the Campus Party may work as a kind of plenary meeting. * FI-WARE OIL terms and conditions * Telefonica has circulated a first draft of terms and conditions and legal departments has been asked to come to a final version by end of July. * The technical/business lead of the different FI-WARE partners should approach their legal departments to make sure they understand the whole thing. * The deadline by end of July is unmovable. FI-WARE GEis for which the corresponding owner do not subscribe the terms and conditions available by then will not be published in the FI-WARE OIL. * FI-WARE Backlog * A report on the status regarding revision and clean up of the FI-WARE Backlog will be submitted to the EC and reviewers by end of June. * Teams have to keep going in all regarding APs related to clean up of the FI-WARE Backlog and adoption of Agile practices * FI-WARE State of the Art deliverable: * We have to get it done. * FI-WARE 3rd Party Innovation Enablement: * We have to find out how we can finish a revised version Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jhierro at tid.es Wed Nov 27 08:50:13 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 27 Nov 2013 08:50:13 +0100 Subject: [Fiware-wpl] open Spec (implcit/essential) legal notice - status for consortium & call to action In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88954@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88954@DEWDFEMB11B.global.corp.sap> Message-ID: <5295A435.6040009@tid.es> Thanks Thorsten for raising this ! Indeed something to be fixed before the month 30 review (and very easy, btw) 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 FI-PPP Architecture Board chairman 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 27/11/13 08:39, Sandfuchs, Thorsten wrote: Dear colleagues, Let me make you aware of a task that we send around in apps chapter, but most probably is relevant for "your" chapter as well (see arian email). Although it says "details on how to link will be provided", I think we can't wait any longer for this - and in some sense the task is a) easy and b) clear. ? 135 pages link still to either the one or the other old open specification legal notice ? For 66 pages there was a transition to the "new" open specification legal notice Frankly: the status & ratio is alarming. :) Related overview pages to ease up click-through & fixing this: NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 It is really easy: 1. Click on both of the link in "OLD" - check if your component still linking wrongly legal notice 2. Change the link as appropriate to one or the other existing (if you don't know which one to link, as you legal contact, this has been agreed on FI-WARE level!) Judging by the email send around by arian, they will look into this & we should not have this 135:66 ratio! Best, /Thorsten (Note: the 135:66 ratio is computed out of the pure links mentioned above - there are some links e.g. the page itself, which might be counted and does not make sense to count - therefore in the end it will not be 135:66 rather 130:63 or something, but excuse this small impreciseness, I think these plus-minus-one is not the point :)) From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Heller, Markus Sent: Montag, 18. November 2013 19:13 To: 'fiware-apps at lists.fi-ware.eu' Subject: [Fiware-apps] WP3: Check your License open Spec (implcit/essential) correct.....open spec legal notice usage in fi-ware wiki Hi all, please make sure that you have your license correctly written in the WIKI, this was a reviewer request. You have chosen implicit or essential license, please update then (most often "interim License" is used in your GEs in WP3). For SAP GEs we have corrected this, feel inspired. See what we wrote for Marketplace as an example (we chose essential ...) --> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Apps.Marketplace You can check your license with these related overview pages to ease up click-through & fixing this: Who used new license "essential" or "implicit": NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 Who uses the outdated licenses: OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 What to do: Go to "License" are on top of WIKI page for your GE(s) and update license statement with a text. Attention, this is not really free text as you know, it is sort of standardized...So better just replace old link to "Interrim license "with link to your license. You have received mails on this from TID. So, If you find yourself in "OLD" then cross the water and join us in the "NEW" section... Best wishes Markus --- Below one old mail on this open task. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 23. Juni 2013 17:03 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] ToDos from now and the following months Dear colleagues, I would like to highlight a number of points that we have to deal with, and we have to concentrate our efforts on, during the following weeks. All these points will be followed up regularly at our joint WPLs/WPAs follow-up confcalls. Staty tuned regarding further clarifications that will come from your WPLs/WPAs or us in the following days. If someone believes there are additional points to add which require a close follow-up, please don't hesitate to comment. Now the list: * FI-WARE Catalogue: * Entries have to comply with the guidelines provided at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * A reference example can be found at: http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud * Entries which do not comply with the guidelines or whose contents are considered weak will not be made visible and corresponding FI-WARE GEis will therefore not be made available as part of the FI-WARE OIL and Testbed, with potential implications in rejection of costs * Don't forget that FI-WARE GEi have to make public their terms of availability beyond the FI-PPP ("External availability" in "Terms and Conditions") * FI-WARE Legal Notice: * All FI-WARE specifications have to be updated (if not already) to make a reference to any of the two final Legal Notices that have been finally approved: * with implicit patents license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) * with explicit license on essential patents: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) * Detailed instructions about how to update the corresponding sections will be provided * Detailed revision of FI-WARE GEi software and accompanying documentation: * A more in-depth and demanding revision will be carried out from now until end of July, targeted to avoid publication of FI-WARE GEis that we may foresee can receive criticism by developers beyond the research community. * This revision will be carried by programmers from Telefonica and Engineering, other volunteers are welcome. * Note that FI-WARE GEis that have been allowed to be part of FI-WARE r2.2 in our recent submission to the EC may be rejected to be made available in OIL. * In-depth revision of the Architecture and FI-WARE Open Specifications on the wiki * FI-WARE OIL, Testbed and internal Cloud environments setup * The teams in WP10 will have to work hard in order to setup three different FI-WARE Clouds for: * internal developments within FI-WARE (testing of patches, development of new releases) * the FI-WARE Testbed offered to UC projects * the FI-WARE OIL, dealing with quotas * Proper security mechanisms have to be put in place * The deliverables that had to do with Integration Plan and Report will have to be submitted * FI-WARE OIL: recipes for automated deployment of FI-WARE GEi dedicated instances * some FI-WARE GEis may be deployed as a global instance, accessible "as a Service" so that functions can be invoked through well-defined Service End Points and APIs * however, it is highly desirable that some FI-WARE GEis can also be instantiated by application developers on top of the virtual infrastructure they will setup to run their application (Dedicated instances). For this, it is highly recommended that FI-WARE GEi owners support one or several of the following options: * virtual machine images with the FI-WARE GEi properly installed and configured * deployment "recipes" that can be used together with the FI-WARE Cloud tools enabling automated deployment of software on individual VMs * deployment "recipes" that can be used together with the FI-WARE Cloud Blueprint management tools * webinars training on how to build "recipes" have to be organized and run * FI-WARE OIL/Testbed and GEis Support * A JIRA environment will be setup per FI-WARE GEi and for each of the three environments defined above (internal, FI-WARE Testbed and FI-WARE OIL) * A workflow will be defined regarding how tickets can be issued, monitored and resolved. * Access to the corresponding JIRA should be made available from the FI-WARE Catalogue * Generation of training material * WP9 will provide an eLearning and webinar platform which will be adopted as main vehicle for providing training contents * FI-WARE GEi owners will be requested to prepare training material targeted to developers. At least one recorded webinar should be made available per FI-WARE GEi * Organization of Campus Party * There will be a 1-hour session at the main starge of the Campus Party, either on Monday afternoon or Tuesday (most likely this second), where the FI-WARE OIL will be announced. Tentatively, the structure of this session might be (not necessarily in this order): * 15' of someone from the Kroes cabinet that will elaborate on the FI-PPP and will announce launch of the FI-WARE OIL * 15' of keynote speech from some reputed person in the Developers' Community endorsing the initiative (and helping to attract audience :-) * 30' of some sort of panel involving executives from some of the major industry partners (maybe they seating in sofas at the stage and someone acting as chairing/interviewer) * A number of workshops should be programmed, targeted to architects and developers and trying to cover programming practices/exercises that enable attendees to make "hands on" the technology: * Currently we have secured 4 2-hours slot workshops in the workshop area of the Campus Party booked for us. We had initially asked for 6 but seems to be not feasible and I'm trying to negotiate for 5. * Following are the workshops that we have currently identified as suitable for the audience of the Campus Party (programmers), we may decide which to go because there may not be enough number of workshop slots: * Cloud (every function provided through the portal, from deployment of Object Storage and individual VMs, through automated deployment of software on top of available VM instances up to the definition and deployment of blueprints) * Context/Data Management platform (combining a comprehensive review of the Context Broker, CEP and BigData GEs) * IoT, focused on how to connect sensors and make measured data available on the FI-WARE OIL * WireCloud * Identity Management and OAuth2-based Access Control to APIs (potentially to be merged with Cloud) * Advanced Middleware * Media-related GEis (subject to availability of GEis coming from FI-INMEDIA) * Advanced 3D and augmented reality (subject to availability of a first version of GEis coming from WeX) * There will be 2 1-hour sessions where we will be able to introduce the FI-PPP, FI-WARE, explain the ambition, main results, etc as well as announce the different challenges. There will be a space for the UC projects to announce their open calls * There will be a booth we will need to agree how to attend so that we can answer people who may come with questions. * We are negotiating a room for FI-WARE internal meetings for about 10 people, with whiteboard and projector. Our intention is that the different chapters may book slots during the Campus Party for them to meet there, therefore having a f2f meeting there. This way, attendance to the Campus Party may work as a kind of plenary meeting. * FI-WARE OIL terms and conditions * Telefonica has circulated a first draft of terms and conditions and legal departments has been asked to come to a final version by end of July. * The technical/business lead of the different FI-WARE partners should approach their legal departments to make sure they understand the whole thing. * The deadline by end of July is unmovable. FI-WARE GEis for which the corresponding owner do not subscribe the terms and conditions available by then will not be published in the FI-WARE OIL. * FI-WARE Backlog * A report on the status regarding revision and clean up of the FI-WARE Backlog will be submitted to the EC and reviewers by end of June. * Teams have to keep going in all regarding APs related to clean up of the FI-WARE Backlog and adoption of Agile practices * FI-WARE State of the Art deliverable: * We have to get it done. * FI-WARE 3rd Party Innovation Enablement: * We have to find out how we can finish a revised version Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed Nov 27 09:24:47 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 27 Nov 2013 09:24:47 +0100 Subject: [Fiware-wpl] IMPORTANT: Deadline for updating the FI-WARE Catalogue In-Reply-To: <52958B16.7020809@tid.es> References: <52958B16.7020809@tid.es> Message-ID: dear juanjo and all, please find attached for your convenience the situation at yesterday evening. ciao, stefano 2013/11/27 Juanjo Hierro : > Hi all and particularly FI-WARE GEi owners, > > This is a reminder for you to update the entries for your GEis in the > FI-WARE Catalogue, particularly with respect to the new sections and the > section on External Availability under the "Terms and Conditions" tab. > > Please be aware that this info will play a key role in the assesment of > GEis that the EC and reviewers are carrying out. In this respect, the EC > has informally communicated us that the review of info available in the > FI-WARE Catalogue will start December 1st, so you have end of November as > deadline for updating the necessary info you wish to be there. > > I would rather advice that you disclose any plans you may have for making > your GEi available under an open source license if you haven't yet done so > but it's planned during Release 3. Note that you should specify what > concrete open source license you will adopt and, in the event it is a > GPL-like license, you should state that it will not have a viral effect on > software packaged together with it (check the Consortium or Collaboration > Agreement for reference in this respect). > > You should also provide useful contact points for third parties who wish > to explore usage of the GEis beyond the FI-PPP. I mean, placing there a > generic email or web site (e.g., pointing to a generic company home website > or stuff like that) won't work. This is info that reviewers are paying > special attention to. > > 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 > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- A non-text attachment was scrubbed... Name: Testbed-V2_catalogue_publication_status.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 70447 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Wed Nov 27 10:02:28 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 27 Nov 2013 09:02:28 +0000 Subject: [Fiware-wpl] provisioning of "forum" in the catalogue at least questionable if not to be deprovisioned! Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88C4F@DEWDFEMB11B.global.corp.sap> Dear colleagues, while browsing the catalog, I discovered that we have an "new" (empty) forum now implemented only with silly content (sorry for being so "blond", but I want to make a point here). Although it might be a nice feature (and somehow opening up our communication channels), I think its not more than "nice-tohave" but even there are strong downsides to this which might even harm the project reputation: - An empty forum will be screened by the reviewers wondering if there is no feedback or uptake - You can only post to the forum once you are logged in (gives the false impression to actually be open & this is probably the main reason that people are not posting to this) - Providing a forum where only FI-WARE personel (which to my knowledge are the only people with logins to the forge) is nonsense as the people would rather use email to communicate or ask questions about the catalogue - Provide a public forum where you can just give feedback towards "the catalogue" but not the enablers, does not make much sense - where is the communication on where to give feedback on the GEs? - It again introduces a new system and feedback channel which seems not related to existing channels and might give the impression that we are not unifying our systems, but rather creating more complexity! Overall as the main focus for the catalogue is to provide externally facing and consistent information (and is in all other apects strongly monitored, I wonder why on earth we should provide fi-ware personnel the ability to post arbitrary stuff in the forum on the catalog and not govern this external facing channel as closely as all the other parts of the system) - the catalogue AFAIK is not entitled to provide a feedback channel & the feedback channels is in the current format even degenerate the quality of the site itself, therefore degenerate the content of the GE information! ? I vote strongly against providing this forum before end of this year (iff at all, and the other downsides as considered above are reconsidered or solved). It should be removed as quickly as possible and as quickly as it "evolved". How can we have a proper resolution on this and implement subsequent changes within this week? And just to top the ability of reacting upon forum-requests - the only "real" posting there is, is even not commented since 2 month! What should I say more... 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: image001.jpg Type: image/jpeg Size: 5764 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11389 bytes Desc: image002.jpg URL: From davide.dallecarbonare at eng.it Thu Nov 28 01:39:31 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Thu, 28 Nov 2013 01:39:31 +0100 Subject: [Fiware-wpl] provisioning of "forum" in the catalogue at least questionable if not to be deprovisioned! In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88C4F@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88C4F@DEWDFEMB11B.global.corp.sap> Message-ID: <529690C3.7000306@eng.it> Dear Thorsten, thank you very much for your valuable point of view and suggestions. The "new" feature is available since more that one year, and it has been setup to support the information sharing between members of the developers community. The proposal at the beginning was to have one forum per entry/GEi but we (Tools chapter) thought that this solution would end up in a fragmentation of information ... it's better to open a top level forum where threads by GEi could be created. There may be various reasons why at the moment this forum is still not so much used, and one may be that, probably, we haven't been able to advertise it in the proper way ... I definitely do not see a conflict in terms of communication channels, we have the forge to collect inputs from UC projects, we have JIRA to collect inputs from the developers community, and this forum to enable the communication between the members of the developers community ... and in respect to this, the best place to have it is in the Catalogue. Given said that, if all the WP leaders want to remove this feature from the Catalogue, we can proceed to remove it very quickly. BR Davide On 27/11/2013 10:02, Sandfuchs, Thorsten wrote: > > Dear colleagues, > > while browsing the catalog, I discovered that we have an "new" (empty) > forum now implemented only with silly content (sorry for being so > "blond", but I want to make a point here). > > Although it might be a nice feature (and somehow opening up our > communication channels), I think its not more than "nice-tohave" but > even there are strong downsides to this which might even *harm* the > project reputation: > > -An empty forum will be screened by the *reviewers* wondering if there > is no feedback or uptake > > -You can only post to the forum once you are logged in (gives the > false impression to actually be open & this is probably the main > reason that people are not posting to this) > > -Providing a forum where only FI-WARE personel (which to my knowledge > are the only people with logins to the forge) is nonsense as the > people would rather use email to communicate or ask questions about > the catalogue > > -Provide a *public *forum where you can just give feedback towards > "the catalogue" but not the enablers, does not make much sense -- > where is the communication on where to give feedback on the GEs? > > -It again introduces a new system and feedback channel which seems not > related to existing channels and might give the impression that we are > not unifying our systems, but rather creating more complexity! > > Overall as the main focus for the catalogue is to provide externally > facing and consistent information (and is in all other apects strongly > monitored, I wonder why on earth we should provide fi-ware personnel > the ability to post arbitrary stuff in the forum on the catalog and > not govern this external facing channel as closely as all the other > parts of the system) -- the catalogue AFAIK is *not* entitled to > provide a feedback channel & the feedback channels is in the current > format even degenerate the quality of the site itself, therefore > degenerate the content of the GE information! > > ?I vote strongly against providing this forum *before end of this > year* (iff at all, and the other downsides as considered above are > reconsidered or solved). It should be removed as quickly as possible > and as quickly as it "evolved". > > *How can we have a proper resolution on this and implement subsequent > changes within this week?* > > And just to top the ability of reacting upon forum-requests - the only > "real" posting there is, is even not commented since 2 month! What > should I say more... > > 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: not available Type: image/jpeg Size: 5764 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 11389 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Thu Nov 28 11:07:05 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 28 Nov 2013 10:07:05 +0000 Subject: [Fiware-wpl] provisioning of "forum" in the catalogue at least questionable if not to be deprovisioned! In-Reply-To: <529690C3.7000306@eng.it> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A88C4F@DEWDFEMB11B.global.corp.sap> <529690C3.7000306@eng.it> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8A957@DEWDFEMB11B.global.corp.sap> Thanks Davide for your effort & proposal to remove it. As I'm currently acting on behalf of WP3-L (Markus being out of office), I vote for the removal of the forum. Best, /Thorsten From: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Sent: Donnerstag, 28. November 2013 01:40 To: Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: provisioning of "forum" in the catalogue at least questionable if not to be deprovisioned! Dear Thorsten, thank you very much for your valuable point of view and suggestions. The "new" feature is available since more that one year, and it has been setup to support the information sharing between members of the developers community. The proposal at the beginning was to have one forum per entry/GEi but we (Tools chapter) thought that this solution would end up in a fragmentation of information ... it's better to open a top level forum where threads by GEi could be created. There may be various reasons why at the moment this forum is still not so much used, and one may be that, probably, we haven't been able to advertise it in the proper way ... I definitely do not see a conflict in terms of communication channels, we have the forge to collect inputs from UC projects, we have JIRA to collect inputs from the developers community, and this forum to enable the communication between the members of the developers community ... and in respect to this, the best place to have it is in the Catalogue. Given said that, if all the WP leaders want to remove this feature from the Catalogue, we can proceed to remove it very quickly. BR Davide On 27/11/2013 10:02, Sandfuchs, Thorsten wrote: Dear colleagues, while browsing the catalog, I discovered that we have an "new" (empty) forum now implemented only with silly content (sorry for being so "blond", but I want to make a point here). [cid:image001.jpg at 01CEEC29.F852BFF0] Although it might be a nice feature (and somehow opening up our communication channels), I think its not more than "nice-tohave" but even there are strong downsides to this which might even harm the project reputation: - An empty forum will be screened by the reviewers wondering if there is no feedback or uptake - You can only post to the forum once you are logged in (gives the false impression to actually be open & this is probably the main reason that people are not posting to this) - Providing a forum where only FI-WARE personel (which to my knowledge are the only people with logins to the forge) is nonsense as the people would rather use email to communicate or ask questions about the catalogue - Provide a public forum where you can just give feedback towards "the catalogue" but not the enablers, does not make much sense - where is the communication on where to give feedback on the GEs? - It again introduces a new system and feedback channel which seems not related to existing channels and might give the impression that we are not unifying our systems, but rather creating more complexity! Overall as the main focus for the catalogue is to provide externally facing and consistent information (and is in all other apects strongly monitored, I wonder why on earth we should provide fi-ware personnel the ability to post arbitrary stuff in the forum on the catalog and not govern this external facing channel as closely as all the other parts of the system) - the catalogue AFAIK is not entitled to provide a feedback channel & the feedback channels is in the current format even degenerate the quality of the site itself, therefore degenerate the content of the GE information! ? I vote strongly against providing this forum before end of this year (iff at all, and the other downsides as considered above are reconsidered or solved). It should be removed as quickly as possible and as quickly as it "evolved". How can we have a proper resolution on this and implement subsequent changes within this week? And just to top the ability of reacting upon forum-requests - the only "real" posting there is, is even not commented since 2 month! What should I say more... [cid:image002.jpg at 01CEEC29.F852BFF0] 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: image001.jpg Type: image/jpeg Size: 5764 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11389 bytes Desc: image002.jpg URL: From mcp at tid.es Thu Nov 28 20:27:42 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 28 Nov 2013 20:27:42 +0100 Subject: [Fiware-wpl] Fwd: Re: open Spec (implcit/essential) legal notice - status for consortium & call to action In-Reply-To: <5295A435.6040009@tid.es> References: <5295A435.6040009@tid.es> Message-ID: <5297992E.4050709@tid.es> Dear all, Be aware that we are still linking the old open specification legal notice. And this is something the reviewers were looking at. It is so simple that it should take no time. The details are at the bottom, read on... Please fix asap. Best regards, Miguel -------- Mensaje original -------- Asunto: Re: [Fiware-wpl] open Spec (implcit/essential) legal notice - status for consortium & call to action Fecha: Wed, 27 Nov 2013 08:50:13 +0100 De: Juanjo Hierro Para: Thanks Thorsten for raising this ! Indeed something to be fixed before the month 30 review (and very easy, btw) 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 FI-PPP Architecture Board chairman 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 27/11/13 08:39, Sandfuchs, Thorsten wrote: Dear colleagues, Let me make you aware of a task that we send around in apps chapter, but most probably is relevant for "your" chapter as well (see arian email). Although it says "details on how to link will be provided", I think we can't wait any longer for this - and in some sense the task is a) easy and b) clear. ? 135 pages link still to either the one or the other old open specification legal notice ? For 66 pages there was a transition to the "new" open specification legal notice Frankly: the status & ratio is alarming. :) Related overview pages to ease up click-through & fixing this: NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 It is really easy: 1. Click on both of the link in "OLD" - check if your component still linking wrongly legal notice 2. Change the link as appropriate to one or the other existing (if you don't know which one to link, as you legal contact, this has been agreed on FI-WARE level!) Judging by the email send around by arian, they will look into this & we should not have this 135:66 ratio! Best, /Thorsten (Note: the 135:66 ratio is computed out of the pure links mentioned above - there are some links e.g. the page itself, which might be counted and does not make sense to count - therefore in the end it will not be 135:66 rather 130:63 or something, but excuse this small impreciseness, I think these plus-minus-one is not the point :)) From: fiware-apps-bounces at lists.fi-ware.eu [mailto:fiware-apps-bounces at lists.fi-ware.eu] On Behalf Of Heller, Markus Sent: Montag, 18. November 2013 19:13 To: 'fiware-apps at lists.fi-ware.eu' Subject: [Fiware-apps] WP3: Check your License open Spec (implcit/essential) correct.....open spec legal notice usage in fi-ware wiki Hi all, please make sure that you have your license correctly written in the WIKI, this was a reviewer request. You have chosen implicit or essential license, please update then (most often "interim License" is used in your GEs in WP3). For SAP GEs we have corrected this, feel inspired. See what we wrote for Marketplace as an example (we chose essential ...) --> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Apps.Marketplace You can check your license with these related overview pages to ease up click-through & fixing this: Who used new license "essential" or "implicit": NEW: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license)?limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Special:WhatLinksHere/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license)?limit=500 Who uses the outdated licenses: OLD: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/Open_Specifications_Interim_Legal_Notice&limit=500 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php?title=Special:WhatLinksHere/FI-WARE_Open_Specifications_Legal_Notice&limit=500 What to do: Go to "License" are on top of WIKI page for your GE(s) and update license statement with a text. Attention, this is not really free text as you know, it is sort of standardized...So better just replace old link to "Interrim license "with link to your license. You have received mails on this from TID. So, If you find yourself in "OLD" then cross the water and join us in the "NEW" section... Best wishes Markus --- Below one old mail on this open task. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Sonntag, 23. Juni 2013 17:03 To: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] ToDos from now and the following months Dear colleagues, I would like to highlight a number of points that we have to deal with, and we have to concentrate our efforts on, during the following weeks. All these points will be followed up regularly at our joint WPLs/WPAs follow-up confcalls. Staty tuned regarding further clarifications that will come from your WPLs/WPAs or us in the following days. If someone believes there are additional points to add which require a close follow-up, please don't hesitate to comment. Now the list: * FI-WARE Catalogue: * Entries have to comply with the guidelines provided at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write * A reference example can be found at: http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud * Entries which do not comply with the guidelines or whose contents are considered weak will not be made visible and corresponding FI-WARE GEis will therefore not be made available as part of the FI-WARE OIL and Testbed, with potential implications in rejection of costs * Don't forget that FI-WARE GEi have to make public their terms of availability beyond the FI-PPP ("External availability" in "Terms and Conditions") * FI-WARE Legal Notice: * All FI-WARE specifications have to be updated (if not already) to make a reference to any of the two final Legal Notices that have been finally approved: * with implicit patents license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) * with explicit license on essential patents: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) * Detailed instructions about how to update the corresponding sections will be provided * Detailed revision of FI-WARE GEi software and accompanying documentation: * A more in-depth and demanding revision will be carried out from now until end of July, targeted to avoid publication of FI-WARE GEis that we may foresee can receive criticism by developers beyond the research community. * This revision will be carried by programmers from Telefonica and Engineering, other volunteers are welcome. * Note that FI-WARE GEis that have been allowed to be part of FI-WARE r2.2 in our recent submission to the EC may be rejected to be made available in OIL. * In-depth revision of the Architecture and FI-WARE Open Specifications on the wiki * FI-WARE OIL, Testbed and internal Cloud environments setup * The teams in WP10 will have to work hard in order to setup three different FI-WARE Clouds for: * internal developments within FI-WARE (testing of patches, development of new releases) * the FI-WARE Testbed offered to UC projects * the FI-WARE OIL, dealing with quotas * Proper security mechanisms have to be put in place * The deliverables that had to do with Integration Plan and Report will have to be submitted * FI-WARE OIL: recipes for automated deployment of FI-WARE GEi dedicated instances * some FI-WARE GEis may be deployed as a global instance, accessible "as a Service" so that functions can be invoked through well-defined Service End Points and APIs * however, it is highly desirable that some FI-WARE GEis can also be instantiated by application developers on top of the virtual infrastructure they will setup to run their application (Dedicated instances). For this, it is highly recommended that FI-WARE GEi owners support one or several of the following options: * virtual machine images with the FI-WARE GEi properly installed and configured * deployment "recipes" that can be used together with the FI-WARE Cloud tools enabling automated deployment of software on individual VMs * deployment "recipes" that can be used together with the FI-WARE Cloud Blueprint management tools * webinars training on how to build "recipes" have to be organized and run * FI-WARE OIL/Testbed and GEis Support * A JIRA environment will be setup per FI-WARE GEi and for each of the three environments defined above (internal, FI-WARE Testbed and FI-WARE OIL) * A workflow will be defined regarding how tickets can be issued, monitored and resolved. * Access to the corresponding JIRA should be made available from the FI-WARE Catalogue * Generation of training material * WP9 will provide an eLearning and webinar platform which will be adopted as main vehicle for providing training contents * FI-WARE GEi owners will be requested to prepare training material targeted to developers. At least one recorded webinar should be made available per FI-WARE GEi * Organization of Campus Party * There will be a 1-hour session at the main starge of the Campus Party, either on Monday afternoon or Tuesday (most likely this second), where the FI-WARE OIL will be announced. Tentatively, the structure of this session might be (not necessarily in this order): * 15' of someone from the Kroes cabinet that will elaborate on the FI-PPP and will announce launch of the FI-WARE OIL * 15' of keynote speech from some reputed person in the Developers' Community endorsing the initiative (and helping to attract audience :-) * 30' of some sort of panel involving executives from some of the major industry partners (maybe they seating in sofas at the stage and someone acting as chairing/interviewer) * A number of workshops should be programmed, targeted to architects and developers and trying to cover programming practices/exercises that enable attendees to make "hands on" the technology: * Currently we have secured 4 2-hours slot workshops in the workshop area of the Campus Party booked for us. We had initially asked for 6 but seems to be not feasible and I'm trying to negotiate for 5. * Following are the workshops that we have currently identified as suitable for the audience of the Campus Party (programmers), we may decide which to go because there may not be enough number of workshop slots: * Cloud (every function provided through the portal, from deployment of Object Storage and individual VMs, through automated deployment of software on top of available VM instances up to the definition and deployment of blueprints) * Context/Data Management platform (combining a comprehensive review of the Context Broker, CEP and BigData GEs) * IoT, focused on how to connect sensors and make measured data available on the FI-WARE OIL * WireCloud * Identity Management and OAuth2-based Access Control to APIs (potentially to be merged with Cloud) * Advanced Middleware * Media-related GEis (subject to availability of GEis coming from FI-INMEDIA) * Advanced 3D and augmented reality (subject to availability of a first version of GEis coming from WeX) * There will be 2 1-hour sessions where we will be able to introduce the FI-PPP, FI-WARE, explain the ambition, main results, etc as well as announce the different challenges. There will be a space for the UC projects to announce their open calls * There will be a booth we will need to agree how to attend so that we can answer people who may come with questions. * We are negotiating a room for FI-WARE internal meetings for about 10 people, with whiteboard and projector. Our intention is that the different chapters may book slots during the Campus Party for them to meet there, therefore having a f2f meeting there. This way, attendance to the Campus Party may work as a kind of plenary meeting. * FI-WARE OIL terms and conditions * Telefonica has circulated a first draft of terms and conditions and legal departments has been asked to come to a final version by end of July. * The technical/business lead of the different FI-WARE partners should approach their legal departments to make sure they understand the whole thing. * The deadline by end of July is unmovable. FI-WARE GEis for which the corresponding owner do not subscribe the terms and conditions available by then will not be published in the FI-WARE OIL. * FI-WARE Backlog * A report on the status regarding revision and clean up of the FI-WARE Backlog will be submitted to the EC and reviewers by end of June. * Teams have to keep going in all regarding APs related to clean up of the FI-WARE Backlog and adoption of Agile practices * FI-WARE State of the Art deliverable: * We have to get it done. * FI-WARE 3rd Party Innovation Enablement: * We have to find out how we can finish a revised version Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From jdps at tid.es Thu Nov 28 23:20:36 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Thu, 28 Nov 2013 22:20:36 +0000 Subject: [Fiware-wpl] FI-WARE: Periodic report M30 - Third iteration Message-ID: <77A22C1085494D48B4018F06A40DB2C730047298@EX10-MB2-MAD.hi.inet> Dear all, please find the second draft version of the Periodic Report M30. Please check it and contact with the WPL if you want/need to update something. We?ll only accept changes from WPL. @WPL: Please if needed, send an updated version with track changes activated to me (using the attached version). Deadline: Monday the 2nd of December, EOB. Note: The following partners have ?No input from partner? or ?No activities? or ?No justification? (regarding their PM in the DoW by task) No input from partner 02 ? SAP 07 - FT 12 ? TRDF 14 ? ATOS 15 ? E-IIS 16 ? ALU-I 19 - INTEL 22 ? INRIA 23 - UPM 32 ? IMINDS 31 ? EPROS 36 - ADMINO No activities 01- TID 03- IBM-IL 06 ? TI 07 - FT 11 - DT 12 ? TRDF 15 ? E-IIS 16 ? ALU-I 18 ? SIEMENS 19 - INTEL 23 ? UPM 28 ? ZHAW 29 ? DFKI 30 ? USAAR-CISPA 31 - EPROS 32 - IMINDS No justification provided 01 ? TID 02 - SAP 03 ? IBM-IL 05 ? THALES 12 ?TRDF 14 ? ATOS 15 ? E-IIS 16 ? ALU-I 22 ? INRIA 23 ? UPM 28 - ZHAW 30 ? USAAR-CISPA 31 ? EPROS 34 - PLAYSIGN BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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.1.2.5 - Periodic Report M30 (DRAFT v2).docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1422035 bytes Desc: D.1.2.5 - Periodic Report M30 (DRAFT v2).docx URL: From mcp at tid.es Fri Nov 29 11:12:29 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 29 Nov 2013 11:12:29 +0100 Subject: [Fiware-wpl] M30 review meeting Message-ID: <5298688D.3010505@tid.es> Dear all, I have just created the skeleton of the google doc for the forthcoming review. I will continue working on this but please start adding your names those who are attending. Also, I'd appreciate it if you could add your names here send me your ID cards. The hard deadline is 3/Dec for names + ID cards, after then no one will be able to be added to the list (the EC needs the details in advance) This is the link: * https://docs.google.com/document/d/1hJW1_XqgK_tTczPJvAkGb4hovDv7hj2nzTZQqf4TWSM/edit# Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Fri Nov 29 12:16:09 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 29 Nov 2013 11:16:09 +0000 Subject: [Fiware-wpl] Agile dynamic : Sprint 3.2.2 Closing -LAST CALL Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89139A34@EX10-MB1-MAD.hi.inet> Dear Partners, Let me remind you of the sprint closing, which is scheduled for today. The unique action needed is to CLOSE those items already finished. I'll be getting a snapshot this afternoon at 6:00 PM. On Monday I'll be informing WP leaders on the chapter performance. Thanks for cooperation! Find the links to today's snapshot below. https://forge.fi-ware.eu/docman/view.php/27/3151/FIWARE.backlog.apps.dashboard.20131129.xlsx https://forge.fi-ware.eu/docman/view.php/27/3152/FIWARE.backlog.cloud.dashboard.20131129.xlsx https://forge.fi-ware.eu/docman/view.php/27/3155/FIWARE.backlog.iot.dashboard.20131129.xlsx https://forge.fi-ware.eu/docman/view.php/27/3153/FIWARE.backlog.data.dashboard.20131129.xlsx https://forge.fi-ware.eu/docman/view.php/27/3154/FIWARE.backlog.i2nd.dashboard.20131129.xlsx https://forge.fi-ware.eu/docman/view.php/27/3156/FIWARE.backlog.security.dashboard.20131129.xlsx 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 mcp at tid.es Fri Nov 29 12:20:39 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 29 Nov 2013 12:20:39 +0100 Subject: [Fiware-wpl] M30 review meeting In-Reply-To: <5298688D.3010505@tid.es> References: <5298688D.3010505@tid.es> Message-ID: <52987887.5060508@tid.es> Hi, I just realised that 3 should be the deadline for the agenda . But 10 should be ok for registration. I modified it on the google doc. BR Miguel El 29/11/2013 11:12, Miguel Carrillo escribi?: Dear all, I have just created the skeleton of the google doc for the forthcoming review. I will continue working on this but please start adding your names those who are attending. Also, I'd appreciate it if you could add your names here send me your ID cards. The hard deadline is 3/Dec for names + ID cards, after then no one will be able to be added to the list (the EC needs the details in advance) This is the link: * https://docs.google.com/document/d/1hJW1_XqgK_tTczPJvAkGb4hovDv7hj2nzTZQqf4TWSM/edit# Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Fri Nov 29 12:34:26 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 29 Nov 2013 11:34:26 +0000 Subject: [Fiware-wpl] Delivery Awareness Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89139A64@EX10-MB1-MAD.hi.inet> Dear Partners, Let me share with you the spreadsheet to be used to create awareness on delivery. It's composed of four tabs. Being the first, the dashboard copied below. It shows delayed, already delivered, and coming deliverables. The other three tabs give perspective for each reporting period. You can find there details for each deliverable. I'd appreciate you gave me feedback on possible errors you may well find on deliverables under your responsibility or knowledge. I took info from Miguel's record (Thanks!!!!), and also from the last EC review report. However, although it should be accurate but there might error as well. Thanks for cooperation!! Kind regards, Manuel [cid:image001.png at 01CEECFF.45E4C800] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 51926 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.DeliveryAwareness.20131129.xls Type: application/vnd.ms-excel Size: 77382 bytes Desc: FIWARE.DeliveryAwareness.20131129.xls URL: From mev at tid.es Fri Nov 29 14:51:35 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 29 Nov 2013 13:51:35 +0000 Subject: [Fiware-wpl] WPL/WPA agenda - SAP's issue on the backlog Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89139BBB@EX10-MB1-MAD.hi.inet> Hi Miguel, I'd appreciate you made a time slot on Monday's agenda for SAP to explain their issues on the backlog, and votes could be taken on their proposals. I'll prepare the corresponding doodle pages. The proposals are the following: 1. Not to fix issues on 'old' items. Concretely belonging to R1 and R2 2. Exclude backlog tests on items from partners withdrawn from the project 3. Exclude backlog tests on arbitrary items according to WP Leader criteria If the agenda allows including this issue, SAP will be explaining them on detail on Monday. On my side I understand the context demands focussing attention on others matters, however I have no other option but to send you this request. Thanks in advance! 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 Fri Nov 29 15:19:47 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 29 Nov 2013 14:19:47 +0000 Subject: [Fiware-wpl] WPL/WPA agenda - SAP's issue on the backlog In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B89139BBB@EX10-MB1-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89139BBB@EX10-MB1-MAD.hi.inet> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8CF5A@DEWDFEMB11B.global.corp.sap> Hi Manuel, thanks for driving this forward, although I like to emphasize that we do not have "issues on the backlog" - we brought forward "proposals which are tailored to improve the quality of the backlog and related backlog-quality insurance processes" and that this is not "SAP" alone, as there are already positive reactions from other work packages, concerning the proposals. And I'm sure that you will as well consider bringing forward the last proposal that we brought forward: Proposal: improving the backlog-calculation-mechanism in relation to the "&" sign-problem. It should not be counted as "issue" any more with negative effects for the chapters. (SAP proposed at least 4 distinct and possible solutions to circumvent this) Thanks and best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Freitag, 29. November 2013 14:52 To: MIGUEL CARRILLO PACHECO Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] WPL/WPA agenda - SAP's issue on the backlog Hi Miguel, I'd appreciate you made a time slot on Monday's agenda for SAP to explain their issues on the backlog, and votes could be taken on their proposals. I'll prepare the corresponding doodle pages. The proposals are the following: 1. Not to fix issues on 'old' items. Concretely belonging to R1 and R2 2. Exclude backlog tests on items from partners withdrawn from the project 3. Exclude backlog tests on arbitrary items according to WP Leader criteria If the agenda allows including this issue, SAP will be explaining them on detail on Monday. On my side I understand the context demands focussing attention on others matters, however I have no other option but to send you this request. Thanks in advance! 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 Fri Nov 29 17:55:57 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 29 Nov 2013 16:55:57 +0000 Subject: [Fiware-wpl] [Fiware-wpa] extracting the catalog to a printed version - PoC In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66486A86703@DEWDFEMB11B.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66486A861B9@DEWDFEMB11B.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66486A86703@DEWDFEMB11B.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66486A8D37B@DEWDFEMB11B.global.corp.sap> Please find attached and updated and "most current" version of the document... I wouldn't recommend to send it to the EC, but at least for internal review and quickly comparing the various entries - I think its might already help. Status of the content of the catalog was captured around 17:20 today... and then some layouting improvements were applied manually. As some GE use different headings (e.g. H1 instead of H2, the layout breaks actually in a number of places and this needs to be fixed manually). 12 GE - WP3 Apps chapters 9 GE - WP4 Cloud chapter 10 GE - WP5 Data chapter 7 GE - WP6 IoT chpater 9 GE - WP7 I2ND chapter 13 GE - WP8 Security chapter 5 Tools WP9 Tools chapter ------------------- 65 number of GEs were processed Best, /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: Dienstag, 26. November 2013 10:30 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; Juanjo Hierro Subject: Re: [Fiware-wpa] extracting the catalog to a printed version - PoC e.g. one might imagine that we layout it with a bit of the new design flavor as shown below. With 2-colum layout where all GE have a page-break before their paragraph.... for some this would be ready for 1-page documents if the font sizes are decreased a bit... I'm not a word-designer, but just to give you some food for thought... Anybody some ideas on the open points or what to change? - Some more of the fields to be exposed here? Contact? Something else? - Should images be supported? I think it's CloudEdge, QueryBroker, IoT-gateway which are using this. - Layout can be improved further improved (whoever is a word guru...) - Chapter level headings are missing (currently I ordered the list in relation to the chapters) - (Automatic) Parsing of the "Availability" and then adding e.g. some icons to visualize better the availability modus: "open source", "FI-PPP", ... - Different table comuns/names/content? - ... Best, /Thorsten From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Montag, 25. November 2013 17:42 To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; Juanjo Hierro Subject: [Fiware-wpl] extracting the catalog to a printed version - PoC Dear colleagues, This is for the discussion on how to make a "printable" version of the catalogue to be submitted either prior to the review or during the review: As first proof-point and just to emphasize that we might manage to compile this kind of information "within this week", I precompiled the "Terms and conditions" and the "overview" tab out of the current cataloge-system automatically. See attachment... There are obvious "problems" but as a PoC this works quite well and reuses the wiki as intermediary (I took for testing the apps wiki, but can have this everywhere...) - Images are not printed and not copied (e.g. Cloud Edge) - Layout can be improved - More fields might be relevant for extraction - Chapter level headings are missing (currently I ordered the list in relation to the chapters) Any comments appreciated. Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IPack.2.1 FI-WARE Catalog Content.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 316797 bytes Desc: IPack.2.1 FI-WARE Catalog Content.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IPack.2.1 FI-WARE Catalog Content.pdf Type: application/pdf Size: 1434991 bytes Desc: IPack.2.1 FI-WARE Catalog Content.pdf URL: