From mcp at tid.es Wed Aug 1 00:29:58 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 01 Aug 2012 00:29:58 +0200 Subject: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP In-Reply-To: <93D28BDF64839C468B848D14227151A2C531E5@FIESEXC014.nsn-intra.net> References: <50116A64.9010907@tid.es> <5012952C.4080503@tid.es> <5012B6F1.4090105@tid.es> <93D28BDF64839C468B848D14227151A2C531E5@FIESEXC014.nsn-intra.net> Message-ID: <50185C66.8010307@tid.es> Hi I am not sure if I answered this. El 29/07/2012 7:55, Farkas, Lorant (NSN - HU/Budapest) escribi?: > Hi Miguel, > > The guidelines are a bit misleading, from 2 perspectives: > 1. for PP assets that are non SaaS the understanding so far was that the partner will upload the binaries and install/admin guide in the testbed on the VM you provide for the GE. Yes, correct. In this case is up to them to put in place the ssh servers or whatever they set up to make them available. No one will help them or provide support (we would help here just for testbed related issues) Alternatively, you can upload it to the SCM in the PPP-Restricted project. > 2. my understanding was that this would be a possibility also for SaaS GE-s: they could have a VM just to host the binaries and the install/admin guide, while the GE runs as a service at the premises of the partner. > Is my understanding wrong? You are right. Alternatively, they could have it on their remote servers hosted at their premises. > > Thanks & Br, A real shame to see you leave, honestly. B.R. > > Lorant > > > -----Original Message----- > From: fiware-wpa-bounces at lists.fi-ware.eu on behalf of ext Miguel Carrillo > Sent: Fri 7/27/2012 5:42 PM > To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Subject: Re: [Fiware-wpa] Format of deliverable linked to software and Installation/Administration Guides of GEs marked as PP > > Dear all, > > > We have received comments to the wording. Anyway, I uploaded the final version to the tutorial to make sure that we do not lean on emails and centralise it a bit. > > . https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverables#Instructions_for_the_delivery_of_the_Installation_and_Administration_Guide > > BR > > Miguel > > > El 27/07/2012 15:18, Miguel Carrillo escribi?: > Dear all, > > Further to this message from Juanjo and after a reasonable wait for comments, I send the definite template that tries to be reasonable uniform with the wiki-generated pdf files. > > Fill in the part in yellow (note that there is also one in the header) and then place them in the installation guide in he place where you would have the part of the PP enabler if it was PU. This implies printing this out to pdf and using the pdf handling tool I mention in the manual to generate pdf deliverables (of course, if you can use another tool if you like). > > Best regards, > > Miguel > > > El 26/07/2012 18:03, Juanjo Hierro escribi?: > Dear colleagues, > > As already announced, the software and Installation/Administration Guides of GEs marked as PP will be covered by the insertion of a page per GE that will be part of the corresponding WP deliverable. > > Following is the draft text of the page we plan to insert for your consideration in case you have any comments (please send them not just to me but with cc to Miguel): > > === > - Software Release and Installation and Administration guide > The GE will be offered as a service by the GE owner. Besides, the software release of the GE and the accompanying Installation and Administration guide are of PP dissemination level[1]. > In accordance with the privacy restrictions requested by GE owner, both the software (binaries) and the Installation and Administration Guides were not reviewed by the FI-WARE coordinator or the Work Package leader and the responsibility for the quality and appropriateness of this part of the deliverables remain solely with the partner who is the GE owner. > The software (binaries) and the Installation and Administration Guides are accessible to the EC for reviewing purposes on a remote server located at via ssh with user: EC and password to be disclaimed upon explicit request to the project coordinator. The partner who is the GE owner will govern this access. > > ________________________________ > [1] Restricted to FI-PPP programme participants (including the Commission Services) upon request in writing, where access to the API is not sufficient for execution of a FI-PPP project. > > > ==== > > > The final version of this text, incorporating any comment you may have, will be provided to you in Word format by tomorrow. > > Best, > > > -- 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 > > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: mcp at tid.es > > Follow FI-WARE on the net > > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: http://twitter.com/Fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: mcp at tid.es > > Follow FI-WARE on the net > > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: http://twitter.com/Fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > . > -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From matteo.melideo at eng.it Wed Aug 1 12:09:53 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Wed, 01 Aug 2012 12:09:53 +0200 Subject: [Fiware-wpa] *** EXTREMELY IMPORTANT *** How to populate the catalogue!!! Message-ID: <50190071.8020308@eng.it> Dear All, sorry if the mail is a bit long but I think it is extremely necessary after the conference call we had yesterday and the current status of the catalogue. The first clarificationis that in our view (catalogue and testbed), these are the existing relationships: - 1 Generic Enabler Open Specification corresponds to 1..N Generic Enabler implementations. - 1 Generic Enabler implementation can have 1...N Generic Enabler Instance\s. (The reason for the last relationship is that in the future, according to the DoW, we assume the possibility to have not only the FI-WARE Testbed but different FI-WARE Instances. For this reason we assume that for 1 Generic Enabler implementation there could be different endpoints (instances) on different FI-WARE Instances). The second clarificationis that the FI-WARE Catalogue is the FI-WARE Generic Enablers Implementations Catalogue(we will change the name accordingly and explain this in the first page as an introduction for the potential users). This means that each entry into the catalogue should represent an implementation (complete or partial) of a Generic Enable Open specification and this MUST be evident!!! The third clarificationconcerns how to populate the different pages arranged for each Generic Enabler Implementation: Overview - Instances - Download - Documentation. (For the "Instances" label we will also try to find a more self explanatory alternative). Overview: this page should explain what you are offering and mainly what GE Open Specification you are implementing, detailing if you are implementing all the specification or only part of it and, if possible an overview of the API. (see attached file for template) To note: Where and when it makes sense you should also include links to wiki pages (e.g., when referring to the Open Specifications, it should be the link to the wiki page where the specifications are published). Instances: this is a very simple page where it should be specified at least one URL of the endpoint where requests to operations of the RESTFul API can be directed in order to interact with the GE. (One endpoint as at the moment there is only the FI-WARE Testbed. Hopefully in the next future we will have more endpoints if there will be more FI-WARE Instances). For this endpoint you have the opportunity to provide any additional information you may consider helpful (e.g. registration required, legal constraints, terms of use, etc.). In this page it is also possible to add links to admin pages or user interface pages related to the specific GE instance (e.g., Cloud Portal) IMPORTANT NOTE: At this time we don't know, but we may lead to multiple instances of the same GE implementation deployed on the FI-WARE Testbed, each serving a concrete UC project (because the GE implementation happens not to be multi-tenant, or there are conditions that recommend so). If that it is the case, the information of each of those instances should be listed here, clear enough as to allow each UC project to find out what instance to use or ask for a specific one. (see attached file for template) Download: this page is to add any client, library, driver, stub or whatever necessary to be installed locally to interact with the GE endpoint. In addition to this, it will be possible to add the source code or binaries (whatever is applicable) of the GE implementation of those GEs that are public plus any other file or necessary document (release notes, license and terms of use, etc.) (see attached file for template) Documentation: any information necessary for the developer to use the endpoint and the sw listed in the download page (e.g code examples, how to use, tricks and tips, etc.). This page should include at least the Users' and Programmers' Guide that has been produced for the release. (see attached file for template) It is important to note that the GEs that will not comply with the rules above will not be published in the catalogue (or unpublished for those already published) and therefore not be made accessible to UC projects. We pretend that the FI-WARE Generic Enablers Implementations Catalogue becomes the single, user-friendly, mean through which the UC projects will get all the information they need to start using the GE implementations available at the FI-WARE Testbed. In this respect, we expect that the catalogue is populated and\or updated in parallel with the deployment of the GE instance in the FI-WARE Testbed. Please do not hesitate to ask for additional clarifications and send us comments and suggestions to improve. Thanks a lot for your cooperation and best regards, Matteo, Davide Stefano and Juanjo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Catalogue sections templates.doc Type: application/msword Size: 18944 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Wed Aug 1 17:05:19 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Aug 2012 17:05:19 +0200 Subject: [Fiware-wpa] [Suspected Spam] Fwd: Availability of the FI-WARE Testbed (first step, accessing to the FI-WARE Catalogue) In-Reply-To: <50194452.9040402@tid.es> References: <50194452.9040402@tid.es> Message-ID: <501945AF.20107@tid.es> FYI. Next steps regarding availability of the FI-WARE Testbed have been announced to the whole FI-PPP community. Please keep focus in delivering. Best regards, -- Juanjo and Stefano -------- Original Message -------- Subject: Availability of the FI-WARE Testbed (first step, accessing to the FI-WARE Catalogue) Date: Wed, 1 Aug 2012 16:59:30 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu , all at fi-ppp.eu CC: stefano de panfilis , Matteo Melideo , "jhierro >> \"Juan J. Hierro\"" Dear members of the FI-PPP and particularly Use Case projects, This mail is to inform you about the process we will follow to announce the availability on the FI-WARE Testbed of FI-WARE GEs being part of the 1st Release of FI-WARE and the steps you will have to perform to get access to each FI-WARE GE and start playing with them. How to understand how to use a FI-WARE GE once it becomes available on the testbed? The FI-WARE Catalogue will become the single, user-friendly mean through which you will get all the information you need to start using the GE implementations available at the FI-WARE Testbed. You should navigate to http://fi-ware.cloud.labs.ericsson.net/ in order to get access to the FI-WARE Catalogue (note that this URL address will change to one under the fi-ware.eu domain later on). There, per each FI-WARE GE, you will find: * An Overview, providing general information about the FI-WARE GE with shortcuts to relevant resources on the FI-WARE wiki that contain valuable information about the GE. We hope this will guide you through the FI-WARE public wiki so you don't get lost in the forest :-) * Information about the Instance of the FI-WARE GE you will be able to play with. This will compile information such as URLs of endpoints serving RESTFul API requests, URLs linked to Web-based User or Admin Interfaces, etc. * Downloads section from which you will be able to download configuration files, binaries or libraries you may need to install locally, etc * Valuable Documentation that will help you using the FI-WARE GE such as Users' and Programmers' Guides Contents in the FI-WARE Catalogue linked to each FI-WARE GE are currently being filled in parallel to deployment of the FI-WARE GE implementation instances on the FI-WARE Testbed. This means that you may find information regarding some FI-WARE GEs not yet finalized. Please, take this into account. We will announce when each FI-WARE GE is fully available and, therefore, the corresponding contents on the FI-WARE Catalogue are complete and ready for you. At that point in time, you will be requested to provide the IP addresses from which to access the FI-WARE GE Instance that has been made available. This is required to grant secured access only to UC projects. The count down has already started and the first set of FI-WARE GEs will be announced before the end of this week. The rest of the FI-WARE GEs planned to be delivered by end of July will be announced as they become available. Unfortunately, FI-WARE Cloud Hosting capabilities will not be offered until mid September because the required servers have not yet been received. On the other hand, you will be able to start playing with the rest of FI-WARE GEs during August, since they will be available from dedicated servers already allocated at the FI-WARE Testbed. Last but not least, please bear in mind that the FI-WARE Catalogue itself is still work in progress meaning basically that: * other functionalities and services still planned will be added to the catalogue to make it more functional and effective * there will be always the opportunity for you to open tickets on the catalogue usage reporting bugs, suggestions, etc. Best regards, Juanjo Hierro, Chief Architect and Technical Manager, FI-WARE Stefano de Panfilis, Leader of the FI-WARE Testbed ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Aug 1 17:15:46 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 01 Aug 2012 17:15:46 +0200 Subject: [Fiware-wpa] IMPORTANT: Deadline for availability of GEs on the Testbed In-Reply-To: <5019013D.3060404@tid.es> References: <5019013D.3060404@tid.es> Message-ID: <50194822.7030806@tid.es> Dear colleagues, This mail is just to remind you that in order to accept that a given GE has been effectively delivered on the Testbed, two requirements have to be fulfilled: * The GE should be available, i.e. deployed on Testbed VMs (or on remote premises for those few GEs that were accepted to be delivered as a Service in remote facilities) * Information of the GE on the FI-WARE Catalogue should be complete and should contain the information that will allow UC projects to start using the GE. Please check the defined guidelines as already mentioned in the mail sent this morning by Matteo (subject "*** EXTREMELY IMPORTANT *** How to populate the catalogue!!!") With the exception of Cloud Hosting GEs, for which deployment has been delayed until September because the final infrastructure won't be ready yet, all the rest of GEs planned to be available on the testbed by end of July have to fulfill these two requirements before August 15th. Failing to meet that deadline will be interpreted so that the resources of the partner allocated in the Testbed WP have not been properly put in place, and therefore corresponding cost statements regarding WP10 (Testbed) will be rejected. Note that the UC projects have been just informed about the existence of the FI-WARE Catalogue for consultation. Best regards, -- Juanjo and Stefano ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Aug 2 06:46:15 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 Aug 2012 06:46:15 +0200 Subject: [Fiware-wpa] Fwd: FI-WARE 2nd Open Call In-Reply-To: <501A05BE.4020107@tid.es> References: <501A05BE.4020107@tid.es> Message-ID: <501A0617.4000803@tid.es> Dear friends, FYI, the announcement of the FI-WARE 2nd Open Call. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE 2nd Open Call Date: Thu, 02 Aug 2012 06:44:46 +0200 From: Juanjo Hierro To: all at fi-ppp.eu CC: ab at fi-ppp.eu Dear members of the FI-PPP, I'm glad to announce that the 2nd Open Call of the FI-WARE project has been launched. You may find all the information at the FI-WARE website: * http://www.fi-ware.eu/open-call/ Please help us to disseminate the call trough all the channels at your hands. Thanks to all who have contributed. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Aug 2 06:55:53 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 Aug 2012 06:55:53 +0200 Subject: [Fiware-wpa] Next steps and responsibilities Message-ID: <501A0859.8070105@tid.es> Dear colleagues, I'm going to be relatively off-line during the coming days because I will be on holidays. However, I will be able to connect every night and send/respond some messages. Nevertheless, Miguel is acting while I'm on holidays. Regarding announcement of the availability of GEs in the FI-WARE Testbed, Stefano de Panfilis will be one who will perform such announcements on behalf of FI-WARE. As per agreement during our last confcall, Stefano, supported by Matteo and Miguel, owns the right to decide when a FI-WARE GE complies with the requirements for announcing its availability to UC projects: * The GE should be available, i.e. deployed on Testbed VMs (or on remote premises for those few GEs that were accepted to be delivered as a Service in remote facilities) * Information of the GE on the FI-WARE Catalogue should be complete and should contain the information that will allow UC projects to start using the GE. Please check the defined guidelines as already mentioned in the mail sent this morning by Matteo (subject "*** EXTREMELY IMPORTANT *** How to populate the catalogue!!!") Sometime during this evening/night, before tomorrow, I will send a couple of emails dealing with: * Peer-review of FI-WARE GE Open Specifications * Peer-review of Architecture document * Guidelines for reviewing the FI-WARE Technical Roadmap (to be submitted early next week) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Thu Aug 2 19:44:46 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Thu, 2 Aug 2012 19:44:46 +0200 Subject: [Fiware-wpa] Deliveraable Message-ID: <2C6296E1876B5C49962495FDACDC7A6361676C53D3@DEWDFECCR01.wdf.sap.corp> --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axel.fasse at sap.com Thu Aug 2 20:11:18 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Thu, 2 Aug 2012 20:11:18 +0200 Subject: [Fiware-wpa] Deliverable D2.5 Message-ID: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> Dear partners, sorry for the first mail without content. So far as I have seen, not all of the comments of Juanjo are handled properly by all of us. I would suggest that you finalize this issue until tomorrow. Maybe we can use the meeting on Monday to walk through the document and share our opinions about the thinks that should be done before have the last review. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 3 10:02:26 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 Aug 2012 10:02:26 +0200 Subject: [Fiware-wpa] Instructions for resubmission of FI-WARE Technical Roadmap Message-ID: <501B8592.9040109@tid.es> Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Aug 3 10:20:15 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 3 Aug 2012 08:20:15 +0000 Subject: [Fiware-wpa] Deliverable D2.5 In-Reply-To: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> References: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> Message-ID: <27280_1343982016_501B89C0_27280_2845_1_976A65C5A08ADF49B9A8523F7F81925C02EF34@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Axel, Some changes are now integrated in D2.5 for IoT. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Fasse, Axel Envoy? : jeudi 2 ao?t 2012 20:11 ? : fiware-wpl at lists.fi-ware.eu Cc : fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Deliverable D2.5 Dear partners, sorry for the first mail without content. So far as I have seen, not all of the comments of Juanjo are handled properly by all of us. I would suggest that you finalize this issue until tomorrow. Maybe we can use the meeting on Monday to walk through the document and share our opinions about the thinks that should be done before have the last review. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. _________________________________________________________________________________________________________________________ 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 axel.fasse at sap.com Fri Aug 3 10:23:51 2012 From: axel.fasse at sap.com (Fasse, Axel) Date: Fri, 3 Aug 2012 10:23:51 +0200 Subject: [Fiware-wpa] Deliverable D2.5 In-Reply-To: <27280_1343982016_501B89C0_27280_2845_1_976A65C5A08ADF49B9A8523F7F81925C02EF34@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> <27280_1343982016_501B89C0_27280_2845_1_976A65C5A08ADF49B9A8523F7F81925C02EF34@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2C6296E1876B5C49962495FDACDC7A636167E876CB@DEWDFECCR01.wdf.sap.corp> Dear Thierry, thank you very much, I will check all contributions later in the evening. Best regards, Axel From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Freitag, 3. August 2012 10:20 To: Fasse, Axel; fiware-wpl at lists.fi-ware.eu Cc: fiware-wpa at lists.fi-ware.eu Subject: RE: Deliverable D2.5 Hi Axel, Some changes are now integrated in D2.5 for IoT. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Fasse, Axel Envoy? : jeudi 2 ao?t 2012 20:11 ? : fiware-wpl at lists.fi-ware.eu Cc : fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Deliverable D2.5 Dear partners, sorry for the first mail without content. So far as I have seen, not all of the comments of Juanjo are handled properly by all of us. I would suggest that you finalize this issue until tomorrow. Maybe we can use the meeting on Monday to walk through the document and share our opinions about the thinks that should be done before have the last review. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. _________________________________________________________________________________________________________________________ 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 matteo.melideo at eng.it Fri Aug 3 10:28:28 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Fri, 03 Aug 2012 10:28:28 +0200 Subject: [Fiware-wpa] "*** EXTREMELY IMPORTANT *** How to populate the catalogue!!!" ... follow up Message-ID: <501B8BAC.2030903@eng.it> Dear all, this is to inform you that on the catalogue it is currently published a GE which perfectly fits with the new guidelines provided. Please look at the Location Platform GE as reference example. Best regards Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From mcp at tid.es Fri Aug 3 16:08:10 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 03 Aug 2012 16:08:10 +0200 Subject: [Fiware-wpa] [Suspected Spam] Re: Deliverable D2.5 In-Reply-To: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> References: <2C6296E1876B5C49962495FDACDC7A6361676C5408@DEWDFECCR01.wdf.sap.corp> Message-ID: <501BDB4A.60804@tid.es> Hi I was thinking whether to keep the meeting or not but after Axel's request we will keep it. I will provide the coordinates to join the meeting on monday morning. I will also produce an agenda that will be as short as possible. BR Miguel El 02/08/2012 20:11, Fasse, Axel escribi?: Dear partners, sorry for the first mail without content. So far as I have seen, not all of the comments of Juanjo are handled properly by all of us. I would suggest that you finalize this issue until tomorrow. Maybe we can use the meeting on Monday to walk through the document and share our opinions about the thinks that should be done before have the last review. Best regards, Axel --------------------------- Axel Fasse Senior Researcher SAP Research Karlsruhe SAP AG Vincenz-Priessnitz-Strasse 1 76131 Karlsruhe, Germany T +49 6227 7-52528 F +49 6227 78-55237 M +4915153858917 E axel.fasse at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 6 10:30:26 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 Aug 2012 10:30:26 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall Message-ID: <501F80A2.8000106@tid.es> Dear all, We are having the weekly confcall as usual Same details as always: * Powwownow. PIN: 050662. Local dial-in phone numbers at: * http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf I will send the minutes shortly. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 6 10:58:04 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 Aug 2012 10:58:04 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall In-Reply-To: <501F80A2.8000106@tid.es> References: <501F80A2.8000106@tid.es> Message-ID: <501F871C.1060106@tid.es> Dear all, Due to unavailability oif meeting rooms here until then, we will start a bit later: 11:15 See you in a bit and sorry for the inconveniences. Miguel El 06/08/2012 10:30, Miguel Carrillo escribi?: Dear all, We are having the weekly confcall as usual Same details as always: * Powwownow. PIN: 050662. Local dial-in phone numbers at: * http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf I will send the minutes shortly. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 6 11:16:24 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 Aug 2012 11:16:24 +0200 Subject: [Fiware-wpa] Joint WPLs/WPAs follow-up confcall In-Reply-To: <501F80A2.8000106@tid.es> References: <501F80A2.8000106@tid.es> Message-ID: <501F8B68.9070100@tid.es> Dear all, The minutes for today. https://docs.google.com/document/d/1w4cPPSuQm9rPIJ1m3V9qXGZ35u9R0AK_89YNbjyMWBg/edit# BR Miguel El 06/08/2012 10:30, Miguel Carrillo escribi?: Dear all, We are having the weekly confcall as usual Same details as always: * Powwownow. PIN: 050662. Local dial-in phone numbers at: * http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf I will send the minutes shortly. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.melideo at eng.it Mon Aug 6 12:34:35 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Mon, 06 Aug 2012 12:34:35 +0200 Subject: [Fiware-wpa] About the catalogue Message-ID: <501F9DBB.8010407@eng.it> Dear All, from now on the contact persons for any problem concerning the FI-WARE Catalogue are: Mattias Wallenberg and Marika Stalnake from Ericsson. Me and Davide will always be in CC as Wp Leader and Wp Architect. For any ticket or issue the bugtracker is anyway available at: https://forge.fi-ware.eu/tracker/?atid=208&group_id=15&func=browse. Best regards, Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Wed Aug 8 10:28:33 2012 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Wed, 08 Aug 2012 10:28:33 +0200 Subject: [Fiware-wpa] *** IMPORTANT TO BE READ *** How to populate the catalogue!!! In-Reply-To: <50190071.8020308@eng.it> References: <50190071.8020308@eng.it> Message-ID: <50222331.8090102@eng.it> Dear All, I forward you again the instructions already provided to the WP leaders, on hot to populate the Catalogue. Please pay attention to the attachment as well. CONTACT PERSONS for the CATALOGUE are: - Mattias Wallenberg (mattias.wallenberg at ericsson.com) - Marika Stalnake (marika.stalnacke at ericsson.com) from August 27th: - Matteo Melideo (matteo.melideo at eng.it) - Davide Dalle Carbonare (davide.dallecarbonare at eng.it) note: please find included on the instructions the indications on how to publish non multi-tenant GE Implementations. Kind Regards, Davide Dalle Carbonare -------- Original Message -------- Subject: *** EXTREMELY IMPORTANT *** How to populate the catalogue!!! Date: Wed, 01 Aug 2012 12:09:53 +0200 From: Matteo Melideo Reply-To: matteo.melideo at eng.it Organization: Engineering Ingegneria Informatica S.p.A. To: FI-WARE WPL , "fiware-wpa at lists.fi-ware.eu" CC: Juanjo Hierro , stefano de panfilis , Dalle Carbonare Davide Dear All, sorry if the mail is a bit long but I think it is extremely necessary after the conference call we had yesterday and the current status of the catalogue. The first clarificationis that in our view (catalogue and testbed), these are the existing relationships: - 1 Generic Enabler Open Specification corresponds to 1..N Generic Enabler implementations. - 1 Generic Enabler implementation can have 1...N Generic Enabler Instance\s. (The reason for the last relationship is that in the future, according to the DoW, we assume the possibility to have not only the FI-WARE Testbed but different FI-WARE Instances. For this reason we assume that for 1 Generic Enabler implementation there could be different endpoints (instances) on different FI-WARE Instances). The second clarificationis that the FI-WARE Catalogue is the FI-WARE Generic Enablers Implementations Catalogue(we will change the name accordingly and explain this in the first page as an introduction for the potential users). This means that each entry into the catalogue should represent an implementation (complete or partial) of a Generic Enable Open specification and this MUST be evident!!! The third clarificationconcerns how to populate the different pages arranged for each Generic Enabler Implementation: Overview - Instances - Download - Documentation. (For the ?Instances? label we will also try to find a more self explanatory alternative). Overview: this page should explain what you are offering and mainly what GE Open Specification you are implementing, detailing if you are implementing all the specification or only part of it and, if possible an overview of the API. (see attached file for template) To note: Where and when it makes sense you should also include links to wiki pages (e.g., when referring to the Open Specifications, it should be the link to the wiki page where the specifications are published). Instances: this is a very simple page where it should be specified at least one URL of the endpoint where requests to operations of the RESTFul API can be directed in order to interact with the GE. (One endpoint as at the moment there is only the FI-WARE Testbed. Hopefully in the next future we will have more endpoints if there will be more FI-WARE Instances). For this endpoint you have the opportunity to provide any additional information you may consider helpful (e.g. registration required, legal constraints, terms of use, etc.). In this page it is also possible to add links to admin pages or user interface pages related to the specific GE instance (e.g., Cloud Portal) IMPORTANT NOTE: At this time we don't know, but we may lead to multiple instances of the same GE implementation deployed on the FI-WARE Testbed, each serving a concrete UC project (because the GE implementation happens not to be multi-tenant, or there are conditions that recommend so). If that it is the case, the information of each of those instances should be listed here, clear enough as to allow each UC project to find out what instance to use or ask for a specific one. (see attached file for template) Download: this page is to add any client, library, driver, stub or whatever necessary to be installed locally to interact with the GE endpoint. In addition to this, it will be possible to add the source code or binaries (whatever is applicable) of the GE implementation of those GEs that are public plus any other file or necessary document (release notes, license and terms of use, etc.) (see attached file for template) Documentation: any information necessary for the developer to use the endpoint and the sw listed in the download page (e.g code examples, how to use, tricks and tips, etc.). This page should include at least the Users' and Programmers' Guide that has been produced for the release. (see attached file for template) It is important to note that the GEs that will not comply with the rules above will not be published in the catalogue (or unpublished for those already published) and therefore not be made accessible to UC projects. We pretend that the FI-WARE Generic Enablers Implementations Catalogue becomes the single, user-friendly, mean through which the UC projects will get all the information they need to start using the GE implementations available at the FI-WARE Testbed. In this respect, we expect that the catalogue is populated and\or updated in parallel with the deployment of the GE instance in the FI-WARE Testbed. Please do not hesitate to ask for additional clarifications and send us comments and suggestions to improve. Thanks a lot for your cooperation and best regards, Matteo, Davide Stefano and Juanjo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Catalogue sections templates.doc Type: application/msword Size: 18944 bytes Desc: not available URL: From mcp at tid.es Wed Aug 8 15:43:26 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 08 Aug 2012 15:43:26 +0200 Subject: [Fiware-wpa] Comments for Features Message-ID: <50226CFE.4040000@tid.es> Dear all, One of the APs from the last WPL/WPA confcall was to assess the status of the Features. I recently contacted Juanjo and one of the things I mentioned was this. He gave me the status, that is as follows: * Apps- - OK save for the Mediator. We have not seen an answer to the initial comments. WP3 will have to see how to handle the changes requested and not implemented. The WPL should look into this. Juanjo is telling me that you have clear directions of how to do so. * Cloud- OK * Data - OK * Sec - OK * IoT - OK * I2ND - OK So all are fine but WP3. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Aug 8 16:21:02 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 08 Aug 2012 16:21:02 +0200 Subject: [Fiware-wpa] Completion of Roadmap document - important Message-ID: <502275CE.4010300@tid.es> Dear WPLs, WPAs and also temporary "replacements", There is something that Juanjo is specifically asking me to send you as it seems that there's a certain degree of confusion. I already warned some of you in private the other day but let us make it clear for everyone. The Roadmap document should be finished urgently. The backlog and its features are complete enough to fill in the table in the Tech. Roadmap. The Release Id should give you the key. Although you may have requested the contribution of partners to provide info, this is something that is asked to the WPLs and therefore it is your direct responsibility. In other words, no one can say that the contribution of a given WP is not available on the grounds of not having a contribution from one partner. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From GLIKSON at il.ibm.com Wed Aug 8 17:02:55 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 8 Aug 2012 18:02:55 +0300 Subject: [Fiware-wpa] [Fiware-wpl] Completion of Roadmap document - important In-Reply-To: <502275CE.4010300@tid.es> References: <502275CE.4010300@tid.es> Message-ID: How urgent? What is the expected delivery process & schedule? Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Miguel Carrillo To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 08/08/2012 05:21 PM Subject: [Fiware-wpl] Completion of Roadmap document - important Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear WPLs, WPAs and also temporary "replacements", There is something that Juanjo is specifically asking me to send you as it seems that there's a certain degree of confusion. I already warned some of you in private the other day but let us make it clear for everyone. The Roadmap document should be finished urgently. The backlog and its features are complete enough to fill in the table in the Tech. Roadmap. The Release Id should give you the key. Although you may have requested the contribution of partners to provide info, this is something that is asked to the WPLs and therefore it is your direct responsibility. In other words, no one can say that the contribution of a given WP is not available on the grounds of not having a contribution from one partner. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Aug 8 17:17:02 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 08 Aug 2012 17:17:02 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Completion of Roadmap document - important In-Reply-To: References: <502275CE.4010300@tid.es> Message-ID: <502282EE.9040706@tid.es> Mmmm ... you made me dig in my old email messages and I found this one that I enclose. It looks like this is for yesterday! It looks a bit challenging, particularly for those who have not started. So the answer is asap. I will ask Juanjo if I have to deliver this soon and when (I do not have a delivery schedule but I suspect that we would have delivered by now I we had been able to!). Best regards Miguel El 08/08/2012 17:02, Alex Glikson escribi?: How urgent? What is the expected delivery process & schedule? Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Miguel Carrillo To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 08/08/2012 05:21 PM Subject: [Fiware-wpl] Completion of Roadmap document - important Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear WPLs, WPAs and also temporary "replacements", There is something that Juanjo is specifically asking me to send you as it seems that there's a certain degree of confusion. I already warned some of you in private the other day but let us make it clear for everyone. The Roadmap document should be finished urgently. The backlog and its features are complete enough to fill in the table in the Tech. Roadmap. The Release Id should give you the key. Although you may have requested the contribution of partners to provide info, this is something that is asked to the WPLs and therefore it is your direct responsibility. In other words, no one can say that the contribution of a given WP is not available on the grounds of not having a contribution from one partner. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: [Fiware-wpa] Instructions for resubmission of FI-WARE Technical Roadmap Date: Fri, 03 Aug 2012 10:02:26 +0200 Size: 21446 URL: From jhierro at tid.es Thu Aug 9 06:46:06 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 09 Aug 2012 06:46:06 +0200 Subject: [Fiware-wpa] Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <501B8592.9040109@tid.es> References: <501B8592.9040109@tid.es> Message-ID: <5023408E.1070900@tid.es> Hi all, I have taken a look at the progress of the Technical Roadmap ... and the results are rather discouraging ... I have to confess that I feel rather frustrated given the fact that I worked at night trying to produce a well defined set of guidelines so that you could start working on this without further delay. So far, the only chapters for which I have seen the requested contributions covered are the Apps chapter (I have realized they have already made them available on the public wiki, no issue at all) and the Security Chapter. I see this empty for the rest, despite it is an exercise that most probably takes a couple of hours maximum if information of the release where a given feature is covered is documented on the tracker or at least known by you (something that I would expect). I rather ask you to urgently tackle this and deliver it no later than TOMORROW 10:30am because I would like to be able to resubmit the Technical Roadmap by end of this week. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 03/08/12 10:02, Juanjo Hierro wrote: Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 10 07:37:16 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Aug 2012 07:37:16 +0200 Subject: [Fiware-wpa] Follow-up of the FI-WARE General Support tracker Message-ID: <50249E0C.3010807@tid.es> Hi all, As you know, we have asked the FI-WARE UC projects to use the "FI-WARE General Support" tracker to drive all their new requests ... leaving the "FI-WARE Theme/Epic/Feature requests" apart for the time being. It would be nice that each WPL takes as a regular duty to review the tracker and handle the tickets that are attached to his chapter. I know that we have all many things on our plates, but bear in mind that collaboration with UC projects is something that is being monitored closely and feedback from UC projects regarding how this collaboration is working will be key. They seem to do all their best on their side using the tools that we put in place, so let's respond to their effort with a reasonable support ! Miguel: I would make this a point in the agenda of our next WPL/WPA follow-up confcall (I understand this monday Aug 13th) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 10 10:56:26 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Aug 2012 10:56:26 +0200 Subject: [Fiware-wpa] POINT THAT MUST BE CRISTAL CLEAR ABOUT GEs and the way they will be offered to UC projects Message-ID: <5024CCBA.7010103@tid.es> Dear colleagues, I would like to make a number of points clear, hoping the issue is not raised again and again: * It has already been discussed many times and decided that FI-WARE GEs are going to be hosted only in the dedicated datacenter facilities linked to the FI-WARE Testbed by default: * Using a set of dedicated VMs for the First Release of FI-WARE. * Relaying on the FI-WARE Cloud that will be available as part of the FI-WARE Testbed for the Second Release of FI-WARE. * This is not just because it is always nice to eat our own dog food, but because we are also asked to go beyond just being able to demonstrate that GEs can run standalone and interoperate. We are asked to demonstrate that a particular player, who wants to play the role of FI-WARE Instance Provider, is able to create an integrated FI-WARE Instance by means of picking and bundle together a number of products implementing FI-WARE GEs. Therefore, the FI-WARE Testbed, besides providing an environment for UC projects to test their Proof of Concepts and provide feedback to FI-WARE Developments and Specifications, is there to prove the feasibility of integrating FI-WARE GEs to build a FI-WARE Instance that can be deployed on a number of concrete datacenter nodes operated by a single operator, as a single platform. Delivering a given FI-WARE GE only as a Service, hosted in facilities provided by the GE owner, raises a lot of questions about the feasibility to build and operate FI-WARE Instances and, therefore, the ability to exploit results of the project. * As consequence of the above: * All FI-WARE GEs have to be made available on the FI-WARE Testbed and offered "as a Service" from there to the UC projects unless explicitly agreed (indeed, the only exceptions to this rule were the Identity Management related GEs, the Location GE and the Cloud Proxy GE, as stated in the FI-WARE Testbed Design deliverable). * We have agreed that there may be some FI-WARE GEs for which there will be instances hosted BOTH in the FI-WARE Tesbed dedicated facilities and in remote facilities, but only with the intend to demonstrate some concrete use cases and provided that the instance located in the FI-WARE Testbed is not delayed (i.e., doesn't get deployed later). * The FI-WARE GEs hosted on the FI-WARE Testbed will be the only ones offered to UC projects for experimentation unless explicitly agreed. * We will not accept justification of any PMs devoted to deploy or support a FI-WARE GE hosted on any infrastructure different than the one linked to the FI-WARE Testbed unless explicitly agreed. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 10 16:21:37 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 Aug 2012 16:21:37 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Instructions for resubmission of FI-WARE Technical Roadmap In-Reply-To: <5023408E.1070900@tid.es> References: <501B8592.9040109@tid.es> <5023408E.1070900@tid.es> Message-ID: <502518F1.9070902@tid.es> Hi, Thanks for those of you that have reacted to my request. Going through a high-level inspection it seems to me that everything is ready there (maybe pending of minor editorial adjustments) for updating the Technical Roadmap pages except for the IoT chapter !!. Please: * Leaders of the IoT chapter: provide your contribution by Sunday EOB at the latest so that we can resubmit the deliverable on Monday. * Rest of the chapters: confirm me by Sunday EOB that everything on your designated placeholders is final. If I receive no mail I will assume contents available on your placeholders were ready for uploading them on the public Wiki Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 09/08/12 06:46, Juanjo Hierro wrote: Hi all, I have taken a look at the progress of the Technical Roadmap ... and the results are rather discouraging ... I have to confess that I feel rather frustrated given the fact that I worked at night trying to produce a well defined set of guidelines so that you could start working on this without further delay. So far, the only chapters for which I have seen the requested contributions covered are the Apps chapter (I have realized they have already made them available on the public wiki, no issue at all) and the Security Chapter. I see this empty for the rest, despite it is an exercise that most probably takes a couple of hours maximum if information of the release where a given feature is covered is documented on the tracker or at least known by you (something that I would expect). I rather ask you to urgently tackle this and deliver it no later than TOMORROW 10:30am because I would like to be able to resubmit the Technical Roadmap by end of this week. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 03/08/12 10:02, Juanjo Hierro wrote: Dear colleagues, Please find here the instructions to be followed to generate a new version of the Technical Roadmap deliverable to be published on the public Wiki and be resubmitted to the EC. The instructions are pretty simple and the best way to explain them is by referring to the example I have created on the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example That example is based on the current contents of the Technical Roadmap linked to the Apps Chapter. Based on that, the steps to follow are: * Update the Introduction: * We should make a reference to contents of the FI-WARE Architecture and Open Specifications part of the wiki, rather than the FI-WARE Product Vision (at the time at which the first version of the Technical Roadmap, the Architecture and Open Specifications didn't exist, but this is no longer the case) * You should also refer to the page dealing with Release and Sprint numbering, with reference to calendar dates. * All of this may be done by simple copy&paste from the reference example. * Description of first Major Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that will be supported. The table shall be preceded by the paragraph: * For a more detailed description of features provided, you can refer to the following table which help to identify what Backlog Features will be supported for each FI-WARE GE: * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. Essentially, you just need to include the references to the Backlog Features that have been addressed in the first Release for each FI-WARE GE (note this list should also include Features supported by the baseline assets) * When you distinguished between the delivery by end of July and by end of September, the above three points indeed apply per each (section for the release by end of July and section for the release by end of September) * Description of second Mayor Release: * The high-level description you had there will be kept, although I have introduced some minor changes in the text to refer to make it clear it was a high-level description (because details will follow). Check the differences between the provided example and the Technical Roadmap of the Apps Chapter currently published on the Wiki. * You will add a table which illustrate, one row per FI-WARE GE planned in the first Major Release, the features that have already been planned or the Epics that will be analyzed and further refine which it is foreseen will lead to specification of Features to be planned as part of the second release. The table shall be preceded by the paragraph: * For a more detailed description of features to be provided, you can refer to the following table which help to identify what Backlog Features have already been specified and planned for the second Major Release of FI-WARE (and indication of the minor release is provided). The table also contain Epics currently under analysis which most probably will lead to the identification of Backlog Features to be planned also in the second Major Release * You will see that table in the reference example, with the details of some of the FI-WARE GEs. I have based them on info available in the public part of the Apps Chapter Backlog available on the public wiki. However, since there were no Backlog Features still planned, I have just created some fictitious features to make the reference example complete. If a FI-WARE GE does have Epics, but not Features, then write down "(not yet specified)" in the column about Features. * Regarding links to Features/Epics. They should be wiki references, as they appear in the reference example. No problem if they do not resolve in the FI-WARE Private Wiki, they should work once translated into the public Wiki * Description of Future Releases: * I believe we can keep this part as it is now I have prepared a section with placeholders for your contributions at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please get them ready by Tuesday 12:00pm CET. It shouldn't be that difficult if you made a good exercise updating Epic/Features in the Backlog. During the rest of August, you should update the stakeholder field of each Epic/Feature in the backlog. Please do it with the best of your knowledge. Put "FI-WARE partners" if an Epic/Feature doesn't come from an UC project but was there within our original plans. Add the name of a UC project if you already know they are looking for it (based, for example, on feedback from the educational sessions). We will ask UC projects in parallel to review the Epics/Features on the wiki and add the name of their project in the plan to use the GE and wish to use the functionality linked to that Epic/Feature. 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 13 08:22:30 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Aug 2012 08:22:30 +0200 Subject: [Fiware-wpa] Peer review of FI-WARE Open Specifications Message-ID: <50289D26.8000202@tid.es> Dear colleagues, One of the actions that we need to carry out is the review of the contents of the FI-WARE Open Specifications. The date that the EC has given to us for re-submitting them is month 18, i.e., end of October. Therefore, we should have enough time. However, it is also true that FI-WARE Open Specifications are one of our key deliverables: they become the ultimate reference UC projects will rely on in order to develop apps based on our GEs. Please find the plan that I would like to follow to carry out a first review of the FI-WARE Open Specifications by end of August. Additional reviews will follow but hopefully this first one will be able to deliver a new version of the specs that is robust and complete enough to be delivered to UC projects: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Leaders of reviewing chapters are asked to designate those members of their teams that own enough technical expertise to judge specifications from the perspective of usefulness by both an application developer (this particularly in the case of RESTFul APIs) and any party that aims to develop a GE implementation in compliance with FI-WARE Open Specifications. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter with cc to fiware-wpl and fiware-wpa: August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes: August 31st, 12:00pm CET Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 13 09:15:01 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Aug 2012 09:15:01 +0200 Subject: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Message-ID: <5028A975.4010405@tid.es> Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 13 09:27:18 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 Aug 2012 09:27:18 +0200 Subject: [Fiware-wpa] [Suspected Spam] Peer review of contents linked to FI-WARE Architecture Description In-Reply-To: <50289D26.8000202@tid.es> References: <50289D26.8000202@tid.es> Message-ID: <5028AC56.60400@tid.es> Dear colleagues, Another of the actions that we need to carry out is also the review of the contents of the FI-WARE Architecture Descriptions. This goes besides the development of the FI-WARE Technical Whitepaper that follows a separate track. We should try to do our best to get the FI-WARE Architecture Description resubmitted by end of August. Please find the plan that I would like to follow to carry out this revision. It is basically the same schema proposed for peer-review of FI-WARE Open Specifications: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND However, I believe that the major caretakers of this review task are WPLs and WPAs themselves. They can forward a request for revision by other members of their team, but mostly to get additional input. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter, with cc to fiware-wpl and fiware-wpa, by August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes by peer-reviewer as well as comments from official reviewers provided in the official FI-WARE review reports: August 31st, 12:00pm CET All WPLs/WPAs should book enough resources the week starting on August 27th to be able to implement their revision. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 13 10:09:30 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 10:09:30 +0200 Subject: [Fiware-wpa] WPL/WPA confcall at 11 Message-ID: <5028B63A.3010801@tid.es> Dear all, This is just a quick reminder. We will have our confcall at 11, as always. The connection details do not change: PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf The minutes will be sent nearer the time. 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 Kay.Haensge at telekom.de Mon Aug 13 10:34:23 2012 From: Kay.Haensge at telekom.de (Kay.Haensge at telekom.de) Date: Mon, 13 Aug 2012 10:34:23 +0200 Subject: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <5028A975.4010405@tid.es> References: <5028A975.4010405@tid.es> Message-ID: <597879B0D1B8E649A12532864A9C949A0148C6954FBD@HE101452.emea1.cds.t-internal.com> Hello Juanjo, I am not sure if I understand your first red marked sentence: "I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing." Does this mean, a or more Feature(s) of the I2ND Materializing Page are missing in the private wiki technical roadmap page? If yes, I will have to double check the entries of the Materializing Page against the Technical Roadmap Page and then put this into the public wiki roadmap page for I2ND. Please give a short feedback about this. Thank you BR Kay H?nsge (Replacement of Pier - I2ND) Mit freundlichen Gr??en / Viele Gr??e / Best Regards Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Montag, 13. August 2012 09:15 An: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 13 10:54:33 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 10:54:33 +0200 Subject: [Fiware-wpa] WPL/WPA confcall at 11 In-Reply-To: <5028B63A.3010801@tid.es> References: <5028B63A.3010801@tid.es> Message-ID: <5028C0C9.3050701@tid.es> Dear all, I have received an email from Juanjo with instructions that have an impact on the agenda. In order to prepare this well I am afraid I need 30 extra minutes. We will therefore postpone our call to 11:30. Sorry for the inconvenience. Best regards, Miguel El 13/08/2012 10:09, Miguel Carrillo escribi?: Dear all, This is just a quick reminder. We will have our confcall at 11, as always. The connection details do not change: PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf The minutes will be sent nearer the time. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 13 11:34:02 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 11:34:02 +0200 Subject: [Fiware-wpa] Link to minutes Message-ID: <5028CA0A.6000509@tid.es> https://docs.google.com/document/d/12FEA380lbmYKEwRPGLHjshqhLqUiWSC8Phuk9BL_kbM/edit# -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Mon Aug 13 12:43:41 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 12:43:41 +0200 Subject: [Fiware-wpa] Summary of WPL/WPA call Message-ID: <5028DA5D.5090506@tid.es> Dear all, Unfortunately, 2 WPs were not represented, namely IoT and Security. This should not happen again in the future, each WP has to appoint people to represent the WPs when the usual representatives are holidays or not available and add them to the WPL list if necessary. The minutes are here: * https://docs.google.com/document/d/12FEA380lbmYKEwRPGLHjshqhLqUiWSC8Phuk9BL_kbM/edit# I would like to stress a few points that need your attention: * 3rd party innovation document * The contribution from some chapters is not uniform with the rest of the WPs. compare with the example provided by SAP and amend accordingly. * This is very serious: this doc explains how we enable actors outside fi-ware to innovate. Some chapters do not provide significant insights in how this capacity will be provided in their WPs. * Delivery delayed to Aug, 16. Please respond quickly to any requests that may come from Juanjo . * WPLs to monitor and attend tickets from the "FI-WARE General Support" Tracker. If you do not know how to monitor a tracker, let me know in private and I'll help. * Technical roadmap: * There is an email from Juanjo with details * IoT and I2ND - blocking resubmission - deadline for contributions: 15 Aug * Rest of chapters: upload it to the public wiki. Link GEs to "materializing..." as the Apps chapter have already done. * Update the Stakeholder field in each backlog entry linked to an Epic or Feature on the wiki * Use the right Release IDs, reflected on * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates * White paper documenting "encompassing usage of GEs" * Will try to provide guidelines by 20 Aug (TOC + examples) - we wanted to put effort here but it got delayed because of the extra work caused by the of lack of quality in the "3rd party innovation" doc * WPL/WPA to be ready to contribute in the 2 last weeks of August. We will possibly ask for just 4 or 5 pages but they will need to have QUALITY * Resubmission of the Architecture document & Peer review * There is an email from Juanjo * The delivery completely decoupled from the technical paper. The edition of the technical paper must not block or interfere with this * Open Specs * There is an email from Juanjo, follow his guidelines Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 13 15:38:10 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 Aug 2012 15:38:10 +0200 Subject: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <597879B0D1B8E649A12532864A9C949A0148C6954FBD@HE101452.emea1.cds.t-internal.com> References: <5028A975.4010405@tid.es> <597879B0D1B8E649A12532864A9C949A0148C6954FBD@HE101452.emea1.cds.t-internal.com> Message-ID: <50290342.2000107@tid.es> Kay, Just to clarify for those who did not attend the call. Apart from minor format issues that will bew addressed by Kay, the problem is that the contribution from I2ND was a broken link (i.e. not linked to the page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4) Kay will look into it. Best regards, Miguel El 13/08/2012 10:34, Kay.Haensge at telekom.de escribi?: Hello Juanjo, I am not sure if I understand your first red marked sentence: ?I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing.? Does this mean, a or more Feature(s) of the I2ND Materializing Page are missing in the private wiki technical roadmap page? If yes, I will have to double check the entries of the Materializing Page against the Technical Roadmap Page and then put this into the public wiki roadmap page for I2ND. Please give a short feedback about this. Thank you BR Kay H?nsge (Replacement of Pier ? I2ND) Mit freundlichen Gr??en / Viele Gr??e / Best Regards Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an ? Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Montag, 13. August 2012 09:15 An: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ 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 Kay.Haensge at telekom.de Tue Aug 14 11:49:41 2012 From: Kay.Haensge at telekom.de (Kay.Haensge at telekom.de) Date: Tue, 14 Aug 2012 11:49:41 +0200 Subject: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <50290342.2000107@tid.es> References: <5028A975.4010405@tid.es> <597879B0D1B8E649A12532864A9C949A0148C6954FBD@HE101452.emea1.cds.t-internal.com> <50290342.2000107@tid.es> Message-ID: <597879B0D1B8E649A12532864A9C949A0148C69557C0@HE101452.emea1.cds.t-internal.com> Hello all, I have updated the I2ND Technical Roadmap in the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please have a look at Chapter I2ND and give me some feedback if it is ok or not. It's is now a convergence from the public page and the feature list (first version) oriented at the apps chapter feature page. BR Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: Miguel Carrillo [mailto:mcp at tid.es] Gesendet: Montag, 13. August 2012 15:38 An: H?nsge, Kay Cc: JUAN JOSE HIERRO SUREDA; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: Re: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Kay, Just to clarify for those who did not attend the call. Apart from minor format issues that will bew addressed by Kay, the problem is that the contribution from I2ND was a broken link (i.e. not linked to the page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4) Kay will look into it. Best regards, Miguel El 13/08/2012 10:34, Kay.Haensge at telekom.de escribi?: Hello Juanjo, I am not sure if I understand your first red marked sentence: "I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing." Does this mean, a or more Feature(s) of the I2ND Materializing Page are missing in the private wiki technical roadmap page? If yes, I will have to double check the entries of the Materializing Page against the Technical Roadmap Page and then put this into the public wiki roadmap page for I2ND. Please give a short feedback about this. Thank you BR Kay H?nsge (Replacement of Pier - I2ND) Mit freundlichen Gr??en / Viele Gr??e / Best Regards Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Montag, 13. August 2012 09:15 An: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu Aug 16 12:00:09 2012 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 16 Aug 2012 12:00:09 +0200 Subject: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap In-Reply-To: <597879B0D1B8E649A12532864A9C949A0148C69557C0@HE101452.emea1.cds.t-internal.com> References: <5028A975.4010405@tid.es> <597879B0D1B8E649A12532864A9C949A0148C6954FBD@HE101452.emea1.cds.t-internal.com> <50290342.2000107@tid.es> <597879B0D1B8E649A12532864A9C949A0148C69557C0@HE101452.emea1.cds.t-internal.com> Message-ID: <502CC4A9.3080906@tid.es> Hi Thanks for the update & all the effort, it looks good. However, Juanjo is the one who gives the final approval (or comments) so let us wait to see if he has something to say. BR Miguel El 14/08/2012 11:49, Kay.Haensge at telekom.de escribi?: Hello all, I have updated the I2ND Technical Roadmap in the private wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4 Please have a look at Chapter I2ND and give me some feedback if it is ok or not. It?s is now a convergence from the public page and the feature list (first version) oriented at the apps chapter feature page. BR Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an ? Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: Miguel Carrillo [mailto:mcp at tid.es] Gesendet: Montag, 13. August 2012 15:38 An: H?nsge, Kay Cc: JUAN JOSE HIERRO SUREDA; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: Re: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Kay, Just to clarify for those who did not attend the call. Apart from minor format issues that will bew addressed by Kay, the problem is that the contribution from I2ND was a broken link (i.e. not linked to the page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4) Kay will look into it. Best regards, Miguel El 13/08/2012 10:34, Kay.Haensge at telekom.de escribi?: Hello Juanjo, I am not sure if I understand your first red marked sentence: ?I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing.? Does this mean, a or more Feature(s) of the I2ND Materializing Page are missing in the private wiki technical roadmap page? If yes, I will have to double check the entries of the Materializing Page against the Technical Roadmap Page and then put this into the public wiki roadmap page for I2ND. Please give a short feedback about this. Thank you BR Kay H?nsge (Replacement of Pier ? I2ND) Mit freundlichen Gr??en / Viele Gr??e / Best Regards Kay H?nsge T-Labs auf der IFA. Innovative L?sungen zu Themen wie Entertain, Security und der App-Welt - besuchen Sie uns vom 31.08.-.05.09.2012, in Halle 6.2 auf dem Telekom-Stand! Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an ? Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. Von: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Montag, 13. August 2012 09:15 An: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Betreff: [Fiware-wpa] Resubmission of FI-WARE Technical Roadmap Dear all, I have checked the contributions by the different chapters to the resubmission of the Technical Roadmap and all are Ok IMHO but the one from the IoT and the I2ND chapters that are still missing. I would suggest that the rest of chapters upload their contributions to the FI-WARE public wiki so that contents of their respective chapter get updated the same way that the Apps Chapter has done. It would be nice that they implement one enhancement that the Apps Chapter has introduced that I rather like: create a wiki link between the names of the GEs when they appear in the Technical Roadmap page (i.e., the tables listing Features/Epics) and the corresponding section on the "Materializing the FI-WARE Vision" part of the wiki. Deadline for the IoT chapter to complete their task is August 15th EOB. Please get it done so that we can officially resubmit by August 16th. Rest of chapters are free to update their contributions until August 15th EOB if they desire to do so. In order to complete the picture, don't miss that one remaining task would be that of updating the Stakeholder field in each backlog entry linked to an Epic or Feature published on the wiki. I would suggest using "FI-WARE" in the case this is a need identified by us, instead of naming a specific partner of FI-WARE. This will avoid questions like "Is only xxx the partner in FI-WARE asking for this feature ?". You can keep information about the specific company that proposed the feature by using the field "Owner". You should also try to add the name of those UC projects that you know are also asking for that Epic or Feature (thanks to interaction during/after the educational weeks). We will nevertheless ask the UC projects to list themselves in the Stakeholder field on another track (but this once we have published the new contents of the Technical Roadmap with the tables of Epics and Features) Besides this, I would kindly ask you to carry out a revision of the tracker of your chapter to make sure it gets aligned with what is currently on the Wiki, thus we can start from a new page in September: * Some of the Epics/Features may have changed, so please translate whatever change on the tracker * Make sure that Release Ids (numbering) is ok. I remind you the conventions at http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Don't forget that reviewers have also asked us to resubmit the tracker contents, so this is an exercise that we definitively have to do. Last but not least, regarding updates of Technical Roadmap wiki pages, a couple of minor comments though: * Regarding contribution of the Cloud chapter: * Please update listing of features linked to the Cloud Proxy GE so that it aligns with the rest of the table * You didn't need a table for "Future Releases". You can mention that you will work in a "stabilized version taking into account new Use Cases requirements" in a dedicated statement within the last paragraph * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) * Regarding contribution of the Security chapter: * Please use references to wiki pages on the public wiki (built using the notation '[[]]') instead of hyperlinks * put a CR after the table to avoid it to be displayed too close to the following header (this will be done by adding '
' right after the table, check Apps Chapter) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Aug 16 12:14:00 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 12:14:00 +0200 Subject: [Fiware-wpa] Update of Technical Roadmap Message-ID: <502CC7E8.9020506@tid.es> Hi all, People from the IoT chapter are trying to recover and complete their contribution to the Technical Roadmap so that it can be resubmitted. We have given them a extended deadline to deal with some final changes. My plan is to perform a final review tonight and upload contents to the public wiki, making it ready to be delivered to the EC tomorrow. This unless I find something that needs to get urgently fixed. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Thu Aug 16 13:00:22 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 13:00:22 +0200 Subject: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement Message-ID: <502CD2C6.2060701@tid.es> Hi all, This is to let you know that I'm still working on the 3rd party Innovation Enablement deliverable. Honestly speaking, there are contributions from some chapters that didn't follow the pattern/example provided with the Apps chapter and, therefore, the whole deliverable doesn't look as homogenous as it should look, at least from an editorial point of view. Consequently, I feel reluctant to deliver it. Unfortunately, it seemed like the caretakers of the two chapters in worst situation (Security and I2ND) are on vacations so it was not just a matter of asking them to implement changes that would allow a better alignment. I'm trying to implement some changes to bring the deliverable into a better shape, at least from an editorial point of view, but I have had less throughput during holidays that I originally foreseen, in part because there was other urgent stuff to deal with (e.g., Technical Roadmap). Therefore, I don't know whether I will be able to get things done during this week. I hope you understand that I'm also on holidays ... Definitively, things have been in a better shape if people had originally followed the example provided by the Apps chapter. We will need to be more strict next time. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From daniel.gidoin at thalesgroup.com Thu Aug 16 18:06:49 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 16 Aug 2012 18:06:49 +0200 Subject: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement In-Reply-To: <502CD2C6.2060701@tid.es> References: <502CD2C6.2060701@tid.es> Message-ID: <15496_1345133214_502D1A9E_15496_2915_1_80d39a66-0e38-4743-8f13-5f3963a71e72@THSONEA01HUB04P.one.grp> Dear Juanjo, Dear Miguel, I just updated the security section of the Deliverable on 3rd Party Innovation Enablement ( https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit?pli=1# ) in accordance with your request (I reproduced the presentation of the Applications & Services chapter) and taking into account the various comments. Hopefully this work will meet your expectations. Best regards Daniel -----Message d'origine----- De?: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: jeudi 16 ao?t 2012 13:00 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement Hi all, This is to let you know that I'm still working on the 3rd party Innovation Enablement deliverable. Honestly speaking, there are contributions from some chapters that didn't follow the pattern/example provided with the Apps chapter and, therefore, the whole deliverable doesn't look as homogenous as it should look, at least from an editorial point of view. Consequently, I feel reluctant to deliver it. Unfortunately, it seemed like the caretakers of the two chapters in worst situation (Security and I2ND) are on vacations so it was not just a matter of asking them to implement changes that would allow a better alignment. I'm trying to implement some changes to bring the deliverable into a better shape, at least from an editorial point of view, but I have had less throughput during holidays that I originally foreseen, in part because there was other urgent stuff to deal with (e.g., Technical Roadmap). Therefore, I don't know whether I will be able to get things done during this week. I hope you understand that I'm also on holidays ... Definitively, things have been in a better shape if people had originally followed the example provided by the Apps chapter. We will need to be more strict next time. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From jhierro at tid.es Thu Aug 16 21:50:17 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 Aug 2012 21:50:17 +0200 Subject: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement In-Reply-To: <15496_1345133214_502D1A9E_15496_2915_1_80d39a66-0e38-4743-8f13-5f3963a71e72@THSONEA01HUB04P.one.grp> References: <502CD2C6.2060701@tid.es> <15496_1345133214_502D1A9E_15496_2915_1_80d39a66-0e38-4743-8f13-5f3963a71e72@THSONEA01HUB04P.one.grp> Message-ID: <502D4EF9.6000308@tid.es> Hi Daniel, Thanks for your contribution ! I have taken a look at it and I feel like it is definitively now in a better shape, more aligned with the rest of the document. I have provided some additional comments I would now kindly ask you to resolve. Once they are resolved, I believe we would be ready to go. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 16/08/12 18:06, GIDOIN Daniel wrote: > Dear Juanjo, > Dear Miguel, > > I just updated the security section of the Deliverable on 3rd Party Innovation Enablement ( https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit?pli=1# ) in accordance with your request (I reproduced the presentation of the Applications & Services chapter) and taking into account the various comments. > > Hopefully this work will meet your expectations. > > Best regards > > Daniel > > > -----Message d'origine----- > De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro > Envoy? : jeudi 16 ao?t 2012 13:00 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement > > Hi all, > > This is to let you know that I'm still working on the 3rd party Innovation Enablement deliverable. > > Honestly speaking, there are contributions from some chapters that didn't follow the pattern/example provided with the Apps chapter and, therefore, the whole deliverable doesn't look as homogenous as it should look, at least from an editorial point of view. Consequently, I feel > reluctant to deliver it. Unfortunately, it seemed like the caretakers > of the two chapters in worst situation (Security and I2ND) are on vacations so it was not just a matter of asking them to implement changes that would allow a better alignment. > > I'm trying to implement some changes to bring the deliverable into a better shape, at least from an editorial point of view, but I have had less throughput during holidays that I originally foreseen, in part because there was other urgent stuff to deal with (e.g., Technical > Roadmap). Therefore, I don't know whether I will be able to get > things done during this week. I hope you understand that I'm also on > holidays ... Definitively, things have been in a better shape if people > had originally followed the example provided by the Apps chapter. We > will need to be more strict next time. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa > . > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From daniel.gidoin at thalesgroup.com Fri Aug 17 15:54:16 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 17 Aug 2012 15:54:16 +0200 Subject: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement In-Reply-To: <502D4EF9.6000308@tid.es> References: <502CD2C6.2060701@tid.es> <15496_1345133214_502D1A9E_15496_2915_1_80d39a66-0e38-4743-8f13-5f3963a71e72@THSONEA01HUB04P.one.grp> <502D4EF9.6000308@tid.es> Message-ID: <26642_1345211660_502E4D0C_26642_3935_1_687237d4-ea96-4620-b602-aebc23666630@THSONEA01HUB06P.one.grp> Dear Juanjo, Thank you very much for your remarks. I have them fully taken into account. Antonio addressed the content-based security & compliance, which I thank him. Your suggestions make it possible to better meet the objective of this document. Best regards Daniel -----Message d'origine----- De?: Juanjo Hierro [mailto:jhierro at tid.es] Envoy??: jeudi 16 ao?t 2012 21:50 ??: GIDOIN Daniel Cc?: Miguel Carrillo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; BISSON Pascal; MUSARAJ Kreshnik Objet?: Re: [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement Hi Daniel, Thanks for your contribution ! I have taken a look at it and I feel like it is definitively now in a better shape, more aligned with the rest of the document. I have provided some additional comments I would now kindly ask you to resolve. Once they are resolved, I believe we would be ready to go. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 16/08/12 18:06, GIDOIN Daniel wrote: > Dear Juanjo, > Dear Miguel, > > I just updated the security section of the Deliverable on 3rd Party Innovation Enablement ( https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit?pli=1# ) in accordance with your request (I reproduced the presentation of the Applications & Services chapter) and taking into account the various comments. > > Hopefully this work will meet your expectations. > > Best regards > > Daniel > > > -----Message d'origine----- > De : fiware-wpa-bounces at lists.fi-ware.eu > [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo > Hierro Envoy? : jeudi 16 ao?t 2012 13:00 ? : > fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : > [Fiware-wpa] Deliverable on 3rd Party Innovation Enablement > > Hi all, > > This is to let you know that I'm still working on the 3rd party Innovation Enablement deliverable. > > Honestly speaking, there are contributions from some chapters that didn't follow the pattern/example provided with the Apps chapter and, therefore, the whole deliverable doesn't look as homogenous as it should look, at least from an editorial point of view. Consequently, I feel > reluctant to deliver it. Unfortunately, it seemed like the caretakers > of the two chapters in worst situation (Security and I2ND) are on vacations so it was not just a matter of asking them to implement changes that would allow a better alignment. > > I'm trying to implement some changes to bring the deliverable into a better shape, at least from an editorial point of view, but I have had less throughput during holidays that I originally foreseen, in part because there was other urgent stuff to deal with (e.g., Technical > Roadmap). Therefore, I don't know whether I will be able to get > things done during this week. I hope you understand that I'm also on > holidays ... Definitively, things have been in a better shape if people > had originally followed the example provided by the Apps chapter. We > will need to be more strict next time. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpa > . > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Aug 20 10:29:24 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 20 Aug 2012 10:29:24 +0200 Subject: [Fiware-wpa] FI-WARE follow-up confcall Message-ID: <5031F564.8000301@tid.es> Hi all, This is a reminder that we will have our regular follow-up confcall. However, because some logistic problems, we shall start at 11:30am We'll use powwownow as always. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 20 11:24:31 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 20 Aug 2012 11:24:31 +0200 Subject: [Fiware-wpa] Shared minutes of today's confcall Message-ID: <5032024F.9000600@tid.es> Available at: https://docs.google.com/document/d/1bCwnzWj6naJF-zZr3eiSNL7EGyOhTf4SOLYMiI2iHTU/edit# Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon Aug 20 15:47:06 2012 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 20 Aug 2012 15:47:06 +0200 Subject: [Fiware-wpa] Release 1 documents on docman Message-ID: <50323FDA.6010709@tid.es> Dear all, I have deposited all the documents associated to Release 1 on the forge. The public versions are here: FI-WARE project docman -> "FI-WARE deliverables" -> "Release 1 (public documentation)". Note that I removed private parts from some of them (namely, the Testing Report and some parts of the Installation manuals). The user manuals should be intact as they are fully public. The private versions are exactly the ones delivered to the EC. They are under "Release 1 deliverables" in the private project. I've done my best but there are a lot of them! Please check them and let me know if you detect anything that should be amended. 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 Aug 21 14:15:54 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 21 Aug 2012 14:15:54 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Shared minutes of today's confcall In-Reply-To: <5032024F.9000600@tid.es> References: <5032024F.9000600@tid.es> Message-ID: Hi Juanjo, at link https://docs.google.com/document/d/1HnmGAJ7LuHJs9oBIhVwbR9LuKMK-Xhb_c7SF-EVQi_Q/edit?pli=1# you can find the updated version of the I2ND chapter contribution (section 3.5) to the deliverable 3rd Party Innovation enablement, ready for review. The overall length is 4 pages, hope it is not too much. Please let us know if there are further improvements you feel necessary. Thanks and 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? 20 agosto 2012 11:25 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Shared minutes of today's confcall Available at: https://docs.google.com/document/d/1bCwnzWj6naJF-zZr3eiSNL7EGyOhTf4SOLYMiI2iHTU/edit# Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From mcp at tid.es Tue Aug 21 17:26:43 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 21 Aug 2012 17:26:43 +0200 Subject: [Fiware-wpa] Deprecated wiki pages Message-ID: <5033A8B3.9010409@tid.es> Dear all, Quite often we work on a wiki page (typically in the chapter wikis or the private wiki) and then we move the final version to the public wiki. Then, we have the same page on two places, which may lead to inconsistencies (different people may add changes in either of them) difficult to trace. The solution is to deprecate the source page and use the destination one as single reference . Our colleague Thorsten Sandfuchs (SAP) was so kind as to create a template that I have added to all the chapter wikis and the private wiki as well. This template eases the work of deprecating wiki pages. It is extremely easy to use, you just have to write this on the deprecated wiki page: {{PageMoved |link= (put the URL of the definite page here) |link_name= (put the label of the link here) }} Just one actual example on the private wiki, an example is always clearer than a thousand explanations! : * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Data-Context_(Resubmission) This is to help you in your work, each WPA/WPL is free to use it or not. My advice is to use it, if you take a look at it you'll see that it is useful and it saves work. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Aug 22 15:31:18 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 Aug 2012 15:31:18 +0200 Subject: [Fiware-wpa] Rationale under the organization of the IP authorised to access the testbed Message-ID: <5034DF26.8020301@tid.es> Dear all, You will remember that one of the APs from last Follow-up confcall was to find out why we had a company wide list of IPs and then one extra list per enabler. I asked Thorsten Sandfuchs, who originally organized the IP collection methodology and his answer gives a straight explanation that sounds rather reasonable: "Administrative access includes in general other ports and IP ranges, than pure "user" access. E.g. I access a server for administration via ssh and port 22 from different IP, than using the company wide proxy and http-protocol. Two lists additionally increase security in theory it is possible to allow only GE providers and their particular IP to access the administration part of their GEs - administration purpose. For larger companies the administration access might even differ for the different chapters/colleagues involved. The IP list on the operations-page on the other hand would allow for user access only and allows company wide access to the complete testbed and all of the GEs. It should be easy enough for a GE provider to only supply his particular IP on the GE page and for a company-coordinator to specify only once one IP for the complete company (on the operations page). Alternative would be to gather all of the IPs from the GE-pages and thus increasing administration and inconsistencies, as there are multiple GEs and multiple IP addresses. Having two lists actually ease up the administrative overhead in the end." Hope this clarifies. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri Aug 24 11:37:51 2012 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 24 Aug 2012 11:37:51 +0200 Subject: [Fiware-wpa] IP for FI-WARE GE testing In-Reply-To: References: <50365411.4000904@tid.es> Message-ID: <50374B6F.3010807@tid.es> Dear all, Please be aware that we are starting to give the UCs access to the Testbed. They will start using our GEs and also asking questions , requesting support, etc. The support must be provided by the GE owner directly, in principle by he/she who is on the catalogue as primary contact for the GE. Best regards, Miguel El 24/08/2012 11:14, HENAR MU?OZ FRUTOS escribi?: > Hi Tim > > You should have access to the following GEs from the IP 82.198.197.188. > > -Apps: > * UPM_composition_editor_execution (Wirecloud Mashup Platform) > * DT_composition_editor_execution (Mashup Factory) > * Mediator > * Marketplace > * Respository > > - Data > * Bigdata > * Location Server > * Complex event processing > > - Security > * DB anonymizer > * Data handling > > Tell me if you have any problem and if you have any question about the GE you can contact the GE owner. > > Regards, > Henar > ________________________________________ > De: MIGUEL CARRILLO PACHECO > Enviado el: jueves, 23 de agosto de 2012 18:02 > Para: Verwaart, Tim > CC: HENAR MU?OZ FRUTOS; JUAN JOSE HIERRO SUREDA; Carlos Maestre Terol (carlos.maestre at atosresearch.eu); 'stefano.depanfilis at eng.it' > Asunto: Re: IP for FI-WARE GE testing > > Dear tim, > > It is good to have news from the UCs. Please try to send all IPs in one go, there many UC project and attending hundreds of emails would be a nightmare (and error prone) > > Anyway, we will try to grant you access to the testbed asap. > > Thank you for your comments, I answer inline. > > Best regards, > > Miguel > > > El 23/08/2012 14:45, Verwaart, Tim escribi?: > Dear Henar and Miguel, > > Congratulations with the availability of the first GE instances on the testbed. > > I agreed with Carlos Maestre Terol of ATOS that I will communicate the IP adresses to you on behalf of the FI-PPP SmartAgriFood project, following Stefano?s e-mail (below). > > We would be happy play with and test the new GE instances. > > The first IP address which we will use to access the testbed (more are to follow) is 82.198.197.188 > We would like to have access to all available GEs > > On top of that we have some Questions: > > ? There are some links within the download-tab of GEs (e.g. http://fi-ware.cloud.labs.ericsson.net/node/98) which require a login and password. How do we access these resources? > > They are private and therefore they shouldn't be mentiones here. We will delete this. Thanks for noticing. > > ? Same holds for some links within the documentation tab (e.g. http://fi-ware.cloud.labs.ericsson.net/node/213). > > ? There are some links to a private-wiki (e.g. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Location_Platform_-_User_and_Programmer_Guide). > > This is a mistake, it points to an internal draft. I amended it and now it points to the final one, that is public. Thanks for noticing and helping us to refine the info on the catalogue. > > Please let me know as soon as we can access the GE?s on the testbed.? > We definitely will. > > With kind regards, > Tim Verwaart > (FI-PPP SmartAgriFood) > > On 09/08/12 22:05, stefano de panfilis wrote: > Dear members of the FI-PPP and particularly of the Use Case projects, > > i'm glad to announce the availability of a first set generic enabler implementations (gei). they are: > * Mediator > * Marketplace > * BigData > * Location Server > * DB anonymizer > > as already announced in a previoius email by browsing the fi-ware catalogue (http://fi-ware.cloud.labs.ericsson.net/) > you'll get all the info on how to acces them, how to use them, and also their specifications. > > of course the access and use of such implelemtations is restricted to use case projects only. > in order to get access you (i.e. ONLY the person member of the fi-ppp ab to avoid confusion and thousands of email circulating ...) have to answer to this email indicating to my colleague henar and miguel (please keep also me in the loop) the ip address(es) from where you'll use to access the gei(s). > > in return you'll receive from henar the green ligth to use the ge(s) you are interested in. > this procedure not only will protect the gei owners, but also will allow us to make ready the machines according to the requested gei usage. > > if you find any problem in using the gei you have not to contact henar or miguel or me, but you have to contact directly the person responsible for the specific gei as indicated in the fi-ware catalogue relevant page (normally on the rigth side of each page concerning the gei). upon this, if it is the case, a proper ticket will be issued. > > as said earlier this is just a first set. > please stay tuned as in the very next days several other geis will be made available! > > i hope you will enjoy > > ciao, > stefano > > -- > Stefano De Panfilis > > > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: mcp at tid.es > > Follow FI-WARE on the net > > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: http://twitter.com/Fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > . > -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From GLIKSON at il.ibm.com Sun Aug 26 14:14:56 2012 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Sun, 26 Aug 2012 15:14:56 +0300 Subject: [Fiware-wpa] [Fiware-wpl] Peer review of contents linked to FI-WARE Architecture Description In-Reply-To: <5028AC56.60400@tid.es> References: <50289D26.8000202@tid.es> <5028AC56.60400@tid.es> Message-ID: Attached comments for the Apps chapter. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 13/08/2012 10:26 AM Subject: [Fiware-wpl] [Suspected Spam] Peer review of contents linked to FI-WARE Architecture Description Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear colleagues, Another of the actions that we need to carry out is also the review of the contents of the FI-WARE Architecture Descriptions. This goes besides the development of the FI-WARE Technical Whitepaper that follows a separate track. We should try to do our best to get the FI-WARE Architecture Description resubmitted by end of August. Please find the plan that I would like to follow to carry out this revision. It is basically the same schema proposed for peer-review of FI-WARE Open Specifications: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND However, I believe that the major caretakers of this review task are WPLs and WPAs themselves. They can forward a request for revision by other members of their team, but mostly to get additional input. This first review should finish by end of this month, executing the following calendar: Reviewing chapter sends comments to leader of reviewed chapter, with cc to fiware-wpl and fiware-wpa, by August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) Each chapters implement recommended changes by peer-reviewer as well as comments from official reviewers provided in the official FI-WARE review reports: August 31st, 12:00pm CET All WPLs/WPAs should book enough resources the week starting on August 27th to be able to implement their revision. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: apps-arch-AG.doc Type: application/octet-stream Size: 60416 bytes Desc: not available URL: From jhierro at tid.es Mon Aug 27 08:39:21 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 08:39:21 +0200 Subject: [Fiware-wpa] Peer review of contents linked to FI-WARE Architecture Description In-Reply-To: <5028AC56.60400@tid.es> References: <50289D26.8000202@tid.es> <5028AC56.60400@tid.es> Message-ID: <503B1619.1020400@tid.es> Hi all, Please find below the results of the peer-review on the Architecture Description of the Cloud Chapter carried out by members of the Data Chapter. === Review by Guy Sharon: 1. [Cloud Hosting Architecture] Perhaps an end to end usage example could help out in what the users of the current GEs could make use of. There is partial information in DCRM page and in SM page but a more wider \ cross GE story could help in understand what you can actually use these GEs for in the current version. Is it just building services made up of several resources that the DCRM manages? What is the cloud edge used for in this regards \ or for other purposes and what is the story around the object store (related or not)? 2. In the DCRM Open Specification API - to understand\work with this it seems someone must be familiar with OCCI - if this is the case then should be mentioned in the intended audience - can the software developer and cloud provider really do just with the 3 described familiarities? I am not so sure - I would not know where to start with this - but I might not have the skills or should I? 3. In [FIWARE.ArchitectureDescription.Cloud.SM] -I think it is worth spending a few sentences explaining what service application is meant here that is being managed (maybe under basic concepts) - a service here is a collection of resources and some rules for managing the resources under this service. - is there connections between services? Is it only using DCRM? If not what else can be covered under service? (It took me a while to understand what services are actually managed by this GE) 4. SM Open Spec API - I see APIs allowing create delete of resources but not clear how these get associated with a service - are their APIs to create a service and add to this service the relevant resources needed? What about the rule APIs? (Seems not to be entirely complete or synced with the descriptions on the architecture description of SM) 5. CloudEdge - Confusing the move between app and service all over the document - it is explained that the AP role provides Apps but who provides services or is this the same? Another such example "End-User (EU): any client that subscribes and consumes a service that runs partly on the Cloud and partly on the Cloud Proxy. In this model, his role is to select those applications that are granted to install and run a piece of code on his Cloud Proxy" 6. CloudEdge - be a good idea to explain what this is for and when you would need to use this - why arent the other GEs used here - same roles, same resources being provisioned. - so whats different - whats the motivation for this. (overview and general description dont cover it - nor in the main Cloud Hosting Architecture page) - well, at least not clear to me 7. Object Store - example and how it fits to the rest would be very helpful Is it really something that belongs to IaaS or more of a PaaS component - I would use to store objects for my application - or would it have to deal or work with the DCRM and SM and vise versa. A bit confusing that its under the same set of GEs but nothing about Infrastructure is covered here. === Review by Peter Amon General remark: I found no information on how users can switch the infrastructure provider. (This question is mentioned in the review report.) [Introduction] - "Cloud Chapter offers Generic Enablers ..." -> "The Cloud Chapter offers Generic Enablers ..." - The link under [1] is HTTPS. Why not just HTTP (i.e., no hassle with security certificates)? [Architecture Overview] - "Service Management GE" -> "Service Management (SE) GE", since the abbreviation "SE" is used in the figure. [Architecture Description of GEs] - Only four GEs listed, while the figure contains six GEs. (Ecosystem GEs are missing.) Confusing, since both seem to be the GEs for the first release. [FIWARE.ArchitectureDescription.Cloud.DCRM] [[Overview]] - "providing the OCCI interface" -> "providing the Open Cloud Computing Interface (OCCI) interface" [[Open Cloud Computing Interface (OCCI)]] - "API for IaaS model based Services" -> "API for IaaS model-based services" (hyphen and lower case "s"?) - "Basic type definitions (attributes, actions, relationships):" the following three sub-items should be indented in order to indicate their dependency. [[Infrastructure] - "Complimenting" -> "Complementing" or "Complimenting these specialised Resources are two specialised Links and a means to capture the notion of templates." -> "Two specialised Links and a means to capture the notion of templates are complimenting these specialised Resources." [[Other Open Specifications]] Sub-section with no content. [FIWARE.ArchitectureDescription.Cloud.SM] [[Overview]] - "Due to it is working at the service level" -> "Since it is working at the service level" - "On the above diagram, the SMI" -> "On the above diagram, the Service Manager Interface (SMI)" [[Components]] - "Due to the Query System could be in a different Host" -> "Since the Query System could be in a different Host" [[Scalability Scenario]] - "This Rule might be changed in future" -> "This Rule might be changed in the future" [[Elasticity & Monitoring operations]] - "the IaaS Service Manager have to implement" -> "the IaaS Service Manager has to implement" [[Design Principles]] - How can "Design Principles" be a subsection of "Basic Design Principles"? - "IaaS Service Manager allows a single instance of service runs on a server" -> "IaaS Service Manager allows running a single instance of service on a server" [[Resolution of Technical Issues]] - Link to "Cloud Hosting Architecture" could be HTTP instead of HTTPS. - "the general design principles outlined at previous section" -> "the general design principles outlined in the previous section" [[Other Open Specifications]] Sub-section with no content. [FIWARE.ArchitectureDescription.Cloud.CloudEdge] [[General Description]] - "The cloud edge consists in one equipment called "cloud proxy" and located in the consumer private network." -> "The cloud edge consists of a component called "cloud proxy" and is located in the consumer private network." ?? - "To this purpose" -> "For this purpose" [[Security and Privacy concern for Virtual Appliances]] - "access to user private data" -> "access to private user data" or "access to the user's private data" [[Virtual Appliance Life Cycle]] - "An AP request to the CO" -> "An AP requests from the CO" - "The CO check into his database" -> "The CO checks into his database" / "The CO checks his database" ?? [[Other Open Specifications]] Sub-section with no content. [[FIWARE.ArchitectureDescription.Cloud.ObjectStorage]] [[Overview]] - "Object storage is a Generic Enabler ." -> "Object storage is a Generic Enabler." (delete space in front of the full stop) [[Basic Concepts]] - "The object store presents it self as a service" -> "The object store presents itself as a service" - "This API" -> The sentence is incomplete. [[Other Open Specifications]] Sub-section with no content. === end of reviews Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 13/08/12 09:27, Juanjo Hierro wrote: Dear colleagues, Another of the actions that we need to carry out is also the review of the contents of the FI-WARE Architecture Descriptions. This goes besides the development of the FI-WARE Technical Whitepaper that follows a separate track. We should try to do our best to get the FI-WARE Architecture Description resubmitted by end of August. Please find the plan that I would like to follow to carry out this revision. It is basically the same schema proposed for peer-review of FI-WARE Open Specifications: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND However, I believe that the major caretakers of this review task are WPLs and WPAs themselves. They can forward a request for revision by other members of their team, but mostly to get additional input. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter, with cc to fiware-wpl and fiware-wpa, by August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes by peer-reviewer as well as comments from official reviewers provided in the official FI-WARE review reports: August 31st, 12:00pm CET All WPLs/WPAs should book enough resources the week starting on August 27th to be able to implement their revision. 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 27 08:42:00 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 08:42:00 +0200 Subject: [Fiware-wpa] Fwd: Re: Fwd: Peer review of FI-WARE Open Specifications In-Reply-To: <50362BFD.8010408@tecsidel.es> References: <50362BFD.8010408@tecsidel.es> Message-ID: <503B16B8.9080804@tid.es> Hi all, Please find below the results of the peer-review of the Open Specifications of the Cloud Chapter carried out by members of the Data Chapter. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 === Review by Grant Croker SM URL * Additional Resources * Link to private wiki for the current version of the spec * The following text should have the URL not "[2]": For more information about OpenStack APIs please refer to [2] * Resources Summary * To be consistent the URI should include //server * Faults * Link goes to a "blank" page in the documentation and the reader is expected to look at the contents tree to expand the section. Perhaps it would be better to provide links to Synchronous Faults and Asynchronous Faults. * API Operations * Whilst the OpenStack Compute Developer Guide gives examples, perhaps it would be useful to direct link to an example for each operation? DCRM URL * Missing sections * API Change History * How to read this document * Versioning * Should be titled 'Versions' * Error and Fault Codes * Should be titled 'Faults' and without a leading space * Resources Summary * No mention of the extensions documented from OCCI Kind Extensions and below. * General comments * When linking to PDF documents the chapter/section name should be referenced in the spec to make the relevant text easier to find (appending #Page=XX to the URL is also an option but requires Adobe Acrobat Reader as the rendering engine). * E.g. See OCCI Kind Extensions Open Storage URL * Missing the following sections: * API Change History table e.g. Big Data revision * How to Read * Additional Resources * Links and References * Error and Fault Codes should be titled 'Faults' * Versioning should be titled 'Versions' * The link in this section could point to http://cdmi.sniacloud.com/cdmi_spec/7-interface_specification/7-interface_specification.htm#TOC_7_1_HTTP_Status_Codesbc-1 * Leading space in the title for Authentication * Leading space in the title for API Operations * Provide direct links to the chapters in http://cdmi.sniacloud.com/? Cloud Edge Service Management. URL * Additional Resources * A link to the private wiki when I guess it should be the public wiki * Link to the vision for cloud should be using Wiki links rather than the absolute URL * Links and References * Wrong sort of link/reference - should be URL redirection which does not apply to XML-RPC * Synchronous Faults * Fault codes don't match with the HTTP1.1 spec, e.g. 900 Internal is 500 Internal Server Error in HTTP/1.1 - I'm not sure this is an issue or not. * API Operations (Methods details) * No examples given - perhaps not explicity needed but I think it was requested in the original mails on this topic. Links and References provides a link to the spec. === end of review -------- Original Message -------- Subject: Peer review of FI-WARE Open Specifications Date: Mon, 13 Aug 2012 08:22:30 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, One of the actions that we need to carry out is the review of the contents of the FI-WARE Open Specifications. The date that the EC has given to us for re-submitting them is month 18, i.e., end of October. Therefore, we should have enough time. However, it is also true that FI-WARE Open Specifications are one of our key deliverables: they become the ultimate reference UC projects will rely on in order to develop apps based on our GEs. Please find the plan that I would like to follow to carry out a first review of the FI-WARE Open Specifications by end of August. Additional reviews will follow but hopefully this first one will be able to deliver a new version of the specs that is robust and complete enough to be delivered to UC projects: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Leaders of reviewing chapters are asked to designate those members of their teams that own enough technical expertise to judge specifications from the perspective of usefulness by both an application developer (this particularly in the case of RESTFul APIs) and any party that aims to develop a GE implementation in compliance with FI-WARE Open Specifications. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter with cc to fiware-wpl and fiware-wpa: August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes: August 31st, 12:00pm CET Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Aug 27 09:44:00 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 09:44:00 +0200 Subject: [Fiware-wpa] Fwd: Peer review of contents linked to FI-WARE Architecture Description In-Reply-To: <5028AC56.60400@tid.es> References: <5028AC56.60400@tid.es> Message-ID: <503B2540.3010201@tid.es> Dear all, This is a reminder that peer-review of FI-WARE Architecture Descriptions were due by today. Please send them to the fiware-wpl and fiware-wpa mailing lists, or at least to the target WPL and WPA with copy to me. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: [Fiware-wpa] [Suspected Spam] Peer review of contents linked to FI-WARE Architecture Description Date: Mon, 13 Aug 2012 09:27:18 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, Another of the actions that we need to carry out is also the review of the contents of the FI-WARE Architecture Descriptions. This goes besides the development of the FI-WARE Technical Whitepaper that follows a separate track. We should try to do our best to get the FI-WARE Architecture Description resubmitted by end of August. Please find the plan that I would like to follow to carry out this revision. It is basically the same schema proposed for peer-review of FI-WARE Open Specifications: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND However, I believe that the major caretakers of this review task are WPLs and WPAs themselves. They can forward a request for revision by other members of their team, but mostly to get additional input. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter, with cc to fiware-wpl and fiware-wpa, by August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes by peer-reviewer as well as comments from official reviewers provided in the official FI-WARE review reports: August 31st, 12:00pm CET All WPLs/WPAs should book enough resources the week starting on August 27th to be able to implement their revision. 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From jhierro at tid.es Mon Aug 27 09:45:57 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 09:45:57 +0200 Subject: [Fiware-wpa] Fwd: Peer review of FI-WARE Open Specifications In-Reply-To: <50289D26.8000202@tid.es> References: <50289D26.8000202@tid.es> Message-ID: <503B25B5.6020600@tid.es> Dear all, This is a reminder that first peer-review of FI-WARE Open Specifications were also due by today. Please send them to the fiware-wpl and fiware-wpa mailing lists, or at least to the target WPL and WPA with copy to me. So far, I have only seen the peer-review on Cloud Open Specifications made by the Data Chapter. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: [Fiware-wpa] Peer review of FI-WARE Open Specifications Date: Mon, 13 Aug 2012 08:22:30 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear colleagues, One of the actions that we need to carry out is the review of the contents of the FI-WARE Open Specifications. The date that the EC has given to us for re-submitting them is month 18, i.e., end of October. Therefore, we should have enough time. However, it is also true that FI-WARE Open Specifications are one of our key deliverables: they become the ultimate reference UC projects will rely on in order to develop apps based on our GEs. Please find the plan that I would like to follow to carry out a first review of the FI-WARE Open Specifications by end of August. Additional reviews will follow but hopefully this first one will be able to deliver a new version of the specs that is robust and complete enough to be delivered to UC projects: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Leaders of reviewing chapters are asked to designate those members of their teams that own enough technical expertise to judge specifications from the perspective of usefulness by both an application developer (this particularly in the case of RESTFul APIs) and any party that aims to develop a GE implementation in compliance with FI-WARE Open Specifications. This first review should finish by end of this month, executing the following calendar: * Reviewing chapter sends comments to leader of reviewed chapter with cc to fiware-wpl and fiware-wpa: August 27, 09:00am (delivery of revisions to be checked in our follow-up confcall at 11:00am) * Each chapters implement recommended changes: August 31st, 12:00pm CET 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpa From uwe.riss at sap.com Mon Aug 27 09:50:13 2012 From: uwe.riss at sap.com (Riss, Uwe) Date: Mon, 27 Aug 2012 09:50:13 +0200 Subject: [Fiware-wpa] FW: IoT Architecture Description and Open Specification Review Message-ID: <1491C91A94302A448D73CD9C6B7A782046C2C11D5E@DEWDFECCR02.wdf.sap.corp> To whom it may concern, Please find the Review of the IoT Architecture Description and Open Specification in the attachment. For the sake of convenience, we copied the wiki content into word documents. We currently plan to have a second look into the IoT Deliverables later today and probably send you some further minor comments by end of business day. Thanks and best regards Andreas & Uwe PS For questions regarding the contents of the review please contact Andreas. Dr. Uwe Riss Senior Researcher, Internet Applications & Services | SAP Research Karlsruhe SAP AG | Vincenz-Priessnitz-Str. 1 | 76131 Karlsruhe | Germany T +49 6227 7-70212 | F +49 6227 78-26158 | M +49 151 16810936 | mailto: uwe.riss at sap.com www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT_Architecure_Review--.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 962918 bytes Desc: IoT_Architecure_Review--.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT_OpenSpec_Review.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 381708 bytes Desc: IoT_OpenSpec_Review.docx URL: From jhierro at tid.es Mon Aug 27 10:26:17 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 10:26:17 +0200 Subject: [Fiware-wpa] Shared minutes for joint WPL/WPA follow-up confcall Message-ID: <503B2F29.6090905@tid.es> Hi all, Here you are the URL of the shared minutes for our joint WPLs/WPAs follow-up confcall. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Aug 27 10:26:41 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 10:26:41 +0200 Subject: [Fiware-wpa] Shared minutes for joint WPL/WPA follow-up confcall In-Reply-To: <503B2F29.6090905@tid.es> References: <503B2F29.6090905@tid.es> Message-ID: <503B2F41.7030000@tid.es> Now with the link :-) https://docs.google.com/document/d/1hnCbmdhGoKuWxc3OAk20IRcXXFLI3rA2j9ud4hQiJwM/edit# Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/08/12 10:26, Juanjo Hierro wrote: > Hi all, > > Here you are the URL of the shared minutes for our joint WPLs/WPAs > follow-up confcall. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon Aug 27 11:17:13 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 Aug 2012 11:17:13 +0200 Subject: [Fiware-wpa] Current draft of 3rd Party Innovation Enablement deliverable Message-ID: <503B3B19.5030406@tid.es> Hi, As promised during our joint WPLs/WPAs confcall. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: Third Party Innovation Enablement in FI-WARE 12-08-27.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 508454 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Tue Aug 28 16:05:35 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 28 Aug 2012 16:05:35 +0200 Subject: [Fiware-wpa] Review of Architecture and Open Specifications of Security Chapter Message-ID: Dear All, Please find attached the document containing the comments for the Security chapter. The document contains two tables concerning Architecture description and Open Specs review respectively. 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: ReviewofSecurity27-Aug-2012.doc Type: application/msword Size: 249856 bytes Desc: ReviewofSecurity27-Aug-2012.doc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jhierro at tid.es Thu Aug 30 07:50:54 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 Aug 2012 07:50:54 +0200 Subject: [Fiware-wpa] Taking care of the FI-WARE General Support Tracker Message-ID: <503EFF3E.9070301@tid.es> Hi all, Now we face a critical point at which we should demonstrate quick response to any request for support by any UC projects. We may foreseen that many request will come as a result of making FI-WARE GEs available on the Testbed and UC projects trying to experiment with them. As per agreement with UC projects, most of the interaction should now be handled through the FI-WARE General Support tracker at: https://forge.fi-ware.eu/tracker/?group_id=7 I have asked Axel and Carlos, as the dedicated team that was designated to monitor interaction with UC projects, to make sure that proper monitor of the status of this tracker is in place so that Chapter Leads and Chapter teams take care of tickets. Note that some tickets may also require actions by members of the Testbed team or the team working on Development Tools. A very basic workflow has been defined to start working. We will see how this evolves but I believe we should keep it as simple as possible. Currently, valid status are: * Open: it means that the ticket remains unassigned it has been formulated (or reformulated) * Assigned: it means someone is taking care of it * ToBeRevised: it means that the original ticket was wrongly formulated and has to be reformulated or closed * ToBeChecked: it means that the one that was assigned to take care of it now thinks is solved but this has to be verified * Closed: it means that the ticket was closed and valid transitions are defined at: https://forge.fi-ware.eu/tracker/admin/?group_id=7&atid=162&workflow=1 Don't wait until Axel or Carlos pursues you to handle a ticket and be proactive checking regularly what you could assign to you ! I have kindly asked Axel and Carlos to brief us during our next follow-up confcall about status of the tracker, APs that we should put in place to move forward, etc. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Aug 30 09:08:12 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 Aug 2012 09:08:12 +0200 Subject: [Fiware-wpa] Fwd: FI-WARE: 3rd review outcome [Ares(2012)1008872] In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D0908B0@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D0908B0@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <503F115C.8060507@tid.es> Hi all, Please find enclosed the final review report from the EC and our team of reviewers. The review report is negative, as expected. However, there are some more negative surprises like the fact that they have rejected 50% of the costs linked to Open Specification deliverables (despite nowhere in the DoW it is specified how much effort would correspond to development of Open Specifications in the DoW). In my honest opinion, the statements regarding evaluation of the Open Specifications deliverable are highly arguable. Just as an example, note that it is stated that "The deliverable does not provide sufficient basis for practical implementation by software developers, which is its main purpose" regarding all Chapters. I don't know what your opinion is but I believe this is fundamentally wrong. I will elaborate on a mail following this one about the statements made in the review regarding Open Specifications and why I believe many of them are fundamentally wrong. Whether we should produce a formal answer or not is unclear to us (TID) so we would like to hear your personal opinion. Certainly answering it will distract us from our main focus now. But on the other hand, resubmission of Open Specifications will depend very much on what we accept as valid comment from reviewers. Maybe the best option is to answer formally but do it later, given the fact that they request to resubmit Open Specifications by end month 18, i.e., end of October. Therefore, we would focus now in stabilizing the FI-WARE Testbed, ensuring that a proper collaboration with UC projects is in place and working well, and finalizing resubmission/submission of deliverables linked to Architecture, Technical Roadmap and 3rd Party Innovation Enablement. Again, we would like to hear your opinion. Definitively this is something we should discuss in our next follow-up confcall. Don't hesitate to share this with your teams. It should be used to encourage people to pay attention to meeting milestones and ensure that contributions come with the required quality. Also to explain why we had to put in place hard measures targeted to ensure that we were going to deliver. We have made a big effort to have the FI-WARE up and running without impacting UC projects, so I feel positive that the overall evaluation of the project will improve soon. But we cannot relax and have to work hard together to ensure that the FI-WARE First Release becomes a success in the upcoming months. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: FI-WARE: 3rd review outcome [Ares(2012)1008872] Date: Wed, 29 Aug 2012 15:51:12 +0000 From: To: CC: , , , , , , , , Dear Jose, Please find enclosed the outcome of the third FI-WARE review and the review meeting that took place on 21-22 June 2012 in Brussels. No paper version will follow. Please distribute the review report to the partners in the consortium. Please acknowledge the receipt of this e-mail. Best regards, Arian Zwegers Scientific Officer European Commission - DG Communication Networks, Content and Technology E3 Net Innovation Avenue de Beaulieu 25, Office 3/095, B - 1160 Brussels, Belgium Tel: +32-2-2984424, Fax: +32-2-2962178 Web site: http://ec.europa.eu/information_society/activities/foi/lead/fippp/index_en.htm Assistant: Vanessa Vanhumbeeck, Tel: +32-2-2964939, Email: Vanessa.Vanhumbeeck at ec.europa.eu Postal mail address: European Commission, Office BU25 03/095, B-1049 Brussels, Belgium ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outcome FI-WARE review 3.pdf Type: application/pdf Size: 55588 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Review 3 Report.pdf Type: application/pdf Size: 414426 bytes Desc: not available URL: From matteo.melideo at eng.it Thu Aug 30 15:03:10 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 30 Aug 2012 15:03:10 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Fwd: FI-WARE: 3rd review outcome [Ares(2012)1008872] In-Reply-To: <503F115C.8060507@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D0908B0@S-DC-ESTF03-B.net1.cec.eu.int> <503F115C.8060507@tid.es> Message-ID: <503F648E.4030707@eng.it> Dear Juanjo, I try to give you my thoughts. I read all the report very carefully and my feeling is that it is better to avoid any formal reply and try to address as much as possible all their remarks. I personally think that if all the reviewers had this impression we have to stay with this without starting endless battle that in the end we will lost and would cost much more than now. Concerning the budget cut, I agree with you that it is not clear what's the policy they adopted as there is no clear statements on how much effort was allocated to each deliverable. Probably a request of clarification rather than complaining formal letter is more than welcome. However, I strongly believe that problems are others and much more serious than this ... at least for the Open Specifications we have the information and data (I guess), it is just a matter of reorganization and better explanation. :-) Concerning the conference call, I would suggest an "ad-hoc" conference call (if not a f2f) to discuss everything in details and plan a very solid and realistic action plan to recover. Regards, M. P.S. Out of the scope of this mail: I am involving few people in the company (mostly senior developers) to look at fi-ware and try to understand if they are able to understnad from the available information what it is, what can they do with its results and so on. I expect some feedbacks in the coming days. However, I was noticing something very interesting. Is it normal that a person looking at our web site www.fi-ware.eu, in the TAG session does not find any single tag regarding software, ICT, Future Internet, platform, etc. ? The key Tag is Events. I know this is now out of the scope of this mail and probably trivial but we should try to put ourselves in the shoes of people not involved in FI-WARE nor in the PPP and try to imagine what they can understand reading at our outcomes. The other important point is: what's our main access point: the web site or the FF instance? I honestly do not know yet. :-( Il 30/08/2012 09:08, Juanjo Hierro ha scritto: > Hi all, > > Please find enclosed the final review report from the EC and our > team of reviewers. > > The review report is negative, as expected. However, there are > some more negative surprises like the fact that they have rejected 50% > of the costs linked to Open Specification deliverables (despite > nowhere in the DoW it is specified how much effort would correspond to > development of Open Specifications in the DoW). > > In my honest opinion, the statements regarding evaluation of the > Open Specifications deliverable are highly arguable. Just as an > example, note that it is stated that "The deliverable does not provide > sufficient basis for practical implementation by software developers, > which is its main purpose" regarding all Chapters. I don't know what > your opinion is but I believe this is fundamentally wrong. > > I will elaborate on a mail following this one about the statements > made in the review regarding Open Specifications and why I believe > many of them are fundamentally wrong. Whether we should produce a > formal answer or not is unclear to us (TID) so we would like to hear > your personal opinion. Certainly answering it will distract us from > our main focus now. But on the other hand, resubmission of Open > Specifications will depend very much on what we accept as valid > comment from reviewers. Maybe the best option is to answer formally > but do it later, given the fact that they request to resubmit Open > Specifications by end month 18, i.e., end of October. Therefore, we > would focus now in stabilizing the FI-WARE Testbed, ensuring that a > proper collaboration with UC projects is in place and working well, > and finalizing resubmission/submission of deliverables linked to > Architecture, Technical Roadmap and 3rd Party Innovation Enablement. > Again, we would like to hear your opinion. > > Definitively this is something we should discuss in our next > follow-up confcall. > > Don't hesitate to share this with your teams. It should be used to > encourage people to pay attention to meeting milestones and ensure > that contributions come with the required quality. Also to explain why > we had to put in place hard measures targeted to ensure that we were > going to deliver. We have made a big effort to have the FI-WARE up > and running without impacting UC projects, so I feel positive that the > overall evaluation of the project will improve soon. But we cannot > relax and have to work hard together to ensure that the FI-WARE First > Release becomes a success in the upcoming months. > > Cheers, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > > -------- Original Message -------- > Subject: FI-WARE: 3rd review outcome [Ares(2012)1008872] > Date: Wed, 29 Aug 2012 15:51:12 +0000 > From: > To: > CC: , , > , , > , , > , , > > > > > Dear Jose, > > Please find enclosed the outcome of the third FI-WARE review and the > review meeting that took place on 21-22 June 2012 in Brussels. No > paper version will follow. > > Please distribute the review report to the partners in the consortium. > > Please acknowledge the receipt of this e-mail. > > Best regards, > > Arian Zwegers > > Scientific Officer > > European Commission - DG Communication Networks, Content and Technology > > E3 Net Innovation > > Avenue de Beaulieu 25, Office 3/095, B - 1160 Brussels, Belgium > > Tel: +32-2-2984424, Fax: +32-2-2962178 > > Web site: > http://ec.europa.eu/information_society/activities/foi/lead/fippp/index_en.htm > > Assistant: > > Vanessa Vanhumbeeck, Tel: +32-2-2964939, Email: > Vanessa.Vanhumbeeck at ec.europa.eu > > Postal mail address: > > European Commission, Office BU25 03/095, B-1049 Brussels, Belgium > > > > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From matteo.melideo at eng.it Thu Aug 30 16:12:59 2012 From: matteo.melideo at eng.it (Matteo Melideo) Date: Thu, 30 Aug 2012 16:12:59 +0200 Subject: [Fiware-wpa] [Fiware-wpl] Taking care of the FI-WARE General Support Tracker In-Reply-To: <503EFF3E.9070301@tid.es> References: <503EFF3E.9070301@tid.es> Message-ID: <503F74EB.4060602@eng.it> Dear Juanjo, I noticed that in the tracker https://forge.fi-ware.eu/tracker/?group_id=7 there are some problems with the tickets assigned to Tools Chapter. Specifically, I suspect ENVIROFI has yet some confusion on what Tools Chapter really do!! :-) We cannot take care of these tickets: 646, 695, 828 and 1149. Best regards M. Il 30/08/2012 07:50, Juanjo Hierro ha scritto: > Hi all, > > Now we face a critical point at which we should demonstrate quick > response to any request for support by any UC projects. We may > foreseen that many request will come as a result of making FI-WARE GEs > available on the Testbed and UC projects trying to experiment with them. > > As per agreement with UC projects, most of the interaction should > now be handled through the FI-WARE General Support tracker at: > > https://forge.fi-ware.eu/tracker/?group_id=7 > > I have asked Axel and Carlos, as the dedicated team that was > designated to monitor interaction with UC projects, to make sure that > proper monitor of the status of this tracker is in place so that > Chapter Leads and Chapter teams take care of tickets. Note that > some tickets may also require actions by members of the Testbed team > or the team working on Development Tools. > > A very basic workflow has been defined to start working. We will > see how this evolves but I believe we should keep it as simple as > possible. Currently, valid status are: > > * Open: it means that the ticket remains unassigned it has been > formulated (or reformulated) > * Assigned: it means someone is taking care of it > * ToBeRevised: it means that the original ticket was wrongly > formulated and has to be reformulated or closed > * ToBeChecked: it means that the one that was assigned to take care > of it now thinks is solved but this has to be verified > * Closed: it means that the ticket was closed > > and valid transitions are defined at: > https://forge.fi-ware.eu/tracker/admin/?group_id=7&atid=162&workflow=1 > > Don't wait until Axel or Carlos pursues you to handle a ticket and > be proactive checking regularly what you could assign to you ! > > I have kindly asked Axel and Carlos to brief us during our next > follow-up confcall about status of the tracker, APs that we should put > in place to move forward, etc. > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es > email:jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico > en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: From jhierro at tid.es Fri Aug 31 09:50:55 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 31 Aug 2012 09:50:55 +0200 Subject: [Fiware-wpa] Fwd: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE In-Reply-To: <50406C77.6030600@tid.es> References: <50406C77.6030600@tid.es> Message-ID: <50406CDF.8010007@tid.es> ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE Date: Fri, 31 Aug 2012 09:49:11 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: Miguel Carrillo , Jose Jimenez , "jhierro >> \"Juan J. Hierro\"" Dear Arian, dear reviewers, This is the official submission of the following deliverable, publicly available from at: https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf * D2.5.1 Third party innovation enablement in FI-WARE Both documents are on our documentation repository (see previous links). Should you have any comments or suggestions, do not hesitate to contact us. Kind regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Aug 31 09:51:48 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 31 Aug 2012 09:51:48 +0200 Subject: [Fiware-wpa] Fwd: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE In-Reply-To: <50406C77.6030600@tid.es> References: <50406C77.6030600@tid.es> Message-ID: <50406D14.7030106@tid.es> FYI. Thanks all for your contributions and particularly Uwe for his great work and Axel for his additional support. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of deliverable D2.5.1 Third party innovation enablement in FI-WARE Date: Fri, 31 Aug 2012 09:49:11 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: Miguel Carrillo , Jose Jimenez , "jhierro >> \"Juan J. Hierro\"" Dear Arian, dear reviewers, This is the official submission of the following deliverable, publicly available from at: https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf * D2.5.1 Third party innovation enablement in FI-WARE Both documents are on our documentation repository (see previous links). Should you have any comments or suggestions, do not hesitate to contact us. Kind regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Aug 31 10:49:05 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 31 Aug 2012 10:49:05 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Taking care of the FI-WARE General Support Tracker In-Reply-To: <503EFF3E.9070301@tid.es> References: <503EFF3E.9070301@tid.es> Message-ID: Hi Juanjo, It looks like UCPs are using not only the General Support tracker but still add a number of tickets in the FI-WARE Theme/Epic/Feature Requests tracker. For I2ND we got additional tickets in August from FINSENY project, and some of them are out of scope for the chapter (and others for the project too presumably). Since this point is not so clear, shouldn't tickets in this tracker be added only as a conclusion of the analysis of FI-WARE + UCPs (e.g. via the general support tracker discussions) about possible inclusion of requested functionality in the FI-WARE backlog later? BR Pier P.S: just a minor correction to the list of valid ticket status you reported: the 'ToBeChecked' status is actually named 'CheckSolved' in the tracker. Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 30 agosto 2012 07:51 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Taking care of the FI-WARE General Support Tracker Hi all, Now we face a critical point at which we should demonstrate quick response to any request for support by any UC projects. We may foreseen that many request will come as a result of making FI-WARE GEs available on the Testbed and UC projects trying to experiment with them. As per agreement with UC projects, most of the interaction should now be handled through the FI-WARE General Support tracker at: https://forge.fi-ware.eu/tracker/?group_id=7 I have asked Axel and Carlos, as the dedicated team that was designated to monitor interaction with UC projects, to make sure that proper monitor of the status of this tracker is in place so that Chapter Leads and Chapter teams take care of tickets. Note that some tickets may also require actions by members of the Testbed team or the team working on Development Tools. A very basic workflow has been defined to start working. We will see how this evolves but I believe we should keep it as simple as possible. Currently, valid status are: * Open: it means that the ticket remains unassigned it has been formulated (or reformulated) * Assigned: it means someone is taking care of it * ToBeRevised: it means that the original ticket was wrongly formulated and has to be reformulated or closed * ToBeChecked: it means that the one that was assigned to take care of it now thinks is solved but this has to be verified * Closed: it means that the ticket was closed and valid transitions are defined at: https://forge.fi-ware.eu/tracker/admin/?group_id=7&atid=162&workflow=1 Don't wait until Axel or Carlos pursues you to handle a ticket and be proactive checking regularly what you could assign to you ! I have kindly asked Axel and Carlos to brief us during our next follow-up confcall about status of the tracker, APs that we should put in place to move forward, etc. 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jhierro at tid.es Fri Aug 31 11:00:04 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 31 Aug 2012 11:00:04 +0200 Subject: [Fiware-wpa] R: [Fiware-wpl] Taking care of the FI-WARE General Support Tracker In-Reply-To: References: <503EFF3E.9070301@tid.es> Message-ID: <50407D14.2050605@tid.es> Hi Pier, I will ask for clarification to UC projects. As you say, they should be issuing tickets at the FI-WARE General Support tracker ... tickets in this tracker should be added only as conclusions of some preliminary analysis between FI-WARE and UCPs (e.g. via the general support tracker discussions). You are also right with the correction regarding your comment on the 'CheckSolved' status. Cheers, -- Juanjo On 31/08/12 10:49, Garino Pierangelo wrote: Hi Juanjo, It looks like UCPs are using not only the General Support tracker but still add a number of tickets in the FI-WARE Theme/Epic/Feature Requests tracker. For I2ND we got additional tickets in August from FINSENY project, and some of them are out of scope for the chapter (and others for the project too presumably). Since this point is not so clear, shouldn't tickets in this tracker be added only as a conclusion of the analysis of FI-WARE + UCPs (e.g. via the general support tracker discussions) about possible inclusion of requested functionality in the FI-WARE backlog later? BR Pier P.S: just a minor correction to the list of valid ticket status you reported: the 'ToBeChecked' status is actually named 'CheckSolved' in the tracker. Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 30 agosto 2012 07:51 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Taking care of the FI-WARE General Support Tracker Hi all, Now we face a critical point at which we should demonstrate quick response to any request for support by any UC projects. We may foreseen that many request will come as a result of making FI-WARE GEs available on the Testbed and UC projects trying to experiment with them. As per agreement with UC projects, most of the interaction should now be handled through the FI-WARE General Support tracker at: https://forge.fi-ware.eu/tracker/?group_id=7 I have asked Axel and Carlos, as the dedicated team that was designated to monitor interaction with UC projects, to make sure that proper monitor of the status of this tracker is in place so that Chapter Leads and Chapter teams take care of tickets. Note that some tickets may also require actions by members of the Testbed team or the team working on Development Tools. A very basic workflow has been defined to start working. We will see how this evolves but I believe we should keep it as simple as possible. Currently, valid status are: * Open: it means that the ticket remains unassigned it has been formulated (or reformulated) * Assigned: it means someone is taking care of it * ToBeRevised: it means that the original ticket was wrongly formulated and has to be reformulated or closed * ToBeChecked: it means that the one that was assigned to take care of it now thinks is solved but this has to be verified * Closed: it means that the ticket was closed and valid transitions are defined at: https://forge.fi-ware.eu/tracker/admin/?group_id=7&atid=162&workflow=1 Don't wait until Axel or Carlos pursues you to handle a ticket and be proactive checking regularly what you could assign to you ! I have kindly asked Axel and Carlos to brief us during our next follow-up confcall about status of the tracker, APs that we should put in place to move forward, etc. 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Fri Aug 31 12:07:08 2012 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 31 Aug 2012 10:07:08 +0000 Subject: [Fiware-wpa] OUTSMART / FI-WARE synchronization Message-ID: Dear colleagues, The next monday September 6th, Fano Ramparany is organizing a second workshop on OUTSMART Architecture Review/synchronization with Fi-WARE. The workshop is to be held in Orange labs premises in Paris, but he's providing facilities for remote access too. Details on the venue and link to the agenda are available at: https://docs.google.com/spreadsheet/ccc?key=0AobKeqMq4hM-dFJFdWtIWEJ0Vk95ckFLQkk5U28zLUE#gid=8 (Agenda: https://docs.google.com/document/d/1Y-ARxhADirv7UeVBg7reRlR1bLHzuXqLJZ1Ll9huO6k/edit ) Fano has provided a screen sharing facility so far that is accessible through the link below, but I am sure he will be providing more details soon that I'll forward in turn. https://coopnet.multimedia-conference.orange-business.com/ What we need at this point is that one (or more) architect per FI-WARE WP is identified to attend the workshop. Please, note that this is a whole-day activity, which is the only way to reach a similar level of discussions/results compared to a trip to the venue. Just reply to this e-mail to me with your WP attendees list and I'll update Fano. Thanks for sending by next Monday EoB the latest. Please, note the minutes from the previous meeting (kick-off of this activity) are available at: https://docs.google.com/document/d/1RXB_hIwTqb93Nw5zPbebbCLqOE6avA1tJNBm2yiuFg8/edit Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Aug 29 06:30:32 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 29 Aug 2012 04:30:32 +0000 Subject: [Fiware-wpa] Joint FI-WARE WPLs/WPAs follow-up confcall Message-ID: <936DECD07EB54B4BAA44E7B823EC89411FA99917@EX10-MB2-MAD.hi.inet> When: Monday, September 03, 2012 3:00 PM-5:00 PM. (UTC+01:00) Sarajevo, Skopje, Warsaw, Zagreb *~*~*~*~*~*~*~*~*~* We'll use powwownow. PIN: 050662. Local dial-in phone numbers at: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3393 bytes Desc: not available URL: From jhierro at tid.es Wed Aug 29 06:33:29 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 29 Aug 2012 04:33:29 +0000 Subject: [Fiware-wpa] Follow-up confcall on September 3th Message-ID: Hi all, I won't be able to attend our regular follow-up confcall on September 3th at the default timeslot (11:00am ? 13:30pm). Therefore, I have changed the timeslot this time to be from 15:00 until 16:30 CET. I hope that most of you can attend. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: