From jhierro at tid.es Mon Sep 3 10:24:52 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Sep 2012 10:24:52 +0200 Subject: [Fiware-wpl] Following Agile more rigorously Message-ID: <50446954.3070505@tid.es> Dear all, Once we have made the effort to clean up the backlog, we should catch-up and start applying Agile more rigorously. We at TID believe that some of the issues we have experienced regarding delay could have been early detected and fixed if we had follow-up Agile and planned Sprints more rigorously. Chapters should make an effort to start planning minor releases and Sprints starting beginning of September. We propose to apply a number of simplifications to the current approach, in order to make it lighter: * Leave the public Wiki only to document Epics and Features in the Backlog. Note that Testing Plans will be formulated over Features. * Drop some fields documenting Epics and Features. Candidates are: * Scope (always Generic Platform) * Relative Priority * Source (doesn't add value over stakeholders+owner) * Rationale (difficult to fill) * Version (Mapping of Features/Epics into releases should be captured on the Technical Roadmap. A field here would introduce risks of inconsistencies. If it were related to version of the contents of the entry, we would be adding complexity over the history that is already controlled by the wiki ... is strictly needed or was just nice to have ?) * Enabler (can be determined from the Id) * Keep User Stories documented only at the level of the trackers. Note, though, that this may require to add custom fields (e.g., description of how a user story will be tested), so that we would like to hear others' opinions. * Work items would remain also documented only at the level of the trackers. All Chapters should plan the Sprint of one month the week before. Due to the holidays, we will make an exception for this September so that Chapters have to have the planning ready by the end of this week. Planning should translate into: * A number of User Stories in the Backlog (tracker) become planned for development during the Sprint (they get assigned the corresponding Sprint Id) * A number of Work Items that are also planned to be carried out during the Sprint (either selected from list of work items pending in the backlog or identified as new during planning). Examples of work items are: * Work required in order to deal with refinement of a Feature into User Stories * Work required in order to deal with refinement of a Epic into Features (and maybe some work items) * Work to be done in the FI-WARE Testbed (e.g., deploying an update of some GE) * Work to be done in the FI-WARE Catalogue * Contributions to development of deliverables in WP2 (e.g., Architecture Description, Technical Roadmap, Open Specifications, etc), WP10, WP11 or WP12 * Participation in some workshop with some UC project * Solution of some ticket(s) issued in the FI-WARE Global Support tracker * Peer Reviews * etc Work items may typically be identified and planned by the WPL. It is expected that work items may help to capture and follow-up Action Points identified within a WP. Costs reports will be compared against activities planned during Sprints. If a partner gets not assigned a User Story or a Work Item during a Sprint, it means that it is not working on anything, therefore cannot justify any cost. I hope to be able to review this proposal during our joint WPLs/WPAs follow-up confcall this afternoon. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Sep 3 10:37:09 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Sep 2012 10:37:09 +0200 Subject: [Fiware-wpl] Reminder and shared minutes of our joint WPLs/WPAs follow-up confcall Message-ID: <50446C35.8@tid.es> Hi all, This is, first of all, a reminder of the joint WPLs/WPAs follow-up confcall that we are going to have starting at 15:00pm today. Please note that today our regular confcall takes place in a different time slot. The shared minutes can be located at: https://docs.google.com/document/d/1p8IF7M1pMzg9Kppal_uzvxZkxGQwY1vrwnjKdjtf0G0/edit Please review them because there are a number of points where your input will be required. It would be great if you can provide that input prior the meeting so that we can make it more effective. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Sep 3 15:17:01 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 03 Sep 2012 15:17:01 +0200 Subject: [Fiware-wpl] Fwd: Re: Availability of the FI-WARE Testbed - Second step: announcement the third set of gei In-Reply-To: References: Message-ID: <5044ADCD.1080804@tid.es> FYI ------------- 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 -------- Original Message -------- Subject: Re: Availability of the FI-WARE Testbed - Second step: announcement the third set of gei Date: Mon, 3 Sep 2012 13:54:39 +0200 From: stefano de panfilis To: ab at fi-ppp.eu , all at fi-ppp.eu CC: Juanjo Hierro , Matteo Melideo , dear all, CloudProxi is, and was since some weeks ago, available as well. ciao, stefano 2012/9/3 stefano de panfilis > Dear members of the FI-PPP and particularly of the Use Case projects, i'm glad to announce the availability of a third set of generic enabler implementations (gei). they are: * Domain Compressed Video Analysis (former Multimedia Analysis) * Light Semantic Compositor Editor * Things Management * Identity Management (two different implementations) the above geis are in addition to the already available: Data Chapter * Complex Event Processing (CEP) * BigData Analysis * Location Server * Semantic Application Support Apps Chapter * Service Description Repository * Marketplace * Mashup Factory * WireCloud * Mediator Security Chapter * Data Handling * DB Anonymizer as already announced in a previoius emails by browsing the fi-ware catalogue (http://fi-ware.cloud.labs.ericsson.net/) you'll get all the info on how to acces them, how to use them, and also their specifications. of course the access and use of such implelemtations is restricted to use case projects only. in order to get access you (i.e. ONLY the person member of the fi-ppp ab to avoid confusion and thousands of email circulating ...) have to answer to this email indicating to my colleagues henar and miguel (please keep also me in the loop) the ip address(es) from where you'll use to access the gei(s). in return you'll receive from henar the green ligth to use the ge(s) you are interested in. this procedure not only will protect the gei owners, but also will allow us to make ready the machines according to the requested gei usage. if you find any problem in using the gei you have not to contact henar or miguel or me, but you have to contact directly the person responsible for the specific gei as indicated in the fi-ware catalogue relevant page (normally on the rigth side of each page concerning the gei). if needed, a proper ticket should be issued. as said earlier in this is the third set of geis, but certainly not the last one! please stay tuned as in the very next days several other geis will be made available! i hope you will enjoy ciao, stefano [https://mail.google.com/mail/u/0/images/cleardot.gif] -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 matteo.melideo at eng.it Tue Sep 4 09:46:59 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 04 Sep 2012 09:46:59 +0200 Subject: [Fiware-wpl] *** TO BE READ *** About the catalogue Message-ID: <5045B1F3.7070808@eng.it> Dear All, as requested by Juanjo I updated the catalogue status by making public only the GEs currently installed on the Testbed and, as Testbed leaders told me, I used the tracker as reference guide to do this. Please check if I did it correctly as unfortunately, in most cases, the names in the tracker or wiki are different from those into the catalogue ... I am personally wondering why!!!! @Apps Chapter: I could not find in the catalogue the GEs referring to CompositionExecutionDT and CompositionExecutionUPM. Please double check. @Data Chapter: I left the GE named Compressed Domain Video Analysis in the catalogue guessing it refers to FIWARE.Testbed.Data.MultimediaAnalysis.R1. Is it correct? @IoT Chapter: please check is the GEs published on the catalogue is the correct one and keep the names aligned. All the other GEs not any more public are, however, available for the owners for editing. Thanks and regards Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Tue Sep 4 16:23:07 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Sep 2012 16:23:07 +0200 Subject: [Fiware-wpl] *** TO BE READ *** About the catalogue In-Reply-To: <5045B1F3.7070808@eng.it> References: <5045B1F3.7070808@eng.it> Message-ID: <50460ECB.9000206@tid.es> Hi Matteo, Please confirm that the list of GEs you consider matches the list of those in the shared spreadsheet with UC projects marked in dark green: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 Those are the ones that have been announced to UC projects as available on the FI-WARE Testbed. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 04/09/12 09:46, Matteo Melideo wrote: Dear All, as requested by Juanjo I updated the catalogue status by making public only the GEs currently installed on the Testbed and, as Testbed leaders told me, I used the tracker as reference guide to do this. Please check if I did it correctly as unfortunately, in most cases, the names in the tracker or wiki are different from those into the catalogue ... I am personally wondering why!!!! @Apps Chapter: I could not find in the catalogue the GEs referring to CompositionExecutionDT and CompositionExecutionUPM. Please double check. @Data Chapter: I left the GE named Compressed Domain Video Analysis in the catalogue guessing it refers to FIWARE.Testbed.Data.MultimediaAnalysis.R1. Is it correct? @IoT Chapter: please check is the GEs published on the catalogue is the correct one and keep the names aligned. All the other GEs not any more public are, however, available for the owners for editing. Thanks and regards Matteo _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://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 matteo.melideo at eng.it Tue Sep 4 16:40:19 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 04 Sep 2012 16:40:19 +0200 Subject: [Fiware-wpl] *** TO BE READ *** About the catalogue In-Reply-To: <50460ECB.9000206@tid.es> References: <5045B1F3.7070808@eng.it> <50460ECB.9000206@tid.es> Message-ID: <504612D3.5000501@eng.it> Hi Juanjo, I double checked twice but just in case I asked also the WPL to review. Regards M. Il 04/09/2012 16:23, Juanjo Hierro ha scritto: > Hi Matteo, > > Please confirm that the list of GEs you consider matches the list of > those in the shared spreadsheet with UC projects marked in dark green: > > https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 > > Those are the ones that have been announced to UC projects as > available on the FI-WARE Testbed. > > Cheers, > > -- Juanjo > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > On 04/09/12 09:46, Matteo Melideo wrote: >> Dear All, >> as requested by Juanjo I updated the catalogue status by making >> public only the GEs currently installed on the Testbed and, as >> Testbed leaders told me, I used the tracker as reference guide to do >> this. >> Please check if I did it correctly as unfortunately, in most cases, >> the names in the tracker or wiki are different from those into the >> catalogue ... I am personally wondering why!!!! >> >> @Apps Chapter: I could not find in the catalogue the GEs referring to >> CompositionExecutionDT and CompositionExecutionUPM. Please double check. >> >> @Data Chapter: I left the GE named Compressed Domain Video Analysis >> in the catalogue guessing it refers to >> FIWARE.Testbed.Data.MultimediaAnalysis.R1. Is it correct? >> >> @IoT Chapter: please check is the GEs published on the catalogue is >> the correct one and keep the names aligned. >> >> >> All the other GEs not any more public are, however, available for the >> owners for editing. >> >> >> Thanks and regards >> >> Matteo >> >> >> >> >> >> _______________________________________________ >> Fiware-wpl mailing list >> Fiware-wpl at lists.fi-ware.eu >> http://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 > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Wed Sep 5 11:51:24 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Sep 2012 11:51:24 +0200 Subject: [Fiware-wpl] Second and third peer reviews of FI-WARE Architecture Description and Open Specifications Message-ID: <5047209C.7060803@tid.es> Hi all, Following the agreement during our last joint WPLs/WPAs follow-up confcall, we will carry out a second and a last third peer-review of the Architecture and Open Specifications during September and October, respectively. We will start this second peer-review starting on September 10th, just to make sure that the first peer-review gets completed and the peer-reviewers can rely on already revised contents. Please, make sure that you have completed the first review by end of this week. We will also try to carry out this reviews more formally, as to make sure that all peer-reviews take into consideration the same points. For this reason, a form that has to be completed by peer-reviewers is provided at: https://forge.fi-ware.eu/docman/view.php/7/1262/FI-WARE+Peer-Review+Form+12-09-05.docx Its usage is therefore mandatory. Since we will not start running this peer review until beginning of next week, don't hesitate to propose any improvement or ask any doubt regarding the peer-review forms in the meantime. Do not forget to incorporate these peer-reviews as part of the Sprint planning that, regarding September, you have been asked to complete the planning of the September Sprint by end of this week (September 7th, EOB). Now regarding planning of the second peer-review, the proposed plan is as follows: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps Leaders of reviewing chapters are empowered to designate those members of their teams that will be involved in the peer-reviews and how peer-review tasks will be assigned to them. As we commented the first time, we encourage that the peer-review of FI-WARE GE Open Specifications parts are carried out by members of the team that have the profile of developers. This second review should finish by end of this month, executing the following calendar: * Personalization of forms per chapter (now until September 10th): we suggest that you take the form and particularize it to peer-review of the chapter that was assigned to your chapter: * add sections corresponding to each GE * personalize section 1.2.6 on handling comments from the project reviewers, so that you include there the excerpts from the project reviewers you believe it is applicable to check * Start of review: September 10th (please plan things, i.e., identify assignments and distribute work after personalization of the peer-review forms, before this date so work starts effectively on September 10th) * Reviewing chapter sends comments to leader of reviewed chapter, following the attached forms, with cc to me: September 20, 09:00am * Each chapters implement recommended changes: September 30 17:00 CET. I know that the calendar is tough, but it is also true that we have to work hard to recover. I count on your commitment to get this done. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Wed Sep 5 17:36:14 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 05 Sep 2012 15:36:14 +0000 Subject: [Fiware-wpl] OUTSMART / FI-WARE synchronization virtual meeting (call and webex details) References: <31973_1346407227_50408B3A_31973_4316_3_1ba7bdfb-9c63-4b64-9b61-c87489d36e05@PEXCVZYH01.corporate.adroot.infra.ftgroup> Message-ID: <024179B2-70A6-47AC-B3C4-B68AE4F0725A@tid.es> Dear Colleagues, Find enclosed below the details to connect tomorrow. Please do forward to those that will be involved. Looking to the googledoc I can see the Fi-WARE testbed attendee field is empty (perhaps got deleted accidentally by someone?) and there is no proposal for a Cloud chapter attendee. Thanks, -- Inicio del mensaje reenviado: De: > Fecha: 31 de agosto de 2012 12:00:22 GMT+02:00 Para: Antonio Filograna > Cc: "BARRELLA, PIERO (PIERO)" >, "Mathieu Hutschemaekers" >, Martien Huysmans >, "torsten.leidig at sap.com" >, "jsoriano at fi.upm.es" >, "rfernandez at fi.upm.es" >, "davide.dallecarbonare at eng.it" >, "uwe.riss at sap.com" >, "h.abangar at surrey.ac.uk" >, "Thomas.Riegel at siemens.com" >, "NAGELLEN Thierry RD-BIZZ" >, ARTUSIO Laurent RD-BIZZ >, "guysh at il.ibm.com" >, "tali at il.ibm.com" >, "boris.moltchanov at telecomitalia.it" >, "pierangelo.garino at telecomitalia.it" >, "p.amon at siemens.com" >, MADHUSUDAN Giyyarpuram RD-TECH >, "levent.gurgen at cea.fr" >, "s.meissner at surrey.ac.uk" >, "boris.pokric at gmail.com" >, "mdohler at worldsensing.com" >, "lydie.desperben at coronis.com" >, "alexey.baraev at create-net.org" >, "jcuesta at tlmat.unican.es" >, "calin.curescu at Ericsson.com" >, "d.ghataoura at surrey.ac.uk" >, "maarten.los at atosresearch.eu" >, "andriy.panchenko at uni.lu" >, "jerome.francois at uni.lu" >, "pascal.bisson at thalesgroup.com" >, "daniel.gidoin at thalesgroup.com" >, "mirko.presser at alexandra.dk" >, "alhj at tid.es" >, stefano de panfilis >, "GALLISSOT Mathieu 234683" >, "Hans.Einsiedler at telekom.de" >, Roberto Di Bernardo >, GRATTARD Gilles RD-BIZZ >, "k.moessner at surrey.ac.uk" >, "ralli at tid.es" >, "jhierro at tid.es" >, "Goldacker, Gabriele" > Asunto: final call and webex details: RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Dear all, Could you please confirmed before today 4:00PM your participation to this meeting, by adding your name (with a mention webex, in case you?ll participate remotely) on this shared document: https://docs.google.com/spreadsheet/ccc?key=0AobKeqMq4hM-dFJFdWtIWEJ0Vk95ckFLQkk5U28zLUE#gid=8 I?ll book WiFi connection for those registered at that time. Juanjo, could you please forward my message to FIWARE chapter leaders and architects for them to register or appoint a representative of their chapter has you?ve agreed at our last FI-PPP Architecture Board meeting. Thank you very much. Here are the WebEx identifiers for connecting remotely ------------------------------------------------------- Meeting information ------------------------------------------------------- Topic: OUTSMART -FIWARE synchronisation Date: Thursday 6 September 2012 Time: 8:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 850 195 Meeting Password: Outsmart123 ------------------------------------------------------- To start or join the online meeting ------------------------------------------------------- Go to https://cea.webex.com/cea-en/j.php?ED=222415942&UID=257057&PW=NMDNkMWFiNjdi&RT=NyMyMw%3D%3D ------------------------------------------------------- Audio conference information ------------------------------------------------------- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. France Num?ro local: +33 17091 8646 Access code:709 850 195 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://cea.webex.com/cea-en/mc 2. On the left navigation bar, click "Support". To check whether you have the appropriate players installed for UCF (Universal Communications Format) rich media files, go to https://cea.webex.com/cea-en/systemdiagnosis.php. http://www.webex.com Thank you to Levent for setting up this WebEx session. Best regards, Fano ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Sep 5 21:39:41 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Sep 2012 21:39:41 +0200 Subject: [Fiware-wpl] [Fiware-wpa] OUTSMART / FI-WARE synchronization virtual meeting (call and webex details) In-Reply-To: <024179B2-70A6-47AC-B3C4-B68AE4F0725A@tid.es> References: <31973_1346407227_50408B3A_31973_4316_3_1ba7bdfb-9c63-4b64-9b61-c87489d36e05@PEXCVZYH01.corporate.adroot.infra.ftgroup> <024179B2-70A6-47AC-B3C4-B68AE4F0725A@tid.es> Message-ID: <5047AA7D.3060705@tid.es> Don't miss this important background info: * OUTSMART D2.3 Functional Architecture Deliverable: https://forge.fi-ware.eu/docman/view.php/7/1204/OUTSMART-D2.3-Final.pdf Cheers, ------------- 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 On 05/09/12 17:36, CARLOS RALLI UCENDO wrote: Dear Colleagues, Find enclosed below the details to connect tomorrow. Please do forward to those that will be involved. Looking to the googledoc I can see the Fi-WARE testbed attendee field is empty (perhaps got deleted accidentally by someone?) and there is no proposal for a Cloud chapter attendee. Thanks, -- Inicio del mensaje reenviado: De: > Fecha: 31 de agosto de 2012 12:00:22 GMT+02:00 Para: Antonio Filograna > Cc: "BARRELLA, PIERO (PIERO)" >, "Mathieu Hutschemaekers" >, Martien Huysmans >, "torsten.leidig at sap.com" >, "jsoriano at fi.upm.es" >, "rfernandez at fi.upm.es" >, "davide.dallecarbonare at eng.it" >, "uwe.riss at sap.com" >, "h.abangar at surrey.ac.uk" >, "Thomas.Riegel at siemens.com" >, "NAGELLEN Thierry RD-BIZZ" >, ARTUSIO Laurent RD-BIZZ >, "guysh at il.ibm.com" >, "tali at il.ibm.com" >, "boris.moltchanov at telecomitalia.it" >, "pierangelo.garino at telecomitalia.it" >, "p.amon at siemens.com" >, MADHUSUDAN Giyyarpuram RD-TECH >, "levent.gurgen at cea.fr" >, "s.meissner at surrey.ac.uk" >, "boris.pokric at gmail.com" >, "mdohler at worldsensing.com" >, "lydie.desperben at coronis.com" >, "alexey.baraev at create-net.org" >, "jcuesta at tlmat.unican.es" >, "calin.curescu at Ericsson.com" >, "d.ghataoura at surrey.ac.uk" >, "maarten.los at atosresearch.eu" >, "andriy.panchenko at uni.lu" >, "jerome.francois at uni.lu" >, "pascal.bisson at thalesgroup.com" >, "daniel.gidoin at thalesgroup.com" >, "mirko.presser at alexandra.dk" >, "alhj at tid.es" >, stefano de panfilis >, "GALLISSOT Mathieu 234683" >, "Hans.Einsiedler at telekom.de" >, Roberto Di Bernardo >, GRATTARD Gilles RD-BIZZ >, "k.moessner at surrey.ac.uk" >, "ralli at tid.es" >, "jhierro at tid.es" >, "Goldacker, Gabriele" > Asunto: final call and webex details: RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Dear all, Could you please confirmed before today 4:00PM your participation to this meeting, by adding your name (with a mention webex, in case you'll participate remotely) on this shared document: https://docs.google.com/spreadsheet/ccc?key=0AobKeqMq4hM-dFJFdWtIWEJ0Vk95ckFLQkk5U28zLUE#gid=8 I'll book WiFi connection for those registered at that time. Juanjo, could you please forward my message to FIWARE chapter leaders and architects for them to register or appoint a representative of their chapter has you've agreed at our last FI-PPP Architecture Board meeting. Thank you very much. Here are the WebEx identifiers for connecting remotely ------------------------------------------------------- Meeting information ------------------------------------------------------- Topic: OUTSMART -FIWARE synchronisation Date: Thursday 6 September 2012 Time: 8:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 850 195 Meeting Password: Outsmart123 ------------------------------------------------------- To start or join the online meeting ------------------------------------------------------- Go to https://cea.webex.com/cea-en/j.php?ED=222415942&UID=257057&PW=NMDNkMWFiNjdi&RT=NyMyMw%3D%3D ------------------------------------------------------- Audio conference information ------------------------------------------------------- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. France Num?ro local: +33 17091 8646 Access code:709 850 195 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://cea.webex.com/cea-en/mc 2. On the left navigation bar, click "Support". To check whether you have the appropriate players installed for UCF (Universal Communications Format) rich media files, go to https://cea.webex.com/cea-en/systemdiagnosis.php. http://www.webex.com Thank you to Levent for setting up this WebEx session. Best regards, Fano ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Sep 5 22:53:23 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 05 Sep 2012 22:53:23 +0200 Subject: [Fiware-wpl] Re-schedule of next joint WPL/WPA follow-up confcall Message-ID: <5047BBC3.5080405@tid.es> Hi all, Again unfortunately I won't be able to attend our next joint WPL/WPA follow-up confcall on September 10th, starting at 11:00am. I would need to re-schedule it to start at 15:00. I will send the invitation right after this email. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Wed Sep 5 22:52:57 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 05 Sep 2012 20:52:57 +0000 Subject: [Fiware-wpl] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <936DECD07EB54B4BAA44E7B823EC89411FA9C2D7@EX10-MB2-MAD.hi.inet> When: Monday, September 10, 2012 3:00 PM-5:00 PM. (UTC+01:00) Sarajevo, Skopje, Warsaw, Zagreb *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3393 bytes Desc: not available URL: From jhierro at tid.es Thu Sep 6 18:53:37 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 06 Sep 2012 18:53:37 +0200 Subject: [Fiware-wpl] Fwd: Re-Submission of deliverable D2.4.1 FI-WARE Technical Roadmap In-Reply-To: <5048D487.8090606@tid.es> References: <5048D487.8090606@tid.es> Message-ID: <5048D511.7090203@tid.es> FYI. I hope that the reviewers and our PO will value the great effort made and also the attempt to generate pretty-printable versions of this deliverable. Definitively, I believe that rejection of the FI-WARE Technical Roadmap deliverable should be solved. Let's focus now on the FI-WARE Architecture Description and the Open Specifications. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Re-Submission of deliverable D2.4.1 FI-WARE Technical Roadmap Date: Thu, 06 Sep 2012 18:51:19 +0200 From: Juanjo Hierro To: 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 , Jose Jimenez , "jhierro >> \"Juan J. Hierro\"" Dear Arian, dear reviewers, This is the official submission of the following deliverable: * D2.4.1 FI-WARE Technical Roadmap The deliverable is publicly available in .pdf and .docx format: * .docx format: https://forge.fi-ware.eu/docman/view.php/7/1287/D2.4.a+FI-WARE+Technical+Roadmap+resubmission.docx * .pdf format: https://forge.fi-ware.eu/docman/view.php/7/1288/D2.4.a+FI-WARE+Technical+Roadmap+resubmission.pdf The .docx version is provided because it would allow you to navigate to the FI-WARE FusionForge from the document. This will allow you to see the description of a given Feature of a FI-WARE GE, for example. Unfortunately, we haven't been able to generate the .pdf file with links. The deliverable is, of course, available on the FI-WARE wiki and keep there constantly updated for reference. Availability of the FI-WARE Technical Roadmap was announced to the UC projects on August 29th (during the virtual meeting of the FI-PPP AB planned that date) but we haven't been able to generate the .docx and .pdf files until now. Please note that .docx or .pdf versions of the FI-WARE Technical Roadmap are pure snapshots of what is published on the FI-WARE wiki, which is the ultimate valid reference. Following is an explanation on how we believe that the re-submitted deliverable addresses the comments that were made during the review in month 9: * The re-submitted version of the deliverable incorporate tables that clearly specify what Epics/Features will be covered in each Release by each of the FI-WARE GEs. Mapping between Releases and Epics/Features defined in the FI-WARE Backlog has been documented in detail for this purpose. By reviewing the description of each Epic/Feature in the Backlog, a potential reader will get enough details about what will be offered by each FI-WARE GE when. This in contrast with the original submission of the deliverable where functionalities/features supported were described in a very high-level. * The provided description of Epics/Features is enough detailed in our opinion and it should allow the Use Case projects to understand the FI-WARE propositions correctly, avoiding wrong expectations and further difficulties in the collaboration. * Several topics have been identified during interaction with UC projects that were not planned in FI-WARE. Those topics are being addressed through the 1st and 2nd Open Call so far. Following an Agile methodology, Epics have been defined for each of those topics. However, no partners have yet joined FI-WARE as a result of the 1st Open Call, so it is still too premature to specify what features linked to topics of the 1st Open Call will be delivered by what FI-WARE GE and when. Current plans are that submitters of winning proposals to the 1st Open Call will join beginning of October 2012. Detailed planning of Features to be developed will not be incorporated into the Technical Roadmap until release D.2.4.2 by end of January 2013. Nevertheless, Deliverable D.2.4.1 comprises references to the Epics linked to topics in the 1st Open Call since they will be subject to analysis and target for development in the 2nd release. * We definitively believe that this Technical Roadmap indicates the delivery schedule for precise Generic Enablers, which have been described in terms of the whole set of features they will provide. * A finer grained estimate of the delivery date for each feature and FI-WARE GE is provided compared to the original submission of the deliverable, but to the extend it is possible taken into account that we are following an Agile approach. We kindly remind that planning what are going to be the features covered in all releases projected in the future at this point would go against Agile as methodology. In summary, we believe that this deliverable brings information about the FI-WARE Technical Roadmap that goes well beyond the amount of information that is typically published by any Platform provider when it publicly announces its roadmap/plan to the market. As per today, UC projects has not yet started to use the FI-WARE GEs on the FI-WARE Testbed. We expect this will bring the opportunity to capture detailed requirements about functionality they will require that in turn will map into Epics/Features to be incorporated in each FI-WARE GE Backlog. However, this process has not started yet. So far, UC projects have been only able to provide very high-level requirements with respect to FI-WARE GEs under development and those requirements neither contradicted nor added functionality that is described in the currently identified set of Epics/Features. We would like to remind that functionality that is not enough detailed cannot be given any priority according to the Agile methodology. Therefore, asking for prioritization of requirements from UC projects is premature at this time. Nevertheless, we are working with them so that they can list themselves as stakeholders of specific Epics/Features and this may help us to prioritize development during the second Release of FI-WARE. They have been requested to do so by means of editing the "stakeholders" field of Epics/Features in the FI-WARE Backlog. 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 pascal.bisson at thalesgroup.com Fri Sep 7 10:02:06 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 7 Sep 2012 10:02:06 +0200 Subject: [Fiware-wpl] Re-schedule of next joint WPL/WPA follow-up confcall In-Reply-To: <5047BBC3.5080405@tid.es> References: <5047BBC3.5080405@tid.es> Message-ID: <19685_1347004930_5049AA02_19685_18042_1_21343ffe-0a19-416b-8eb0-aa10be4bb327@THSONEA01HUB06P.one.grp> Dear Juanjo, Let me inform you that postponing our Weekly WPL/WPA audio conf to next Monday at the time you propose is not that convenient to also me due to other appointments I have in the late afternoon. As such not sure I could make it (except perhaps for one hour). Apologize for the inconvenience. Best 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 Juanjo Hierro Envoy??: mercredi 5 septembre 2012 22:53 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] Re-schedule of next joint WPL/WPA follow-up confcall Hi all, Again unfortunately I won't be able to attend our next joint WPL/WPA follow-up confcall on September 10th, starting at 11:00am. I would need to re-schedule it to start at 15:00. I will send the invitation right after this email. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From thierry.nagellen at orange.com Mon Sep 10 14:04:56 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 10 Sep 2012 12:04:56 +0000 Subject: [Fiware-wpl] Alert: status UC projects phase 1 and preparation phase 2 Message-ID: <10907_1347278697_504DD769_10907_887_3_976A65C5A08ADF49B9A8523F7F81925C04F7C7@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Some information from current UC projects and potential proposals for phase 2, based of course on the projects where Orange is partner and some additional information. Phase 1: it seems that for many Proof of Concept developments or prototype in phase 1, despite the good feedback we had during the Architect Weeks, many UC projects are now working with their own enablers, especially because the Fi-Ware timeline is not align with what they have to deliver. This point could be explained to the Commission but based on the last Review Report the Commisison asks us to state what are the expected GEs the UC projects will use, so it is a critical point for further developments. Phase 2 At least 7 proposals are some follow-up of existing UC projects... and some other proposals are also expected! This is clearly not in line with the spirit of the PPP FI and as big companies which have pushed this program we should have the same objective to fulfill program requirements. We had this comment from the Commission several times that they expect some different projects, pushing us to merge some of them or to introduce new vertical areas especially to demonstrate that FIWARE WILL BE GENERIC ENOUGH! As all consortiums are working separately we will have a stronger competition for phase 2 and we will miss the objective to demonstrate that FI-Ware GEs are generic. The projects should propose vertical approach with their own standards and so on. We have here a high risk to fail at the program level. Conclusion I would ask all of you to check what your teams have planned in several proposals, first to reduce the competition (in the best way: merging some proposals) and second to check what are the Fi-Ware GEs implementation they have planned because this part is very obscure today. Following at least 4 UC projects for phase 2 and 6 weeks before the deadline there are few details on Fi-Ware and GEs and how they would be implemented in the phase 2. >From Orange side we are ready to withdraw from some proposals if they are not following PPP FI spirit and will not support a strong approach regarding Fi-Ware GEs implementation or use. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Sep 10 14:56:55 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 10 Sep 2012 14:56:55 +0200 Subject: [Fiware-wpl] Shared minutes for the joint WPLs/WPAs confcall Message-ID: <504DE397.4050000@tid.es> Hi, As always, we will use shared minutes. You can locate them at: https://docs.google.com/document/d/1Yk1jqEa87aavZl3VetyBG3kIscQaPUHuA7vBXwnsj_A/edit# Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From ralli at tid.es Mon Sep 10 14:58:21 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 10 Sep 2012 12:58:21 +0000 Subject: [Fiware-wpl] Minutes of last week meeting with OUTSMART References: Message-ID: FYI Inicio del mensaje reenviado: De: "BARRELLA, PIERO (PIERO)" > Fecha: 10 de septiembre de 2012 11:06:02 GMT+02:00 Para: "fano.ramparany at orange.com" > Cc: Juanjo Hierro >, 'Martien Huysmans' >, "'jsoriano at fi.upm.es'" >, "'rfernandez at fi.upm.es'" >, "'davide.dallecarbonare at eng.it'" >, "'uwe.riss at sap.com'" >, "'h.abangar at surrey.ac.uk'" >, "'antonio.filograna at eng.it'" >, "'Thomas.Riegel at siemens.com'" >, ARTUSIO Laurent RD-BIZZ >, "'guysh at il.ibm.com'" >, "'tali at il.ibm.com'" >, "'pierangelo.garino at telecomitalia.it'" >, "'p.amon at siemens.com'" >, "'boris.pokric at gmail.com'" >, "'mdohler at worldsensing.com'" >, "'lydie.desperben at coronis.com'" >, "'alexey.baraev at create-net.org'" >, "'jcuesta at tlmat.unican.es'" >, "'calin.curescu at Ericsson.com'" >, "'d.ghataoura at surrey.ac.uk'" >, "'maarten.los at atosresearch.eu'" >, "'andriy.panchenko at uni.lu'" >, "'daniel.gidoin at thalesgroup.com'" >, "'alhj at tid.es'" >, 'stefano de panfilis' >, 'GALLISSOT Mathieu 234683' >, 'Roberto Di Bernardo' >, "'ralli at tid.es'" >, "Hans.Einsiedler at telekom.de" >, "henk.heijnen at technicolor.com" > Asunto: R: Draft of the OUTSMART software architecture review meeting minutes, for review Hi Fano. In attachment You can find the subjected meeting minute with some comments of mine. Regards. Piero -----Messaggio originale----- Da: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Inviato: venerd? 7 settembre 2012 18.31 A: Juanjo Hierro; 'Martien Huysmans'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; BARRELLA, PIERO (PIERO); 'Thomas.Riegel at siemens.com'; ARTUSIO Laurent RD-BIZZ; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'pierangelo.garino at telecomitalia.it'; 'p.amon at siemens.com'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; 'andriy.panchenko at uni.lu'; 'daniel.gidoin at thalesgroup.com'; 'alhj at tid.es'; 'stefano de panfilis'; 'GALLISSOT Mathieu 234683'; 'Roberto Di Bernardo'; 'ralli at tid.es'; Hans.Einsiedler at telekom.de; henk.heijnen at technicolor.com Oggetto: Draft of the OUTSMART software architecture review meeting minutes, for review Dear all, This mail is intended to participants of the OUTSMART architecture review meeting that held yesterday, for them to review the draft minutes. As some connected remotely and anonymously I'm not sure the attendants list is accurate. https://docs.google.com/document/d/1Y-ARxhADirv7UeVBg7reRlR1bLHzuXqLJZ1Ll9huO6k/edit Could you please enter your comment directly on the online document on next Monday the latest please so that I can finalize it on Tuesday. Juanjo, could you please forward this message to Jozsef Varga from NSN, as I don't have his email address. Thank you in advance and have a nice WE, Fano -----Message d'origine----- De : RAMPARANY Fano RD-TECH Envoy? : vendredi 7 septembre 2012 14:35 ? : 'Juanjo Hierro' Cc : 'Mathieu Hutschemaekers'; 'Martien Huysmans'; 'torsten.leidig at sap.com'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; 'piero.barrella at alcatel-lucent.com'; 'Denes.Bisztray at nsn.com'; 'Lorant.Farkas at nsn.com'; 'Thomas.Riegel at siemens.com'; NAGELLEN Thierry RD-BIZZ; ARTUSIO Laurent RD-BIZZ; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'boris.moltchanov at telecomitalia.it'; 'pierangelo.garino at telecomitalia.it'; 'randradas at libresoft.es'; 'p.amon at siemens.com'; MADHUSUDAN Giyyarpuram RD-TECH; 'levent.gurgen at cea.fr'; 's.meissner at surrey.ac.uk'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; 'andriy.panchenko at uni.lu'; 'jerome.francois at uni.lu'; 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com'; 'mirko.presser at alexandra.dk'; 'alhj at tid.es'; 'stefano de panfilis'; 'GALLISSOT Mathieu 234683'; 'Roberto Di Bernardo'; GRATTARD Gilles RD-BIZZ; 'k.moessner at surrey.ac.uk'; 'ralli at tid.es' Objet : RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Hi Juanjo and all, When Webex shut down (I think the alloted time was elapsed), the meeting was already over. We were the holding a project internal discussion about the PoC implementation task scheduling initiated by Antonio. This discussion was offtopic, but I would like to apologize to those who were participating remotely to this discussion. The AP resulting from the discussion is that I will check the milestones and deliverables of this task (T6.3). Thank again for your participation to the meeting and more generally for your involvement in the synchronization process. I hope to issue the minutes before the WE. Best regards, Fano -----Message d'origine----- De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : vendredi 7 septembre 2012 06:43 ? : RAMPARANY Fano RD-TECH Cc : 'Mathieu Hutschemaekers'; 'Martien Huysmans'; 'torsten.leidig at sap.com'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; 'piero.barrella at alcatel-lucent.com'; 'Denes.Bisztray at nsn.com'; 'Lorant.Farkas at nsn.com'; 'Thomas.Riegel at siemens.com'; NAGELLEN Thierry RD-BIZZ; ARTUSIO Laurent RD-BIZZ; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'boris.moltchanov at telecomitalia.it'; 'pierangelo.garino at telecomitalia.it'; 'randradas at libresoft.es'; 'p.amon at siemens.com'; MADHUSUDAN Giyyarpuram RD-TECH; 'levent.gurgen at cea.fr'; 's.meissner at surrey.ac.uk'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; 'andriy.panchenko at uni.lu'; 'jerome.francois at uni.lu'; 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com'; 'mirko.presser at alexandra.dk'; 'alhj at tid.es'; 'stefano de panfilis'; 'GALLISSOT Mathieu 234683'; 'Roberto Di Bernardo'; GRATTARD Gilles RD-BIZZ; 'k.moessner at surrey.ac.uk'; 'ralli at tid.es'; jhierro >> "Juan J. Hierro" Objet : Re: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Hi, We were waiting for quite sometime after the communication was interrupted ... but didn't receive any message ... We also tried to connect again to the Webex several times but it still told us that the meeting had been cancelled ... Could someone summarize the last part of the meeting ? We got disconnected right after we had reviewed the second cluster system architecture I believe ... Anyways, I believe it was a quite fruitful meeting and I found that it worked pretty well despite most of us were connected via Webex. I almost didn't experience so much difference compared to being there f2f. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 06/09/12 17:04, Juanjo Hierro wrote: Hi, We have lost the connectivity here ... it says that the Webex meeting has been cancelled ... We'll wait for further news. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 06/09/12 09:21, fano.ramparany at orange.com wrote: -----Message d'origine----- De : RAMPARANY Fano RD-TECH Envoy? : vendredi 10 ao?t 2012 15:22 ? : RAMPARANY Fano RD-TECH; 'Mathieu Hutschemaekers'; 'Martien Huysmans'; 'torsten.leidig at sap.com'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; 'piero.barrella at alcatel-lucent.com'; 'Denes.Bisztray at nsn.com'; 'Lorant.Farkas at nsn.com'; 'Thomas.Riegel at siemens.com'; NAGELLEN Thierry RD-BIZZ; ARTUSIO Laurent RD-BIZZ; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'boris.moltchanov at telecomitalia.it'; 'pierangelo.garino at telecomitalia.it'; 'randradas at libresoft.es'; 'p.amon at siemens.com'; MADHUSUDAN Giyyarpuram RD-TECH; 'levent.gurgen at cea.fr'; 's.meissner at surrey.ac.uk'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; andriy.panchenko at uni.lu; 'jerome.francois at uni.lu'; 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com'; 'mirko.presser at alexandra.dk'; alhj at tid.es; stefano de panfilis; GALLISSOT Mathieu 234683; 'Roberto Di Bernardo'; 'jhierro at tid.es' Cc : GRATTARD Gilles RD-BIZZ; 'k.moessner at surrey.ac.uk'; 'ralli at tid.es' Objet : RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Hi, Thank you for those who answered. For this architecture review meeting, we are still missing representatives for - OUTSMART: Santander Cluster, Aahrus Cluster - FIWARE: IoT, Service, Security, Testbed Juanjo, it would be great if you could participate as you would represent all FIWARE chapters altogether, and I'd also like to remind that it is from your initial suggestion that we've organized this synchronization process, and for which you assured at the FI-PPP Architecture Board that FIWARE would be ready and happy to help in reviewing OUTSMART architecture. Thank you in advance for your collaboration. Fano -----Message d'origine----- De : RAMPARANY Fano RD-TECH Envoy? : mercredi 8 ao?t 2012 15:57 Objet : RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Dear all, This is a reminder of a call for participation to the OUTSMART architecture review. Thank you for those of you who already confirmed. It would be great if: - from the OUTSMART side at least one person per technical WP and selected UC (Santander/Birmingham/Aarhus) could participate - from the FIWARE side if Juanjo or a team from FIWARE which is collectively knowledgeable about the CP ambit could participate, as well as Stefano or somebody representing the testbed. You can get here: https://docs.google.com/spreadsheet/ccc?key=0AobKeqMq4hM-dFJFdWtIWEJ0Vk95ckFLQkk5U28zLUE#gid=8 the list of confirmed participant, a link to the provisional agenda (please suggest additional items you think are missing) as well as some logistic info. Tomorrow afternoon, I'll pinpoint unrepresented parties with respect to participation. Best regards, Fano -----Message d'origine----- De : RAMPARANY Fano RD-TECH Envoy? : lundi 6 ao?t 2012 12:03 ? : RAMPARANY Fano RD-TECH; 'Mathieu Hutschemaekers'; 'Martien Huysmans'; 'torsten.leidig at sap.com'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; 'piero.barrella at alcatel-lucent.com'; 'Denes.Bisztray at nsn.com'; 'Lorant.Farkas at nsn.com'; 'Thomas.Riegel at siemens.com'; NAGELLEN Thierry RD-BIZZ; ARTUSIO Laurent RD-BIZZ; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'boris.moltchanov at telecomitalia.it'; 'pierangelo.garino at telecomitalia.it'; 'randradas at libresoft.es'; 'p.amon at siemens.com'; MADHUSUDAN Giyyarpuram RD-TECH; 'levent.gurgen at cea.fr'; 's.meissner at surrey.ac.uk'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; andriy.panchenko at uni.lu; 'jerome.francois at uni.lu'; 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com'; 'mirko.presser at alexandra.dk'; alhj at tid.es; stefano de panfilis; GALLISSOT Mathieu 234683 Cc : GRATTARD Gilles RD-BIZZ; 'k.moessner at surrey.ac.uk'; 'ralli at tid.es'; 'jhierro at tid.es' Objet : RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Dear all, Thank you to those who filled the doodle. The best date for our OUTSMART architecture review is Thursday, Sept. 6th. In order to minimize cost and optimize time, I propose a full day meeting (9AM-6PM) in Orange Labs Paris. I also remind you that we've agreed to complete the technical discussions on "OUTSMART components / FIWARE GEs alignment" by the end of this month and that the conclusion of these discussions should by then, be reported in the following document: https://docs.google.com/document/d/1MKyI1BYAhiTaXSmL0ZWTWQWWEThH-vDiu8NdDNf1lCs/edit If you are the contact person for a OUTSMART component (thus you're tagged in orange in the sheet "Dedicated Teams" of the following document: https://docs.google.com/spreadsheet/ccc?key=0AobKeqMq4hM-dFJFdWtIWEJ0Vk95ckFLQkk5U28zLUE#gid=2 ), you are responsible for organizing the discussion with the FIWARE team and the dedicated team, and responsible for reporting in the document mentioned above. It is important to stick to these dates, so that we can finalize the architecture before the review meeting. Could you please confirm your participation to this meeting as soon as possible, preferably before Aug. 10th (this Friday), so that I can book the meeting room accordingly. Thank you in advance, Fano -----Message d'origine----- De : RAMPARANY Fano RD-TECH Envoy? : vendredi 20 juillet 2012 19:07 ? : 'Mathieu Hutschemaekers'; 'Martien Huysmans'; 'torsten.leidig at sap.com'; 'jsoriano at fi.upm.es'; 'rfernandez at fi.upm.es'; 'davide.dallecarbonare at eng.it'; 'uwe.riss at sap.com'; 'h.abangar at surrey.ac.uk'; 'antonio.filograna at eng.it'; 'piero.barrella at alcatel-lucent.com'; 'Denes.Bisztray at nsn.com'; 'Lorant.Farkas at nsn.com'; 'Thomas.Riegel at siemens.com'; 'Thierry.nagellen at orange.com'; 'laurent.artusio at orange.com'; 'guysh at il.ibm.com'; 'tali at il.ibm.com'; 'boris.moltchanov at telecomitalia.it'; 'pierangelo.garino at telecomitalia.it'; 'randradas at libresoft.es'; 'p.amon at siemens.com'; MADHUSUDAN Giyyarpuram RD-TECH; 'levent.gurgen at cea.fr'; 's.meissner at surrey.ac.uk'; 'boris.pokric at gmail.com'; 'mdohler at worldsensing.com'; 'lydie.desperben at coronis.com'; 'alexey.baraev at create-net.org'; 'jcuesta at tlmat.unican.es'; 'calin.curescu at Ericsson.com'; 'd.ghataoura at surrey.ac.uk'; 'maarten.los at atosresearch.eu'; andriy.panchenko at uni.lu; 'jerome.francois at uni.lu'; 'pascal.bisson at thalesgroup.com'; 'daniel.gidoin at thalesgroup.com'; 'mirko.presser at alexandra.dk'; 'alhj at tid.es' Cc : GRATTARD Gilles RD-BIZZ; 'k.moessner at surrey.ac.uk'; 'ralli at tid.es'; 'jhierro at tid.es' Objet : RE: OUTSMART / FI-WARE synchronization - finding a date for the OUTSMART software architecture review Dear all, As agreed during our OUTSMART/FI-WARE synchronization kick-off meeting, we will review the result of our synchronization work, and more generally review our system (SW/HW) architecture beginning of September (DEC-2 in the minutes (*)) Please provide your availability on the following doodle before aug. 1rst: http://www.doodle.com/iu4zvr9cddpxbirw Note that this doesn't imply any hard commitment from your side because I guess not everybody will come. This is simply to set the best date. The location will depends on who will attend, which will do in a second round beginning of august. Best regards, Fano * kick-off minutes: https://docs.google.com/document/d/1RXB_hIwTqb93Nw5zPbebbCLqOE6avA1tJNBm2yiuFg8/edit _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: OUTSMARTArchitectureReviewMeeting mod ALU.zip Type: application/x-zip-compressed Size: 20565 bytes Desc: OUTSMARTArchitectureReviewMeeting mod ALU.zip URL: From stefano.depanfilis at eng.it Mon Sep 10 15:38:51 2012 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 10 Sep 2012 15:38:51 +0200 Subject: [Fiware-wpl] Shared minutes for the joint WPLs/WPAs confcall In-Reply-To: <504DE397.4050000@tid.es> References: <504DE397.4050000@tid.es> Message-ID: dear juanjo, as anticipated i'm not attending the phc today for previous engagements. i'll read the minutes and please let me know what expected by us (testbed team). by the way, we will meet tomorrow evening, isn't it? ciao, stefano 2012/9/10 Juanjo Hierro > Hi, > > As always, we will use shared minutes. You can locate them at: > > https://docs.google.com/**document/d/**1Yk1jqEa87aavZl3VetyBG3kIscQaP** > UHuA7vBXwnsj_A/edit# > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/**FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/**groups/FIWARE-4239932 > > > ______________________________**__ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/**disclaimer.aspx > ______________________________**_________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/**listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Mon Sep 10 16:46:59 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 10 Sep 2012 16:46:59 +0200 Subject: [Fiware-wpl] *** IMPORTANT *** ON catalogue status and actions to do Message-ID: <504DFD63.7000506@eng.it> Dear All, as agreed during the today conference call here below is the list of published GE which deserve some stylish revision according to the attached guidelines. APPS: - Light Semantic Composition Editor (font size not compliant) - Marketplace - Mashup Factory - Mediator - Service Description Repository - Wirecloud Mashup Platform Data: - CEP GE (fonts size not compliant) IoT: - Gataway Device Management - Things Management GE I2N: - CloudEdge Security: - DataHandling - DB Anonymiser Security Service - Identity Management One - IDM @All: despite we went through all of them, please check that also those GEs not mentioned in the list respect the fort size and style reported in the attached guidelines. Do not hesitate to contact me or Davide for any additional clarification. Best regards Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Catalogue sections templates.1.doc Type: application/msword Size: 45056 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Tue Sep 11 06:02:57 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Sep 2012 06:02:57 +0200 Subject: [Fiware-wpl] [Suspected Spam] Fwd: RE: Notes from confcall on analysis of the status of FI-WARE and the FI-PPP In-Reply-To: <8D75402F31CB9044A8BE98020FB2D7A508EF04@S-DC-ESTB03-B.net1.cec.eu.int> References: <8D75402F31CB9044A8BE98020FB2D7A508EF04@S-DC-ESTB03-B.net1.cec.eu.int> Message-ID: <504EB7F1.80909@tid.es> Dear colleagues, This is an email that may provide some background/input to our discussions on recovery steps within the FI-WARE PCC. We had a confcall with the Peter Fatelning and Arian Zwegers from the EC on September 3th trying to understand what are the priorities where we should concentrate our efforts in FI-WARE during the upcoming months, taking an overall FI-PPP program perspective. We took some notes of this interesting discussion and sent them back to Peter and Arian so that they could confirm our notes were accurate and/or make any further comments. I'm forwarding their response to you below of my signature "as it was", so that there is no any doubt about how accurate it could be any translation we may elaborate and send to you. There are a number of points that we believe are remarkable. Here you are our elaboration on them: * The top priority issue for the EC seems to be, by far, the sustainability of what we deliver. Regarding specifications of FI-WARE GEs, this has to do with sustainability of any reference implementation we will develop in FI-WARE but also with completeness/quality of published specifications and the terms and conditions established in Legal Notices attached to them, which should warrant that 3rd parties can, and will be attracted to, implement products in compliance with specifications. Note that most of this was capture in check point number 11 of the list of check points on page 10 of the month 12 official review report. Our conversation with the EC has been helpful to highlight how crucial this checkpoint is compared to the the rest. * Regarding sustainability of the reference implementations we will develop in FI-WARE, it seems like the EC will ask for a formal statement by partners owning the implementations about their intends to commercialize them as products under FRAND terms or provide them as Open Source if those commercial plans become not viable. We feel like we are going to be asked to provide such formal statement sometime end of October, early November (probably close to our next review). It is not clear to us to what extend we will be asked by the EC to drop any FI-WARE GE for which such a formal statement cannot be made, but certainly the EC wants that UC Trials in second phase of the FI-PPP take an informed decision on what FI-WARE GEs to use in the second phase of the FI-PPP based on statements provided. We personally believe that there may not be anything on our contract that may force us to drop a given FI-WARE GE in, say it, the second Release of FI-WARE, if such a statement cannot be made, but we guess it will be rather difficult to seek for funding to be devoted to maintain/evolve those GEs within the context of the Technology Foundation continuation project planned in phase 3. We would also add that we probably have to reconsider their inclusion in the Second Release of FI-WARE anyway, given the fact that we would not be backed by the EC on keeping them. * The EC is concerned about the completeness/quality of FI-WARE GE Open Specifications but not that much about the need to fix this "tomorrow". Clearly we should show a clear improvement in month 18, of course. However, the timing that is critical is that of making them rather usable by UC Trials in phase 2, and be able to provide an statement on commercial sustainability before that, rather than serving UC Projects needs in phase 1. * Clearly, supporting UC projects in phase 1 is important but not the critical thing from the EC's perspective. Providing a "perfect" support to the UC projects in phase 1 regarding usage of a given FI-WARE GE implementation is rather nice, but of no use if we are not going to be able to make any statement about commercial viability of that implementation (under FRAND terms, which may include provision of Open Source licenses or not). Making a statement about commercial viability of the implementation of a FI-WARE GE may minimize the impact of not providing a "perfect" support to UC projects in phase 1. Of course, we shouldn't use this as an alibi for a lack of support to UC projects in phase 1. We should try to do our best in that respect ... though priorities are clear. * The EC clearly welcomes our last efforts to make the FI-WARE Testbed available and welcome the management decisions implemented during the last months leading those efforts. We at TID know that some of those decisions were tough, and still we have to work on being more rigorous with planning and follow-up of activities. But all of this will pave the way to success. We hope that you share this. We would also like to share with you that Telefonica welcomes any constructive feedback and ideas that may help to improve overall performance. We would like to know if you would share this elaboration. Your comments/feedback is rather welcome. Anyways, take this as input for discussion during our PCC meeting. Cheers, -- Juanjo -------- Original Message -------- Subject: RE: Notes from confcall on analysis of the status of FI-WARE and the FI-PPP Date: Wed, 5 Sep 2012 16:25:28 +0000 From: To: CC: , , , Dear Juanjo, Please find below our comments to your summary. Kind regards, Peter From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Tuesday, September 04, 2012 8:10 AM To: FATELNIG Peter (CNECT); ZWEGERS Arian (CNECT) Cc: VILLASANTE Jesus (CNECT); Jose Jimenez; jhierro >> "Juan J. Hierro" Subject: Notes from confcall on analysis of the status of FI-WARE and the FI-PPP Dear Peter and Arian, Thanks for the open conversation maintained yesterday. The goal for us was to understand what are the priorities in which FI-WARE should concentrate on during the upcoming months, so that we make sure that we recover from the current situation, taking an overall FI-PPP program perspective. I would like to summarize the notes I took on your feedback in order to make sure that we deliver an accurate message to the rest of the FI-WARE partners. According to my notes: ? The very first priority of FI-WARE should be to make sure that, in month 18, each partner that owns a reference implementation of a given FI-WARE GE makes a commitment to make such reference implementation commercially available within the context of the FI-PPP and beyond. This means that: o The FI-WARE GE reference implementation owner should make a clear commitment to commercialize the FI-WARE GE reference implementation it owns under FRAND conditions during and beyond the FI-PPP, accompanied by a commitment to deliver such reference implementation as Open Source in the case that commercialization of a reference implementation of the GE in compliance with FI-WARE specifications is discontinued; or o The FI-WARE GE reference implementation owner makes a clear commitment to deliver a reference implementation of the GE as Open Source The commitment statement must contain all information that possible users need in order to decide about using the GE reference implementation concerned or not, within the context of the PPP and outside. This means, for instance, that a timing needs to be indicated, the exact conditions and constraints need to be specified, etc. All details might not be known at this stage, for call 2, but as much information as possible should be provided. ? The second priority of FI-WARE should be to make sure that the FI-WARE Architecture Description and Open Specifications are usable by both application developers and potential FI-WARE GE implementors, meaning they gather all the necessary information to allow them to develop applications and compliant implementation. Despite these Architecture Description and Open Specifications may be improved over time (the project is 3 years long), FI-WARE should be able to reach a certain minimum level of quality in month 18 The GE Open Specifications must contain all information needed to implement the GE; they must be self-contained (also without FI-WARE Architecture Description). We are currently looking at the different Legal Notices associated to the GE Open Specifications and will come back to that. ? Rest is of less priority, including support to FI-PPP UC projects in phase 1. Of course, this not meaning that FI-WARE should try to make its best to support usage of the FI-WARE Testbed during this period. We have indicated the points which are a clear priority and we think we have been consistent in doing so from the beginning. This does not mean that FI-WARE should ignore other points mentioned in the review reports and outcome letter. We are confident that the partners in the consortium have the ability to address the points in the review reports and outcome letters and to deliver results that are useful to themselves, other partners in the PPP, and third parties. We are also confident that the FI-WARE management will be able to take a leading role, and we are happy to see that actions taken after month 12 have resulted in improvements already, for instance by the delivery of the Testbed. Your confirmation that these notes are accurate is rather welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Sep 11 09:31:28 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Sep 2012 09:31:28 +0200 Subject: [Fiware-wpl] *** IMPORTANT *** ON catalogue status and actions to do In-Reply-To: <504DFD63.7000506@eng.it> References: <504DFD63.7000506@eng.it> Message-ID: <504EE8D0.5000704@tid.es> Hi, Please take care of this as soon as possible. There will be an InfoDay tomorrow where we will present the FI-WARE Catalogue and this means that lot of people will connect afterwards. Our work may not look that professional if entries follow totally disparate formats. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 10/09/12 16:46, Matteo Melideo wrote: Dear All, as agreed during the today conference call here below is the list of published GE which deserve some stylish revision according to the attached guidelines. APPS: - Light Semantic Composition Editor (font size not compliant) - Marketplace - Mashup Factory - Mediator - Service Description Repository - Wirecloud Mashup Platform Data: - CEP GE (fonts size not compliant) IoT: - Gataway Device Management - Things Management GE I2N: - CloudEdge Security: - DataHandling - DB Anonymiser Security Service - Identity Management One - IDM @All: despite we went through all of them, please check that also those GEs not mentioned in the list respect the fort size and style reported in the attached guidelines. Do not hesitate to contact me or Davide for any additional clarification. Best regards Matteo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.dallecarbonare at eng.it Tue Sep 11 15:26:02 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 11 Sep 2012 15:26:02 +0200 Subject: [Fiware-wpl] *** IMPORTANT *** ON catalogue status and actions to do In-Reply-To: <504EE8D0.5000704@tid.es> References: <504DFD63.7000506@eng.it> <504EE8D0.5000704@tid.es> Message-ID: <504F3BEA.3090102@eng.it> Dear All, I apologize for this last minute update but we discovered a misalignment between the the guidelines circulated yesterday and what's reported on the Catalogue page of the public FI-WARE wiki. The headers of the sections for Overview and Description pages have to start from H2 while H3 and H4 have to be used for nested levels. I attach the updated document and I'm going report everything also on the wiki page right now https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue For those pages that already respect the template and have used the H3 for section headers, I proceed to update the tag to H2 for them. For the others that still do not respect the template, they will set that tag by themselves. Thank you for your collaboration, Kind Regards, Davide On 11/09/2012 09:31, Juanjo Hierro wrote: > Hi, > > Please take care of this as soon as possible. > > There will be an InfoDay tomorrow where we will present the FI-WARE > Catalogue and this means that lot of people will connect afterwards. > Our work may not look that professional if entries follow totally > disparate formats. > > Cheers, > > -- Juanjo > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > On 10/09/12 16:46, Matteo Melideo wrote: >> Dear All, >> as agreed during the today conference call here below is the list of >> published GE which deserve some stylish revision according to the >> attached guidelines. >> >> APPS: >> - Light Semantic Composition Editor (font size not compliant) >> - Marketplace >> - Mashup Factory >> - Mediator >> - Service Description Repository >> - Wirecloud Mashup Platform >> >> Data: >> - CEP GE (fonts size not compliant) >> >> IoT: >> - Gataway Device Management >> - Things Management GE >> >> I2N: >> - CloudEdge >> >> Security: >> - DataHandling >> - DB Anonymiser Security Service >> - Identity Management One - IDM >> >> >> @All: despite we went through all of them, please check that also >> those GEs not mentioned in the list respect the fort size and style >> reported in the attached guidelines. >> >> >> Do not hesitate to contact me or Davide for any additional clarification. >> >> >> Best regards >> >> Matteo > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Catalogue sections templates.1.1.doc Type: application/msword Size: 19968 bytes Desc: not available URL: From jhierro at tid.es Mon Sep 17 08:37:35 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 17 Sep 2012 08:37:35 +0200 Subject: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs Message-ID: <5056C52F.8020403@tid.es> Hi all, I'm currently in Israel and despite I thought I was going to be able to connect our regular follow-up confcall I won't finally be able to do so for logistic reasons. Therefore, the joint follow-up confcall today will be cancelled. I believe we can follow-up progress of the activities off-line this week. In this respect, I would like to remind you the following critical APs (see also requests about reporting): * Fix information published on the Catalogue about FI-WARE GEs available on the FI-WARE Testbed so that it complies with defined templates (Matteo, please report on the status of this) * Stefano to give Matteo a list of people in the Testbed team that would keep read privileges on entries associated to GEs that are under progress (Stefano or Matteo, please report on the status of this) * Some GEs were planned to be available mid September: QueryBroker, Semantic Annotation Support, Ericsson Composition Editor and Gateway Device Management GE (Carlos, Uwe and Thierry, please report on the status of the GEs in this list within your chapter) * All chapters were supposed to close a stable version of the "Architecture and Open Specifications" so we could carry out a second peer-review of them starting on September 11, 12:00 CET. It is planned that reviewing chapters deliver the results of their revision, using the provided forms, by September 20th. (please, all WPLs to report on the status of this) * Planning of September Sprint by each Chapter reflected on the corresponding Chapter tracker. This was a must and it was expected to be finished by Thursday last week at the latest. We will check the tracker and get back to you about any issue we may find. Note that those partners that do not have any assignment are supposed that are not working during the Sprint, or keeping a minimum level of activity, therefore their costs reports may be rejected. It would be great if Uwe Riss from SAP can send us some brief report on how was the InfoDay in Brussels. Here, I would like to share with the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of the need to make a presentation in the InfoDay to produce two valuable elements now in the public wiki: * A "Quick FI-WARE tour" wiki page that may help people to navigate through the big ocean of FI-WARE available information * A "FI-WARE FAQ" wiki page that may be also helpful in understanding of FI-WARE Regarding the FI-PPP AB last week, I would like to highlight the following topics (I will distribute the minutes as soon as a stable draft is available): * The shared spreadsheet about inteded usage of the FI-WARE GEs by Use Case projects in phase 1 will be updated because a new "state" will be introduced (not relevant at this point but in the near future, taking into account that the document will be a living document). I believe that the notes in the spreadshet are self-explanatory, so you just need to revisit * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 * It was agreed that we can add a given Use Case project as "stakeholder" of all features of a GE for which the project has assigned label "U" in the spreadsheet of the previous point (which means that they have already taken the GE into consideration in their design). Chapter leaders should monitor the status of this table because, hopefully, some "E"s will transit into "U"s * Architecture documents delivered by the Use Case projects have been uploaded on the FI-WARE docman system. You can find them within the folder titled "FI-PPP UC Projects Architecture Documentation" (note that you should have logged in FusionForge first) * The issue about Secured Access to the FI-WARE Testbed was labeled as critical so FI-WARE were requested to provide a solution as soon as possible. I will send a more elaborated email on this later today. * I reported that we have started to take care of tickets issued by UC projects on the "FI-WARE General Support" tracker but let me share with you that some of them share their concern that most of the tickets changed to the "assigned" state right before the FI-PPP AB meeting after more than one month being open without feedback. Therefore, some UC projects suspect it was a "cosmetic" change so they will keep an eye on how this evolves ... Therefore, we have to start working on it in a regular, constant, basis * I commit to prepare a paper and presentation on how applications can be designed to take advantage of the integration of the different Data/Context Management GEs planned in Release 2 and the ability to support an Open Data approach. I will target a virtual workshop with UC projects on September 25th. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Mon Sep 17 10:46:31 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 17 Sep 2012 10:46:31 +0200 Subject: [Fiware-wpl] Brief report of the InfoDay in Brussels Message-ID: <1491C91A94302A448D73CD9C6B7A782046C4227005@DEWDFECCR02.wdf.sap.corp> Hi all, In the following I briefly summarize the morning session of the Info Day in Brussels that took place last Wednesday, 12 September: ? Goal of the Info Day was to give parties that have planned to take part in FI-PPP Call 2, that is, as successors of the current UC projects, an overview of the FI-PPP programme. Moreover, it opened up opportunities to communicate with people who are already working in one of FI-PPP projects. ? Presenters for the EC were: o Mario Campolargo, who welcomed the participants and explained that the FI-PPP already shows some promising development. o Arian Zwegers, who presented the Call 2 Work Programme, pointing at the roles and interactions between the different FI-PPP projects. o Peter Fatelnig, who explained the high expectations related to the FI-PPP. It has been emphasized that the EC expects considerable impact of the programme in terms of business impact. In the upcoming project 10% of the budget is planned to be used for Open Calls. ? Presenters for FI-PPP were: o Mikko Riepula (Aalto Univisity) for Concord (Collaboration): Mikko Presented the different boards that coordinate the FI-PPP and explained their roles in the programme. o Uwe Riss (SAP) for FI-WARE (Technology Foundation): Uwe gave an overview presentation on the goal and spectrum of the FI-WARE Technology Foundations including the focus of the chapters and the principle ideas of the FI-WARE Architecture. It was emphasized which important role the communication between FI-WARE and the UC projects plays for the success of FI-PPP. o Mike Surridge (IT Innovation) for Infinity ( Phase 2/3 Capacity Building): Mike reported on the planned supporting infrastructure for future Call 2 UC Trial projects. ? Points relevant for FI-WARE: o FI-WARE will use their best endeavours to support the proposers and the new UC Trial project. Cornerstones of this support are: ? A wikipage (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Quick_FI-WARE_tour) jointly suggested by TID and SAP and provided by Juanjo that give proposers quick and comprehensive access to the central FI-WARE information resources. This approach was high appreciated by Arian. ? An FAQ page (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_FAQ ) similar to one that we had already used in the Open Call to address open questions on the proposers' side. The link is available on the wiki page mentioned before. ? A mailing list (mailto:fiware-help at lists.fi-ware.eu ) that allows proposers to directly ask experts in FI-WARE questions related to the project. This channel should be seen as the starting point for later communication with the UC Trial projects. The link is available on the wiki page mentioned before. o There were various questions from the proposers' side regarding FI-WARE: ? Who will be able to access the GE provided by FI-WARE? ? Why does FI-PPP one support one Architecture approach instead of various competing approaches? ? Is there some kind of certification process for 3rd party implementations in order to check that they are compliant with the Open Specifications? ? How is the quality of the provided GEs ensured? ? Where can proposers find information about discussions and decisions on the development of GEs? Why will certain GEs be developed and why had other GE suggestions been rejected? ? There were representatives of various current UC projects in the meeting. ? Since I had to travel back I could not attend the afternoon session consisting of proposers' presentations: o E. Rosenberg, City Flow Concept o C. Camacho, Smart home for the Smart Grid o J. Bertolin, e'Living Lab: STP + LL = Innoconnector for the creation of SmartRegions o S. Gusmeroli, FIT-MAN Future InTernet for the MANufacturing SMWs o M. Fiedler, Expression of Interest: Participation in a FI-PPP Use Case on e-Health o P. Martinez, FI-PPP Call 2 - Collaborative topics o J. Pielorz, UBIMET Partner Presentation o R. Vonhout, Optical experimental facility o Stan, IN2 Search Interfaces Development partner Presentation o T. Omitola, Real-time Semantic Sensing and Processing for the Intelligent City The presentations of the FI-PPP Info Day are online. Please follow the link attached to access them: http://ec.europa.eu/information_society/activities/foi/events/call2infoday/index_en.htm Best regards, Uwe Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Mon Sep 17 11:06:43 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 17 Sep 2012 11:06:43 +0200 Subject: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs In-Reply-To: <5056C52F.8020403@tid.es> References: <5056C52F.8020403@tid.es> Message-ID: <5056E823.9080505@eng.it> Dear Juanjo, below the requested info. I was wondering if you sent to the PO the mail on the roadmap. Thx and regards, M. Il 17/09/2012 08:37, Juanjo Hierro ha scritto: > Hi all, > > I'm currently in Israel and despite I thought I was going to be able > to connect our regular follow-up confcall I won't finally be able to > do so for logistic reasons. > > Therefore, the joint follow-up confcall today will be cancelled. I > believe we can follow-up progress of the activities off-line this > week. In this respect, I would like to remind you the following > critical APs (see also requests about reporting): > > * Fix information published on the Catalogue about FI-WARE GEs > available on the FI-WARE Testbed so that it complies with defined > templates (Matteo, please report on the status of this) > [MM] Status of the GEs on the FI-WARE Catalogue: - MEDIATOR GE not yet compliant with the template. - Wirecloud Mashup Platform not yet compliant with the template. - Gateway Device Management GE not yet compliant with the template. - Things Management GE not yet compliant with the template. - Data Handling not yet compliant with the template. > > * Stefano to give Matteo a list of people in the Testbed team that > would keep read privileges on entries associated to GEs that are > under progress (Stefano or Matteo, please report on the status of > this) > No news on this. > > * Some GEs were planned to be available mid September: QueryBroker, > Semantic Annotation Support, Ericsson Composition Editor and > Gateway Device Management GE (Carlos, Uwe and Thierry, please > report on the status of the GEs in this list within your chapter) > [MM] Gateway Device Management GE is already published according to the info I have from the Testbed. Should I hide this GE from the catalogue? > > * All chapters were supposed to close a stable version of the > "Architecture and Open Specifications" so we could carry out a > second peer-review of them starting on September 11, 12:00 CET. > It is planned that reviewing chapters deliver the results of their > revision, using the provided forms, by September 20th. (please, > all WPLs to report on the status of this) > * Planning of September Sprint by each Chapter reflected on the > corresponding Chapter tracker. This was a must and it was > expected to be finished by Thursday last week at the latest. We > will check the tracker and get back to you about any issue we may > find. Note that those partners that do not have any assignment > are supposed that are not working during the Sprint, or keeping a > minimum level of activity, therefore their costs reports may be > rejected. > > > It would be great if Uwe Riss from SAP can send us some brief report > on how was the InfoDay in Brussels. Here, I would like to share with > the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of > the need to make a presentation in the InfoDay to produce two valuable > elements now in the public wiki: > > * A "Quick FI-WARE tour" wiki page that may help people to navigate > through the big ocean of FI-WARE available information > * A "FI-WARE FAQ" wiki page that may be also helpful in > understanding of FI-WARE > > > Regarding the FI-PPP AB last week, I would like to highlight the > following topics (I will distribute the minutes as soon as a stable > draft is available): > > * The shared spreadsheet about inteded usage of the FI-WARE GEs by > Use Case projects in phase 1 will be updated because a new "state" > will be introduced (not relevant at this point but in the near > future, taking into account that the document will be a living > document). I believe that the notes in the spreadshet are > self-explanatory, so you just need to revisit > o https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 > > > * It was agreed that we can add a given Use Case project as > "stakeholder" of all features of a GE for which the project has > assigned label "U" in the spreadsheet of the previous point (which > means that they have already taken the GE into consideration in > their design). Chapter leaders should monitor the status of this > table because, hopefully, some "E"s will transit into "U"s > > * Architecture documents delivered by the Use Case projects have > been uploaded on the FI-WARE docman system. You can find them > within the folder titled "FI-PPP UC Projects Architecture > Documentation" (note that you should have logged in FusionForge > first) > > * The issue about Secured Access to the FI-WARE Testbed was labeled > as critical so FI-WARE were requested to provide a solution as > soon as possible. I will send a more elaborated email on this > later today. > > * I reported that we have started to take care of tickets issued by > UC projects on the "FI-WARE General Support" tracker but let me > share with you that some of them share their concern that most of > the tickets changed to the "assigned" state right before the > FI-PPP AB meeting after more than one month being open without > feedback. Therefore, some UC projects suspect it was a > "cosmetic" change so they will keep an eye on how this evolves ... > Therefore, we have to start working on it in a regular, constant, > basis > > * I commit to prepare a paper and presentation on how applications > can be designed to take advantage of the integration of the > different Data/Context Management GEs planned in Release 2 and the > ability to support an Open Data approach. I will target a > virtual workshop with UC projects on September 25th. > > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From mcp at tid.es Tue Sep 18 12:42:24 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 18 Sep 2012 12:42:24 +0200 Subject: [Fiware-wpl] Local infodays Message-ID: <50585010.7070501@tid.es> Dear all, As agreed in a WPL/WPA follow up call in mid August, we should have prospective answers from the local clusters (Germany, Italy, Spain and France at least) telling us if there is scope for local infodays and the answer you got from your contacts with the national authorities of your respective countries. This will be mentioned tomorrow in the PCC meeting, where we could start planning the strategy for the near future. The 2nd open call opened on the 1st of August (http://www.fi-ware.eu/open-call/) and it is closing at the beginning of novermber, we should not put it off much longer. 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 thierry.nagellen at orange.com Tue Sep 18 15:46:45 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 18 Sep 2012 13:46:45 +0000 Subject: [Fiware-wpl] Local infodays In-Reply-To: <50585010.7070501@tid.es> References: <50585010.7070501@tid.es> Message-ID: <9275_1347976006_50587B46_9275_2666_21_976A65C5A08ADF49B9A8523F7F81925C05F715@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all I'm in contact with Ubifrance which is working with our National Contact Point and we try to organize the infoday on the beginning of October. The potential dates are 1st, 8th, 9th or 10th of October. I should finalize the agenda and fix the date for the end of the week. BR Thierry -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mardi 18 septembre 2012 12:42 ??: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Objet?: [Fiware-wpl] Local infodays Dear all, As agreed in a WPL/WPA follow up call in mid August, we should have prospective answers from the local clusters (Germany, Italy, Spain and France at least) telling us if there is scope for local infodays and the answer you got from your contacts with the national authorities of your respective countries. This will be mentioned tomorrow in the PCC meeting, where we could start planning the strategy for the near future. The 2nd open call opened on the 1st of August (http://www.fi-ware.eu/open-call/) and it is closing at the beginning of novermber, we should not put it off much longer. 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 http://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. From jhierro at tid.es Wed Sep 19 16:13:32 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 19 Sep 2012 16:13:32 +0200 Subject: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs In-Reply-To: <5056C52F.8020403@tid.es> References: <5056C52F.8020403@tid.es> Message-ID: <5059D30C.4060209@tid.es> Hi all, Could those I kindly ask to send a report on status to send it ? So far, I have only seen a response by Matteo (thanks, BTW) and Uwe (but just on the InfoDay) Cheers, -- Juanjo On 17/09/12 08:37, Juanjo Hierro wrote: Hi all, I'm currently in Israel and despite I thought I was going to be able to connect our regular follow-up confcall I won't finally be able to do so for logistic reasons. Therefore, the joint follow-up confcall today will be cancelled. I believe we can follow-up progress of the activities off-line this week. In this respect, I would like to remind you the following critical APs (see also requests about reporting): * Fix information published on the Catalogue about FI-WARE GEs available on the FI-WARE Testbed so that it complies with defined templates (Matteo, please report on the status of this) * Stefano to give Matteo a list of people in the Testbed team that would keep read privileges on entries associated to GEs that are under progress (Stefano or Matteo, please report on the status of this) * Some GEs were planned to be available mid September: QueryBroker, Semantic Annotation Support, Ericsson Composition Editor and Gateway Device Management GE (Carlos, Uwe and Thierry, please report on the status of the GEs in this list within your chapter) * All chapters were supposed to close a stable version of the "Architecture and Open Specifications" so we could carry out a second peer-review of them starting on September 11, 12:00 CET. It is planned that reviewing chapters deliver the results of their revision, using the provided forms, by September 20th. (please, all WPLs to report on the status of this) * Planning of September Sprint by each Chapter reflected on the corresponding Chapter tracker. This was a must and it was expected to be finished by Thursday last week at the latest. We will check the tracker and get back to you about any issue we may find. Note that those partners that do not have any assignment are supposed that are not working during the Sprint, or keeping a minimum level of activity, therefore their costs reports may be rejected. It would be great if Uwe Riss from SAP can send us some brief report on how was the InfoDay in Brussels. Here, I would like to share with the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of the need to make a presentation in the InfoDay to produce two valuable elements now in the public wiki: * A "Quick FI-WARE tour" wiki page that may help people to navigate through the big ocean of FI-WARE available information * A "FI-WARE FAQ" wiki page that may be also helpful in understanding of FI-WARE Regarding the FI-PPP AB last week, I would like to highlight the following topics (I will distribute the minutes as soon as a stable draft is available): * The shared spreadsheet about inteded usage of the FI-WARE GEs by Use Case projects in phase 1 will be updated because a new "state" will be introduced (not relevant at this point but in the near future, taking into account that the document will be a living document). I believe that the notes in the spreadshet are self-explanatory, so you just need to revisit * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 * It was agreed that we can add a given Use Case project as "stakeholder" of all features of a GE for which the project has assigned label "U" in the spreadsheet of the previous point (which means that they have already taken the GE into consideration in their design). Chapter leaders should monitor the status of this table because, hopefully, some "E"s will transit into "U"s * Architecture documents delivered by the Use Case projects have been uploaded on the FI-WARE docman system. You can find them within the folder titled "FI-PPP UC Projects Architecture Documentation" (note that you should have logged in FusionForge first) * The issue about Secured Access to the FI-WARE Testbed was labeled as critical so FI-WARE were requested to provide a solution as soon as possible. I will send a more elaborated email on this later today. * I reported that we have started to take care of tickets issued by UC projects on the "FI-WARE General Support" tracker but let me share with you that some of them share their concern that most of the tickets changed to the "assigned" state right before the FI-PPP AB meeting after more than one month being open without feedback. Therefore, some UC projects suspect it was a "cosmetic" change so they will keep an eye on how this evolves ... Therefore, we have to start working on it in a regular, constant, basis * I commit to prepare a paper and presentation on how applications can be designed to take advantage of the integration of the different Data/Context Management GEs planned in Release 2 and the ability to support an Open Data approach. I will target a virtual workshop with UC projects on September 25th. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://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 pierangelo.garino at telecomitalia.it Wed Sep 19 16:44:44 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 19 Sep 2012 16:44:44 +0200 Subject: [Fiware-wpl] R: Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs In-Reply-To: <5059D30C.4060209@tid.es> References: <5056C52F.8020403@tid.es> <5059D30C.4060209@tid.es> Message-ID: Dear Juanjo, I have inserted the feedback about items concerning I2ND chapter in your mail below. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 19 settembre 2012 16:14 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs Hi all, Could those I kindly ask to send a report on status to send it ? So far, I have only seen a response by Matteo (thanks, BTW) and Uwe (but just on the InfoDay) Cheers, -- Juanjo On 17/09/12 08:37, Juanjo Hierro wrote: Hi all, I'm currently in Israel and despite I thought I was going to be able to connect our regular follow-up confcall I won't finally be able to do so for logistic reasons. Therefore, the joint follow-up confcall today will be cancelled. I believe we can follow-up progress of the activities off-line this week. In this respect, I would like to remind you the following critical APs (see also requests about reporting): * Fix information published on the Catalogue about FI-WARE GEs available on the FI-WARE Testbed so that it complies with defined templates (Matteo, please report on the status of this) * Stefano to give Matteo a list of people in the Testbed team that would keep read privileges on entries associated to GEs that are under progress (Stefano or Matteo, please report on the status of this) * Some GEs were planned to be available mid September: QueryBroker, Semantic Annotation Support, Ericsson Composition Editor and Gateway Device Management GE (Carlos, Uwe and Thierry, please report on the status of the GEs in this list within your chapter) * All chapters were supposed to close a stable version of the "Architecture and Open Specifications" so we could carry out a second peer-review of them starting on September 11, 12:00 CET. It is planned that reviewing chapters deliver the results of their revision, using the provided forms, by September 20th. (please, all WPLs to report on the status of this) I2ND: Review of assigned chapter pages (Cloud) nearly complete. It should be ready according to plan. * Planning of September Sprint by each Chapter reflected on the corresponding Chapter tracker. This was a must and it was expected to be finished by Thursday last week at the latest. We will check the tracker and get back to you about any issue we may find. Note that those partners that do not have any assignment are supposed that are not working during the Sprint, or keeping a minimum level of activity, therefore their costs reports may be rejected. I2ND: Most of the September Sprint assignments done, process under refinement. It should complete by Sep 21. It would be great if Uwe Riss from SAP can send us some brief report on how was the InfoDay in Brussels. Here, I would like to share with the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of the need to make a presentation in the InfoDay to produce two valuable elements now in the public wiki: * A "Quick FI-WARE tour" wiki page that may help people to navigate through the big ocean of FI-WARE available information * A "FI-WARE FAQ" wiki page that may be also helpful in understanding of FI-WARE Regarding the FI-PPP AB last week, I would like to highlight the following topics (I will distribute the minutes as soon as a stable draft is available): * The shared spreadsheet about inteded usage of the FI-WARE GEs by Use Case projects in phase 1 will be updated because a new "state" will be introduced (not relevant at this point but in the near future, taking into account that the document will be a living document). I believe that the notes in the spreadshet are self-explanatory, so you just need to revisit * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 * It was agreed that we can add a given Use Case project as "stakeholder" of all features of a GE for which the project has assigned label "U" in the spreadsheet of the previous point (which means that they have already taken the GE into consideration in their design). Chapter leaders should monitor the status of this table because, hopefully, some "E"s will transit into "U"s I2ND: On going. * Architecture documents delivered by the Use Case projects have been uploaded on the FI-WARE docman system. You can find them within the folder titled "FI-PPP UC Projects Architecture Documentation" (note that you should have logged in FusionForge first) * The issue about Secured Access to the FI-WARE Testbed was labeled as critical so FI-WARE were requested to provide a solution as soon as possible. I will send a more elaborated email on this later today. * I reported that we have started to take care of tickets issued by UC projects on the "FI-WARE General Support" tracker but let me share with you that some of them share their concern that most of the tickets changed to the "assigned" state right before the FI-PPP AB meeting after more than one month being open without feedback. Therefore, some UC projects suspect it was a "cosmetic" change so they will keep an eye on how this evolves ... Therefore, we have to start working on it in a regular, constant, basis I2ND: We took care of the tickets assigned to/concerning the chapter. Currently either in ToBeRevised or CheckSolved status. Question: what are the guidelines to manage tickets with Chapter=Hard to determine i.e. who's taking first look at them? * I commit to prepare a paper and presentation on how applications can be designed to take advantage of the integration of the different Data/Context Management GEs planned in Release 2 and the ability to support an Open Data approach. I will target a virtual workshop with UC projects on September 25th. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From ralli at tid.es Wed Sep 19 17:07:47 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 19 Sep 2012 15:07:47 +0000 Subject: [Fiware-wpl] [Fiware-wpa] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs In-Reply-To: <5059D30C.4060209@tid.es> References: <5056C52F.8020403@tid.es> <5059D30C.4060209@tid.es> Message-ID: <8F57BAB4-DC3A-41B0-8F77-3136B434A79A@tid.es> Juanjo, Enclosed the items related to Data/Context: - Catalogue: all GEs are aligned with the template as confirmed by Davide. - Mid-Sep GEs: QueryBroker & Semantic Annotation. Query Broker: correctly installed and info available for catalogue. However there seems to be a problem on passing the sanity check being addressed by Siemens guys. Semantic Annotation: An access problem is now preventing the installation completion. There's an ongoing interaction with the testbed team to address it (Nacho/Henar). - Review of Arch. Open Specs. 1st review. Almost all changes have been applied. There are some 2-3 that will be applied together with the second review results for sync purposes. 2nd review: We've got some delay although we have selected the reviewers and in some cases started the work. We would like to know if the 20th deadline will be extended. - Planning of September Sprint: All GEs except PubSub and S.Annotation have already included user-stories and work-items related to September ongoing tasks. From the WPA we are also adding some common and/or particular work-items. For instance, I have suggested S.Annotation to include their testbed installation during september as w-i. Regarding the "stakeholder" field in the Wiki, several should be already ok and others have been told to speed up. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ El 19/09/2012, a las 16:13, Juanjo Hierro escribi?: Hi all, Could those I kindly ask to send a report on status to send it ? So far, I have only seen a response by Matteo (thanks, BTW) and Uwe (but just on the InfoDay) Cheers, -- Juanjo On 17/09/12 08:37, Juanjo Hierro wrote: Hi all, I'm currently in Israel and despite I thought I was going to be able to connect our regular follow-up confcall I won't finally be able to do so for logistic reasons. Therefore, the joint follow-up confcall today will be cancelled. I believe we can follow-up progress of the activities off-line this week. In this respect, I would like to remind you the following critical APs (see also requests about reporting): * Fix information published on the Catalogue about FI-WARE GEs available on the FI-WARE Testbed so that it complies with defined templates (Matteo, please report on the status of this) * Stefano to give Matteo a list of people in the Testbed team that would keep read privileges on entries associated to GEs that are under progress (Stefano or Matteo, please report on the status of this) * Some GEs were planned to be available mid September: QueryBroker, Semantic Annotation Support, Ericsson Composition Editor and Gateway Device Management GE (Carlos, Uwe and Thierry, please report on the status of the GEs in this list within your chapter) * All chapters were supposed to close a stable version of the "Architecture and Open Specifications" so we could carry out a second peer-review of them starting on September 11, 12:00 CET. It is planned that reviewing chapters deliver the results of their revision, using the provided forms, by September 20th. (please, all WPLs to report on the status of this) * Planning of September Sprint by each Chapter reflected on the corresponding Chapter tracker. This was a must and it was expected to be finished by Thursday last week at the latest. We will check the tracker and get back to you about any issue we may find. Note that those partners that do not have any assignment are supposed that are not working during the Sprint, or keeping a minimum level of activity, therefore their costs reports may be rejected. It would be great if Uwe Riss from SAP can send us some brief report on how was the InfoDay in Brussels. Here, I would like to share with the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of the need to make a presentation in the InfoDay to produce two valuable elements now in the public wiki: * A "Quick FI-WARE tour" wiki page that may help people to navigate through the big ocean of FI-WARE available information * A "FI-WARE FAQ" wiki page that may be also helpful in understanding of FI-WARE Regarding the FI-PPP AB last week, I would like to highlight the following topics (I will distribute the minutes as soon as a stable draft is available): * The shared spreadsheet about inteded usage of the FI-WARE GEs by Use Case projects in phase 1 will be updated because a new "state" will be introduced (not relevant at this point but in the near future, taking into account that the document will be a living document). I believe that the notes in the spreadshet are self-explanatory, so you just need to revisit * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 * It was agreed that we can add a given Use Case project as "stakeholder" of all features of a GE for which the project has assigned label "U" in the spreadsheet of the previous point (which means that they have already taken the GE into consideration in their design). Chapter leaders should monitor the status of this table because, hopefully, some "E"s will transit into "U"s * Architecture documents delivered by the Use Case projects have been uploaded on the FI-WARE docman system. You can find them within the folder titled "FI-PPP UC Projects Architecture Documentation" (note that you should have logged in FusionForge first) * The issue about Secured Access to the FI-WARE Testbed was labeled as critical so FI-WARE were requested to provide a solution as soon as possible. I will send a more elaborated email on this later today. * I reported that we have started to take care of tickets issued by UC projects on the "FI-WARE General Support" tracker but let me share with you that some of them share their concern that most of the tickets changed to the "assigned" state right before the FI-PPP AB meeting after more than one month being open without feedback. Therefore, some UC projects suspect it was a "cosmetic" change so they will keep an eye on how this evolves ... Therefore, we have to start working on it in a regular, constant, basis * I commit to prepare a paper and presentation on how applications can be designed to take advantage of the integration of the different Data/Context Management GEs planned in Release 2 and the ability to support an Open Data approach. I will target a virtual workshop with UC projects on September 25th. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://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 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Wed Sep 19 17:33:33 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 19 Sep 2012 18:33:33 +0300 Subject: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs In-Reply-To: <5059D30C.4060209@tid.es> References: <5056C52F.8020403@tid.es> <5059D30C.4060209@tid.es> Message-ID: Cloud architecture is stable. Review of Data architecture underway. Likely to be delayed (current target date: end of day Monday). Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu, "fiware-wpa at lists.fi-ware.eu" , Date: 19/09/2012 05:13 PM Subject: Re: [Fiware-wpl] Joint WPLs/WPAs follow-up confcall cancelled but IMPORTANT REMINDER about pending APs Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi all, Could those I kindly ask to send a report on status to send it ? So far, I have only seen a response by Matteo (thanks, BTW) and Uwe (but just on the InfoDay) Cheers, -- Juanjo On 17/09/12 08:37, Juanjo Hierro wrote: Hi all, I'm currently in Israel and despite I thought I was going to be able to connect our regular follow-up confcall I won't finally be able to do so for logistic reasons. Therefore, the joint follow-up confcall today will be cancelled. I believe we can follow-up progress of the activities off-line this week. In this respect, I would like to remind you the following critical APs (see also requests about reporting): Fix information published on the Catalogue about FI-WARE GEs available on the FI-WARE Testbed so that it complies with defined templates (Matteo, please report on the status of this) Stefano to give Matteo a list of people in the Testbed team that would keep read privileges on entries associated to GEs that are under progress (Stefano or Matteo, please report on the status of this) Some GEs were planned to be available mid September: QueryBroker, Semantic Annotation Support, Ericsson Composition Editor and Gateway Device Management GE (Carlos, Uwe and Thierry, please report on the status of the GEs in this list within your chapter) All chapters were supposed to close a stable version of the "Architecture and Open Specifications" so we could carry out a second peer-review of them starting on September 11, 12:00 CET. It is planned that reviewing chapters deliver the results of their revision, using the provided forms, by September 20th. (please, all WPLs to report on the status of this) Planning of September Sprint by each Chapter reflected on the corresponding Chapter tracker. This was a must and it was expected to be finished by Thursday last week at the latest. We will check the tracker and get back to you about any issue we may find. Note that those partners that do not have any assignment are supposed that are not working during the Sprint, or keeping a minimum level of activity, therefore their costs reports may be rejected. It would be great if Uwe Riss from SAP can send us some brief report on how was the InfoDay in Brussels. Here, I would like to share with the rest of WPLs/WPAs that we, SAP and Telefonica, took advantage of the need to make a presentation in the InfoDay to produce two valuable elements now in the public wiki: A "Quick FI-WARE tour" wiki page that may help people to navigate through the big ocean of FI-WARE available information A "FI-WARE FAQ" wiki page that may be also helpful in understanding of FI-WARE Regarding the FI-PPP AB last week, I would like to highlight the following topics (I will distribute the minutes as soon as a stable draft is available): The shared spreadsheet about inteded usage of the FI-WARE GEs by Use Case projects in phase 1 will be updated because a new "state" will be introduced (not relevant at this point but in the near future, taking into account that the document will be a living document). I believe that the notes in the spreadshet are self-explanatory, so you just need to revisit https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 It was agreed that we can add a given Use Case project as "stakeholder" of all features of a GE for which the project has assigned label "U" in the spreadsheet of the previous point (which means that they have already taken the GE into consideration in their design). Chapter leaders should monitor the status of this table because, hopefully, some "E"s will transit into "U"s Architecture documents delivered by the Use Case projects have been uploaded on the FI-WARE docman system. You can find them within the folder titled "FI-PPP UC Projects Architecture Documentation" (note that you should have logged in FusionForge first) The issue about Secured Access to the FI-WARE Testbed was labeled as critical so FI-WARE were requested to provide a solution as soon as possible. I will send a more elaborated email on this later today. I reported that we have started to take care of tickets issued by UC projects on the "FI-WARE General Support" tracker but let me share with you that some of them share their concern that most of the tickets changed to the "assigned" state right before the FI-PPP AB meeting after more than one month being open without feedback. Therefore, some UC projects suspect it was a "cosmetic" change so they will keep an eye on how this evolves ... Therefore, we have to start working on it in a regular, constant, basis I commit to prepare a paper and presentation on how applications can be designed to take advantage of the integration of the different Data/Context Management GEs planned in Release 2 and the ability to support an Open Data approach. I will target a virtual workshop with UC projects on September 25th. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From nuria.delama at atosresearch.eu Thu Sep 20 15:20:51 2012 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Thu, 20 Sep 2012 15:20:51 +0200 Subject: [Fiware-wpl] Local and regional Infodays for the Second Open Call Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A0121EBF9@INTMAIL03.es.int.atosorigin.com> Dear all, (ANSWERS ONLY TO ME INCLUDING PEOPLE FROM TID IN CC; I WILL INTEGRATE THEM FOR THE PCC) As a follow up of an e-mail recently sent my Miguel on Local Infodays to promote the Second Open Call of FI-WARE I would like to inform you that I have had a discussion this morning with Ana Garc?a, of CONCORD just to work on the possible collaboration for the organization of such Infodays. This is very important because the Call is closing at the beginning of November and one of the comments of the EC in the last review was that we HAD TO further disseminate the Open Calls, widening the constituency and representing major countries in Europe. This topic was discussed in the last PCC meeting and some local Infodays are under preparation, but please, read this information and follow the instructions. ? FI-WARE should at least organize Infodays in Spain, France, Italy, Germany... ? I am aware of ongoing work for: o Infoday in Madrid ? already fixed on the 4th October o Infoday in France (Paris?) ? potential dates are 1st, 8th, 9th or 10th of October o Please, other members of the PCC ? can you please send me the details of your Infodays? Now, these are the additional opportunities CONCORD is offering (they will take care of the organization of the Infodays/events but will not cover the cost of travels) ? Spain o Bilbao (Basque Country) ? 8 or 9, October (supported by GAIA; potential audience of 300+ SMEs) o Castell?n ? 15, October (technology Park) o Action: TID, ATOS to confirm interest and availability for these dates ? UK (dates TBC) o Coventry o Manchester o Action: all partners (preference: UK-based partners) to confirm interest and their availability to discuss with CONCORD the organization ? Greece o Action: all partners to confirm interest and their availability in the coming weeks (especially important feedback by Italian partners) ? Belgium (a region different from Brussels) o Action: all partners to confirm interest and their availability in the coming weeks ? Helsinki o Action: all partners to confirm interest and their availability in the coming weeks ? Sweden (Lulea) o Action: all partners to confirm interest and their availability in the coming weeks Note that: ? Main goal is to present the Open Call and be able to answer questions (therefore, a technical speaker is desirable); ? Explaining as secondary goal the Open Innovation Lab and how to get involved later on could also be useful (for some SMEs) ? ALL partners have responsibility in this, so events will be assigned to the partners that are close to the venues if no volunteers Thanks for your collaboration. Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net ________________________________ ------------------------------------------------------------------ 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 nuria.delama at atosresearch.eu Fri Sep 21 09:55:21 2012 From: nuria.delama at atosresearch.eu (Nuria De-Lama Sanchez) Date: Fri, 21 Sep 2012 09:55:21 +0200 Subject: [Fiware-wpl] [INES] Segunda convocatoria FI-WARE Message-ID: <66E3B1FDDB04BE4D92DC3A2BA8D98D9A0121EE0B@INTMAIL03.es.int.atosorigin.com> Hi all, We are disseminating the Open Call of FI-WARE through many channels. Of course I did it internally in Atos so that our employees and colleagues can send it to other technology providers. Find below the dissemination through the Spanish Technology Platform INES (devoted to Software and Services), of course in Spanish.. I think it is important that all partners in the consortium do the same (regarding regional and national initiatives) that could widen the target audience of FI-WARE. This is not only useful for the purpose of the Open Call, but to make people aware of the project and have already a "seed" for community building. Please, keep us informed about your actions so that they can be reported later on. Thanks! Nuria de Lama Research & Innovation Representative to the European Commission T +34 91214 9321 F +34 91754 3252 nuria.delama at atosresearch.eu Albarrac?n 25 28037 Madrid Spain www.atosresearch.eu es.atos.net ________________________________ From: ines-miembros-bounces at lists.atosresearch.eu [mailto:ines-miembros-bounces at lists.atosresearch.eu] On Behalf Of Secretaria de Ines Sent: viernes, 21 de septiembre de 2012 9:00 To: Ines-miembros at lists.atosresearch.eu Subject: [Ines-miembros] Segunda convocatoria FI-WARE Al inter?s de los miembros de INES, El proyecto FI-WARE, ha puesto en marcha la segunda Convocatoria para la incorporaci?n de nuevos socios al proyecto. FI-WARE desarrollar? una nueva infraestructura de servicios, construida sobre bloques de c?digo gen?ricos y reutilizables llamados "Generic Enablers". En esta convocatoria se busca organizaciones que deseen contribuir o desarrollar los "Generic Enablers" relacionadas con las interfaces de usuarios, desarrollo y manejo de plataformas Cloud y transmisi?n y flujo de contenido. Inicio Convocatoria: Agosto 1, 2012 Cierre Convocatoria: Noviembre 7, 2012 Financiaci?n de la Convocatoria: 6 Millones de Euros Para obtener m?s informaci?n visite la Web: http://www.fi-ware.eu/open-call/ . Saludos. SECRETARIA DE INES Web: www.ines.org.es Email: sines at mail.atosresearch.eu ------------------------------------------------------------------ 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.emz Type: application/octet-stream Size: 4255 bytes Desc: image001.emz URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5220 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 78 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.gif Type: image/gif Size: 816 bytes Desc: image005.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.emz Type: application/octet-stream Size: 4255 bytes Desc: image006.emz URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 2312 bytes Desc: image007.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT2057319.txt URL: From jhierro at tid.es Mon Sep 24 10:46:21 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 24 Sep 2012 10:46:21 +0200 Subject: [Fiware-wpl] Shared minutes for our weekly joint WPLs/WPAs follow-up confcall Message-ID: <50601DDD.1070402@tid.es> Folks, Here you are the link to the shared minutes we are going to use during our confcall: https://docs.google.com/document/d/1VjL8cM0H5-OEzB_reY_Iyo2C1E6wTnXiQOTkpAleiQg/edit# Talk to you at 11:00am Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Sep 24 18:11:21 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 24 Sep 2012 18:11:21 +0200 Subject: [Fiware-wpl] Approach regarding the whitepaper document about FI-WARE including description of common usage scenarios of FI-WARE GEs In-Reply-To: <50607BD8.5010004@tid.es> References: <50607BD8.5010004@tid.es> Message-ID: <50608629.3010005@tid.es> Hi all, I'll try to describe the approach that we have agreed to follow, after some discussion during our regular confcall this morning, regarding development of the whitepaper document about FI-WARE including description of common usage scenarios of FI-WARE GEs. Thanks to all those who contributed with rather good ideas that have helped to improve the approach proposed initially. In this description I will also give more details about the general approach that I had in mind. I hope they will help to get a better clue of how the whitepaper / product-vision document may look like. The whitepaper would come as a result of reviewing the FI-WARE Product Vision, so that the following changes would be introduced: 1. Introduction would stay at it is now (see http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision). Note that it would provide a link to the "Overall FI-WARE Vision" where the basic concepts of FI-WARE would get introduced. 2. Regarding each chapter, we will keep for sure the "Overview" and "Terms and Definitions" section. We would essentially drop the contents linked to description of each individual GE that should go wherever it is appropriate in the Architecture Description of FI-WARE GEs (probably "Overview" and "Basic Concepts" sections) but we may also capture part of the description of each GE in the Overview section if suitable. 3. We will add per each of the chapters a number of sections each dealing with a description on how GEs in the chapter can be used or integrated, together or with other GEs from other chapters, in order to address a given common usage scenario. This sections will become "recipes" that a given application developer can read to understand how to address/solve a given scenario. Some of these scenarios will imply integration of GEs coming from several chapters, so we will have to make a choice regarding what is the chapter where description of the scenario will be more appropriate. Some examples of sections dealing with description of usage scenarios are the following (the title may change): * "Developing context-aware applications": here, we would elaborate on how several of the different GEs of the Data/Context Management chapter (particularly the Pub/Sub Broker GE, the CEP GE, the BigData GE, the Semantic Application Support GE and the Semantic Annotation Support GE) can be integrated together to support the notion of a "Context Managament Platform" that make it easier to develop context-aware applications. We would explain how data gathered by the Pub/Sub Broker GE may feed the CEP GE so that this last one can trigger actions based on detected scenarios, for example. We would also elaborate on how data generated by the CEP or the BigData GE may ultimately enrich context information, etc. The natural place where this section could fit is would be the chapter on Data/Context Management. * "Capturing data from the physical world and making it part of the context": here, we would elaborate on how data from sensors, captured through the IoT chapter GEs will feed the Context Broker, therefore the whole Context Management Platform we envision. We may place this section in any of the two chapters, the IoT or the Data chapter, but we would go for a compromise so that, for example, this section would go into the IoT chapter and would be referred from somewhere in the Data Chapter (for example, the section on "Developing context-aware applications" where we can mention that "part of the contextual information may come from physical objects. Check section on Capturing data from the physical world and making it part of the context" (text in blue would be link to the referred section) * "Supporting an Open Data approach": here, we would elaborate on how the envisioned Context Management Platform could be used to support an Open Data approach. We would elaborate on how organization willing to publish their data as open data would make that data available on a single Context Management platform linked to a FI-WARE Instance serving that purpose. We would also elaborate on how such FI-WARE Instance may bring GEs for the Apps chapter enabling services from the Context Management Platform to be published so that it becomes available to third parties and even end users ... Despite we would refer to GEs from the App Chapter, probably this section would fit more naturally as part of the Data/Context Management chapter, despite we may add a cross reference from the Apps Chapter * "Authenticaded access to APIs exported by FI-WARE GEs": here, we would elaborate on what architecture is supported that will enable authenticaded access control to APIs provided by the GEs, relying on usage of the Identity Management GE. The described architecture would be generic and should work for any GE, no matter what chapter it belongs to, but the description of the scenario would naturally fit as part of the Security chapter. * etc. 4. Telef?nica will come with a first draft of the FI-WARE Product Vision where we will drop out all those contents from the current FI-WARE Product Vision which will not longer be kept as part of the FI-WARE Product Vision. We will try that this draft be available by Wednesday EOB. Together with this first draft, we will come with a list of "usage scenario" / "recipe" sections that we would like to propose for each chapter. Once agreed with the corresponding chapter leader, it will be up to the chapter leader to organize the work as to deliver the final contents of each section. Note that development of some of this "recipe" sections may require contribution by more than one chapter so they have to organize how contents will be developed (for example, section on "Supporting an Open Data approach"). Our suggestion is that the chapter leaders take the responsibility of providing a first draft of the section and then the other complementary chapters perform a peer review (following the same example, the Data/Context Management leader would provide a first draft of the section titled "Supporting an Open Data approach" and then the Apps Chapter Leader should review it). 5. We will share the table of contents derived from previous points with UC projects and will check whether they feel like there is some "usage scenario" / "recipe" section that is missing. This would allow us to arrive at the review meeting with a document that has been validated by UC projects. Of course, we would work on a copy of the FI-WARE Product Vision we will setup on the FI-WARE Private Wiki. We will replace the current FI-WARE Product Vision once a solid version is already available (may not contain all the final sections but at least consistent with the FI-WARE Architecture Description and Open Specifications) Let me repeat again the rationale behind this approach: I may be wrong, but I believe that the reviewers look for something that is relatively stand-alone. Something someone may read to get a clear vision about what we are envisioning in FI-WARE without too many references to other parts of the FI-WARE documentation. In this respect, I believe it would be difficult to develop such a target whitepaper without repeating a lot of the good stuff that was already there in the FI-WARE Product Vision document (which, I remind you, got overall good acceptance by the reviewers). On the other hand, introducing references to contents of the FI-WARE Product Vision doesn't solve the problem because we have found that peopled ends not reading the referred contents and, besides, even those sections on the current FI-WARE Product Vision that are in the best shape would still require some update. Bottom line: it would be difficult to generate the target whitepaper without reviewing at least partially the FI-WARE Product Vision, at least to keep some consistency between the whitepaper and the FI-WARE Product Vision, so let's make it a single exercise. Your comments/feedback is welcome. I will come with specific input regarding point 3 by Wednesday this week. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Wed Sep 26 16:17:54 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Wed, 26 Sep 2012 16:17:54 +0200 Subject: [Fiware-wpl] FI-WARE-review Proposal for the Resubmission of Open Specifications Message-ID: <1491C91A94302A448D73CD9C6B7A782046C51DE362@DEWDFECCR02.wdf.sap.corp> Hi all, Actually I had planned to raise an additional issue in the WPL/WPA call yesterday, however, due to the other pressing topics there had not been enough to discuss it. Therefore I distribute it offline. Our suggestion concerns the following points: 1. We suggest to proactively adopted the central points raised by the reviewers by providing a new template & example page that addresses the issues. The new page is: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template the example page can be reached from this page by a link. The work is not finished and not all of the content in the example is stable, but due to timing constraints we would like to now start the discussion 2. on the following requirements, at which the new template is particularly aiming: a. Every open specification should be self contained b. Target audience is not only users, but as well people providing implementations of GEs, based on their open specifications c. Scope, behavior and intended use is documented d. Clear IPR statements & legal notices 3. We assume the proposed changes to be rather small and therefore we see a substantial chance that we might be able to implement them in due time quickly enough. 4. For the overall submission there needs to be a separate Adoption of the book-template, which would include as well standard sections like "Introductions" and "Appendixes" (details will follow) 5. It would not be possible to compile this template in such a quick way, without the great work that the TID team has already carried out. 6. Finally: There is a number of inconsistencies in the guidelines of currently in the FI-WARE-private wiki - these should be updated/marked as deprecated or deleted after consensus is found. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Common_aspects_in_FI-WARE_Open_Restful_API_Specifications https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/RESTful_API_specification_template The rationale behind these suggestions is that the reviewers clearly articulated that the Open Specifications in the submitted format were not sufficient in relation to the content being promised in the FI-WARE DoW. We regard this as one of the reasons why they were rejected and budget cuts were implemented. We analyzed the situation and come to the following conclusions: 1. The requirements stated in the DoW and outlined by the reviewers have to be accepted and subsequently there needs to be a resubmission in relation to the given criteria ASAP, if not until M18 2. The current submission included only the RESTful-API pages which lead to the situation that in deed there were major differences in proposed vs. submitted content 3. Although stated as planned in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions: "the Architecture deliverable will become an integral part of the final GE open specifications", this has never been submitted in this format to the commission, which finally lead to the bad review in relation to the this topic 4. We fear that even the 2nd review of the Open Specification is currently not sufficiently addressing major changes in the content and resubmission of the open specifications 5. Most of the requested content is already present in the wiki or in subsequent pages, but was not compiled in the right way and references was often missing. We hope to start a productive offline discussion by making these suggestions and hope for your feedback. Otherwise if you do not bring forward arguments against this suggestions we would assume that you generally agree with them and further urge for their implementation. Best regards, Thorsten & Uwe Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Sep 26 20:02:27 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 26 Sep 2012 20:02:27 +0200 Subject: [Fiware-wpl] FI-WARE-review Proposal for the Resubmission of Open Specifications In-Reply-To: <1491C91A94302A448D73CD9C6B7A782046C51DE362@DEWDFECCR02.wdf.sap.corp> References: <1491C91A94302A448D73CD9C6B7A782046C51DE362@DEWDFECCR02.wdf.sap.corp> Message-ID: <50634333.7050602@tid.es> Dear Uwe and Thorsten, Thanks for your valuable input. I rather appreciate this kind of pro-activeness in providing constructive concrete proposals (like this one) as compare to simply ranting about what is being proposed. It is nice because your proposal seems to be based on the same premise I was starting to suspect was right after recently carefully reviewing once again the review report, looking at some early results of some of the peer reviewers and considering what we have there on the public Wiki: Regarding specifications of each FI-WARE GE, I suspect that the reviewers were expecting something which could have been well covered by just delivering together (in the same document deliverable) the architecture description of the GE with the specifications of the APIs linked to that GE. This suspicion is somehow confirmed based on an informal conversation a third party (allow me not to disclose the source :-) has recently had with Arian. During this conversation, it seems like he was claiming that "Open Specifications of a given GE cannot be two pages long as they are" ... apparently Arian (and reviewers) didn't get the point that what we submitted was just the API specifications ... Because anyone reading those specifications was expected to have read the architecture description of the GE before. This person explained that the complete specifications of a FI-WARE GE was indeed made of the architecture description plus the Open API specifications and this apparently was a view that Arian hadn't taken into consideration (this was the feedback this person that talked to him has given to me). Assuming this is correct, it actually makes sense to "regenerate" the Open Specifications deliverable so that we "embed" the architecture description of each FI-WARE GE as part of the "Open Specifications of that GE". I thought this was actually difficult to implement because I though that Mediawiki didn't have any sort of "include" directive ... but you seem to have found the technical solution by means of using the {{:page_name_of_the_architecture_description}} functionality ... Great !! However, before taking a final decision and jumping on this direction, I would like to raise the following points and gather your feedback: * Do you believe that this is easier than trying to explain Arian and reviewers how the Architecture and Open Specification documentation was indeed structured in order to change their perception ? I tend to agree and think "let's not waste our time explaining how and why we had done things like we did, just give them what they want to see" ... However: * There is the risk that they realize that we were "copying" contents from one place to another (well, indeed referring inline) and then they come back to us saying "Hey ! you were trying to cheat us and spare efforts by copying things that belong to another deliverable" ... Do we like to risk that much ? * My answer would be that we shouldn't risk and, no matter whether we decide to go for adopting the new template, we should explain our view on the matter and tell them ... "look, this is the rationale of what we did and how you could collect the complete specification of a GE, but we can implement this artifact if that is more suitable to you so that one way or another you will get a complete specification". I believe one benefit of giving this explanation is that they hopefully would realize that we didn't do things that bad as they thought. Given said all this, we still need to finalize the peer review we are doing and start a second review. The feedback that I have got from some reviewers is that we also had many things to improve content-wise, so it is not ONLY a matter of "formatting" of the deliverable. What we need to agree on is whether the second review to carry out is something we should after adopting a template like the one you suggested or not. At a minimum, we should instruct peer reviewers to review the architecture description and API open specifications of each GE all together as part of the target complete specification. Comments/views are welcome. Cheers, -- Juanjo On 26/09/12 16:17, Riss, Uwe wrote: Hi all, Actually I had planned to raise an additional issue in the WPL/WPA call yesterday, however, due to the other pressing topics there had not been enough to discuss it. Therefore I distribute it offline. Our suggestion concerns the following points: 1. We suggest to proactively adopted the central points raised by the reviewers by providing a new template & example page that addresses the issues. The new page is: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template the example page can be reached from this page by a link. The work is not finished and not all of the content in the example is stable, but due to timing constraints we would like to now start the discussion 2. on the following requirements, at which the new template is particularly aiming: a. Every open specification should be self contained b. Target audience is not only users, but as well people providing implementations of GEs, based on their open specifications c. Scope, behavior and intended use is documented d. Clear IPR statements & legal notices 3. We assume the proposed changes to be rather small and therefore we see a substantial chance that we might be able to implement them in due time quickly enough. 4. For the overall submission there needs to be a separate Adoption of the book-template, which would include as well standard sections like "Introductions" and "Appendixes" (details will follow) 5. It would not be possible to compile this template in such a quick way, without the great work that the TID team has already carried out. 6. Finally: There is a number of inconsistencies in the guidelines of currently in the FI-WARE-private wiki - these should be updated/marked as deprecated or deleted after consensus is found. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Common_aspects_in_FI-WARE_Open_Restful_API_Specifications https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/RESTful_API_specification_template The rationale behind these suggestions is that the reviewers clearly articulated that the Open Specifications in the submitted format were not sufficient in relation to the content being promised in the FI-WARE DoW. We regard this as one of the reasons why they were rejected and budget cuts were implemented. We analyzed the situation and come to the following conclusions: 1. The requirements stated in the DoW and outlined by the reviewers have to be accepted and subsequently there needs to be a resubmission in relation to the given criteria ASAP, if not until M18 2. The current submission included only the RESTful-API pages which lead to the situation that in deed there were major differences in proposed vs. submitted content 3. Although stated as planned in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions: "the Architecture deliverable will become an integral part of the final GE open specifications", this has never been submitted in this format to the commission, which finally lead to the bad review in relation to the this topic 4. We fear that even the 2nd review of the Open Specification is currently not sufficiently addressing major changes in the content and resubmission of the open specifications 5. Most of the requested content is already present in the wiki or in subsequent pages, but was not compiled in the right way and references was often missing. We hope to start a productive offline discussion by making these suggestions and hope for your feedback. Otherwise if you do not bring forward arguments against this suggestions we would assume that you generally agree with them and further urge for their implementation. Best regards, Thorsten & Uwe Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Sep 28 08:53:51 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 28 Sep 2012 08:53:51 +0200 Subject: [Fiware-wpl] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Message-ID: <5065497F.9050006@tid.es> Hi all, I would need a explicit answer from every of you by EOB TODAY, so please don't forget to answer. According to Article II.23.8 of the grant agreement, we can make observations on the result of the review of our project within one month of reception of the review report letter (attached for your convenience) After the first and second peer-review of the FI-WARE Architecture and Open Specifications, not only me and TID but several of us have reached the conclusion that the reviewers didn't consider all the information that was already there on the Wik when they were evaluating the FI-WARE GE Open Specifications. Actually, architecture description of the GEs seem to be covering part of what the reviewers had expected in a complete specification. What we delivered as the deliverable didn't include this but was just what was needed to be provided, in addtion to what was already there as part of the FI-WARE Architecture Specifications, regarding specifications of APIs, languages, etc. In my honest opinion, we do not risk anything sending this observation because: * we would explain that: * we believe there were actually much more information regarding specifications of FI-WARE GEs than what the reviewers have evaluated (e.g., the part that was common to the FI-WARE Architecture documentation), and clarifying this should not be harmful but may help to explain we have actually worked hard in producing something complete * we recognize that we failed in explaining this when the open specifications were delivered, so we are actually recognizing it was not their fault that they didn't find the information. * we would also explain that we plan to resubmit the specifications so that the issue is solved and third parties do not fall also in the same problem (here, the kind of changes that were being proposed in a recent email by Uwe are in this direction) * last but not least, we would tell them that we are carrying out peer-reviews of the contents anyway, to make sure that content-wise, the specifications are as much complete as possible. Additionally, we may add that we are going to submit to them a report on how the different check-points are being addressed. This may help to reinforce we are taking their review report very much in consideration. The worst we can get is a 'not accepted". I don't believe that, if we deliver the right words, we will get any problem. I will come with a specific text proposal along this morning, but prior to do this, I would like to start collecting your feedback. I have copied the whole list of FI-WARE WPLs/WPAs since some of them may not be part of the FI-WARE PCC mailing list and I believe it was fair to let them object if they believe there are good reasons for doing so. I believe we don't need to involve the rest of the consortia since this a) would take too much time and b) IMHO is not that much a risk as stated above. Looking forward your quick answer Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Fri Sep 28 09:20:46 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 28 Sep 2012 09:20:46 +0200 Subject: [Fiware-wpl] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <5065497F.9050006@tid.es> References: <5065497F.9050006@tid.es> Message-ID: <50654FCE.1060703@eng.it> Dear Juanjo, provided that from Engineering side Stefano's word is the last one, I have no objections on this. However, keep into account that the exercise we did here in Engineering with the current FI-WARE results produced the same reviewers' outcomes. Then, I would strongly stress the following to points you raised: * to recognize that we failed in explaining this when the open specifications were delivered, so we are actually recognizing it was not their fault that they didn't find the information. * to explain that we plan to resubmit the specifications so that the issue is solved and third parties do not fall also in the same problem (here, the kind of changes that were being proposed in a recent email by Uwe are in this direction) My two cents. BR M. Il 28/09/2012 08:53, Juanjo Hierro ha scritto: > Hi all, > > I would need a explicit answer from every of you by EOB TODAY, so > please don't forget to answer. > > According to Article II.23.8 of the grant agreement, we can make > observations on the result of the review of our project within one > month of reception of the review report letter (attached for your > convenience) > > After the first and second peer-review of the FI-WARE Architecture > and Open Specifications, not only me and TID but several of us have > reached the conclusion that the reviewers didn't consider all the > information that was already there on the Wik when they were > evaluating the FI-WARE GE Open Specifications. Actually, > architecture description of the GEs seem to be covering part of what > the reviewers had expected in a complete specification. What we > delivered as the deliverable didn't include this but was just what was > needed to be provided, in addtion to what was already there as part of > the FI-WARE Architecture Specifications, regarding specifications of > APIs, languages, etc. > > In my honest opinion, we do not risk anything sending this > observation because: > > * we would explain that: > o we believe there were actually much more information regarding > specifications of FI-WARE GEs than what the reviewers have > evaluated (e.g., the part that was common to the FI-WARE > Architecture documentation), and clarifying this should not be > harmful but may help to explain we have actually worked hard > in producing something complete > o we recognize that we failed in explaining this when the open > specifications were delivered, so we are actually recognizing > it was not their fault that they didn't find the information. > * we would also explain that we plan to resubmit the specifications > so that the issue is solved and third parties do not fall also in > the same problem (here, the kind of changes that were being > proposed in a recent email by Uwe are in this direction) > * last but not least, we would tell them that we are carrying out > peer-reviews of the contents anyway, to make sure that > content-wise, the specifications are as much complete as possible. > > > Additionally, we may add that we are going to submit to them a > report on how the different check-points are being addressed. This may > help to reinforce we are taking their review report very much in > consideration. > > The worst we can get is a 'not accepted". I don't believe that, if > we deliver the right words, we will get any problem. > > I will come with a specific text proposal along this morning, but > prior to do this, I would like to start collecting your feedback. > > I have copied the whole list of FI-WARE WPLs/WPAs since some of them > may not be part of the FI-WARE PCC mailing list and I believe it was > fair to let them object if they believe there are good reasons for > doing so. I believe we don't need to involve the rest of the > consortia since this a) would take too much time and b) IMHO is not > that much a risk as stated above. > > Looking forward your quick answer > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From thierry.nagellen at orange.com Fri Sep 28 09:26:17 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 28 Sep 2012 07:26:17 +0000 Subject: [Fiware-wpl] [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <5065497F.9050006@tid.es> References: <5065497F.9050006@tid.es> Message-ID: <4833_1348817179_5065511A_4833_3526_1_976A65C5A08ADF49B9A8523F7F81925C06371F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Juanjo, We can send this comment to the reviewers but we really have to chose the right words because as a reviewer you have to evaluate the deliverables you receive for the deadline. What does it mean? In fact this is related to all discussions we had with the Commission that they want pdf files to clearly check what is the status for a dedicated milestone. So it is absolutely normal, from the review process point of view, that they evaluate only the pdf and not the wiki. What we can comment is, because the project is focusing on development and update regularly the wiki dedicated to external teams (UC projects but potentially other people), and as we explain at the review, the content was up to date and much more detailed than the pdf files. We can be surprised that this part was not evaluated because this is part of the agile process the project is using... But at the end, we delivered late the expected pdf (this a fact) and the content was poor regarding the content of the wiki for the review... and we have not to deliver something for the review because always based on the review process, reviewers must have the deliverables 15 days before for evaluation. My concern here is just to claim that we know the process but we did our best also to improve what was not at the right level and not to tell the Commission that they are wrong. BR Thierry De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 28 septembre 2012 08:54 ? : fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Hi all, I would need a explicit answer from every of you by EOB TODAY, so please don't forget to answer. According to Article II.23.8 of the grant agreement, we can make observations on the result of the review of our project within one month of reception of the review report letter (attached for your convenience) After the first and second peer-review of the FI-WARE Architecture and Open Specifications, not only me and TID but several of us have reached the conclusion that the reviewers didn't consider all the information that was already there on the Wik when they were evaluating the FI-WARE GE Open Specifications. Actually, architecture description of the GEs seem to be covering part of what the reviewers had expected in a complete specification. What we delivered as the deliverable didn't include this but was just what was needed to be provided, in addtion to what was already there as part of the FI-WARE Architecture Specifications, regarding specifications of APIs, languages, etc. In my honest opinion, we do not risk anything sending this observation because: * we would explain that: * we believe there were actually much more information regarding specifications of FI-WARE GEs than what the reviewers have evaluated (e.g., the part that was common to the FI-WARE Architecture documentation), and clarifying this should not be harmful but may help to explain we have actually worked hard in producing something complete * we recognize that we failed in explaining this when the open specifications were delivered, so we are actually recognizing it was not their fault that they didn't find the information. * we would also explain that we plan to resubmit the specifications so that the issue is solved and third parties do not fall also in the same problem (here, the kind of changes that were being proposed in a recent email by Uwe are in this direction) * last but not least, we would tell them that we are carrying out peer-reviews of the contents anyway, to make sure that content-wise, the specifications are as much complete as possible. Additionally, we may add that we are going to submit to them a report on how the different check-points are being addressed. This may help to reinforce we are taking their review report very much in consideration. The worst we can get is a 'not accepted". I don't believe that, if we deliver the right words, we will get any problem. I will come with a specific text proposal along this morning, but prior to do this, I would like to start collecting your feedback. I have copied the whole list of FI-WARE WPLs/WPAs since some of them may not be part of the FI-WARE PCC mailing list and I believe it was fair to let them object if they believe there are good reasons for doing so. I believe we don't need to involve the rest of the consortia since this a) would take too much time and b) IMHO is not that much a risk as stated above. Looking forward your quick answer Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Sep 28 13:59:05 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 28 Sep 2012 13:59:05 +0200 Subject: [Fiware-wpl] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <50658796.3030707@tid.es> References: <50658796.3030707@tid.es> Message-ID: <50659109.1010704@tid.es> Hi, This is the wording that I would propose (comments on wording, please accompanied with concrete editing proposals, are welcome): == Dear PO and reviewers, According to Article II.23.8 of the grant agreement, we can make observations on the result of the review of our project within one month of reception of the review report letter. This email elaborates on the observation we would like to submit regarding review of deliverables linked to Open Specifications. Right after reception of the review report, we have carried out a number of peer-reviews (still under way) targeted to answer the concerns expressed by reviewers. This is one activity we have assigned the highest priority because we agree with reviewers that there is a critical need to release a complete and comprehensive set of Generic Enabler (GE) Open Specifications in FI-WARE. In the review report, it is actually stated that the delivered Open Specifications were "inadequate for communication and unified understanding with the Use Case projects, are not of the required quality to serve the needs of those projects, and do not provide sufficient basis for practical implementation by software developers" One of the conclusions reached after the first peer-reviews that were conducted was that it seems like there may have been a mismatch between what reviewers were expecting to be the contents of each FI-WARE GE Chapter's Open Specification deliverable and what it was actually formally delivered, considering the deliverable standalone. However, this didn't mean that the missing contents were not already there on the public, published and available to the Use Case projects and the general public. FI-WARE deliverables were structured in a manner that would allow sharing information with Use Case projects as soon as it was available, without waiting for having all the details fixed. The complete Open Specification of a given FI-WARE GE comprises, following some best practices of existing standards, a table of contents like the following: 1. Overview * Introduction * Usage Example scenarios 2. Basic Concepts (this may include a description of the underlying conceptual model) 3. Reference Architecture 4. Main interactions * (here, a description of the external behavior exposed by the GE will be provided and this would be essentially covered by explaining how interactions with the GE, through the APIs it will support, are expected to work) 5. Basic Design Principles 6. Detailed Open API specifications 7. References The first 5 points and point 7 were provided as soon as possible making it part of the FI-WARE Architecture deliverable, because that way we could share with UC projects part of the specifications as soon as possible, without waiting for the finalization of the detailed API specifications. Therefore, when we delivered the FI-WARE GE Open Specifications deliverable we just submitted the Detailed Open API Specifications. Now we realize that we made a mistake not explaining this, but at least we would like to explain what we did, in the hope this will improve the overall judgement of the work that we did. In the light of this explanations we would also kindly ask the reviewers and PO to consider reduction of the costs rejection formula that was announced. Having said all this, we would like to share with you that we are anyway performing a deep peer-review of the contents of the specifications (considering the whole table of contents described above). Sure there are point to improve, and we have identified some of them already, so that we are implementing them as soon as possible. Besides this review of contents, we plan to re-structure the contents of the wiki so that we can produce a complete .pdf per each FI-WARE GE, comprising the table of contents above. We hope this will prevent other audience for getting the same impression as reviewers got. Best regards, == ------------- 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 On 28/09/12 08:53, Juanjo Hierro wrote: Hi all, I would need a explicit answer from every of you by EOB TODAY, so please don't forget to answer. According to Article II.23.8 of the grant agreement, we can make observations on the result of the review of our project within one month of reception of the review report letter (attached for your convenience) After the first and second peer-review of the FI-WARE Architecture and Open Specifications, not only me and TID but several of us have reached the conclusion that the reviewers didn't consider all the information that was already there on the Wik when they were evaluating the FI-WARE GE Open Specifications. Actually, architecture description of the GEs seem to be covering part of what the reviewers had expected in a complete specification. What we delivered as the deliverable didn't include this but was just what was needed to be provided, in addtion to what was already there as part of the FI-WARE Architecture Specifications, regarding specifications of APIs, languages, etc. In my honest opinion, we do not risk anything sending this observation because: * we would explain that: * we believe there were actually much more information regarding specifications of FI-WARE GEs than what the reviewers have evaluated (e.g., the part that was common to the FI-WARE Architecture documentation), and clarifying this should not be harmful but may help to explain we have actually worked hard in producing something complete * we recognize that we failed in explaining this when the open specifications were delivered, so we are actually recognizing it was not their fault that they didn't find the information. * we would also explain that we plan to resubmit the specifications so that the issue is solved and third parties do not fall also in the same problem (here, the kind of changes that were being proposed in a recent email by Uwe are in this direction) * last but not least, we would tell them that we are carrying out peer-reviews of the contents anyway, to make sure that content-wise, the specifications are as much complete as possible. Additionally, we may add that we are going to submit to them a report on how the different check-points are being addressed. This may help to reinforce we are taking their review report very much in consideration. The worst we can get is a 'not accepted". I don't believe that, if we deliver the right words, we will get any problem. I will come with a specific text proposal along this morning, but prior to do this, I would like to start collecting your feedback. I have copied the whole list of FI-WARE WPLs/WPAs since some of them may not be part of the FI-WARE PCC mailing list and I believe it was fair to let them object if they believe there are good reasons for doing so. I believe we don't need to involve the rest of the consortia since this a) would take too much time and b) IMHO is not that much a risk as stated above. Looking forward your quick answer Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ste.depanfilis at gmail.com Fri Sep 28 14:13:29 2012 From: ste.depanfilis at gmail.com (ste.depanfilis at gmail.com) Date: Fri, 28 Sep 2012 12:13:29 +0000 Subject: [Fiware-wpl] R: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <5065497F.9050006@tid.es> References: <5065497F.9050006@tid.es> Message-ID: <1231895006-1348833997-cardhu_decombobulator_blackberry.rim.net-934687620-@b17.c14.bise7.blackberry> Dear Juanjo and all, It is a surprise you ask us something so important not discussed at pcc to be approved so shortly ..... Although i psycologiacally agree with you, it is also very well true that by contract only "paper" is what matter, so i completely second thierry. Such a statement should not be sent it is dangerous and contractually wrong. Sorry but this is the true reality.... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-pcc-bounces at lists.fi-ware.eu Date: Fri, 28 Sep 2012 08:53:51 To: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow _______________________________________________ Fiware-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc From ste.depanfilis at gmail.com Fri Sep 28 14:38:33 2012 From: ste.depanfilis at gmail.com (ste.depanfilis at gmail.com) Date: Fri, 28 Sep 2012 12:38:33 +0000 Subject: [Fiware-wpl] R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <50659109.1010704@tid.es> References: <50658796.3030707@tid.es> <50659109.1010704@tid.es> Message-ID: <1342699893-1348835501-cardhu_decombobulator_blackberry.rim.net-1826196267-@b17.c14.bise7.blackberry> Dear Juanjo all, This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. The latter is the crucial point of interest of reviwers! Are we sure we cover it???? If YES this is what you have also to write! Btw all the cost will be accepted only after this i'm afraid Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Sender: fiware-pcc-bounces at lists.fi-ware.eu Date: Fri, 28 Sep 2012 13:59:05 To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow _______________________________________________ Fiware-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc From jhierro at tid.es Fri Sep 28 15:22:45 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 28 Sep 2012 15:22:45 +0200 Subject: [Fiware-wpl] R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <1342699893-1348835501-cardhu_decombobulator_blackberry.rim.net-1826196267-@b17.c14.bise7.blackberry> References: <50658796.3030707@tid.es> <50659109.1010704@tid.es> <1342699893-1348835501-cardhu_decombobulator_blackberry.rim.net-1826196267-@b17.c14.bise7.blackberry> Message-ID: <5065A4A5.4070604@tid.es> Dear Stefano, It is still unclear if you support sending this letter. We cannot send it if someone objects. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 14:38, ste.depanfilis at gmail.com wrote: > Dear Juanjo all, > > This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. > > The latter is the crucial point of interest of reviwers! > > Are we sure we cover it???? If YES this is what you have also to write! > > Btw all the cost will be accepted only after this i'm afraid > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-pcc-bounces at lists.fi-ware.eu > Date: Fri, 28 Sep 2012 13:59:05 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review > of FI-WARE within one month of reception of the review report letter EXPIRES > tomorrow > > _______________________________________________ > Fiware-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 ste.depanfilis at gmail.com Fri Sep 28 15:40:22 2012 From: ste.depanfilis at gmail.com (ste.depanfilis at gmail.com) Date: Fri, 28 Sep 2012 13:40:22 +0000 Subject: [Fiware-wpl] R: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <5065A4A5.4070604@tid.es> References: <50658796.3030707@tid.es> <50659109.1010704@tid.es> <1342699893-1348835501-cardhu_decombobulator_blackberry.rim.net-1826196267-@b17.c14.bise7.blackberry> <5065A4A5.4070604@tid.es> Message-ID: <309725654-1348839210-cardhu_decombobulator_blackberry.rim.net-1867440347-@b17.c14.bise7.blackberry> I support but those points should be adressed..... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Date: Fri, 28 Sep 2012 15:22:45 To: Cc: ; fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Dear Stefano, It is still unclear if you support sending this letter. We cannot send it if someone objects. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 14:38, ste.depanfilis at gmail.com wrote: > Dear Juanjo all, > > This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. > > The latter is the crucial point of interest of reviwers! > > Are we sure we cover it???? If YES this is what you have also to write! > > Btw all the cost will be accepted only after this i'm afraid > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-pcc-bounces at lists.fi-ware.eu > Date: Fri, 28 Sep 2012 13:59:05 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review > of FI-WARE within one month of reception of the review report letter EXPIRES > tomorrow > > _______________________________________________ > Fiware-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 pierangelo.garino at telecomitalia.it Fri Sep 28 16:55:04 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 28 Sep 2012 16:55:04 +0200 Subject: [Fiware-wpl] R: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Message-ID: I do agree with the comments by Stefano and Thierry. We cannot say they were wrong in the review of our deliverables, and we need to assure next deliveries will comply with the expected contents i.e. Specifications for GE users AND developers. Then we can say that the rejected ones were probably not well combined and presented, as most of that information was already present, but this needs to come later in the observations. Apologise i cannot contribute better to wording as I'm with the smartphone only , and with connection issues. Br Pier Inviato da Samsung Mobile -------- Original message -------- Subject: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow From: "ste.depanfilis at gmail.com" To: Juanjo Hierro CC: "fiware-wpa at lists.fi-ware.eu" ,"fiware-pcc at lists.fi-ware.eu" ,"fiware-pcc-bounces at lists.fi-ware.eu" ,"fiware-wpl at lists.fi-ware.eu" I support but those points should be adressed..... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Date: Fri, 28 Sep 2012 15:22:45 To: Cc: ; fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Dear Stefano, It is still unclear if you support sending this letter. We cannot send it if someone objects. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 14:38, ste.depanfilis at gmail.com wrote: > Dear Juanjo all, > > This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. > > The latter is the crucial point of interest of reviwers! > > Are we sure we cover it???? If YES this is what you have also to write! > > Btw all the cost will be accepted only after this i'm afraid > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-pcc-bounces at lists.fi-ware.eu > Date: Fri, 28 Sep 2012 13:59:05 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review > of FI-WARE within one month of reception of the review report letter EXPIRES > tomorrow > > _______________________________________________ > Fiware-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jhierro at tid.es Fri Sep 28 21:04:36 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 28 Sep 2012 21:04:36 +0200 Subject: [Fiware-wpl] R: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: References: Message-ID: <5065F4C4.6060204@tid.es> Hi all, Given the fact that we didn't reach enough consensus, also some people questioned the benefits of this against the risks and, last but not least, some members of the PCC didn't respond, we will finally not send a letter with observations. On another track, I was planning to send the PO and reviewers an email explaining how we are addressing the different checkpoints they setup, in order to demonstrate our engagement to deal with issues raised in the project review report and how things are progressing. I will share a draft of this message as soon as I get it finished so that we can all review it. But there is no a strict deadline for that as there was regarding sending observations. To all those who has responded this request, many thanks for your quick reaction and constructive comments. Have a nice weekend. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 16:55, Garino Pierangelo wrote: I do agree with the comments by Stefano and Thierry. We cannot say they were wrong in the review of our deliverables, and we need to assure next deliveries will comply with the expected contents i.e. Specifications for GE users AND developers. Then we can say that the rejected ones were probably not well combined and presented, as most of that information was already present, but this needs to come later in the observations. Apologise i cannot contribute better to wording as I'm with the smartphone only , and with connection issues. Br Pier Inviato da Samsung Mobile -------- Original message -------- Subject: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow From: "ste.depanfilis at gmail.com" To: Juanjo Hierro CC: "fiware-wpa at lists.fi-ware.eu" ,"fiware-pcc at lists.fi-ware.eu" ,"fiware-pcc-bounces at lists.fi-ware.eu" ,"fiware-wpl at lists.fi-ware.eu" I support but those points should be adressed..... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Date: Fri, 28 Sep 2012 15:22:45 To: Cc: ; fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Dear Stefano, It is still unclear if you support sending this letter. We cannot send it if someone objects. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 14:38, ste.depanfilis at gmail.com wrote: > Dear Juanjo all, > > This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. > > The latter is the crucial point of interest of reviwers! > > Are we sure we cover it???? If YES this is what you have also to write! > > Btw all the cost will be accepted only after this i'm afraid > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-pcc-bounces at lists.fi-ware.eu > Date: Fri, 28 Sep 2012 13:59:05 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review > of FI-WARE within one month of reception of the review report letter EXPIRES > tomorrow > > _______________________________________________ > Fiware-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From uwe.riss at sap.com Fri Sep 28 21:23:50 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Fri, 28 Sep 2012 21:23:50 +0200 Subject: [Fiware-wpl] [Fiware-pcc] R: R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <5065F4C4.6060204@tid.es> References: <5065F4C4.6060204@tid.es> Message-ID: <1491C91A94302A448D73CD9C6B7A782046C53FE6AC@DEWDFECCR02.wdf.sap.corp> Hi Juanjo, I fully support the approach that you suggest and will support it where possible. Thanks and have nice weekend, too. BR, Uwe From: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 28. September 2012 21:05 To: Garino Pierangelo Cc: fiware-pcc-bounces at lists.fi-ware.eu; ste.depanfilis at gmail.com; fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: Re: [Fiware-pcc] R: R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Hi all, Given the fact that we didn't reach enough consensus, also some people questioned the benefits of this against the risks and, last but not least, some members of the PCC didn't respond, we will finally not send a letter with observations. On another track, I was planning to send the PO and reviewers an email explaining how we are addressing the different checkpoints they setup, in order to demonstrate our engagement to deal with issues raised in the project review report and how things are progressing. I will share a draft of this message as soon as I get it finished so that we can all review it. But there is no a strict deadline for that as there was regarding sending observations. To all those who has responded this request, many thanks for your quick reaction and constructive comments. Have a nice weekend. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 16:55, Garino Pierangelo wrote: I do agree with the comments by Stefano and Thierry. We cannot say they were wrong in the review of our deliverables, and we need to assure next deliveries will comply with the expected contents i.e. Specifications for GE users AND developers. Then we can say that the rejected ones were probably not well combined and presented, as most of that information was already present, but this needs to come later in the observations. Apologise i cannot contribute better to wording as I'm with the smartphone only , and with connection issues. Br Pier Inviato da Samsung Mobile -------- Original message -------- Subject: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow From: "ste.depanfilis at gmail.com" To: Juanjo Hierro CC: "fiware-wpa at lists.fi-ware.eu" ,"fiware-pcc at lists.fi-ware.eu" ,"fiware-pcc-bounces at lists.fi-ware.eu" ,"fiware-wpl at lists.fi-ware.eu" I support but those points should be adressed..... Ciao Stefano Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! -----Original Message----- From: Juanjo Hierro Date: Fri, 28 Sep 2012 15:22:45 To: Cc: ; fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow Dear Stefano, It is still unclear if you support sending this letter. We cannot send it if someone objects. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/09/12 14:38, ste.depanfilis at gmail.com wrote: > Dear Juanjo all, > > This text better, but still you should say, if true, that our specifications are meant to serve both users of ges, but also developers of ges. > > The latter is the crucial point of interest of reviwers! > > Are we sure we cover it???? If YES this is what you have also to write! > > Btw all the cost will be accepted only after this i'm afraid > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Sender: fiware-pcc-bounces at lists.fi-ware.eu > Date: Fri, 28 Sep 2012 13:59:05 > To: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the result of the review > of FI-WARE within one month of reception of the review report letter EXPIRES > tomorrow > > _______________________________________________ > Fiware-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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-pcc mailing list Fiware-pcc at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-pcc 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 matteo.melideo at eng.it Fri Sep 28 22:21:58 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 28 Sep 2012 22:21:58 +0200 Subject: [Fiware-wpl] [Fiware-pcc] R: R: Re: R: Re: VERY URGENT: Observations on the result of the review of FI-WARE within one month of reception of the review report letter EXPIRES tomorrow In-Reply-To: <1491C91A94302A448D73CD9C6B7A782046C53FE6AC@DEWDFECCR02.wdf.sap.corp> References: <5065F4C4.6060204@tid.es> <1491C91A94302A448D73CD9C6B7A782046C53FE6AC@DEWDFECCR02.wdf.sap.corp> Message-ID: <506606E6.6070706@eng.it> +1 BR M. Il 28/09/2012 21:23, Riss, Uwe ha scritto: > > Hi Juanjo, > > I fully support the approach that you suggest and will support it > where possible. > > Thanks and have nice weekend, too. > > BR, Uwe > > *From:*fiware-pcc-bounces at lists.fi-ware.eu > [mailto:fiware-pcc-bounces at lists.fi-ware.eu] *On Behalf Of *Juanjo Hierro > *Sent:* Freitag, 28. September 2012 21:05 > *To:* Garino Pierangelo > *Cc:* fiware-pcc-bounces at lists.fi-ware.eu; ste.depanfilis at gmail.com; > fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; > fiware-wpl at lists.fi-ware.eu > *Subject:* Re: [Fiware-pcc] R: R: Re: R: Re: VERY URGENT: Observations > on the result of the review of FI-WARE within one month of reception > of the review report letter EXPIRES tomorrow > > Hi all, > > Given the fact that we didn't reach enough consensus, also some > people questioned the benefits of this against the risks and, last but > not least, some members of the PCC didn't respond, we will finally not > send a letter with observations. > > On another track, I was planning to send the PO and reviewers an > email explaining how we are addressing the different checkpoints they > setup, in order to demonstrate our engagement to deal with issues > raised in the project review report and how things are progressing. > I will share a draft of this message as soon as I get it finished so > that we can all review it. But there is no a strict deadline for > that as there was regarding sending observations. > > To all those who has responded this request, many thanks for your > quick reaction and constructive comments. > > Have a nice weekend. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > On 28/09/12 16:55, Garino Pierangelo wrote: > > I do agree with the comments by Stefano and Thierry. > > We cannot say they were wrong in the review of our deliverables, > and we need to assure next deliveries will comply with the > expected contents i.e. Specifications for GE users AND developers. > Then we can say that the rejected ones were probably not well > combined and presented, as most of that information was already > present, but this needs to come later in the observations. > > Apologise i cannot contribute better to wording as I'm with the > smartphone only , and with connection issues. > > Br > > Pier > > Inviato da Samsung Mobile > > > > > -------- Original message -------- > Subject: [Fiware-pcc] R: Re: R: Re: VERY URGENT: Observations on > the result of the review of FI-WARE within one month of reception > of the review report letter EXPIRES tomorrow > From: "ste.depanfilis at gmail.com" > > To: Juanjo Hierro > CC: "fiware-wpa at lists.fi-ware.eu" > > ,"fiware-pcc at lists.fi-ware.eu" > > ,"fiware-pcc-bounces at lists.fi-ware.eu" > > > ,"fiware-wpl at lists.fi-ware.eu" > > > > I support but those points should be adressed..... > > Ciao > Stefano > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > -----Original Message----- > From: Juanjo Hierro > Date: Fri, 28 Sep 2012 15:22:45 > To: > Cc: > ; > fiware-pcc at lists.fi-ware.eu > > ; fiware-wpl at lists.fi-ware.eu > > ; fiware-wpa at lists.fi-ware.eu > > > Subject: Re: R: Re: [Fiware-pcc] VERY URGENT: Observations on the > result of the > review of FI-WARE within one month of reception of the review > report letter > EXPIRES tomorrow > > Dear Stefano, > > It is still unclear if you support sending this letter. We cannot > send it if someone objects. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 28/09/12 14:38, ste.depanfilis at gmail.com > wrote: > > Dear Juanjo all, > > > > This text better, but still you should say, if true, that our > specifications are meant to serve both users of ges, but also > developers of ges. > > > > The latter is the crucial point of interest of reviwers! > > > > Are we sure we cover it???? If YES this is what you have also to > write! > > > > Btw all the cost will be accepted only after this i'm afraid > > > > Ciao > > Stefano > > > > Le mail ti raggiungono ovunque con BlackBerry? from Vodafone! > > > > -----Original Message----- > > From: Juanjo Hierro > > Sender: fiware-pcc-bounces at lists.fi-ware.eu > > > Date: Fri, 28 Sep 2012 13:59:05 > > To: fiware-pcc at lists.fi-ware.eu > > ; fiware-wpl at lists.fi-ware.eu > > ; fiware-wpa at lists.fi-ware.eu > > > > Subject: Re: [Fiware-pcc] VERY URGENT: Observations on the > result of the review > > of FI-WARE within one month of reception of the review report > letter EXPIRES > > tomorrow > > > > _______________________________________________ > > Fiware-pcc mailing list > > Fiware-pcc at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware-pcc > > > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo > electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its 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-pcc mailing list > Fiware-pcc at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-pcc > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra > azione derivante dalla conoscenza di queste informazioni sono > rigorosamente vietate. Qualora abbiate ricevuto questo documento > per errore siete cortesemente pregati di darne immediata > comunicazione al mittente e di provvedere alla sua distruzione, > Grazie. > > /This e-mail and any attachments //is// confidential and may > contain privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is > unauthorised. If you are not the intended recipient, please delete > this message and any attachments and advise the sender by return > e-mail, Thanks./ > > *rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail > se non ? necessario.* > > ------------------------------------------------------------------------ > > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: