From jeanpierre.lerouzic at orange.com Mon Jul 2 14:54:26 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Mon, 2 Jul 2012 12:54:26 +0000 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <4FF19873.3040904@eng.it> References: <4FF19873.3040904@eng.it> Message-ID: <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> Dear Matteo, I am the owner of API mediation and WSC enablers. The API mediation enabler code could be find here: https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 The WSC code is intended to be delivered in a few months. Please let me know what is the issue with those two enablers and what you want me to do. Best regards, Jean-Pierre De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Matteo Melideo Envoy? : lundi 2 juillet 2012 14:48 ? : fiware at lists.fi-ware.eu Cc : WP9_fi-ware Objet : [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear All, sorry for spamming you with this mail. The catalogue is now going to be filled with real GEs with the goal to be fully ready by the end of July with all the GEs available in the testbed. In this respect, there are currently in the catalogue three GEs that needs some revisions. Namely: - API Mediation - Service Description Repository - WSC. I would kindly ask the owner of these GEs to contact me or the Wp9 mailing list for further clarifications. Thanks a lot and regards, Matteo Melideo P.S: Further info about the catalogue can be found at the public page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue _________________________________________________________________________________________________________________________ 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 jeanpierre.lerouzic at orange.com Mon Jul 2 17:31:02 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Mon, 2 Jul 2012 15:31:02 +0000 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <4FF19D9D.4070808@eng.it> References: <4FF19873.3040904@eng.it> <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF19D9D.4070808@eng.it> Message-ID: <23436_1341243064_4FF1BEB8_23436_3_1_AE39E5C17FB7AF45883102E30247E3C3EF58@PEXCVZYM12.corporate.adroot.infra.ftgroup> Dear all, Please find the Word document filled included file. I improved a bit the documentation on the Ericsson site. Please let me know of any issues. Best regards, Jean-Pierre De : Matteo Melideo [mailto:matteo.melideo at eng.it] Envoy? : lundi 2 juillet 2012 15:10 ? : LE ROUZIC Jean-Pierre RD-MAPS Cc : Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu; John Sandberg Objet : Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear Jean-Pierre, first of all thank you very much for the prompt reply and your effort in populating the catalogue. If you go now to the catalogue portal you will see that other information is requested for each GE: the belonging Chapter, the Contact Person and the Contact details. In addition to this, as you already have the code, it could be extremely useful to provide also some additional description about the software provided. How to use it, some reference documentation, some code example. In this respect, please find the attached questionnaire that could be extremely useful to understand what we are looking for. Here it is important to provide the selling value of your GEs rather than a replication of what already available on the wiki. Here the USe Case projects should find info that convince them to use your GE and push others to do the same. Please do not hesitate to ask the support from me or Ericsson people reading in CC. Thanks 1000 again and regards Matteo Il 02/07/2012 14:54, jeanpierre.lerouzic at orange.com ha scritto: Dear Matteo, I am the owner of API mediation and WSC enablers. The API mediation enabler code could be find here: https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 The WSC code is intended to be delivered in a few months. Please let me know what is the issue with those two enablers and what you want me to do. Best regards, Jean-Pierre De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Matteo Melideo Envoy? : lundi 2 juillet 2012 14:48 ? : fiware at lists.fi-ware.eu Cc : WP9_fi-ware Objet : [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear All, sorry for spamming you with this mail. The catalogue is now going to be filled with real GEs with the goal to be fully ready by the end of July with all the GEs available in the testbed. In this respect, there are currently in the catalogue three GEs that needs some revisions. Namely: - API Mediation - Service Description Repository - WSC. I would kindly ask the owner of these GEs to contact me or the Wp9 mailing list for further clarifications. Thanks a lot and regards, Matteo Melideo P.S: Further info about the catalogue can be found at the public page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Questions for GE providers-v2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 17742 bytes Desc: Questions for GE providers-v2.docx URL: From matteo.melideo at eng.it Mon Jul 2 15:09:49 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 02 Jul 2012 15:09:49 +0200 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <4FF19873.3040904@eng.it> <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <4FF19D9D.4070808@eng.it> Dear Jean-Pierre, first of all thank you very much for the prompt reply and your effort in populating the catalogue. If you go now to the catalogue portal you will see that other information is requested for each GE: the belonging Chapter, the Contact Person and the Contact details. In addition to this, as you already have the code, it could be extremely useful to provide also some additional description about the software provided. How to use it, some reference documentation, some code example. In this respect, please find the attached questionnaire that could be extremely useful to understand what we are looking for. Here it is important to provide the selling value of your GEs rather than a replication of what already available on the wiki. Here the USe Case projects should find info that convince them to use your GE and push others to do the same. Please do not hesitate to ask the support from me or Ericsson people reading in CC. Thanks 1000 again and regards Matteo Il 02/07/2012 14:54, jeanpierre.lerouzic at orange.com ha scritto: > > Dear Matteo, > > I am the owner of API mediation and WSC enablers. > > The API mediation enabler code could be find here: > https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 > > The WSC code is intended to be delivered in a few months. > > Please let me know what is the issue with those two enablers and what > you want me to do. > > Best regards, > > Jean-Pierre > > *De :*fiware-bounces at lists.fi-ware.eu > [mailto:fiware-bounces at lists.fi-ware.eu] *De la part de* Matteo Melideo > *Envoy? :* lundi 2 juillet 2012 14:48 > *? :* fiware at lists.fi-ware.eu > *Cc :* WP9_fi-ware > *Objet :* [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear All, > sorry for spamming you with this mail. > The catalogue is now going to be filled with real GEs with the goal to > be fully ready by the end of July with all the GEs available in the > testbed. > > In this respect, there are currently in the catalogue three GEs that > needs some revisions. Namely: > - API Mediation > - Service Description Repository > - WSC. > > I would kindly ask the owner of these GEs to contact me or the Wp9 > mailing list for further clarifications. > > Thanks a lot and regards, > > Matteo Melideo > > P.S: > Further info about the catalogue can be found at the public page: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > _______________________________________________ > Fiware mailing list > Fiware at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Questions for GE providers-v2.doc Type: application/msword Size: 29184 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 matteo.melideo at eng.it Tue Jul 3 10:55:39 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Tue, 03 Jul 2012 10:55:39 +0200 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <23436_1341243064_4FF1BEB8_23436_3_1_AE39E5C17FB7AF45883102E30247E3C3EF58@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <4FF19873.3040904@eng.it> <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF19D9D.4070808@eng.it> <23436_1341243064_4FF1BEB8_23436_3_1_AE39E5C17FB7AF45883102E30247E3C3EF58@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <4FF2B38B.9040003@eng.it> Dear Jean-Pierre, thank you very much indeed. I have done some additional modifications to the description you provided in the Catalogue. Please have a look. I would also specify a reasonable date to know when the instance will be available in the testbed. It could be helpful for the interested developers. Concerning the questionnaires I have some questions and for a matter of convenience I have put some comments on your questionnaire, ok? (see attached file) I do apologise for the ignorance and some trivial questions but this is not my knowledge area at all :-( Thanks again and regards M. Il 02/07/2012 17:31, jeanpierre.lerouzic at orange.com ha scritto: > > Dear all, > > Please find the Word document filled included file. > > I improved a bit the documentation on the Ericsson site. > > Please let me know of any issues. > > Best regards, > > Jean-Pierre > > *De :*Matteo Melideo [mailto:matteo.melideo at eng.it] > *Envoy? :* lundi 2 juillet 2012 15:10 > *? :* LE ROUZIC Jean-Pierre RD-MAPS > *Cc :* Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu; John Sandberg > *Objet :* Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear Jean-Pierre, > first of all thank you very much for the prompt reply and your effort > in populating the catalogue. > If you go now to the catalogue portal you will see that other > information is requested for each GE: the belonging Chapter, the > Contact Person and the Contact details. > > In addition to this, as you already have the code, it could be > extremely useful to provide also some additional description about the > software provided. > How to use it, some reference documentation, some code example. In > this respect, please find the attached questionnaire that could be > extremely useful to understand what we are looking for. > > Here it is important to provide the selling value of your GEs rather > than a replication of what already available on the wiki. Here the USe > Case projects should find info that convince them to use your GE and > push others to do the same. > > Please do not hesitate to ask the support from me or Ericsson people > reading in CC. > > Thanks 1000 again and regards > > Matteo > > Il 02/07/2012 14:54, jeanpierre.lerouzic at orange.com > ha scritto: > > Dear Matteo, > > I am the owner of API mediation and WSC enablers. > > The API mediation enabler code could be find here: > https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 > > The WSC code is intended to be delivered in a few months. > > Please let me know what is the issue with those two enablers and > what you want me to do. > > Best regards, > > Jean-Pierre > > *De :*fiware-bounces at lists.fi-ware.eu > > [mailto:fiware-bounces at lists.fi-ware.eu] *De la part de* Matteo > Melideo > *Envoy? :* lundi 2 juillet 2012 14:48 > *? :* fiware at lists.fi-ware.eu > *Cc :* WP9_fi-ware > *Objet :* [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear All, > sorry for spamming you with this mail. > The catalogue is now going to be filled with real GEs with the > goal to be fully ready by the end of July with all the GEs > available in the testbed. > > In this respect, there are currently in the catalogue three GEs > that needs some revisions. Namely: > - API Mediation > - Service Description Repository > - WSC. > > I would kindly ask the owner of these GEs to contact me or the Wp9 > mailing list for further clarifications. > > Thanks a lot and regards, > > Matteo Melideo > > P.S: > Further info about the catalogue can be found at the public page: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > > > _______________________________________________ > > Fiware mailing list > > Fiware at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Questions for GE providers-v2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 17170 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 pierangelo.garino at telecomitalia.it Wed Jul 4 10:19:51 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 4 Jul 2012 10:19:51 +0200 Subject: [Fiware-i2nd] R: Periodic I2ND call Message-ID: Dear All, Tomorrow we'll have the usual PhC devoted to I2ND chapter, although I'm aware some of you is involved in the Future Network Summit currently held in Berlin. Proposed agenda includes the items: * Review of Action Plan (Features description, Technical roadmap, etc), along with updated guidelines * Status of GE activities (please each Task/GE coord to shortly report on what is on going, highlighting issues which need to be addressed jointly within the Chapter) * AOB Talk to you tomorrow! Pier -----Appuntamento originale----- Da: Garino Pierangelo Inviato: venerd? 13 aprile 2012 17:29 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Cc: Wuenstel, Klaus (Klaus); andi at dis.uniroma1.it; Banniza, Thomas-Rolf (Thomas-Rolf); Kurt Essigmann; Woods, Chris; Henrik Abramowicz; jeanpierre.lerouzic at orange.com; Roman.Szczepanski at telekom.de; Corici, Marius-Iulian Oggetto: Periodic I2ND call Data: gioved? 5 luglio 2012 10:00-11:30 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Percorso: PhC (new) Reminder for periodic I2ND audioconference. Below are listed the call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com << File: USA_en_pwn-dial-in-numbers.pdf >> BR Pier 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 jeanpierre.lerouzic at orange.com Thu Jul 5 14:04:31 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 5 Jul 2012 12:04:31 +0000 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <4FF2B38B.9040003@eng.it> References: <4FF19873.3040904@eng.it> <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF19D9D.4070808@eng.it> <23436_1341243064_4FF1BEB8_23436_3_1_AE39E5C17FB7AF45883102E30247E3C3EF58@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF2B38B.9040003@eng.it> Message-ID: <13537_1341489872_4FF582D0_13537_59_2_AE39E5C17FB7AF45883102E30247E3C3F73A@PEXCVZYM12.corporate.adroot.infra.ftgroup> Dear all, I added answers (I hope !) in the comments, they are tagged with [JPLR] plus some text. The main thing is that API mediation doesn't expose any of its APIs because it's a mediation layer between an API provider and an API consumer. https://en.wikipedia.org/wiki/API_Management For example AT&T uses Apigee's commercial solution for managing its customer API usage and its third parties that are API providers. This is a complex ecosystem where for example (not sure if it's the case) Google could charge AT&T if too much AT&T customers use Google's Maps API. So AT&T needs some need to regulate API usage by its customers. What we provide is doing more or less the same functionality. Don't hesitate to ask any further question. Best regards, Jean-Pierre De : Matteo Melideo [mailto:matteo.melideo at eng.it] Envoy? : mardi 3 juillet 2012 10:56 ? : LE ROUZIC Jean-Pierre RD-MAPS Cc : Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu; John Sandberg; Garino Pierangelo Objet : Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear Jean-Pierre, thank you very much indeed. I have done some additional modifications to the description you provided in the Catalogue. Please have a look. I would also specify a reasonable date to know when the instance will be available in the testbed. It could be helpful for the interested developers. Concerning the questionnaires I have some questions and for a matter of convenience I have put some comments on your questionnaire, ok? (see attached file) I do apologise for the ignorance and some trivial questions but this is not my knowledge area at all :-( Thanks again and regards M. Il 02/07/2012 17:31, jeanpierre.lerouzic at orange.com ha scritto: Dear all, Please find the Word document filled included file. I improved a bit the documentation on the Ericsson site. Please let me know of any issues. Best regards, Jean-Pierre De : Matteo Melideo [mailto:matteo.melideo at eng.it] Envoy? : lundi 2 juillet 2012 15:10 ? : LE ROUZIC Jean-Pierre RD-MAPS Cc : Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu; John Sandberg Objet : Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear Jean-Pierre, first of all thank you very much for the prompt reply and your effort in populating the catalogue. If you go now to the catalogue portal you will see that other information is requested for each GE: the belonging Chapter, the Contact Person and the Contact details. In addition to this, as you already have the code, it could be extremely useful to provide also some additional description about the software provided. How to use it, some reference documentation, some code example. In this respect, please find the attached questionnaire that could be extremely useful to understand what we are looking for. Here it is important to provide the selling value of your GEs rather than a replication of what already available on the wiki. Here the USe Case projects should find info that convince them to use your GE and push others to do the same. Please do not hesitate to ask the support from me or Ericsson people reading in CC. Thanks 1000 again and regards Matteo Il 02/07/2012 14:54, jeanpierre.lerouzic at orange.com ha scritto: Dear Matteo, I am the owner of API mediation and WSC enablers. The API mediation enabler code could be find here: https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 The WSC code is intended to be delivered in a few months. Please let me know what is the issue with those two enablers and what you want me to do. Best regards, Jean-Pierre De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Matteo Melideo Envoy? : lundi 2 juillet 2012 14:48 ? : fiware at lists.fi-ware.eu Cc : WP9_fi-ware Objet : [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue Dear All, sorry for spamming you with this mail. The catalogue is now going to be filled with real GEs with the goal to be fully ready by the end of July with all the GEs available in the testbed. In this respect, there are currently in the catalogue three GEs that needs some revisions. Namely: - API Mediation - Service Description Repository - WSC. I would kindly ask the owner of these GEs to contact me or the Wp9 mailing list for further clarifications. Thanks a lot and regards, Matteo Melideo P.S: Further info about the catalogue can be found at the public page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Questions for GE providers-v2 (2).doc Type: application/msword Size: 30720 bytes Desc: Questions for GE providers-v2 (2).doc URL: From matteo.melideo at eng.it Thu Jul 5 14:44:21 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 05 Jul 2012 14:44:21 +0200 Subject: [Fiware-i2nd] [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue In-Reply-To: <13537_1341489872_4FF582D0_13537_59_2_AE39E5C17FB7AF45883102E30247E3C3F73A@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <4FF19873.3040904@eng.it> <2244_1341233667_4FF19A03_2244_3849_2_AE39E5C17FB7AF45883102E30247E3C3E62D@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF19D9D.4070808@eng.it> <23436_1341243064_4FF1BEB8_23436_3_1_AE39E5C17FB7AF45883102E30247E3C3EF58@PEXCVZYM12.corporate.adroot.infra.ftgroup> <4FF2B38B.9040003@eng.it> <13537_1341489872_4FF582D0_13537_59_2_AE39E5C17FB7AF45883102E30247E3C3F73A@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <4FF58C25.60203@eng.it> Dear Jean-Pierre, thanks a lot and regards, M. Il 05/07/2012 14:04, jeanpierre.lerouzic at orange.com ha scritto: > > Dear all, > > I added answers (I hope !) in the comments, they are tagged with > [JPLR] plus some text. > > The main thing is that API mediation doesn?t expose any of its APIs > because it?s a mediation layer between an API provider and an API > consumer. > > https://en.wikipedia.org/wiki/API_Management > > For example AT&T uses Apigee?s commercial solution for managing its > customer API usage and its third parties that are API providers. > > This is a complex ecosystem where for example (not sure if it?s the > case) Google could charge AT&T if too much AT&T customers use Google?s > Maps API. So AT&T needs some need to regulate API usage by its > customers. What we provide is doing more or less the same functionality. > > Don?t hesitate to ask any further question. > > Best regards, > > Jean-Pierre > > *De :*Matteo Melideo [mailto:matteo.melideo at eng.it] > *Envoy? :* mardi 3 juillet 2012 10:56 > *? :* LE ROUZIC Jean-Pierre RD-MAPS > *Cc :* Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu; John > Sandberg; Garino Pierangelo > *Objet :* Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear Jean-Pierre, > thank you very much indeed. > I have done some additional modifications to the description you > provided in the Catalogue. Please have a look. > I would also specify a reasonable date to know when the instance will > be available in the testbed. It could be helpful for the interested > developers. > > Concerning the questionnaires I have some questions and for a matter > of convenience I have put some comments on your questionnaire, ok? > (see attached file) > > I do apologise for the ignorance and some trivial questions but this > is not my knowledge area at all :-( > > Thanks again and regards > > M. > > Il 02/07/2012 17:31, jeanpierre.lerouzic at orange.com > ha scritto: > > Dear all, > > Please find the Word document filled included file. > > I improved a bit the documentation on the Ericsson site. > > Please let me know of any issues. > > Best regards, > > Jean-Pierre > > *De :*Matteo Melideo [mailto:matteo.melideo at eng.it] > *Envoy? :* lundi 2 juillet 2012 15:10 > *? :* LE ROUZIC Jean-Pierre RD-MAPS > *Cc :* Mattias Wallenberg; fiware-i2nd at lists.fi-ware.eu > ; John Sandberg > *Objet :* Re: [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear Jean-Pierre, > first of all thank you very much for the prompt reply and your > effort in populating the catalogue. > If you go now to the catalogue portal you will see that other > information is requested for each GE: the belonging Chapter, the > Contact Person and the Contact details. > > In addition to this, as you already have the code, it could be > extremely useful to provide also some additional description about > the software provided. > How to use it, some reference documentation, some code example. In > this respect, please find the attached questionnaire that could be > extremely useful to understand what we are looking for. > > Here it is important to provide the selling value of your GEs > rather than a replication of what already available on the wiki. > Here the USe Case projects should find info that convince them to > use your GE and push others to do the same. > > Please do not hesitate to ask the support from me or Ericsson > people reading in CC. > > Thanks 1000 again and regards > > Matteo > > Il 02/07/2012 14:54, jeanpierre.lerouzic at orange.com > ha scritto: > > Dear Matteo, > > I am the owner of API mediation and WSC enablers. > > The API mediation enabler code could be find here: > https://forge.fi-ware.eu/frs/?group_id=10&release_id=47 > > The WSC code is intended to be delivered in a few months. > > Please let me know what is the issue with those two enablers > and what you want me to do. > > Best regards, > > Jean-Pierre > > *De :*fiware-bounces at lists.fi-ware.eu > > [mailto:fiware-bounces at lists.fi-ware.eu] *De la part de* > Matteo Melideo > *Envoy? :* lundi 2 juillet 2012 14:48 > *? :* fiware at lists.fi-ware.eu > *Cc :* WP9_fi-ware > *Objet :* [Fiware] *** IMPORTANT ** About the FI-WARE Catalogue > > Dear All, > sorry for spamming you with this mail. > The catalogue is now going to be filled with real GEs with the > goal to be fully ready by the end of July with all the GEs > available in the testbed. > > In this respect, there are currently in the catalogue three > GEs that needs some revisions. Namely: > - API Mediation > - Service Description Repository > - WSC. > > I would kindly ask the owner of these GEs to contact me or the > Wp9 mailing list for further clarifications. > > Thanks a lot and regards, > > Matteo Melideo > > P.S: > Further info about the catalogue can be found at the public > page: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > > > > _______________________________________________ > > Fiware mailing list > > Fiware at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware > > _________________________________________________________________________________________________________________________ > > > > 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. > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 368 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Fri Jul 6 12:00:48 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 6 Jul 2012 12:00:48 +0200 Subject: [Fiware-i2nd] Remarks on Release/Sprint numbering, Feature/User Stories etc Message-ID: Hi All, as agreed in the call yesterday, here I forward you some remarks derived from a mail exchange with Thomas, about Sprints, Releases etc. Please have a look and provide further comments and/or clarifications if necessary. General remarks: * First of all: please read again the page on methodology at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology to gather more confidence with it and maybe discover further interesting details. * A sprint lasts for one month, a release lasts between two and four sprints (i.e. two to four months). * The correct release/sprint numbering can be found at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering If an EPIC/feature/user story/work item is 'under execution' (that means you are working on it), the following applies: * A user story is expected to be worked out in one sprint, so we should be able to assign easily the sprint ID (and consequently also the release ID). Typically a sprint ID is assigned at the beginning of the sprint (not earlier) in which we assume we'll complete that user story. * A Feature should be worked out in the period of a release, so release ID should be clear. We can leave the sprint ID open for features (in the case that the feature is further structured into user stories, the different user stories should be linked to sprints, and this should be sufficient). * For EPICs or work items, we should set the release ID, in which we expect that the EPIC is fully worked out. sprint ID should be left open. * If you see that related work is not finished within the originally assigned sprint/release, then increment the sprint ID or the release ID (this should be decided at the periodic meetings among the development team, at end of a sprint/beginning of next one - ) Ifan EPIC/feature/user story/work item is 'open' (that means that it is already defined, but currently nobody is working on it), the following applies: * If we already know when the EPIC/feature/user story/work item is intended to be worked out, we can set the release ID to the expected value for completion (to give an estimation when it might be available). If no distinct timeframe is envisaged yet in your time plan, the release ID should be left open. * The sprint ID should be left open in any case. In any case it would be good for the visibility of our activities in the task if we all spent some (small) time per month to update the sprint and release IDs (e.g. setting it to the next value if time is exceeded and work is still going on) or update the work status (if item is completed), because tracker activites are monitored by the project lead and used for reporting. Furthermore, the backlog tracker is also a reporting tool inside our WP, so we can see more easily what's going on. Please also don't forget to define new Features (and also user stories where appropriate) when proceeding in your work, and to define them both in the backlog tracker and in the 'materializing' WIKI pages. Thanks to Thomas for putting all in a more structured manner :) BR Pier 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 pierangelo.garino at telecomitalia.it Fri Jul 6 12:14:12 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 6 Jul 2012 12:14:12 +0200 Subject: [Fiware-i2nd] PhC Minutes Message-ID: Hi All, the PhC minutes are available at link https://forge.fi-ware.eu/docman/view.php/10/1163/I2ND_Confcall_20120705_minutes.doc BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Fri Jul 6 15:24:04 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 6 Jul 2012 15:24:04 +0200 Subject: [Fiware-i2nd] R: Remarks on Release/Sprint numbering, Feature/User Stories etc In-Reply-To: References: Message-ID: Hi All, some small modifications concerning work items: also Work Items have to be assigned to Sprints (see corrected text below)! Apologise for this mistake... BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: venerd? 6 luglio 2012 12:01 A: fiware-i2nd at lists.fi-ware.eu Cc: Banniza, Thomas-Rolf (Thomas-Rolf) Oggetto: [Fiware-i2nd] Remarks on Release/Sprint numbering, Feature/User Stories etc Hi All, as agreed in the call yesterday, here I forward you some remarks derived from a mail exchange with Thomas, about Sprints, Releases etc. Please have a look and provide further comments and/or clarifications if necessary. General remarks: * First of all: please read again the page on methodology at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology to gather more confidence with it and maybe discover further interesting details. * A sprint lasts for one month, a release lasts between two and four sprints (i.e. two to four months). * The correct release/sprint numbering can be found at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering If an EPIC/feature/user story/work item is 'under execution' (that means you are working on it), the following applies: * A user story is expected to be worked out in one sprint, so we should be able to assign easily the sprint ID (and consequently also the release ID). Typically a sprint ID is assigned at the beginning of the sprint (not earlier) in which we assume we'll complete that user story. * A Feature should be worked out in the period of a release, so release ID should be clear. We can leave the sprint ID open for features (in the case that the feature is further structured into user stories, the different user stories should be linked to sprints, and this should be sufficient). * For EPICs or work items, we should set the release ID, in which we expect that the EPIC is fully worked out. sprint ID should be left open. * For work items, we should set the release ID, along with the sprint ID we expect that the Work Item is fully worked out. * If you see that related work is not finished within the originally assigned sprint/release, then increment the sprint ID or the release ID (this should be decided at the periodic meetings among the development team, at end of a sprint/beginning of next one - ) Ifan EPIC/feature/user story/work item is 'open' (that means that it is already defined, but currently nobody is working on it), the following applies: * If we already know when the EPIC/feature/user story/work item is intended to be worked out, we can set the release ID to the expected value for completion (to give an estimation when it might be available). If no distinct timeframe is envisaged yet in your time plan, the release ID should be left open. * The sprint ID should be left open in any case. In any case it would be good for the visibility of our activities in the task if we all spent some (small) time per month to update the sprint and release IDs (e.g. setting it to the next value if time is exceeded and work is still going on) or update the work status (if item is completed), because tracker activites are monitored by the project lead and used for reporting. Furthermore, the backlog tracker is also a reporting tool inside our WP, so we can see more easily what's going on. Please also don't forget to define new Features (and also user stories where appropriate) when proceeding in your work, and to define them both in the backlog tracker and in the 'materializing' WIKI pages. Thanks to Thomas for putting all in a more structured manner :) BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CD5B8B.6072F220]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Fri Jul 13 16:54:25 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 13 Jul 2012 16:54:25 +0200 Subject: [Fiware-i2nd] Next week I'll be unavailable Message-ID: Dear All, as I already anticipated, I'll be on holiday next week; of course Hans will continue to manage the interaction with Project Management, as well as within the chapter, so please refer to him for any issue you might have. Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From serge.defrance at technicolor.com Thu Jul 19 08:56:56 2012 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 19 Jul 2012 08:56:56 +0200 Subject: [Fiware-i2nd] Next week I'll be unavailable In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01A81C62E8@MOPESMBX01.eu.thmulti.com> Dear All, Do we have a conf call planned this morning ? Best Regards, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Friday, July 13, 2012 4:54 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Next week I'll be unavailable Dear All, as I already anticipated, I'll be on holiday next week; of course Hans will continue to manage the interaction with Project Management, as well as within the chapter, so please refer to him for any issue you might have. Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CD658C.7347E210]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Hans.Einsiedler at telekom.de Thu Jul 19 16:22:03 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 19 Jul 2012 16:22:03 +0200 Subject: [Fiware-i2nd] Periodic I2ND call (Special request to Task 7.1 - please check it) Message-ID: Dear all, Please find below the summary of the telephone call: - Serge - Jozef - Klaus and Thomas - Kay and Hans Task 7.1 ? please ckeck this minutes carefully. Open issues: - Unit Testing Plan & Report: Report is sent out, no feedback, it seems everything is okay. (Serge) - Standardisation deliverable: contribution from NSN is done. - 3rd party innovation enablement ? Google document, missing input. - Still no ToC for the White Paper. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary -----Original Appointment----- From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Freitag, 13. April 2012 17:29 To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Periodic I2ND call When: Donnerstag, 19. Juli 2012 10:00-11:30 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: PhC (new) Reminder for periodic I2ND audioconference. Below are listed the call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier 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. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001.c >> << File: logo Ambiente_foglia2.jpg >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas-rolf.banniza at alcatel-lucent.com Thu Jul 19 16:27:25 2012 From: thomas-rolf.banniza at alcatel-lucent.com (Banniza, Thomas-Rolf (Thomas-Rolf)) Date: Thu, 19 Jul 2012 16:27:25 +0200 Subject: [Fiware-i2nd] Periodic I2ND call (Special request to Task 7.1 - please check it) In-Reply-To: References: Message-ID: <049CB02683973B4EB7D42A5CD6B62134891CA28A29@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> Hi Hans and Pier, a small correction concerning 3rd party innovation enablement: both Serge and me have added some first text for WP7 into the Google doc as requested by Pier. Up to now we did not receive any reaction or feedback... Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Hans.Einsiedler at telekom.de Gesendet: Donnerstag, 19. Juli 2012 16:22 An: pierangelo.garino at telecomitalia.it; fiware-i2nd at lists.fi-ware.eu Betreff: Re: [Fiware-i2nd] Periodic I2ND call (Special request to Task 7.1 - please check it) Dear all, Please find below the summary of the telephone call: * Serge * Jozef * Klaus and Thomas * Kay and Hans Task 7.1 - please ckeck this minutes carefully. Open issues: * Unit Testing Plan & Report: Report is sent out, no feedback, it seems everything is okay. (Serge) * Standardisation deliverable: contribution from NSN is done. * 3rd party innovation enablement - Google document, missing input. * Still no ToC for the White Paper. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary -----Original Appointment----- From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Freitag, 13. April 2012 17:29 To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Periodic I2ND call When: Donnerstag, 19. Juli 2012 10:00-11:30 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: PhC (new) Reminder for periodic I2ND audioconference. Below are listed the call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier 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. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001.c >> << File: logo Ambiente_foglia2.jpg >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hans.Einsiedler at telekom.de Fri Jul 20 16:06:02 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Fri, 20 Jul 2012 16:06:02 +0200 Subject: [Fiware-i2nd] Status 3rd Party Innovation Enablement Message-ID: Dear all, Please find on the "Google" work space (owned by Google) the S3C contribution. I have also started with the introduction. 3rd Party Innovation Enablement: https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit# Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary Please note, my fax number has changed! ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423 Fax: +49 391 580220712 Mobile: +49 170 22 74 682 hans.einsiedler at telekom.de > www.telekom.com ================================================================ Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Jul 23 23:03:10 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 23 Jul 2012 23:03:10 +0200 Subject: [Fiware-i2nd] Measures established + urgent actions to be addressed Message-ID: Dear All, the WPL/WPA PhC today was very important to address a number of items which need to be taken into account for the remaining period of project activity. There has been also the definition of actions to be addressed in the next few days, although most of the crucial action points concerning the completion of first WP7 deliverables have been addressed (hopefully!) with success in the last few days, thanks to the commitment of Technicolor people who are the main involved ones. Here are the items that is important every Partner, and everybody, perfectly understand and take into account: ---------------------------------------------------- Measures for not delivering by due time ---------------------------------------------------- It is reminded that delay of some deliverables until end of June was not approved by the PO (software release, unit testing plan, accompanying guides) and they remain delayed since month 12 (end of April). None of the partners have delivered by end of June, despite this was what we committed to do with the PO when we asked for a formal re-planning. Being this the situation, TID proposed to impose measures that translate into rejection of costs by those partners that do not deliver by due time. The following measures are in place: * Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver. Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted. Planning of PMs for the remaining of the project will be adjusted accordingly. * Delivery of software that doesn't work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered. This intends to prevent that some partner delivers software which doesn't meet enough quality by July 23rd just to avoid costs rejections. * Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point). This means they would not suffer any impact. * PMs of any partner within a given WP (WP3-8) are distributed from month 10 on across deliverables as follows (note: we propose to include whatever distribution gets approved in the next amendment of the DoW): * Contributions to WP2 deliverables: 10% * FI-WARE Open Specifications: 20% * SW Release: 40% * Installation and Admin Guides: 7,5% * Users' and Programmers' Guides: 7,5% * Unit Testing Plan and Report: 15% * Deliverables of a given WP rejected by the WPL will be rejected. TID and the WPL agree on any amendment of the above rules that may apply (e.g., failing to deliver a given GE may not be the fault of all partners involved in development of that GE so they may agree not to apply penalizations to some partners). TID may reject some additional deliverables if it considers that they do not meet the defined guidelines or expected quality, after discussion with the WPL. * Similar rules would apply to WP9 (development tools) These measures have been approved by the PCC in a PhC last week. During today's WPL/WPA confcall, the deadline on July 23rd was postponed a little bit, i.e. most of the deliverables need to be ready by July 25th otherwise the measures above explained will be adopted. As I told you, most of the current actions concern the D7.Xa deliverables, for which we have managed to provide all the necessary inputs in accordance with Technicolor (the only GE owner involved in the first FI-WARE release), but keep in mind that similar rules might be applied for next releases, as well as in general for other contributions required by chapters and partners. -------------------------- 2 - Standardisation plan -------------------------- - Completion of the three tables necessary. Deadline is Wednesday 25th. See the attached mail for the details on what is to be done for our chapter. Please *All* the partners need (with supervision of GE coords) to updated the tables according to the instructions given. -------------------------- 3 - Technical Roadmap wiki page -------------------------- This is to be likned to the Features listed in the 'Materialising' wiki page, which is still not yet complete. See minutes of previous I2ND PhCs for details on what to do. I suggest that, looking at what inserted so far in the Tech roadmap page, the Features are updated (or created) in accordance with the functionality which will be delivered, for our GEs, in the second (or third) FI-WARE release. The completion of *all* Tech roadmap update is July 31st, but Features and audits will be started earlier, expecting the Features are stable by July 26th. As this is a very old item (I mentioned it the first time at end of May...), and it is related to WP2 contributions, the measures above explained would apply for those not providing in time the expected inputs. -------------------------- 4 - Population of the FI-WARE catalogue -------------------------- The CE description is still missing, being part of first release it is urgent to provide it. Henk, Serge, can you do that, according to the rules explained in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue Hope all these items are sufficiently clear, otherwise let us know, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Ernoe Kovacs Subject: Re: [Fiware-wpl] NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Date: Mon, 23 Jul 2012 09:30:40 +0200 Size: 80375 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 frank.schulze at fokus.fraunhofer.de Tue Jul 24 15:47:57 2012 From: frank.schulze at fokus.fraunhofer.de (Frank Schulze) Date: Tue, 24 Jul 2012 15:47:57 +0200 Subject: [Fiware-i2nd] New Fraunhofer Member Message-ID: Hello I2ND team, due to Marius parental leave for the next two months, I would like to introduce Marc Emmelmann from Fraunhofer FOKUS institute as new I2ND member. He will support the I2ND team for the time Marius is not available. Pier, can you add him to the mailing list? BR Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hans.Einsiedler at telekom.de Tue Jul 24 18:12:46 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Tue, 24 Jul 2012 18:12:46 +0200 Subject: [Fiware-i2nd] [FI-WARE, I2ND] Standardisation ... Message-ID: Dear Pier, dear all, We have concluded the S3C contribution regarding the standardization process. Please have a look to the figure, we have included as a link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/images/e/e2/3GPP-standardisation-process.jpg The figure was provided by the DTAG's standardization people. Cheers, Hans Message Classification: [ ] Public [ ] Private [X] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary Please note, my fax number has changed! ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423 Fax: +49 391 580220712 Mobile: +49 170 22 74 682 hans.einsiedler at telekom.de > www.telekom.com ================================================================ Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Jul 26 15:06:06 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 26 Jul 2012 15:06:06 +0200 Subject: [Fiware-i2nd] I: [Fiware-pcc] Report on conversation with our PO on status of the FI-WARE project In-Reply-To: <500DDAB8.3060303@tid.es> References: <500DDAB8.3060303@tid.es> Message-ID: Dear All, I forward FYI the outcomes of the conversation of FI-WARE ProjCoord and the PO. If you have any comment or remark please let me know. BR Pier -----Messaggio originale----- Da: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: marted? 24 luglio 2012 01:14 A: fiware-pcc at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-pcc] Report on conversation with our PO on status of the FI-WARE project Hi all, I have had a confcall with our PO where we have addressed a number of important issues and have discussed about general status of the project and the program. This email is trying to share with you information about what has been discussed. Don't hesitate to share this information with members of your respective chapter/WP teams. As I have already reported in a previous mail, the first thing we discussed had to do with how to manage deliverables linked to software and Installation/Administration Guides marked as PP. I hope this solves major concerns raised by some of the partners. Second point that was addressed had to do with measurements defined to avoid further delays in meeting defined deadlines. PO is backing us on the decision taken and welcome them. Even in the case that TID were not legally able to reject submission of financial/cost statements (something he doubts because he believes it can), he believes that TID not only can but must identify financial/costs reports TID believes are not in line with what is the actual work carried out and the EC would take decisions accordingly. Nevertheless, I shared with the PO that we believe that all partners will do their best to comply with the defined milestones not just to avoid implementation of the defined measurements but for the sake of the project. I believe that the PO feels confident about the status but let's try not to let him down. I reported about the status of the Testbed and the contingency plan that we put in place. He seemed to be fine with that. I asked him about the 1st year FI-WARE Review Report and he told me that we shouldn't expect this earlier than mid August. I explained Arian our plans regarding resubmission of the Technical Roadmap (in line with what we proposed during the 1st year FI-WARE Review meeting) and he seemed to be fine with them. He confirmed the relevance of the white paper describing the encompassing usage of GEs. I already announced him that it would be rather difficult to get it finished by the end of July because we are all so busy. It seemed that his major concern was to to make sure it be ready before an Information Day regarding the phase 2 of the FI-PPP that the EC has planned by August 30 in Brussels. I reported also that we were working hard on the deliverable regarding 3rd party innovation enablement and trying to get it ready by end of July or, if not, just a few days later. He seemed to be happy with that. Regarding results of the 1st Open Call, Arian expects that the next step will be that we elaborate an amendment of the DoW which incorporates the new partners and their description of work. However, we agreed that such DoW amendment should try to go after the one where we will try to incorporate all pending changes which were summarized and agreed during the last PCC meetings. He was ok with the planning of the second Open Call but would like to see the third Open Call later than what we proposed (January next year instead of end of October) in order to allow incorporation of topics that may be demanded by UC trials selected in phase 2 (hearings are planned to end beginning of December this year). I proposed him the possibility to formulate the 2nd Open Call so that it may consider topics with different closing dates for final publication of Epics and different submission deadlines. This would allow to incorporate topics like Security in this 2nd Open Call. Arian believes this may be feasible. Definitively, I will propose discussing this during the confcall of the FI-PPP AB that will take place this week. I think this was all. I'm happy to respond any question that you may have. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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-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. From pierangelo.garino at telecomitalia.it Thu Jul 26 23:46:34 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 26 Jul 2012 23:46:34 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] Standardization Plan FI-WARE D11.4 Deliverable- LAST CALL FOR CONTRIBUTIONS In-Reply-To: References: Message-ID: Dear All, please check whether you can update a little bit more the tables 7b and 7c, according to the suggestions reported by Lindsay in his mail below, concerninf I2ND chapter. I made already some few updates to some item I better know, for the others I rely on your support. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juan Bare?o Guerenabarrena Inviato: gioved? 26 luglio 2012 10:37 A: fiware-wpl at lists.fi-ware.eu Cc: Ernoe.Kovacs at neclab.eu; carmen.perea at atosresearch.eu; Lindsay.Frost at neclab.eu Oggetto: [Fiware-wpl] Standardization Plan FI-WARE D11.4 Deliverable- LAST CALL FOR CONTRIBUTIONS Dear WPLs As we agreed on the last WPL weekly phone conference the deadline for last contributions, expired yesterday, and there has been few progress on this issue Please review the NEC comments on the status of each chapter, and complete the missing information in each table, see guidelines about how to complete the tables in the last part of the mail form NEC below, additionally we need a picture of the overall architecture and exposed interfaces which we want to standardize, see (1) point and proceed accordingly We set a final deadline for this contributions, before Saturday 28.07.2012 at 17:00, so please proceed accordingly and complete the missing information ASAP Thanks for your contribution Juan From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] Sent: jueves, 26 de julio de 2012 0:05 To: Juan Bare?o Guerenabarrena Cc: Carmen Perea Escribano; Nuria De-Lama Sanchez; Ernoe Kovacs Subject: RE: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Dear Juan, I looked at https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2 and do find quite some material has been input, but of course not enough to satisfy the EC. So far I2ND is best and Data Context Management is worst. Please see action items below. I explain below the status and what is missing, and I ask you to fwd this email to the WPLs to get them to urgently add new material by Saturday 28.07.2012 at 17:00. Comments in red below are action items. Please note that the intention is to show: - FI-WARE knows what it wants to monitor/contribute - FI-WARE has done monitoring and already some contributions - FI-WARE has a plan to get some important interfaces (reference points) openly standardized. At the end of this email I include an explanation in some detail for each required cell in the tables .. Progress in the Standardization Plan plus action items https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Standardization_Plan_v2 (1) Architecture diagram and labels of exposed interfaces We need a picture of the overall architecture and exposed interfaces which we want to standardize. We need the lists of Reference Points in Table(a)-Column3 to match those names on that picture. So far the Table-a names do not even match the partial architectures found on the wiki at these places, we need a single consistent picture. ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_%28IoT%29_Services_Enablement_Architecture ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security_Architecture ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Architecture_of_Applications_and_Services_Ecosystem_and_Delivery_Frameworkhttp://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Data/Context_Management_Architecture (2) Cloud Hosting Table 7a (IF to SDO) is existing with quite a lot of content, thanks to GLIKSON, Alex >. But the Reference Points do not match the partial architecture in this figure. Please provide right figure and names. The dates in Column1 are generic and do not show any history of contributions/monitoring of past meetings. Please put in dates of some previous meetings and future ones and mention specific contributions. The dates in Column1, even for the future, do not show any specific ideas to Contribute. The list of Partners is present, thank you, but no list of names - that makes it look like nobody is allocated! Please name the delegates who attend. Worst case, look at the meeting minutes! Table 7b (partner responsibility) Delegate names are missing. Table 7c (Timeline) are empty. Please add brief current status for each SDO. (3) Data Context Management CARLOS RALLI UCENDO ralli at tid.es has put nothing there yet (4) Internet of Things Table 7a is existing with quite a lot of content, thanks to thierry.nagellen at orange.com and lorant.farkas at nsn.com But the Reference Points do not match well the partial architecture in this figure. Please provide right figure and names. The IETF CORE gives a quite good example of how to fill in the table with real contribution links Please provide titles/links to contributions in other SDOs listed. Table 7b is existing, but the names of reference points do not match Table 7a Please fill in correct reference point names in Column2 (should be identical to table 7a) Table 7C only started Please fill in more specific goals and estimated dates. Should be something for each interface. (5) Applications Services Ecosystem Inputs from torsten.leidig at sap.com (see above example explanations) (6) Security Table for 7a, 7b, 7c partially filled in. Thanks to pascal.bisson at thalesgroup.com and daniel.gidoin at thalesgroup.com Some entries missing, but it is coming into shape. Please see above example explanations to improve it. (7) I2ND Table 7a is very good, thanks to pierangelo.garino at telecomitalia.it Table 7b is existing, but the names of reference points do not match Table 7a Please fill in correct reference point names in Column2 (should be identical to table 7a) Table 7c is very good, but does not include any future goals. Are all needed specs completed? If not, say what is needing more work. General explanations of what goes in each Table (comments in red) The Table (a) is intended as a sequential sequence of dates to record past activities at specific meetings, and also to write in what future activities are planned. TABLE (a) : Summary of SDO activities and interfaces for Cloud Hosting chapter (This is meant to outline _future_ intended contributions or monitoring of _specific_ events, like a calendar, and to _record_ successful contributions or monitoring-reports of the past) Dates SDO as link Exposed FI-WARE Interface Contribute or Monitor Contribution title as link and SDO ID Responsible Partner(s) and Person(s) Stds-Phase IPR-issues Comment & Status (Date should be specific for when a meeting occurred and FI-WARE either monitored or contribute ... not just a span of xx months!) (should be link to the main page of the SDO so EC can quickly see the Org.) (should be _consistent_ name for the FI-WARE interface(s) which are _influenced_ by the SDO or are intended to be standardized openly in the SDO). (Monitor an SDO which provides useful _input_ for FI-WARE and Contribute to an SDO where a FI-WARE interfaced needs open standardization.) (Write specific document and link if possible, or for planned contributions give an indicative title.) (Partner corporation) (For the specific date of a meeting or planned meeting, write what was achieved or what is the monitored status of the specifications which are being tracked). Table 7b (This is meant to show which Person from which Partner is responsible for monitoring or contributing for each "Exposed Interface" in each identified SDO. It shows who does what, for planning purposes) SDO Exposed FI-WARE Interface Responsible Partner Responsible Person Comment (duplicated from Table 7a) (duplicated from Table 7a) (duplicated from Table 7a) (Add a delegate name. This is the key information!) (Can be empty, or can say "delegate is vice-chair" or "delegate is expert in ontologies" or something like that) Table 7c (This table is intended as a summary of a long history of contributions in Tables 7a and 7b, just showing to the EC the current/final result in Column7. ) Dates SDO or event contribution title and SDO ID Exposed Interface responsible partner responsible person phase/IPR/comment/status ... ... ... ... ... ... (Explain if the work is Feasibility Study, Architecture, Protocol phase; explain if IPR is included from FI-WARE; explain if work is completed or blocked or ongoing ...) From: Juan Bare?o Guerenabarrena [mailto:juan.bareno at atosresearch.eu] Sent: Donnerstag, 5. Juli 2012 15:49 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: jhierro at tid.es; mcp at tid.es; nuria.delama at atosresearch.eu; carmen.perea at atosresearch.eu; Ernoe Kovacs; Lindsay Frost Subject: FW: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear WPLs Please find below the detailed plan for complete the standardization deliverable for M15, end of this month Please react to what NEC, task leader, ask from you: - Identify a responsible partner per WP - Provide the inputs required in the wiki - Review content and format requirements For any doubt please contact Lindsay/Ernoe, in cc Thanks for your contribution Juan From: Lindsay Frost [mailto:Lindsay.Frost at neclab.eu] Sent: jueves, 05 de julio de 2012 15:12 To: Juan Bare?o Guerenabarrena; Miguel Carrillo; Nuria De-Lama Sanchez; Carmen Perea Escribano; lorant.farkas at nsn.com; thierry.nagellen at orange.com Cc: Ernoe Kovacs Subject: NEC Commitments for MONTH-15 FI-WARE D11.4 Deliverable and requests confirmation //email 1 of 2// Importance: High Dear FI-WARE management team, Please distribute this email on PCC; fiware-wpl at lists.fi-ware.eu; and fiware-wpa at lists.fi-ware.eu We refer to information provided to NEC in a teleconference on 02.07 by FI-WARE management regarding providing in the next 3 weeks a new Standardization Plan. NEC protests at the way the management decision was reached and communicated. The decision took no account of NEC proposals which were sent 23.05.2012 and for which responses were twice requested. The decision now requires NEC to make a burst of effort in the next 3 weeks to immediately create a new Standardization Plan, without considering NEC staff availability. Furthermore, the needed strategic inputs are not in the hands of NEC to create. Nevertheless, NEC has created a new fast-track plan with some chance of success, assuming continuous and strong input from partners. Endorsement, help and support from FI-Ware management and PCC is strongly requested. Depending on the inputs from FI-WARE partners and the later review of the EC, NEC will reconsider its' future participation in this part of WP11. Outline of Plan (detailed plan below): ? FI-WARE WPLs identify which Generic Enabler interfaces are important and therefore crucial for standardization. It is essential that a FI-WARE software architect complete such a list/diagram immediately to focus the work. ? FI-WARE WPLs nominate responsible partners and _persons_ who will input the plan and status for standardization at _specific_ SDOs, for _each_ of those important interfaces (a subset of all interfaces) ? The nominated responsible persons input their plan into the private Wiki as described below, and update the Wiki FI-WARE Standardization v2 (private wiki) with (their) past contributions as well as planned future ones. FI-WARE management team has promised weekly oversight of this activity. ? NEC summarizes results in last week of July, creating D11.4b pdf from the Wiki NEC requests confirmation of this plan, which is detailed below. Yours sincerely, Dr. Lindsay Frost, Dr. Ernoe Kovacs ATTACHMENTs (1) Old, still valid Action Plan to react to EC comments (file 2012-05-23-ActionPlan.txt) (2) Detailed Plan for D11.4.b by End July (see below) Attachment 2: The following is the step-by-step plan: (D) NEC Conclusions for Standardization Plan content and format 6. General content required (to be generated by FI-WARE partners) a. identify what standardization makes sense for FI-WARE (targets), taking account of specific gaps which the EC requested fixed b. identify where to do it (selected SDOs) /note: should reference "Section 2 CONTRIBUTE" actions in D11.4a/ c. explain (if it is planned) where IP generated in FI-WARE is inserted into SDOs specifications d. for each selected SDO and FI-WARE target, show the timeline of how to achieve the target, with "concrete steps" and partners, starting work "even before usable results" as requested by EC e. show how ongoing actual contributions to SDOs fulfill the "concrete steps" (i.e. ongoing status) 7. Step by step Format a. WPLs create a webpage mapping important FI-WARE interfaces/protocols to the Target SDO which could be responsible. It should also indicate any IPR which FI-WARE may bring in. This webpage would satisfy (D)6.a and (D)6.b and (D)6.c above. In the opinion of NEC, standardization is most valuable for the exposed interfaces, and in a secondary way to efficiently design the internal interfaces. Therefore all exposed interfaces are important, and some internal ones. As an example of some important interfaces, the (old) picture https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/Snapshot_2012.06.01_of_Deliverable_Page_for_D2.3_Architecture_Specifications could be used. b. WPLs create a webpage showing which partner is responsible for each important interface and their responsible person to make it standardized. The format can be a table ("Target SDO / Responsible Persons") with entries . c. Responsible persons add to FI-WARE Standardization v2 (private wiki) page, for each Target SDO, a timeline based on the SDO meeting schedules and methods, which is designed to get the exposed interface standardized. A partial example is given for ETSI M2M. This satisfies (D)6.d. This can only be created by the responsible persons who also ensure that that Target SDO work happens. It should indicate the phases as e.g. (1) feasibility-study (2) architecture (3) datamodels and protocols. The format can be a table ("Target SDO / Contributions Table ") ordered by date, so later it is easier for the information to be integrated into a complete project plan, e.g. d. The responsible person updates the Target SDO / Contributions Table every week, with new planned inputs and new results. Care should be taken to note any IPR. This satisfies (D)6.e. e. NEC creates an integrated timetable showing the aggregated copies of all tables from step (c) above, which is the overview for the EC. NEC will combine it with (a) and (b) - assuming all partners have strongly contributed - so as to resolve all EC requests. f. Optionally partners can extend the information in (c) above, to include highly relevant non-FI-WARE results which are monitored (M). Also partners can include relevant work they do which however is not part of the agreed important interface work. Monitoring standards is also part of the standardization plan and this work should be reported to the EC, as long as it is shown as supporting a significant amount of active contributions work. NEC rejects proposals to use Googledocs because NEC was required to change from doc to Wiki during the previous phase of the project and the good reasons for doing that still hold. ------------------------------------------------------------------ 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. ------------------------------------------------------------------ ------------------------------------------------------------------ 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. ------------------------------------------------------------------ ------------------------------------------------------------------ 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. ------------------------------------------------------------------ ------------------------------------------------------------------ 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. ------------------------------------------------------------------ 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 -------------- An embedded message was scrubbed... From: Lindsay Frost Subject: FI-WARE Exposed Interfaces Date: Wed, 25 Jul 2012 15:31:19 +0200 Size: 547461 URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From mcp at tid.es Fri Jul 27 09:31:42 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jul 2012 09:31:42 +0200 Subject: [Fiware-i2nd] Installation on the Testbed and procedures Message-ID: <501243DE.3010807@tid.es> Dear all, As leader of the task D10.2 "FI-WARE Integration" and also from the coordination I'd like to make some clarifications of general interest. As you know, WP10 (Experimentation Support, Integrated Testing and Validation) has as main task the set-up and running of the FI-WARE Testbed. Given the importance of this goal, WP10 has a representative of each partner. This representative (not the WPL) should make sure that all people within his/her company are well informed of the situation and what we expect from them in the Testbed and the experimentation stage. Several partners are not doing this work (in same cases never attended the WP10 phc) and the project coordination is receiving complaints as many people don't seem to be well informed. We sometimes resort to the WPL to help here, but this is not the "official" channel. I will try to recap to give all the consortium an overview of the situation and what we need from you. GENERAL INFO * The Testbed Team is starting to send the details on how to install the testbed to the GE owners who declared that they are going to install their GE in July * Theoretically you should install your GE yourselves but we can give a hand deploying a KVM image for those who prefer this method (other hypervisors are not supported) * The GE owner is the one who administrates and maintains the GE, not the testbed team. If something goes wrong, he/she has to put it up and running again, the WP10 will only monitor the situation and will prompt about abnormal behaviour of the GE . * We have two tools to follow this up: * Implementation cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit * Integration Tracker : https://forge.fi-ware.eu/tracker/?atid=224&group_id=18&func=browse * Each release of each GE is represented by a ticket * The use of this is explained here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Integration_Plan#Integration_Process * If you do not have access to the testbed project and cannot reach this wiki and the tracker, request access following the standard procedure REQUESTS FOR GE OWNERS * We have an installation calendar. Please fill in the responsible person per GE and state the dates when you could install * http://www.doodle.com/bymgm9h9gnbfms8k * Fill the GE template in the Testbed Cockpit (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit ) declaring if the GE is multi-tenant or not (this deeply affects the GE usage by different Use case projects at the same time) * The access to the Testbed is limited per IP. Make sure that the IPs from which you are going to access the Testbed are listed here (if not, you will not be able to enter the testbed): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit (click on your enabler and see the wiki page with the details per enabler) * Alternatively, there is also a page that has company wide IPs (not particular to an enabler): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Operations_Cockpit * Make sure that when you install your GE, you update the corresponding ticket on the Integration tracker and also the Implementation cockpit. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Tue Jul 31 16:17:28 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 31 Jul 2012 16:17:28 +0200 Subject: [Fiware-i2nd] R: Periodic I2ND call Message-ID: Dear All, this the proposed agenda concerning our periodic PhC this week, I assume that some of us will be available although the holidays period: * Anticipation on official outcomes of review meeting (another mail will be sent to you later). Actions planned * Status of deliverables * Further actions to be tackled in short term * Short status on GEs (Task coords if available) BR Pier -----Appuntamento originale----- Da: Garino Pierangelo Inviato: venerd? 13 aprile 2012 17:29 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Cc: Wuenstel, Klaus (Klaus); andi at dis.uniroma1.it; Banniza, Thomas-Rolf (Thomas-Rolf); Kurt Essigmann; Woods, Chris; Henrik Abramowicz; jeanpierre.lerouzic at orange.com; Roman.Szczepanski at telekom.de; Corici, Marius-Iulian; Hans.Einsiedler at telekom.de Oggetto: Periodic I2ND call Data: gioved? 2 agosto 2012 10:00-11:30 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Percorso: PhC (new) Reminder for periodic I2ND audioconference. Below are listed the call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com << File: USA_en_pwn-dial-in-numbers.pdf >> BR Pier 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 pierangelo.garino at telecomitalia.it Tue Jul 31 17:07:13 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 31 Jul 2012 17:07:13 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] Fwd: FI-WARE: extract executive summary draft review report In-Reply-To: <50164CB7.1060804@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D07CB70@S-DC-ESTF03-B.net1.cec.eu.int> <50164CB7.1060804@tid.es> Message-ID: Dear All, I forward you the first official result of the FI-WARE review meeting, as you'll see it's not particularly enthusiastic. Today in a WPL/WPA call it was drafted a plan to make sure we're not falling into more severe critical conditions for the project. The outcomes having a more immediate effect on our activity (we'll discuss them in the PhC on Thursday) are the following: 1) Resubmission of the FI-WARE Technical Roadmap is to be accomplished *this week*. This will consist in incorporating references to the now revised Epics and Features in the Backlog. This would be a matter of adding some tables regarding major releases for each Chapter. If you go to the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4I2ND#Placeholder_for_preparation_of_updated_technical_Roadmap you'll find a set of tables (one for each FI-WARE major release) we have to fill with the Features of each GE which will be available in the specific release. The wiki page is in the fiware-private wiki, but please insert in the table the link to the Features corresponding to the public wiki (i.e. those links you get from the 'Materialising' page: once we move the page to the public wiki the links will automatically point to those Features. If some of you dind't complete yet the update of Features, please complete it asap!! 2) D2.5a: contributions were provided, it's now the turn of WPLs to review the contents, and possibly ask for some improvement. This process will end up with the deliverable released on Aug 10th. It might happen that you'll be asked to contribute these improvements, if necessary Other points will be discussed in the PhC. 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: luned? 30 luglio 2012 10:59 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: FI-WARE: extract executive summary draft review report Dear colleagues, We have just received the following extract of the executive summary draft review report. We haven't had time to review it. But certainly the review report is not as positive as we thought after the first year review meeting. Overall, it is worth to highlight that the project's assestment is: * Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule)" This, among other things, confirms us that the recent measurements put in place were required. Now, it's critical to demonstrate that we are going to deliver what was due and that the testbed will not get delayed. We'll come with additional comments later. Best regards, -- Juanjo -------- Original Message -------- Subject: FI-WARE: extract executive summary draft review report Date: Mon, 30 Jul 2012 08:42:05 +0000 From: To: , CC: , , Dear all, Below is an extract from the draft executive summary of the draft M12 review report. The extract may deviate from the executive summary in the final version of the review report. It is sent since it contains some information, e.g. about deliverable acceptance, that you may want to know asap. Best regards, Arian. ====================== The objectives of the project during this period remain unchanged, but are brought into sharp focus due to the delay of two months plus now apparent, and the critical need to release the complete and comprehensive Generic Enabler (GE) Open Specifications and accompanying reference code as soon as possible in order to not risk destabilizing the entire FI PPP. Many primary technical deliverables expected at M12 are not yet available, which is extremely poor progress given that they are some of the main achievements planned for Month 12 and create the first useable foundation for Use Cases projects to build upon. Compounding this failure is the poor quality and incompleteness of various technical deliverables; a quite astounding result given the resources available to the project. According to the Description of Work (DoW), the main achievements for this period should be the first version of the GE open specifications, software prototypes and related guidance material and test plan. Only the specifications were delivered so far. However, they are 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 - all of which are fundamental to the rationale for and objectives of FI-WARE. It is unclear in many of the GE specifications which are the reusable and commonly shared functions, and which usage areas across various sectors would utilize these GEs. There are also no details on the protocols that support interoperability with other GEs or third party products or how this interoperability would be achieved. Moreover, a consolidated and consistent presentation of the specifications is still missing. There is a lot of confusion about what the GEs really are, or meant to be, within the FI-WARE consortium, and most probably the UC projects, not to mention the world at large. They are a mixed bag, including functional descriptions, specifications of (not necessarily well-defined) technical functions, specification of access and other operational protocols, specification of access to other existing "modules"/"components"/"devices" and so on, specifications to enable interfaces between existing protocols, specifications to enable deployment of other collection of protocols as "engines", etc. As mentioned in the DoW, "GE Open Specifications will contain all the information required in order to build compliant products which can work as alternative implementations of GEs developed in FI-WARE and therefore may replace a GE implementation developed in FI-WARE within a particular FI-WARE Instance." However, given the current state of the GE deliverables, there are severe doubts about how a FI-WARE instance ("platform") could be built from the GEs without a massive amount of "imagination" and tweaking to make them work together. There are also severe doubts about how a "Future Internet Application" could be portable across different FI-WARE Instances that implement the (same set of?) GEs that the Future Internet Application relies on. The GEs as currently defined are not, by themselves, implementable in the sense of delivering a practical software solution ("platform"). This is compounded by the difficulty of understanding what is really meant by a "coherent" set of GEs. Some GEs seem to have closer inter-relationships than others. Notwithstanding the (useful) clarifications and information orally provided at the review meeting, the inadequate and indeed scarce information within these specifications and the discrepancies between the Technical Roadmap and the available GE contents lead the reviewers to cast doubts on the project achievement so far, and its prospect. FI-WARE failed to meet its milestones for Month 12. Given the above, technical progress of the project for the first year is unacceptable. Moreover, any further delay is likely to significantly risk integrity of the entire FI-PPP and the smooth transition to Phase 2. The consortium made a generally positive and concerted effort so far as the review meeting is concerned. It presented itself as a credible team. The verbal presentations made at the meeting were typically more informative and explanatory than the written deliverables would lead readers to expect (some material within the presentation, such as the matrix of use cases using GEs, is highly appreciated by the reviewers). With evident technical capability, but lack of timely and quality delivery, managerial action is an absolute and urgent must for an accelerated FI-WARE recovery, and to ensure that the FI-PPP programme will deliver meaningful innovations. Collaboration with Use Case projects appears to be improving markedly thanks to key face-to-face training weeks, and enhancements to the way the Fusion Forge system is managed. However, there are still significant issues concerning the processing and documentation of the requirements/backlogs. A main conclusion from the review is that the Use Cases requirements are still not considered as high priority by FI-WARE. Feedback from Use Case projects, including implications for the technology perspective and choices made by FI-WARE, should be (more visibly) taken into account and demonstrated as such. Traceability is crucial for the credibility of the FI-WARE technical deliverables and uptake beyond the consortium; and accountability is required to justify financing from the public purse. The recently conducted architecture training weeks should be used as a stepping stone towards building an FI-PPP "culture" between all Programme participants. More such sessions should be planned, particularly around the test-bed integration deployment and use of the DevComE toolset. For its own part, DevComE is presently a positive highlight of the project. Integration planning for the test-bed is sound and detailed. The testing and the integration activities are among the project highlights. Both are carefully planned and well specified. As the development of the GEs is delayed, the integration activities still lack concreteness in terms of specific scenarios in which several of the GEs will be involved, which is a pity. Work undertaken regarding communication and dissemination is showing significant advancement, albeit with still substantial opportunity for improvement. Given the overall delay in the work plan, the postponement of many key deliverables, and the insufficient quality (and quantity) of the technical specifications, the reviewers consider that the resources were not utilized effectively within the first project year. The consortium has put reasonable effort into analysing and positioning FI-WARE in the current market context. The exploitation within the scope of "Smart Cities" is promising and welcome, but the Use Cases projects should be targeted as prime users. The business strategy is however absent, in so far that no credible and preliminary quantified business case has been presented yet. The consortium's position that the business case will arrive in the second year of the project is a matter of serious concerns; for example, the reviewers have the strong impression that nobody in the consortium has any notion of the overall amount of investment required to take FI-WARE results to the market, and the work presented is clearly (still) lacking substantive input from the business departments of the industrial partners. Despite the extensive comments in the Month 6 Review Report and notwithstanding the voluminous deliverable D11.2.1, there is still no unified or compelling marketing message, including no compelling unique selling proposition, of the FI-WARE results. The individual exploitation plans of the partners are timid. There is inadequate consideration of third party development and SME exploitation at the business level. The globalisation dimension of the exploitation plan is unconvincing. The consortium is reminded that the success of FI-WARE depends on the delivery of a genuine global solution, exploitable by partners inside and outside the consortium and beyond Europe. In summary, there is a glaring and alarming discrepancy between the high ambitions of FI-WARE given in the DoW and the very limited perspective of exploitation offered so far. The reviewers are disappointed that many of the recommendations made - dating back to the Month 6 review or even earlier - have not been sufficiently considered. Additionally, the reviewers are frustrated by the pattern of (extremely) late submission of the majority of the deliverables, and hastily communicated rescheduling of other deliverables with debatable arguments. Such behaviour is not acceptable in the business world; it is equally unacceptable in the context of European collaborative activity, especially in view of the public funding involved. b. Recommendations concerning the period under review The following deliverables require re-submission: * D2.3.1 by Month 15 (from Month 9 review) * D2.4.1 by Month 15 (from Month 9 review) * D2.1.2 by Month 18 * D3.1.1 by Month 18 * D4.1.1 by Month 18 * D5.1.1 by Month 18 * D6.1.1 by Month 18 * D7.1.1 by Month 18 * D8.1.1 by Month 18 * D11.1.1 by Month 18 * D11.2.1 by Month 18 * D11.3.1 by Month 18 The following recommendations are reiterated from the Month 6 review report (with the timeframe for R[1][2]1 adjusted in light of the Month 9 review) and were expected to be addressed in a satisfactory manner by the Month 12 review (original recommendations re-produced in italics): R [1-3]1. Given FI-WARE's intent to remain domain neutral, a comprehensive technology map must be created that clearly and unambiguously illustrates the relationships between all Generic Enablers to be produced by FI-WARE. This was expected to be documented in deliverable D2.3.1 originally due Month 9, for which re-submission is now due Month 15. Still to be addressed in the forthcoming resubmission of D2.3.1 due Month 15. As regards the "transparent encompassing architecture" for FI-WARE as a whole also asked for already in the first recommendation of the review report at M3, we advise the consortium to keep in mind and log this recommendation, and re-visit it in 2013, after the projects selected under Phase 2 have joined the FI PPP. R [1-3]3. Ensure meaningful interaction with standards bodies including Internet-related standards groups such as the IETF, the W3C, the IEEE, the ITU-T, the OMA, and the 3GPP/2. This is expected to be reported in deliverable D12.3.2 due Month 12 and/or deliverable D11.4.1 due Month 9. Still to be addressed in the forthcoming D11.4.2 due Month 15. R [1-3]6. Ensure there is a focus on attracting a development community for FI-WARE, and not only within the FI-PPP, but where possible within the partner organisations and the open community of potential users. This is expected to be considered in relation to deliverable D2.5.1 and reported in deliverable D12.2.2. Still to be addressed in the forthcoming D2.5.1. R [1-3]7. As there is substantial reliance on external technology sources, e.g., other FP7 projects and open source projects, contingencies should be prepared which address what actions to take should those projects fail to deliver, or are delayed with planned delivery upon which FI-WARE depends. This is expected to be documented in deliverable D1.1.2 due Month 12. The sourcing of technology is still not sufficiently clear. Contingency planning is still not adequately provided for or documented in D1.1.2. Please provide an adequate plan in the online version of the Project Management Handbook asap. R [1-3]8. There is a reasonable likelihood that FI-WARE chapters will be unable to achieve all that they would like to. A risk mitigation strategy should be put in place for this, with thought given in advance on how the project plans to prioritise resources if insufficient resources are available to cope with all planned work. This is expected to be documented in deliverable D1.1.2. The consortium is reminded that effort and funding allocations in the DoW are indicative and not sacrosanct. A robust risk management strategy is still missing from D1.1.2. Please provide such a strategy in the online version of the Project Management Handbook asap. R [1-3]9. Make sustained effort to enrol the support of stakeholders from the business and marketing departments of all major commercial partners in the project. External to the consortium, dissemination should go considerably beyond the "traditional groups" that are usually targeted for dissemination in FP7 projects. This concerns both the RTD communities and the business communities at large, within as well as outside Europe. Consumer organisations should also be considered and inputs be sought, to make sure that the FI-PPP results will be successfully adopted by the mass market. This is expected to be reported in deliverable D12.2.2. Progress has been made in relation to dissemination. The active involvement and support of the business and marketing personnel from the industrial project partners is still largely absent. R [1-3]10. Ensure that planning of the Open Calls starts early and the Open Calls are inclusive enough to attract any prospective submitters including specialist SMEs (without making a priori assumptions about who might be interested in the calls). The Open Calls should be used as a strategic opportunity for disseminating FI-WARE to FI stakeholders and engaging their interest in FI-WARE outputs. The Open Call processes and experience, including lessons learnt, should be documented and assimilated by the consortium for subsequent calls, and included in the relevant editions of deliverable D1.2.x for reporting and auditing purposes. Please take into full account our remarks on the management and administration of the Open Calls in Section 1a of the previous (M6) Review Report, and clarify the rationale for the selection of the topic(s) for the forthcoming first Open Call and to what extent the use case projects have a voice in the topic selection in the first and subsequent calls. The reviewers are still awaiting the reporting of the first Open Call. Progress to be re-assessed in relation to the planning/reporting of the next Open Call in the forthcoming D1.3.2. R [1-3]11. The reviewers cannot over-emphasise the importance of exploitation planning, including detailed documentation of IPR management. In our view, this is also intimately linked to enablement of third party exploitation. Please refer to our remarks in Sections 1a and 1b of the previous (M6) Review Report. It is obvious that high expectations are placed by the reviewers on deliverables D11.2.1 and D2.5.1 due Month 12. Please do not treat this as a paper exercise for satisfying the reviewers. Instead, they should be treated as initial blueprints for realistic business models backed by genuine commitment from especially the industrial partners. Unsatisfactory addressed. Exploitation planning lacks credibility and market traction. To be addressed in the resubmission of D11.2.1 due M18. R [1-3]12. All future deliverables should continue to be made available to the reviewers in pdf format. They should also be submitted on time. The consortium should investigate whether posting such files on its website or wiki might provide value for potential users, in addition to the wiki pages (at least those files relating to key deliverables). Please report the findings of the investigation at the next review. Unsatisfactory addressed. Large numbers of deliverables not submitted on time, yet again. Others have been rescheduled in a hasty manner. The reviewers strongly recommend corrective actions. Additionally, the reviewers request that project deliverables be made available as a consolidated file for future reviews. The consortium has no inclination to make deliverables available in a file format, other than to the EC and reviewers for pure compliance purposes, after evident resistance. The need to investigate the usefulness of such files to would-be users was dismissed. R [1-3]13. Improve the usefulness and attractiveness of the project website: make the information (even) more easy to find, bearing in mind that users might not be familiar with the FI-PPP; enhance the website as a marketing tool to would-be third parties and 'customers' of FI-WARE results (make the website answer the question to companies not involved in EU funded activities: why should I be interested in what FI-WARE is doing, and what is in it for me?). Consider the use of creditable Search Engine Optimization techniques. Unsatisfactorily addressed - no evidence of website improvement as a marketing tool. Significant improvement required for Month 17. The consortium is also encouraged to bring forward the implementation of the FI-WARE GE portal (not in DoW, but highly welcome) currently planned for Year 3. R [1-3]14. Put in place contingencies for loss of key people from the project. This is expected to be documented in deliverable D1.1.2. Recommendation addressed to some degree, for example by involving WP leaders in the management of backlog. Please provide a clear update in the online version of the Project Management Handbook asap. Recommendations still outstanding from the initial review of D2.2.1: * R2: the relationship between GEs and the Specific Enablers needs to be clarified and documented, bearing in mind that the former are potential candidates for standardisation in due course, and the latter are critical from the view point of making business out of FI-WARE results. Documentation is now expected at Month 9 with deliverable D2.3.1. Still to be addressed in the resubmitted version of the D2.3.1 due Month 15. * R9: The requested delivery schedule for the GEs, or at a minimum indication of prioritisation, has not been presented. This is now expected for deliverable D2.4.1 at Month 9. The information should be made visibly available in the public domain. Still not addressed, with mismatches between the Backlog, the Technical Roadmap and the Open Specifications delivered; To be addressed in the resubmitted version of the D2.4.1 due Month 15. c. Recommendations concerning future work R[3]15. Ensure that the quality of the GE specifications is high and consistent. Use GE specification for WP8 as a template for all other WPs. R[3]16. Clean up the backlog, and keep it up to date at all times. Specific resources must be dedicated to this. R[3]17. Focus on delivery of critical-path, high-priority (for the Use Cases) GEs. R[3]18. GE code releases must be synchronized with GE priorities indicated by Use Case projects. R[3]19. Ensure that architectural documentation clearly and unambiguously indicates the trace of source requirements and justification. R[3]20. Transparency and visibility in what was delivered and what is going to be delivered by the consortium in all future FI-WARE Releases. R[3]21. Meeting the "check points" set by the reviewers. For the next period leading up to the M18 review, the reviewers will be monitoring and assessing project progress against the following key "check points", in addition to DoW compliance and assessment of the project deliverables due: 1. Technical Paper including common usage scenarios for the GEs for wide dissemination (incl. to Use Case projects and third parties), month 15 2. Public availability matrix of use cases using the GEs; continuous update of the matrix, month 15 & thereafter 3. FI-WARE software release, month 15 4. Public availability of the SAP GEs in WP3, month 15 (done) 5. Testbed in operation, feedback from UC projects on using the testbed, month 17 6. Enhancement/re-design of the current website for impact creation, month 17 7. Hold additional architectural weeks, develop training plan for use of the DevComE framework, consider inviting 3rd party developers, month 18 8. Develop and publish a plan for fostering developer communities, month 18 9. Live demonstration of the FI-WARE test-bed with deployed GE software, Next review meeting 10. Presentation by senior business personnel from the main commercial partners of the consortium (at a minimum: TID, SAP, TI, Orange/FT) on corporate plans to bring the FI-WARE key results to the market, Next review meeting R[3]22. For the next period overall project resource allocation should be reviewed to identify the specific weaknesses leading to the failings identified in this review project; resources should be re-planned and re-allocated to rectify the failings where necessary. d. Assessment Unsatisfactory progress (The project has failed to achieve key objectives and/or is not at all on schedule) ============================== Some other considerations: After one year in the project, one may want to evaluate what has been achieved, esp taking into account that 12 MEuro has been spent. A specific feature of the first reporting period, and a direct result of the delays, is that efforts have been spent on tasks that did not result in submitted deliverables. The economy, effectiveness and efficiency of these efforts can therefore not be evaluated. More importantly, after one year in the project, one may want to evaluate what can be realistically achieved at the end of the project: - The status and maturity of single GEs differ a lot. More consistency and maturity in the specification of GEs needs to be achieved. The litmus test is that these specifications need to be sufficiently mature and complete so that independent software developers can use them to develop implementations that are interchangeable. Prospect: good. - It is not clear to what extent the GE Open Specifications satisfy the requirements from use cases, FI-WARE organisations, or otherwise. There is a risk that at the end of the project the GE Open Specifications do not satisfy the requirements of the use cases. - The baseline assets of each individual GE are not clear. Partly because of this, the roadmap is not clear. At the end of the project, there will be reference implementations, no doubt, but it is not clear to what extent the GE Open Specifications follow the existing baseline assets or v.v. There is a risk that the reference implementations do not satisfy the requirements of the use cases. - The IPR protection of the reference implementations is unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - Likewise, the exploitation plans of the owners of the reference implementations are unclear. At the end of the project, the use cases need clarity on this. It is essential that this information becomes available as soon as possible. - The division of budgets in FI-WARE is (largely) based on the existence of baseline assets. The more baseline assets a partner brought into the project, the larger its budget in FI-WARE. The advantage is that the work does not start from scratch. It is likely that these baseline assets are typically proprietary solutions. It can be expected that partners will give priority to their baseline assets, further developing these assets, and give less priority to fulfilling use case requirements. Although access to these assets by use case projects after the end of the FI-WARE project is addressed by clause 41, the exact conditions for access, the availability of the assets, and their maturity are unknown. This leaves use cases, possible FI-WARE Instance providers, and third party application developers in an uncertain situation, and clarity is necessary. - There is a high risk that current developments on GE reference implementations do not fulfil the requirements of the use cases. This could be accepted to some extent if these reference implementations would be based on clear requirements from the business departments of the technology providers, and if there were clear exploitation plans for these reference implementations. In such situation, usefulness to use cases would be offset by wide availability and accessibility. However, at the moment there is a high risk that at the end of the FI-WARE project the reference implementations will not fulfil the requirements from the use cases AND will not be accessible. The month 18 review and the Call 2 evaluation will provide an opportunity to analyse the situation with respect to a) the FI-WARE GEs and their reference implementations, b) the priorities of the phase 2 use cases, and c) the commitments of the FI-WARE beneficiaries. Regarding the FI-WARE GEs and their reference implementations, information is needed a.o. concerning: - The final list of GEs for which Open Specifications will be written - The extent to which these GEs fulfil requirements (from all sources), providing justification and accountability - For each GE: the reference implementation(s) of the GE - For each GE reference implementation: the baseline asset(s) upon which the reference implementation will be based, the current status, the owner, the relation to other GE (reference implementations) Regarding the phase 2 use cases: - The list of GEs the phase 2 use cases plan to use, and their priority - The list of GE reference implementations the phase 2 use cases plan to use, and their priority Regarding the commitment of the FI-WARE beneficiaries: - For each GE reference implementation: the conditions under which it will be available for FI-PPP programme participants and third parties beyond the lifetime of FI-WARE With respect to the last point, stated intentions in confidential exploitation plans are not sufficient. True commitment and therefore true assurance of the use cases and third parties of the sustainability of their efforts building on FI-WARE can be shown via e.g. a public statement by the GE reference implementation IPR holders. Such a public statement could follow lines as sketched below: - "Our developments in FI-WARE/FI-PPP will be made available as open-source, and/or - Our developments in FI-WARE will be proprietary, conforming to the GE Open Specifications, and we guarantee that they will be available on the market as of [date] under FRAND conditions and will be available for at least [y] years. The exact conditions will be specified within [x] months. In case our companies determine the product will no longer be commercially offered, the source code will be made available as open source and donated to [xyz], and/or - Company X is developing an implementation of a certain GE. Within FI-WARE, an open source reference implementation of the same GE is being developed. Company X builds a proprietary implementation, outside the FI-WARE project, using own funds, and/or - Our companies encourage the development of multiple implementations of a certain GE, will develop a reference implementation for each of the specified GEs within the context of the FI-WARE project, using public money, and will develop additional proprietary implementations [for GEs g,h,k] using own funds - We commit to safeguard the evolution and nature of the GEs for at least [x] years after the FI-PPP programme. - Etc" ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt 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: