From jhierro at tid.es Thu May 2 12:30:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 02 May 2013 12:30:23 +0200 Subject: [Fiware-wpl] Fwd: FI-WARE: M24 review in Brussels In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06DA69A6@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06DA69A6@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <5182403F.3040105@tid.es> Please find enclosed the official invitation by the EC to the FI-WARE 2nd year review meeting. Arian has confirmed to me that the meeting is scheduled to start early in the morning on June 12 and finish at 17:00 CET on June 13. Please book your flights accordingly (even considering that the review may close at 18:00 CET) Cheers, -- Juanjo -------- Original Message -------- Subject: FI-WARE: M24 review in Brussels Date: Thu, 2 May 2013 09:48:37 +0000 From: To: , CC: , Dear all, As announced before, the next review meeting will be held on 12-13 June 2013 (two full days), in Brussels, in room 0/S9. The official invitation will follow shortly. Best regards, Arian. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu May 2 15:34:36 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 2 May 2013 13:34:36 +0000 Subject: [Fiware-wpl] FW: [Fiware-testbed] Observationsdraft for 10.5.1 report on validation process References: <2981E9D6242FCF47ADC9B5DBA5DFD6646101768A@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646106E7B5@DEWDFEMB11A.global.corp.sap> Dear WPL/WPA-colleagues, Following up on the review report, find down below my draft of four observations given to the review report conserning the rejection of D.10.5.1 - it was decided to deliver this on a WP level - nonetheless every WPL/WPA should have a look at it - in the end there are some "assumptions" mentioned in relation to how the "agil" methodology was applied, which may save life of WP10 but might bring other WPs into trouble - therefore: PLEASE review the rational given to the EC. TID clarified with the Project Officer: The EC will not put into question the assessment of suitably qualified experts. Yes-no discussions about opinions are not very meaningful, and we would not enter into such discussions. Only factual statements (and not opinions dressed up as factual statements, as is often the case) would be considered Please excuse the "german" style, potentially having to many lengthy sentences down below and feel free to break things up or change them at your will :) Please provide your input and corrections as soon as possible. In order to join the discussion and to cater for a shorter "release"-cycle I will add the chief architect directly to this discussion. Best, /Thorsten PS: find the original reviewer comments at the bottom of this mail Observation towards "D10.5.1 Report on Validation Process including Validation with Use Case projects" - Deliverable D10.5.1 is rejected. No re-submission is required. 1. "The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases." Observation by FI-WARE: - The validation process was initially proposed by FI-WARE to the Use-Case projects. This approach was discussed and agreed by representatives of the Use-Case projects within the Architecture Board. - The architecture board recognized the reviewers comments in M6 and FI-WARE proposed a subsequent "initial feedback survey" to cater for short-term feedback cycle and to allow feedback on the first Testbed instances (therefore being closely aligned with the FI-WARE project and FI-WARE release - major fi-ware release end of M17/30.09.2012 - survey send out: Di 02.10.2012 01:03). - Subsequent and proposed validation schedules are by definition of the process to be aligned within the involved stakeholders: FI-WARE and use case projects. There is no defined schedule by the validation process, therefore alignment towards subsequent FI-WARE Release is part of the involved partners and not of the process. The process allows maximum flexibility. 2. "The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. " Observation by FI-WARE: - FI-WARE agrees with the reviewers comments that the validation process as outlined and executed within the FI-WARE project within Task 10.5 does not completely follow the description of the task in the DoW - but again as this was decided and discussed within the highest possible technology board (the FI-WARE architecture board) this deviation from the DoW is in line with all related parties and the deviation in general should be acceptable. As changes to the DoW take time, these changes in the process could only be reflected as part of the upcoming amendment 4 to the DoW. 3. "According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. [..]The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterisation of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Observation by FI-WARE - The D.10.5.1 deliverables states: "The design phase occurs taking care also requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters." - which does not imply a given fact that requirements actually were successfully communicated and does not imply that these requirements can be tracked throughout the whole process in the current way, agile is implemented and "lived". The deliverable in this point may have wrongly lead to the assumption that there were successfully communicated requirements, which the validation team itself couldn't really judge or imply. As the deliverable outlined later there is no tight linkage between defined requirements and the features provided. - Secondly the decision taken by the Architecture board reached was bond to the fact that validation based on all relevant features/epics provided by the FI-WARE project was not reasonable for the given amount of time and expected efforts - As of today FI-WARE features do comprise of more than 900 features (please bear in mind that only limited resources were foreseen in the DoW to actually execute on the validation task towards the core platform). - Finally it was decided by the Architecture board that a "validation questionnaire" to be provided by FI-WARE has to cater for validation and mainly will be based upon questions related to "validation context" and "generic enablers" and not based on features and requirements. The use case projects therefore were only bound to give the scenarios and their descriptions to FI-WARE and not their requirements. - Enrichment of the characterization of use case scenarios and boost of GE uptake was not in scope of the validation approach as implied in the reviewer statement. - As the amendment 4 foresees there will be again a reiteration of the validation process towards the phase 2 projects and their trials, where further changes in the process are currently being considered by the architecture board, potentially leading to a tighter linkage between requirements and GEs which might lead to a better validation. E.g. it is foreseen that use case projects will input their requirements to GE-based trackers and not to a common fi-ware tracker any more. One of the feedbacks received by the use case projects almost speaks for itself: As a general impression, the validation questions were quite helpful to provide feedback. The only issue we faced in our case was due to the fact that we evaluated the GEs per prototype component and not for specific scenarios. 4. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. Observation by FI-WARE - Checking non-functional capabilities was again reiterated within the architecture board and no common consensus could be found towards the validation process. This recommendation will be taken into the next discussion which will redefine the process for FIWARE v2 (but will not be part of the D.10.5.2 deliverable as for time constraints: phase 2 projects did not start to redefine the validation process and potentially won't do so for the next two month ) Here is again the complete text from the Review Report (only broken up with some newlines): D10.5.1 Report on Validation Process including Validation with Use Case projects This deliverable outlines the designed and recommended validation process for the use cases to follow. Additionally the initial feedback survey, which was initiate and send to the use case projects and the main findings are outlined. The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases. The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. As explained in the document, there is no tight linkage between the defined requirements and the features provided by the GE providers. Hence, the validation and requirements evaluation will not be based on a requirements matrix, but will follow an open questionnaire approach. The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterisation of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri May 3 03:13:18 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 May 2013 03:13:18 +0200 Subject: [Fiware-wpl] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51830F2E.9@tid.es> Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: * FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: * @All: to double-check that no FI-WARE GE planned in Release 2 is missing * @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. * @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. * @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I've proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Fri May 3 06:49:32 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Fri, 3 May 2013 04:49:32 +0000 Subject: [Fiware-wpl] [Fiware-wpa] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: <51830F2E.9@tid.es> References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> <51830F2E.9@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646106F187@DEWDFEMB11A.global.corp.sap> Hi Juanjo, My initial thought on the "gathering" of Business Framework GEs: I don't like it - TID is for example not delivering anything right now and the marketplace would be already available and "usable". This picture would be now blurred. The store, marketplace and the RSS is provided by various partners and even complete different technologies, that would be completely blurred as well. The marketplace is clearly a separated thing, which is already usable and even completely open source for quite some time. My second thought on the new table concerning timing: you now give them the impression that they can only start working on the GEs with the end of July. - This is a high risk and I would propose to change this. We are restraining them now towards this date in the future, but in fact they should be able and they need to use us "before" - the original version of the table depicted this fact. Now they could argue against the EC: FI-WARE only delivered in the end of july the access to ALL of their GEs. Which is not true. In fact it's legal or some other constraints, but we don't wan to restrain them from using us! As I said: e.g. the marketplace - but as well other components - can be used "now" & at any time. Third one: the sums are wrong which are given in the 1st and 2nd release of the table - e.g. in the service repository there is on D which is not counted - and potentially more, given the complete table. Can you please change the table accordingly? Thanks and best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 3. Mai 2013 03:13 To: thierry.nagellen at orange.com Cc: stefano de panfilis; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: * FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: * @All: to double-check that no FI-WARE GE planned in Release 2 is missing * @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. * @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. * @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I've proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 May 3 08:03:57 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 May 2013 08:03:57 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646106F187@DEWDFEMB11A.global.corp.sap> References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> <51830F2E.9@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646106F187@DEWDFEMB11A.global.corp.sap> Message-ID: <5183534D.3050600@tid.es> On 03/05/13 06:49, Sandfuchs, Thorsten wrote: Hi Juanjo, My initial thought on the "gathering" of Business Framework GEs: I don't like it - TID is for example not delivering anything right now and the marketplace would be already available and "usable". This picture would be now blurred. The store, marketplace and the RSS is provided by various partners and even complete different technologies, that would be completely blurred as well. The marketplace is clearly a separated thing, which is already usable and even completely open source for quite some time. It is unclear to me whether you only comply about making the marketplace be part of that package or not. To be hones, my opinion is that we have to distinguish between a GE being "usable" and "useful". In you want my honest opinion, I may agree that the marketplace alone might be usable but I have serious doubts it will be useful (at least with the current functionality today) ... but, anyhow, I'm fine with keeping it separate. I'll wait to hear Torsten's opinion if you don't mind. What about keeping the package that gathers together the store, RSS and the BM&BE editors ? My only intention is to make it easy to Use Case projects the decision about planned usage of a given GE or package of related GEs. Again, a good example was the Cloud chapter. Most of the UC projects in phase 1 understood how to respond to the question: would you use the part of the FI-WARE Cloud functionality that has to do with enabling you to create VMs ? It had been much more difficult for them to understand what to do with the SM GE or the DCRM GE, for instance. That would mean understanding the different components that make up the FI-WARE Cloud architecture, when the real fact is that they don't care so much about it, they mostly care about what they can do as users (application providers). Similarly, it would be easier for you to answer what you want to use of Amazon Web Services rather that what you plan to use of Amanzon Web Services' Architecture. Another hint I use is to think about what are the GEs for which it would make sense to perform training in a joint session. There are GEs that can be clearly explained standalone in a webinar. However, there are other GEs for which it would make much more sense to perform a joint session. From that perspective, I tend to link rows in the table with what it could match a training session/webinar. Again, this are my thoughts and I just training to make a form that can easily be understood and completed by UC projects. My second thought on the new table concerning timing: you now give them the impression that they can only start working on the GEs with the end of July. - This is a high risk and I would propose to change this. We are restraining them now towards this date in the future, but in fact they should be able and they need to use us "before" - the original version of the table depicted this fact. Now they could argue against the EC: FI-WARE only delivered in the end of july the access to ALL of their GEs. Which is not true. In fact it's legal or some other constraints, but we don't wan to restrain them from using us! As I said: e.g. the marketplace - but as well other components - can be used "now" & at any time. The third sheet has to do with the 2nd Release of FI-WARE. As far as I understand, but Miguel can correct me if I'm wrong, we have only committed to deliver the software and accompanying documentation of the minor release 2.2. A different story is whether it will be deployed on the FI-WARE Testbed and has been made available by end of April (or during May) or not. I understand that there was flexibility in the decision but I may be wrong. I didn't want to commit to availability of release 2.2 on the FI-WARE Testbed for all GEs. However, WPs are free to update the column "Planned 1st Deployment / Next Update" as to reflect a date earlier than July 31 if they are planning to deploy minor release 2.2 on the Testbed and make it available on the Testbed. Besides this, one of the messages we will pass to the UC projects is that the FI-WARE Testbed IS ALREADY AVAILABLE and Release 1 is already deployed there. Therefore, looking at the column "Already in 1st release (Y/N/P)" they can figure out whether they can use it already or not. In summary, this is what we will explain to UC projects: * If the column "Already in 1st release (Y/N/P)" is marked as "Y", the GEi in question was part of FI-WARE Release 1 and is already available in the FI-WARE Testbed. Therefore, please start making hands on it. * The date at the column "Planned 1st Deployment / Next Update" has the following meaning: * If the column "Already in 1st release (Y/N/P)" is marked as "Y", it then contains the date at which an update of the FI-WARE GEi is planned on the FI-WARE Testbed, in order to incorporate developed functionality planned in the 2nd Release. That update will take place for sure in July 31st, but may come earlier for some FI-WARE GEis which will be updated in the FI-WARE Testbed once minor release 2.2 was closed. We will update the value of this column accordingly during the next week. * If the column "Already in 1st release (Y/N/P)" is marked as "N", it then contains the date at which a first release of the FI-WARE GEi is planned on the FI-WARE Testbed. The FI-WARE GEi will be available for sure in July 31st, but it may come earlier for some FI-WARE GEis which will be deployed in the FI-WARE Testbed once minor release 2.2 was closed. We will update the value of this column accordingly during the next week. BTW, the "P" in "Already in 1st release (Y/N/P)" means "Partially". There is no "P" in any cell now, but just in case you would need it to better reflect the status. Third one: the sums are wrong which are given in the 1st and 2nd release of the table - e.g. in the service repository there is on D which is not counted - and potentially more, given the complete table. Ok, thanks for rising it up. Honestly I didn't have time to verify the column. I'll do it as soon as possible today. Can you please change the table accordingly? Regarding you first point, I'll wait for Torsten regarding the package that would bring together the store, RSS and BM&BE. I have separated the marketplace already. Regarding your second point, I hope that my explanations are enough as to keep current approach. Regarding the third point. Yes, sure. Thanks for your valuable feedback. -- Juanjo Thanks and best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 3. Mai 2013 03:13 To: thierry.nagellen at orange.com Cc: stefano de panfilis; fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: * FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: * @All: to double-check that no FI-WARE GE planned in Release 2 is missing * @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. * @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. * @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I've proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Fri May 3 08:26:43 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Fri, 3 May 2013 09:26:43 +0300 Subject: [Fiware-wpl] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: <51830F2E.9@tid.es> References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> <51830F2E.9@tid.es> Message-ID: > @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. The rows for Cloud are fine. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: thierry.nagellen at orange.com, Cc: "fiware-wpa at lists.fi-ware.eu" , "fiware-wpl at lists.fi-ware.eu" Date: 03/05/2013 04:12 AM Subject: [Fiware-wpl] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) Sent by: fiware-wpl-bounces at lists.fi-ware.eu Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: @All: to double-check that no FI-WARE GE planned in Release 2 is missing @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I?ve proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri May 3 08:43:28 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 3 May 2013 08:43:28 +0200 Subject: [Fiware-wpl] R: Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: <51830F2E.9@tid.es> References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> <51830F2E.9@tid.es> Message-ID: Dear Juanjo, My opinion concerning I2ND is that, although some of the chapter GEs are not physically located in the FI-WARE Testbed nor can be 'tested' there (but there will also be 'proxies' on the testbed which give access to the remote implementation), it is important we list them in the cockpit. In this way we can easily keep track of the planned usage by the UCPs in Phase 2. As you say the cockpit plays an important role in the review, and we already collected some expression of interest for the networking GEs during the architect week in Madrid last month (e.g. at least two UCPs plan to use S3C GE), so it would be important to show this together with all the other GEs. For what concerns CDI, I consider it 'manageable' at the same level of the Cloud Proxy: both are GEs which can be in the hands of a 'user', therefore I don't see specific issues in collecting the planned usage in the table. If you believe there are additional possibilities to collect this information, please let us know what are your proposals, so that we can evaluate them. 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: venerd? 3 maggio 2013 03:13 A: thierry.nagellen at orange.com Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-wpl] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: * FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: * @All: to double-check that no FI-WARE GE planned in Release 2 is missing * @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. * @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. * @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I've proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 mev at tid.es Fri May 3 09:15:14 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 03 May 2013 07:15:14 +0000 Subject: [Fiware-wpl] Backlog - Items Identifiers available Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89049AB5@EX10-MB2-MAD.hi.inet> Dear WP Leaders, According to the issue raised by Thorsten regarding the degree the original naming convention has been followed for the backlog items, there's need to check whether the identifiers have followed the naming rules properly - as agreed on last weekly management meeting. In order to easy the process, I've uploaded spreadsheets for each chapter where you can find all identifiers. They are available at FI-WARE Private - Docs. From now on, I'll upload reviews, snapshots, and dashboards there . @Thorsten: https://forge.fi-ware.eu/docman/view.php/27/2170/FIWARE.backlog.tracker.Apps.Identifiers.20130502-0821.xlsx @Alex: https://forge.fi-ware.eu/docman/view.php/27/2171/FIWARE.backlog.tracker.Cloud.Identifiers.20130502-0821.xlsx @Thierry/Carlos: https://forge.fi-ware.eu/docman/view.php/27/2172/FIWARE.backlog.tracker.IoT.Identifiers.20130502-0821.xlsx @Sergio: https://forge.fi-ware.eu/docman/view.php/27/2173/FIWARE.backlog.tracker.Data.Identifiers.20130502-0821.xlsx @Pier: https://forge.fi-ware.eu/docman/view.php/27/2174/FIWARE.backlog.tracker.I2ND.Identifiers.20130502-0821.xlsx @Pascal: https://forge.fi-ware.eu/docman/view.php/27/2175/FIWARE.backlog.tracker.Security.Identifiers.20130502-0822.xlsx In those files, there's a column with all identifiers, my suggestion on how to proceed is the following: 1. Order the items according to their actual hierarchy and provide the output to me 2. I'll analyse the files in order to get a quantifier showing the degree the original naming rules have been followed. 3. Once we get the big picture, we can discuss on how to overcome the actual situation. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri May 3 09:19:13 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 03 May 2013 09:19:13 +0200 Subject: [Fiware-wpl] R: Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) In-Reply-To: References: <20819_1366728607_51769F9F_20819_321_13_976A65C5A08ADF49B9A8523F7F81925C0DEA92@PEXCVZYM13.corporate.adroot.infra.ftgroup> <51830F2E.9@tid.es> Message-ID: <518364F1.30000@tid.es> Ok. Just wanted to confirm your views on it. Could you elaborate on what concrete rows you would add ? I may take simply the name of the GEs in the Architecture I2ND chapter but just to be sure ... On the other hand, each row doesn't just refer to a GE but a given GEi (implementation). Since I don't have the "product name" for them, please provide. I will add the rows once you provide this info. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 03/05/13 08:43, Garino Pierangelo wrote: Dear Juanjo, My opinion concerning I2ND is that, although some of the chapter GEs are not physically located in the FI-WARE Testbed nor can be 'tested' there (but there will also be 'proxies' on the testbed which give access to the remote implementation), it is important we list them in the cockpit. In this way we can easily keep track of the planned usage by the UCPs in Phase 2. As you say the cockpit plays an important role in the review, and we already collected some expression of interest for the networking GEs during the architect week in Madrid last month (e.g. at least two UCPs plan to use S3C GE), so it would be important to show this together with all the other GEs. For what concerns CDI, I consider it 'manageable' at the same level of the Cloud Proxy: both are GEs which can be in the hands of a 'user', therefore I don't see specific issues in collecting the planned usage in the table. If you believe there are additional possibilities to collect this information, please let us know what are your proposals, so that we can evaluate them. 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: venerd? 3 maggio 2013 03:13 A: thierry.nagellen at orange.com Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-wpl] Revised version of cockpit on planned usage of GE by UC projects (was Re: Request from Xifi project) Dear all, Just to let you know, I have updated the spreadsheet in Google docs in preparation of the AB meeting tomorrow. You can take a look at it: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=8 There are three sheets there: * FI-WARE GEi (1st Release) planned usage in Phase 1: collecting info about usage of GEs delivered in FI-WARE Release 1 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 1: collecting info about planned usage of GEs announced in FI-WARE Release 2 that UC projects reported in phase 1 * FI-WARE GEi (2nd Release) planned usage in Phase 2: which is the info we now have to collect from UC projects in phase 2 You will notice that I have added new rows regarding FI-WARE GEs in the third sheet. They match new FI-WARE GEs to be incorporated in Release 2. I have added a column to label those FI-WARE GEs that were already there in Release 1. I filled the values of those UC projects that are continuation of some project(s) in Phase 1. I did it by extrapolation but of course they will be requested to double-check their input. All WPLs/WPAs are asked to check the information provided. You know that this cockpit is highly visible and will play an important role in the review as well as during coordination with UC projects. Specifically, I would like to highlight the following APs: * @All: to double-check that no FI-WARE GE planned in Release 2 is missing * @I2ND: the cockpit is mostly to monitor planned usage of GEs in the FI-WARE Testbed (or deployed locally). It's a bit unclear to me how to record information about I2ND GEs other than the Proxy. Those ones more related to the network won't be testable in the Testbed, as far as I understand. Also I see different possibilities to capture infor about the CDI. I rather welcome your feedback here. * @Cloud: I still believe, like in Release 1, that it doesn't make sense to ask about planned usage of individual FI-WARE Cloud GEs. Instead, we can/should ask for specific Cloud functionality and check whether UC projects plan to use it. I hope you agree with the approach but your feedback is welcome. * @Apps: while I believe that it makes sense to refer to the individual Composition/Mediation GEs, I believe that similarly to Cloud, it doesn't make sense to refer to some of the GEs that define the Business Framework separately, namely, the Marketplace, Store, BM&BE editor and RSS GEs. Therefore, I have gathered all of them together in a "package". Then, UC projects can more easily respond whether they plan to use that "functional package" or not, depending on whether they plan to setup some sort of Apps Marketplace or not. Anyhow, your feedback is welcome. Please try to provide your input before end of next week. We should stabilize its contents by that time. Best regards, -- juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 23/04/13 16:50, thierry.nagellen at orange.com wrote: Hi colleagues We are currently in a Xifi meeting and they prepare a survey for UC which should target a bit the same things that what we are doing through Architecture Board with UC projects interest into Fi-Ware GE. I've proposed to used the list of GEs available in release 2.2 to be sure to have the right name for each GE. Do you agree to provide this list? (I hope yes of course) and can I used the spreadsheet in Googledocs for AB or do we have to update it before to provide it officially to Xifi? Of course we should have the same results in Xifi and in the AB but Xifi is also asking in which node they should implement the GE depending the specific trials the UC projects have planned. Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 mcp at tid.es Fri May 3 10:56:25 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 03 May 2013 10:56:25 +0200 Subject: [Fiware-wpl] Focus of State of the Art deliverable Message-ID: <51837BB9.8030504@tid.es> Dear all, after a few interactions withe the WPs, I would like to remark something that we partially mentioned in the confcall on monday but among so much info messages sometimes get lost. * Some WPL ask about the desired length. The answer is that there is not a standard number of pages. We do not expect a chunky doc of 100 pages per WP, we want significant and solid messages. I do not mind if we get 20 pages per chapter as long as they are well written and give the right information. * The focus is twofold: * What there is out there (current situation) * What it is going to be there (trends, foreseable future) * We must say what innovations we offer in each chapter y how it compares with other research projects or products on the market. Research projects do not necessarily mean FP7 or PPP related, not even subsidised. Please avoid a document where 80% of the text is a long list of project subsidised by the EC or national authorities. Subsidised research can be mentioned (must, if it is relevant) but let us avoid a narrow view. Hope this clarifies a bit. Please let your partners know in each chapter. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Fri May 3 15:14:32 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 03 May 2013 13:14:32 +0000 Subject: [Fiware-wpl] Delivery : D2.1.5 (e)-Requirements Backlog Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89049D32@EX10-MB2-MAD.hi.inet> Dear Partners, Let me inform that we have delivered: D2.1.5 (e)-Requirements Backlog this morning. Public link: https://forge.fi-ware.eu/docman/view.php/7/2178/FIWARE+-+Backlog+20130502.xlsx Private link: https://forge.fi-ware.eu/docman/view.php/27/2179/FIWARE+-+Backlog+20130502-Source.xlsm I've done some house-keeping at FIWARE-Private Doc, where I'll upload periodic info about the backlog, reviewes, snapshot, dashboards, etc. [cid:image001.png at 01CE4810.E84A40A0] If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15249 bytes Desc: image001.png URL: From jhierro at tid.es Mon May 6 02:07:30 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 06 May 2013 02:07:30 +0200 Subject: [Fiware-wpl] Part II of weekly joint WPLs/WPAs follow-up confcalls Message-ID: <5186F442.2010603@tid.es> Hi all, As we agreed during our last confcall, we will structure the agenda of our weekly joint WPLs/WPAs follow-up confcalls so that: * Part I (morning session) will be devoted to project management aspects, i.e., follow-up of deliverables, milestones, dissemination activities and other project management activities * Part II (afternoon session) will be devoted to architectural/technical aspects as well as preparation of contents for the project review There are two major points that we will address during Part II in the afternoon: * Presentation of the new blueprint management capabilities to be provided as part of the FI-WARE Cloud Reference Architecture in Release 2 * Description of approach regarding Live Demo App backlog development and usage in an updated version of the FI-WARE product vision Blueprint management capabilities will enable application providers to perform the automated deployment of FI-WARE GEi instances or packages of related FI-WARE GEi instances. They will also allow application providers to define how the deployment of their applications can be automated. In a nutshell, a Blueprint template defines a virtual infrastructure structured in multiple tiers, each comprising a flexible number of VMs, together with a number of recipes that enable to automate the deployment of software (part of a final application, package of FI-WARE GEis, individual FI-WARE GEis, etc) on top. It would be very important to define the Blueprint template associated to many of the GEis in FI-WARE and even some packages of related FI-WARE GEis, that's why we believe the presentation of Blueprint management capabilities is relevant to all Chapters. I won't be able to attend Part I tomorrow because I'm traveling to the FIA in Dublin but I expect to be able to join and chair Part II in the afternoon. Miguel will take care of the session in the morning (Part I). In the event that I cannot make it in the afternoon, he will chair it as well. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 6 10:42:22 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 May 2013 10:42:22 +0200 Subject: [Fiware-wpl] Minutes of meeting for WPL/WPA meeting Message-ID: <51876CEE.1020502@tid.es> Here you are: * https://docs.google.com/document/d/1K-ZlPZHFd-ErVEGHjUhIUO3YdX-ZhXYOHgrmC1C2YLs/edit?pli=1# Still doing some editing... 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 juan.bareno at atosresearch.eu Mon May 6 11:57:23 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Mon, 6 May 2013 11:57:23 +0200 Subject: [Fiware-wpl] ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Message-ID: Dear Colleagues Just 2 exploitation plans updated so far please update them in a separate word template as SIEMENS and Intel did, see folders below Regarding the update please take into account the recommendations form the M18 Review cited below, that summarizing want us to identify: - The main FIWARE outcomes (which concrete GEs and Instances are we going to exploit and how we are going to exploit or sell these concrete ones: Cloud Stack, PaaS, Big Data....) - In which ecosystems are you going to focus or prioritize (M2M, Big Data, PaaS...)including industrial partners as utilities, cities.... ? "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, FI-WARE is in essence a set of independent GEs for "pick-and-choose", rather than a (core) platform. It needs to be positioned as such. The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: Juan Bare?o Guerenabarrena Sent: martes, 30 de abril de 2013 13:08 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: RE: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Please update into the Forge, as a separated document, named XXXX Exploitation plan M24 with all the track changes and I will include it into the deliverable Thanks Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: Juan Bare?o Guerenabarrena Sent: lunes, 29 de abril de 2013 16:31 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Regarding ACTION 3: To Update of the individual exploitation plans, last version from M18, please do that directly into the document within the folder "Work Versions", "WP11 Final Deliverables M24" WP11.2.2 Exploitation Plan ANNEX I https://forge.fi-ware.eu/docman/index.php?group_id=16 - Each FI WARE Partner before 3rd of May. Not use the wiki links as the last version do not content the initial questions answered into the M12 Review "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" For the new comers eprosima and red.es please follow the same structure and answer the following questions: * Organization Profile * FI-WARE relevance in your current business model * Identification of main project outcomes * How are you going to exploit the project results in distinct environments? * Which customers do we want to serve? * Which channels will be used to reach the various customer segments? * Which benefits are the participants going to take to the market thanks to FIWARE? * How are the benefits going to be sold? * How will the sales process work? * Globalisation of the exploitation plan * How will make money from FIWARE Platform? Thanks Juan From: Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu) Cc: 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu); fiware-pcc at lists.fi-ware.eu Subject: FW: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 339 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.gif Type: image/gif Size: 4064 bytes Desc: image006.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 76225 bytes Desc: image001.jpg URL: From juan.bareno at atosresearch.eu Mon May 6 12:17:23 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Mon, 6 May 2013 12:17:23 +0200 Subject: [Fiware-wpl] ACTION 3: To Update of the individual exploitationplans, last version from M18- directly into the ANNEX I from D11.2.2 Document Message-ID: Dear Colleagues At the end the final purpose of this "pick and choose" platform strategy, as described the reviewers in M18 review report, is to determinate the real added value provided by FI WARE, selecting among the 90 GEs or potential Instances the ones with real market potential (USDL, CEP, IoT ..., PaaS+Big Data,...) in identified industries, because is something that is not currently in the market or with very limited presence or with real added value respect to current ones and has been tested by: - Market analysis - UC feedback on these GE and Instances - Individual Exploitation Plans from FI WARE partners for the GEs or Instances identified/prioritized individually by partner Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: lunes, 06 de mayo de 2013 11:57 To: fiware-exploitation at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: jaimemartin at eprosima.com; antonio.fuentes at rediris.es Subject: Re: [Fiware-wpl] ACTION 3: To Update of the individual exploitationplans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Just 2 exploitation plans updated so far please update them in a separate word template as SIEMENS and Intel did, see folders below Regarding the update please take into account the recommendations form the M18 Review cited below, that summarizing want us to identify: - The main FIWARE outcomes (which concrete GEs and Instances are we going to exploit and how we are going to exploit or sell these concrete ones: Cloud Stack, PaaS, Big Data....) - In which ecosystems are you going to focus or prioritize (M2M, Big Data, PaaS...)including industrial partners as utilities, cities.... ? "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, FI-WARE is in essence a set of independent GEs for "pick-and-choose", rather than a (core) platform. It needs to be positioned as such. The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: Juan Bare?o Guerenabarrena Sent: martes, 30 de abril de 2013 13:08 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: RE: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Please update into the Forge, as a separated document, named XXXX Exploitation plan M24 with all the track changes and I will include it into the deliverable Thanks Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: Juan Bare?o Guerenabarrena Sent: lunes, 29 de abril de 2013 16:31 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Regarding ACTION 3: To Update of the individual exploitation plans, last version from M18, please do that directly into the document within the folder "Work Versions", "WP11 Final Deliverables M24" WP11.2.2 Exploitation Plan ANNEX I https://forge.fi-ware.eu/docman/index.php?group_id=16 - Each FI WARE Partner before 3rd of May. Not use the wiki links as the last version do not content the initial questions answered into the M12 Review "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" For the new comers eprosima and red.es please follow the same structure and answer the following questions: * Organization Profile * FI-WARE relevance in your current business model * Identification of main project outcomes * How are you going to exploit the project results in distinct environments? * Which customers do we want to serve? * Which channels will be used to reach the various customer segments? * Which benefits are the participants going to take to the market thanks to FIWARE? * How are the benefits going to be sold? * How will the sales process work? * Globalisation of the exploitation plan * How will make money from FIWARE Platform? Thanks Juan From: Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu) Cc: 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu); fiware-pcc at lists.fi-ware.eu Subject: FW: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 76225 bytes Desc: image004.jpg URL: From mcp at tid.es Mon May 6 13:01:36 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 May 2013 13:01:36 +0200 Subject: [Fiware-wpl] Link for Hernr's presentation Message-ID: <51878D90.5050008@tid.es> Dear all, SAP has kindly provided facilities for screensharing today. We will use it in Henar's timeslot. This is the link: * https://sap.emea.pgiconnect.com/sandfuchs 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 Mon May 6 14:55:25 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 6 May 2013 14:55:25 +0200 Subject: [Fiware-wpl] R: Link for Hernr's presentation In-Reply-To: <51878D90.5050008@tid.es> References: <51878D90.5050008@tid.es> Message-ID: Hi , is it possible to get the slides as well? I'm experiencing some connection problem... Thanks! Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Miguel Carrillo Inviato: luned? 6 maggio 2013 13:02 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: FERMIN GALAN MARQUEZ; HENAR MU?OZ FRUTOS; Fernando L?pez Aguilar Oggetto: [Fiware-wpl] Link for Hernr's presentation Dear all, SAP has kindly provided facilities for screensharing today. We will use it in Henar's timeslot. This is the link: * https://sap.emea.pgiconnect.com/sandfuchs 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 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 Mon May 6 15:45:14 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 May 2013 15:45:14 +0200 Subject: [Fiware-wpl] Henar's presentation on "FI-WARE Blueprints" Message-ID: <5187B3EA.6030408@tid.es> Dear all, This is just to circulate Henar's presentation from today's call. 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE Blueprints.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 2554513 bytes Desc: not available URL: From jhierro at tid.es Mon May 6 16:47:57 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 06 May 2013 16:47:57 +0200 Subject: [Fiware-wpl] Fwd: FP7-ICT-285248 FI-WARE - Official Invitation to M24 Review Meeting In-Reply-To: References: Message-ID: <5187C29D.8070206@tid.es> FYI, -- Juanjo -------- Original Message -------- Subject: FP7-ICT-285248 FI-WARE - Official Invitation to M24 Review Meeting Date: Mon, 6 May 2013 13:47:14 +0000 From: To: CC: , , , , , , Dear Mr. Hierro, In accordance with Article II.23 of the contract, and as agreed with you recently, I hereby inform you of the Commission's intention to hold a review meeting of the project FP7-ICT-285248 FI-WARE in Brussels, Belgium on 12th & 13th June 2013. The meeting will take place in the premises of the European Commission in avenue de Beaulieu, 1160 Brussels Meeting rooms: 12th & 13th June 2013, avenue de Beaulieu BU25 0/S9 As agreed with you, the Commission will be assisted by the following independent experts: - Dr Renaud Di Francesco - Dr. Dominic Greenwood - Ms Man-Sze Li - Mr. Michele Marzola - Ms Irena Pavlova The objectives of the review are, in particular, to establish: * the degree of fulfillment of the project work plan for the relevant period and of the related deliverables; * the continued relevance of the objectives and breakthrough potential with respect to the scientific and industrial state of the art; * the resources planned and utilized in relation to the achieved progress, in a manner consistent with the principles of economy, efficiency and effectiveness; * the management procedures and methods of the project; * the beneficiaries' contributions and integration within the project; * the expected potential impact in scientific, technologic, economic, competitive and social terms (where relevant), and the plans for the use and dissemination of results. If you have not sent the deliverables for this review period (months 19 to 24) to the European Commission yet, please do so as soon as possible and put the experts (see cc) in copy. Please send us the draft agenda of this meeting before Friday 24th May 2013. Please send me the names of the people attending the review before Friday 7th June 2013. Should you have any questions before the meeting, please do not hesitate to contact me. Thank you for your co-operation. Best Regards, Vanessa Vanhumbeeck European Commission DG CONNECT Unit E3 - Net Innovation Tel.: +32 2 296 49 39 Email: vanessa.vanhumbeeck at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 6 18:19:17 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 May 2013 18:19:17 +0200 Subject: [Fiware-wpl] Reviewers for the Open Specs Message-ID: <5187D805.3020506@tid.es> Dear all, I was looking at the reviewers of each part of the Open Specs and checking against the assignement. Theoretically, we have the same reviewers as we chose for the 2nd rounds of reviews of the Architecture. However, Apps have taken the reviewers used in round 1 (I guess that by mistake). As I understand this is work ongoing and to minimise the disruption, I have discussed it with Thierry and they are taking Data (initial assignment of Apps - so just swapping both assignments). The rest of the chapters remain as they were. We added a note in the Open specs cockpit to make sure that each reviewing chapter is identified: * https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 In summary: * Cloud - reviewed by Apps * Data - reviewed by IoT * IoT - reviewed by Data * Apps - reviewed by I2ND * Security - reviewed by Cloud * I2ND - reviewed by Security I kindly remind you that the reviews should be 100% completed and uploaded by Wednesday. Links to the reviews to be added in column D. I do not know what's going in with the Security chapter. As they did not join the WPL/WPA call either, it is difficult to tell. 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 thorsten.sandfuchs at sap.com Mon May 6 18:19:38 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 6 May 2013 16:19:38 +0000 Subject: [Fiware-wpl] signoff D.10.5.2 Report on Validation Process including Validation with Use Case projects Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461074349@DEWDFEMB11A.global.corp.sap> Dear colleagues, I was compiling the final version of the "in time" version of the deliverable D.10.5.2: Report on Validation Process including Validation with Use Case projects. Find this attached. You can track the changes that I introduced (some small typos & mainly summarizing the rational given before in the "executive" summary), as I used "track changes". Please shortly indicate if you would VETO a submission of this deliverable to the EC before Wednesday, 08.05.2013, 14:00. Depending on the we would submit to the EC the deliverable as attached by the end of the 8th May 2013. If you veto, please indicate to us when potential contributions would be ready and issue an alternative date for submission. The major concern with the deliverable are - ...that there were only very little contributions and review comments throughout the complete process (although send multiple times around). - .... we expose internal rational and information from the resolution in the WPL/WPA meeting - ...overall there is not much "delta" between D.10.5.1 and D.10.5.2 and the former deliverable has been rejected (see 4th review report for details) Additional contributions still very much welcomed, they will be integrated prior to submission. Thanks for your support in the matter and best regards, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.10.5.2 Report on Validation Process including Validation with Use Case projects.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1714630 bytes Desc: D.10.5.2 Report on Validation Process including Validation with Use Case projects.docx URL: From jhierro at tid.es Mon May 6 18:31:00 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 06 May 2013 18:31:00 +0200 Subject: [Fiware-wpl] Fwd: Future Internet Public Private Partnership In-Reply-To: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> Message-ID: <5187DAC4.9030802@tid.es> Just for your info. Seems like not to difficult exercise, but it is also true that there are too many things on the plate ... :-( We'll try to circulate a first draft and gather your comments. Cheers, -- Juanjo -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:part1.07090603.06040805 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 1585 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche XIFI.doc Type: application/msword Size: 32768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche USE-CASES.doc Type: application/msword Size: 38912 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche FIWARE.doc Type: application/msword Size: 38400 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Cover Note FI-PPP Fiches (060513).doc.pdf Type: application/pdf Size: 34650 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche INFINITY.doc Type: application/msword Size: 26112 bytes Desc: not available URL: From thorsten.sandfuchs at sap.com Mon May 6 19:32:11 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 6 May 2013 17:32:11 +0000 Subject: [Fiware-wpl] [Fiware-wpa] Fwd: Future Internet Public Private Partnership In-Reply-To: <5187DAC4.9030802@tid.es> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> <5187DAC4.9030802@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610744EE@DEWDFEMB11A.global.corp.sap> Hi Juanjo, As most of the needed information from FI-WARE is part of the catalogue (the GE descriptions & functionalities & more), couldn't CONCORD somehow be allowed access to the catalogue in order to fill their knowledgebase? Or even tight their knowledgebase and the related questions they gather more closely to the catalogue? Thanks for your consolidation and clarifying this. /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 6. Mai 2013 18:31 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: Future Internet Public Private Partnership Just for your info. Seems like not to difficult exercise, but it is also true that there are too many things on the plate ... :-( We'll try to circulate a first draft and gather your comments. Cheers, -- Juanjo -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:image001.jpg at 01CE4A90.675C95B0] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1585 bytes Desc: image001.jpg URL: From mcp at tid.es Mon May 6 20:05:14 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 06 May 2013 20:05:14 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Fwd: Future Internet Public Private Partnership In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610744EE@DEWDFEMB11A.global.corp.sap> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> <5187DAC4.9030802@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD664610744EE@DEWDFEMB11A.global.corp.sap> Message-ID: <5187F0DA.3080801@tid.es> Hi If I understand it well, no one needs access to the catalogue as its info is mostly public. From your message I understand that you are simply suggesting that CONCORD could go to the catalogue (public info available) and fill this in for us. I clarify this as someone with no so clear ideas could not understand it properly. I clarify this because I keep on getting requests for "being able to access the catalogue", even from FI-WARE members - I do not know why people believe we have hidden parts here, all is public once approved. The only reason to have a user in the catalogue is to be able to edit a GE. Incidentally, the catalogue is obsolete and we will have to review all the info once we finish the delivery. There are about 100 edits awaiting moderation. In fact, this is held on because we need to settle for new guidelines for the catalogue. If there are volunteers to take up this part, they will be wholeheartedly welcomed. Best regards, Miguel El 06/05/2013 19:32, Sandfuchs, Thorsten escribi?: Hi Juanjo, As most of the needed information from FI-WARE is part of the catalogue (the GE descriptions & functionalities & more), couldn't CONCORD somehow be allowed access to the catalogue in order to fill their knowledgebase? Or even tight their knowledgebase and the related questions they gather more closely to the catalogue? Thanks for your consolidation and clarifying this. /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 6. Mai 2013 18:31 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: Future Internet Public Private Partnership Just for your info. Seems like not to difficult exercise, but it is also true that there are too many things on the plate ... :-( We'll try to circulate a first draft and gather your comments. Cheers, -- Juanjo -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:part27.08040704.03030005 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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 -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 1585 bytes Desc: not available URL: From jhierro at tid.es Mon May 6 23:58:48 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 06 May 2013 23:58:48 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Fwd: Future Internet Public Private Partnership In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610744EE@DEWDFEMB11A.global.corp.sap> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> <5187DAC4.9030802@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD664610744EE@DEWDFEMB11A.global.corp.sap> Message-ID: <51882798.1080808@tid.es> On 06/05/13 19:32, Sandfuchs, Thorsten wrote: Hi Juanjo, As most of the needed information from FI-WARE is part of the catalogue (the GE descriptions & functionalities & more), Yes. My plan in this respect was to just include there a link to the proper entry in the FI-WARE Catalogue. couldn't CONCORD somehow be allowed access to the catalogue in order to fill their knowledgebase? Or even tight their knowledgebase and the related questions they gather more closely to the catalogue? I believe that the EC would not agree to rely on CONCORD for filling the FI-WARE form. I'm afraid we have to deal with our part in the assignment (as you can see, other projects have been assigned also some homework). On the other hand, let's see the bottle half filled: filling the proposed form may help us to prepare contents from our review ... Thus: * We will sure have to prepare, as part of an overall project presentation, a couple of slides elaborating on major achievements ==> let's use Part D of the form to develop that part of the presentation * We should also elaborate on plans regarding the FI-WARE OIL ==> Let's structure the presentation we will have to prepare on the mater based on the points identified in Part B The question about "What is the market position in relation to competitive products? What is the competitive advantage?" should be easy to cover if we have done a decent work within the State of the Art deliverable. Cheers, -- Juanjo Thanks for your consolidation and clarifying this. /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 6. Mai 2013 18:31 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-wpa] Fwd: Future Internet Public Private Partnership Just for your info. Seems like not to difficult exercise, but it is also true that there are too many things on the plate ... :-( We'll try to circulate a first draft and gather your comments. Cheers, -- Juanjo -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:part27.03060807.08030007 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 1585 bytes Desc: not available URL: From jhierro at tid.es Tue May 7 09:00:29 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 May 2013 09:00:29 +0200 Subject: [Fiware-wpl] Draft minutes of the last FI-PPP AB meeting and related URGENT Action Points on Chapter teams and FI-WARE GEi owners Message-ID: <5188A68D.3060302@tid.es> Dear all, Last Friday, May 3rd, we celebrated the first FI-PPP AB virtual meeting involving the new projects in phase 2 of the FI-PPP. You can take a look at the minutes available at: https://docs.google.com/document/d/1_DXfn7qSY4UEidfBv3E9MhplU1wcVOzkEpWhQ_0QK-M/edit?usp=sharing There are two URGENT Action Points that we have to finalize along this week so I ask for the cooperation of the several FI-WARE chapter teams and GEi owners: * Updating spreadsheet about "FI-WARE Testbed/GEis planned usage" available at https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing * All chapter teams have to review the sheets linked "FI-WARE GEi (2nd Release) planned usage in Phase 1/2" if they haven't done so yet and send me their comments so that I can implement the proposed changes: * @I2ND was going to provide the name of FI-WARE GE and GEis (two first columns) for rows that have to be inserted for the new FI-WARE GEis in 2nd Release * @Apps was going to provide final feedback on whether it would make sense to split the package linked to Business Framework or not * Remember that this is to collect info about planned usage by UC projects, that's why it makes sense to have some rows in the sheets linked to packages of GEis / functionalities (e.g., Cloud) than as individual GEis * Please, don't edit yourself, forward feedback to me through your chapter leader * VERY IMPORTANT for FI-WARE GEi owners: Proposal on first series of webinars regarding FI-WARE GEis already available for UC projects in the Testbed (or to be available by end of May): * Deadline: Thursday May 9 EOB. * You should edit the following spreadsheet in Google docs yourself: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c&usp=sharing * You just have to provide two alternative dates during the period from May 20th until June 14th. Try to make them in two alternative weeks. * Note that these webinars are not mandatory for all FI-WARE GEis but strongly recommended for GEis/functionality that can be already demonstrated in the Testbed while in the webinars or at least presented as mockup (e.g., this might be useful for some new Cloud functions) * You can select your favorite bridge tools. How do you declare the tools you plan to use so that people will connect ? Defining a hashtag * This will be used as an Id for the bridge/webex details to be provided in sheet "Logistics details" * It will be referred from the cell associated to the row linked to your GEi and the column "Logistic details" of sheet "FI-WARE GEi (2nd Release) - series of webinars" * We advise you also to use this hashtag in posts to the @FIware twitter account during the webinar. It may be helpful to collect questions on-line so people do not necessarily interrupt you (you can watch the twitter account and then decide when to answer those questions) * UC projects will declare their interest to attend the different webinars along the week of May 17th Please pay attention to this two urgent actions. We believe that their implementation can be rather useful for a successful project review mid June. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrea.manieri at gmail.com Tue May 7 14:22:23 2013 From: andrea.manieri at gmail.com (Andrea Manieri) Date: Tue, 7 May 2013 14:22:23 +0200 Subject: [Fiware-wpl] [Fiware-administrative] FI-WARE: Amendment 4. Final GPF In-Reply-To: <77A22C1085494D48B4018F06A40DB2C72FA1AEE4@EX10-MB2-MAD.hi.inet> References: <77A22C1085494D48B4018F06A40DB2C72FA1AEE4@EX10-MB2-MAD.hi.inet> Message-ID: Dear Javier, between the xls linked and the NEF uploaded theres an unbalance of 33k on ENG. Is that a typo or there is a reason for that? Who agreed on that from ENG? thanks in advance, A. 2013/4/30 JAVIER DE PEDRO SANCHEZ > Dear all, > > After a long time working on it, there are no pending comments/objections > about changes of amendment 4. > > So, please find enclosed the final version of GPF. It is recorded on NEF > already. > > *Only the new partner NSNG1 has to sign it*. > > Please find enclosed the last version of the spreadsheet with the final > modifications too. > > > > Excel changes-effort-budget-funding: > http://forge.fi-ware.eu/docman/view.php/27/2152/FI-WARE+effort-budget-funding+-+Amendment+4+v32+%28FINAL%29.xlsx > > New GPF: > http://forge.fi-ware.eu/docman/view.php/27/2151/GPF+FI-WARE+%28285248%29+2013-04-30.pdf > > > > The final version of DoW will be sent to you as soon as Project Officer > has approved it. We are answering his comments yet. > > > > Thank you very much to all of you, for your help, contribution and time. > > > > BR > > Javier. > > *De:* subsidies-bounces at tid.es [mailto:subsidies-bounces at tid.es] *En > nombre de *JAVIER DE PEDRO SANCHEZ > *Enviado el:* lunes, 08 de abril de 2013 1:16 > *Para:* 'fiware-administrative at lists.fi-ware.eu'; > fiware-legal at lists.fi-ware.eu; 'fiware-wpl at lists.fi-ware.eu'; > fiware-wpa at lists.fi-ware.eu > *CC:* subsidies at tid.es > *Asunto:* [Subsidies] FI-WARE: Amendment 4 to be reviewed > *Importancia:* Alta > > > > Dear all, > > Thank you very much for your contributions, especially to all the WPL. > > Please find enclosed the first version of the updated DoW of the amendment > 4. > > > > Updated DoW: > http://forge.fi-ware.eu/docman/view.php/27/2066/FI-WARE-DoW-Amendment4+-+v1+%28version+date-11-04-13%29.docx(Note: WP4 is still under revision.) > > Excel changes-effort-budget-funding: > http://forge.fi-ware.eu/docman/view.php/27/2059/FI-WARE+effort-budget-funding+-+Amendment+4+v30.xlsx > > New GPF: > http://forge.fi-ware.eu/docman/view.php/27/2068/GPF+FI-WARE+%28285248%29+2013-04-07+%28DRAFT+version+-+amendment+4%29.pdf > > > > Please, I kindly ask you to review them and send to us (subsidies at tid.es) > and WPL relevant comments if needed, by April 11th, 2013 12:00h. I > suggest avoiding spam for the rest. Please only errors or very relevant > comments. > > > > The DoW has been modified accordingly with the attached spreadsheet of the > changes (version 30) that has been modified with the received comments from > you so far today. Thank you. > > NEF has been updated too, so, please find enclosed a new version of GPF > (don?t sign it until we have delivered the final version) > > > > The DoW, spreadsheet of changes, and GPF will be sent to Project Officer > on April 11th, 2013. (As you know, we are working hard in order to > approval the amendment 4 before reporting period, that begins May 1st, > 2013. > > > > Thank you for your contribution and support. > > > > BR > > Javier. > > > > > > > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-administrative mailing list > Fiware-administrative at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-administrative > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 8 07:06:08 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 08 May 2013 07:06:08 +0200 Subject: [Fiware-wpl] Kindly REMINDER ON URGENT Action Points on Chapter teams and FI-WARE GEi owners In-Reply-To: <5188A68D.3060302@tid.es> References: <5188A68D.3060302@tid.es> Message-ID: <5189DD40.5020105@tid.es> Hi all, This is just a reminder about the request to provide your input to the spreadsheet on dates for the 1st series of webinars on FI-WARE GEis in the 2nd Release. Find below the original mail where the request was issued, which included the instructions to follow. You can take a look to what the owners of the WireCloud and the PROTON CEP GEis did as a reference. Thanks for those who already provided your input. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 07/05/13 09:00, Juanjo Hierro wrote: Dear all, Last Friday, May 3rd, we celebrated the first FI-PPP AB virtual meeting involving the new projects in phase 2 of the FI-PPP. You can take a look at the minutes available at: https://docs.google.com/document/d/1_DXfn7qSY4UEidfBv3E9MhplU1wcVOzkEpWhQ_0QK-M/edit?usp=sharing There are two URGENT Action Points that we have to finalize along this week so I ask for the cooperation of the several FI-WARE chapter teams and GEi owners: * Updating spreadsheet about "FI-WARE Testbed/GEis planned usage" available at https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing * All chapter teams have to review the sheets linked "FI-WARE GEi (2nd Release) planned usage in Phase 1/2" if they haven't done so yet and send me their comments so that I can implement the proposed changes: * @I2ND was going to provide the name of FI-WARE GE and GEis (two first columns) for rows that have to be inserted for the new FI-WARE GEis in 2nd Release * @Apps was going to provide final feedback on whether it would make sense to split the package linked to Business Framework or not * Remember that this is to collect info about planned usage by UC projects, that's why it makes sense to have some rows in the sheets linked to packages of GEis / functionalities (e.g., Cloud) than as individual GEis * Please, don't edit yourself, forward feedback to me through your chapter leader * VERY IMPORTANT for FI-WARE GEi owners: Proposal on first series of webinars regarding FI-WARE GEis already available for UC projects in the Testbed (or to be available by end of May): * Deadline: Thursday May 9 EOB. * You should edit the following spreadsheet in Google docs yourself: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c&usp=sharing * You just have to provide two alternative dates during the period from May 20th until June 14th. Try to make them in two alternative weeks. * Note that these webinars are not mandatory for all FI-WARE GEis but strongly recommended for GEis/functionality that can be already demonstrated in the Testbed while in the webinars or at least presented as mockup (e.g., this might be useful for some new Cloud functions) * You can select your favorite bridge tools. How do you declare the tools you plan to use so that people will connect ? Defining a hashtag * This will be used as an Id for the bridge/webex details to be provided in sheet "Logistics details" * It will be referred from the cell associated to the row linked to your GEi and the column "Logistic details" of sheet "FI-WARE GEi (2nd Release) - series of webinars" * We advise you also to use this hashtag in posts to the @FIware twitter account during the webinar. It may be helpful to collect questions on-line so people do not necessarily interrupt you (you can watch the twitter account and then decide when to answer those questions) * UC projects will declare their interest to attend the different webinars along the week of May 17th Please pay attention to this two urgent actions. We believe that their implementation can be rather useful for a successful project review mid June. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.bareno at atosresearch.eu Thu May 9 10:28:48 2013 From: juan.bareno at atosresearch.eu (=?iso-8859-1?Q?Juan_Bare=F1o_Guerenabarrena?=) Date: Thu, 9 May 2013 10:28:48 +0200 Subject: [Fiware-wpl] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Message-ID: Dear Colleagues Please find here enclosed the status of the 3 main contribution identified actions for WP11, please try to complete them ASAP as next week, final deadline next Wednesday EOB, will be the last week to gather all the outputs and individual exploitation plans . - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o Not contributions so far: ? WP3- SAP, Thorsten, confirmed that they are working on that and that they will send their contributions ? WP4- IBM, Alex? ? WP5- TID, takeover the leadership of FT, Carlos? ? WP6- TID, Sergio confirming that he is working on that ? WP7- Telecom Italy, Pier? ? WP8- Thales, Pascal? - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May ? SAP ? Nokia Siemens Networks ? SIEMENS ? NEC ? INTEL ? Atos ? TID confirming is working on it ? Rest??? Thanks for your contribution Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From mev at tid.es Thu May 9 16:38:54 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 09 May 2013 14:38:54 +0000 Subject: [Fiware-wpl] Backlog - Items hierarchy Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8904C70B@EX10-MB2-MAD.hi.inet> Dear Partners, In order to help you to identify what backlog items have wrong names, I've extracted the current hierarchy, which makes more visual current state. I would appreciate having feedback from you - specifically having a mark to the wrong (or to the right) items. Apps (Thorsten): https://forge.fi-ware.eu/docman/view.php/27/2236/FIWARE.backlog.identifiers.apps.20130509-1552.xlsx Cloud (Alex): https://forge.fi-ware.eu/docman/view.php/27/2238/FIWARE.backlog.identifiers.cloud.20130509-1552.xlsx IoT (Thierry): https://forge.fi-ware.eu/docman/view.php/27/2234/FIWARE.backlog.identifiers.iot.20130509-1552.xlsx Data (Sergio): https://forge.fi-ware.eu/docman/view.php/27/2237/FIWARE.backlog.identifiers.data.20130509-1552.xlsx I2nd (Pier): https://forge.fi-ware.eu/docman/view.php/27/2239/FIWARE.backlog.identifiers.i2nd.20130509-1552.xlsx Security (Pascal) : https://forge.fi-ware.eu/docman/view.php/27/2235/FIWARE.backlog.identifiers.security.20130509-1552.xlsx If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri May 10 17:59:56 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 10 May 2013 17:59:56 +0200 Subject: [Fiware-wpl] Unit tests report Message-ID: <518D197C.9000605@tid.es> Dear all, Please note that the Unit test report (to be included in D.x.5.2 Unit Testing Plan and Report) is now added to the cover linked from the cockpit: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit Important to take into account: * Please do not delete it! * Gop to the cover, click on the link and fill it in. WP3 has a good example now if you need to see how this is done: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-review/index.php/Unit_Testing_Report_-_Apps * It has to be the last line in the "Structure of this Document " section. Keep it there. 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 jhierro at tid.es Mon May 13 08:28:56 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 May 2013 08:28:56 +0200 Subject: [Fiware-wpl] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis In-Reply-To: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> References: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> Message-ID: <51908828.3070908@tid.es> Hi, Please find below the response by our PO, Arian Zwegers, to my email describing the issue on IPR management of background associated to FI-WARE GEis. Essentially, our PO: 1. asks us to clearly state what is our position regarding IPRs to background associated to the FI-WARE GEis 2. would go for a solution consisting in a formal letter by Jes?s Villasante o Peter Fatelning (Head and Deputy Head of Unit, respectively) stating that the fact that contents of B.2.3.4 are refining contents of clause 41 is considered valid from a legal perspective by the EC I understand that, regarding point 1, we can clearly state that: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Unless we receive any objection by end of this week, in which case we would have to confirm the position of each partner to send a detailed report on each partner's position to the EC, I will provide this statement in a response to the mail of our PO. Regarding point 2, the solution proposed by our PO it's ok for Telef?nica, but we need to know if anyone objects. Please also express any objection by the end of this week. Please ask your legal representatives about the questions above, if you need to. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: Issue on IPR management of background associated to background of FI-WARE GEis Date: Thu, 9 May 2013 04:34:04 +0000 From: To: , CC: , , Dear Juanjo, Your explanation of the collaboration agreement is surprising. As you know, we don't know the contents. The SAP explanation is a surprise, since it always came across that - SAP did not want to be obliged to provide background to complementary beneficiaries, only to beneficiaries. I always thought that that was in the collaboration agreement, if anything at all. - (since providing background needs to be done and royalty-free) removing the paragraph still keeps the perceived conflict between clause 41 (as you mentioned on Friday, SAP perceives that the clause does not allow any background to be provided to complementary beneficiaries) and the collaboration agreement. That argument is not mentioned anymore??? The second point is also still valid in the Telefonica solution. Perhaps we should start from the beginning. What is it that the FI-WARE consortium want to say about background to complementary beneficiaries? Note that we are not interested in Telefonica's or SAP's position, only the consortium's. Depending on the answer to the question above, I would favour the last option. Peter or Jesus could write an email. "Valid from a legal perspective" can only be tested in a court of law anyway; until then, all is opinion. Best regards, Arian ________________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 07 May 2013 19:24 To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: CNECT-ICT-285248; Javier de Pedro Sanchez; LUIS GARCIA GARCIA; jhierro >> "Juan J. Hierro" Subject: Issue on IPR management of background associated to background of FI-WARE GEis Dear Arian and Ragnar, Following our conversation last friday, I would like to explain the IPR management issue we have potentially identified in the current Grant Agreement which we would like to get solved in amendment 5. In this mail, I will elaborate on: 1. The issue itself 2. The alternative solutions proposed by some of the partners in FI-WARE 3. Some thoughts about next steps trying to find how to solve the issue 1. The issue itself The issue is derived from a contradiction that has been detected by SAP on different places of the Grant Agreement (the contract). On one hand, the B.3.2.4 section on IPR included in the FI-WARE DoW (formally referred as Annex I of the Grant Agreement) states the following: [cid:part1.08040204.00010208 at tid.es] This paragraph was based on what we already stated in our proposal and was also requested by the EC. It was also aligned with clauses related to access rights to FI-WARE GE specifications and implementations in the FI-PPP Collaboration Agreement. However, special clause 41 in article 7 of the Grant Agreement states the following which apparently contradicts what was said in section B.3.2.4 of the DoW: [cid:part2.04080501.01050601 at tid.es] Besides this, there is article of the Grant Agreement that elaborates on what interpretation should prevail in case of conflicts between different parts of the Grant Agreement: [cid:part3.07080809.01050802 at tid.es] That would mean that what was stated in special clause 41 in article 7 would take precedence over what was stated in section B.3.2.4 of the DoW. It seems like it would be worth fixing this contradictions in an amendment of the DoW. 2. The alternative solutions proposed by SAP and Telefonica 2.1 Solution proposed by SAP The solution proposed by SAP is simple: drop the conflicting paragraph on section B.3.2.4. Consequently, just relying on what the Grant Agreement states, users of FI-WARE in the context of the FI-PPP could be charged for the background associated to a FI-WARE GE implementation. However, since the Collaboration Agreement states that access to background associated to FI-WARE GE implementations has to be granted royalty-free, this 'ability' to charge for background associated to a FI-WARE GE implementation would not be executable in practice unless breaking the Collaboration Agreement. Implementing the proposal, the Grant Agreement would become consistent, and the goal to keep access to both background and foreground granted royalty-free would be kept preserved through the Collaboration Agreement. 2.2. Solution proposed by Telefonica Telefonica's proposal was also simple: * Fix special clause 41 so that it reads as follows (changes marked in red): Complementary beneficiaries enjoy the rights and bear the obligations of beneficiaries with regard to Articles II.32, II.33 and II.34 of Annex II {Access Rights}. However, for complementary beneficiaries, these rights and obligations are limited to foreground and background associated only to FI-WARE GE implementations developed in FI-WARE the project. Therefore, they do not extend to background that is not part of FI-WARE GE implementations or required for them to run. Complementary beneficiaries are not members of the consortium for the purpose of this grant agreement * Clarify paragraph in section B.3.2.4 of the DoW for the avoidance of doubt: Access Rights to Foreground and Background associated to FI-WARE GE implementations needed for the execution of the FI-PPP projects and users who carry out experiments in the FI-WARE Open Innovation Lab as long as the FI-WARE project lasts, shall be deemed granted on a Royalty-Free basis. Other than in exceptional circumstances and only for Background specifically identified, no costs shall be charged for granting such Access Rights. The FI-WARE beneficiaries will not charge any such costs to the project. The whole idea would be to fix the Grant Agreement as to reflect what was the spirit of the program since the beginning, without the need to rely on the Collaboration Agreement. Note that the EC is party in the Grant Agreement but not the Collaboration Agreement, therefore this proposal allows the EC to act against any partner that doesn't grant royalty-free access to background and foreground associated to a FI-WARE GE implementation for the execution of projects in the FI-PPP. With SAP's proposal, it is up to partners signing the Collaboration Agreement to decide whether to sue or not any partner who decides to charge for background associated to a FI-WARE GE implementation. Furthermore, the proposal intends to fix any uncertainties regarding usage of background of FI-WARE GE implementations by third parties users of the FI-WARE Open Innovation Lab (could be a party running an experiment on the FI-WARE Open Innovation Lab be considered as a partner of the FI-PPP ? We believe it is not so clear, so better that we make it clear that access to background and foreground associated to FI-WARE GE implementations will be granted royalty-free to third parties users of the FI-WARE Open Innovation Lab 3. Some thoughts about next steps trying to find how to solve the issue It would be important that this issue be solved in amendment 5. Obviously, one potential alternative would be to go for one of the two proposals described in the previous point. At the current moment, the solution proposed by Telefonica was endorsed by more partners within FI-WARE (up to 14 partners). The proposal made by SAP was supported by two partners (one being SAP). The rest of partners seem to abstain. Another possibility would be that the EC makes a formal statement that the special clause 41 doesn't get into contradiction with the mentioned paragraph in section B.3.2.4 of the DoW so the DoW in practice is refining what the clause 41 was stating in a first approach. Note that such statement to be provided by the EC should be formal and valid from a legal perspective. Looking forward your response. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.png Type: image/png Size: 26719 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00002.png Type: image/png Size: 49073 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00003.png Type: image/png Size: 55743 bytes Desc: not available URL: From jhierro at tid.es Mon May 13 09:29:03 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 May 2013 09:29:03 +0200 Subject: [Fiware-wpl] URGENT action on FI-WARE GEi owners regarding webinars Message-ID: <5190963F.9060409@tid.es> Dear all, Still there are some FI-WARE GEis about which no date or timeslot has been proposed for running a webinars that UC projects in phase 2 will attend. Please note that execution of these webinars may be a relevant achievement to be reported in our 2nd year review. There may be some FI-WARE GEis for which a webinar is not feasible before actual delivery of release 2, but this is not arguable for all cases where a proposed date×lot is missing. In particular, I miss webinars on Cloud functions, at least for "Allocation of single VMs (image instances)", "Management of Blueprints" and "Allocation of Object Storage". Most probably these three may be merged in a single webinar. Please fill this before EOB today, because I will forward the available spreadsheet to the UC projects tomorrow. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From GLIKSON at il.ibm.com Mon May 13 09:35:01 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Mon, 13 May 2013 10:35:01 +0300 Subject: [Fiware-wpl] [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis In-Reply-To: <51908828.3070908@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> <51908828.3070908@tid.es> Message-ID: Dear Juanjo, Regarding point #1.. IMO, if we want to make progress faster, it might be a good idea to distinguish between Use Cases and OIL. IPR for Use Cases has been discussed many times, including Collaboration Agreement, and it sounds feasible to reach a decision there (maybe with some facilitation from EC). However, the discussion on terms and conditions for OIL only started, and it might be premature at the moment to assume a very specific approach to IPR. Clearly, it should have some sort of alignment with the spirit of the terms and conditions for Use Cases -- but there are many details which yet need to be nailed down and agreed. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-pcc at lists.fi-ware.eu" , Cc: "Theilmann, Wolfgang" , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , "fiware-ga at lists.fi-ware.eu" Date: 13/05/2013 09:27 AM Subject: [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis Sent by: fiware-pcc-bounces at lists.fi-ware.eu Hi, Please find below the response by our PO, Arian Zwegers, to my email describing the issue on IPR management of background associated to FI-WARE GEis. Essentially, our PO: 1. asks us to clearly state what is our position regarding IPRs to background associated to the FI-WARE GEis 2. would go for a solution consisting in a formal letter by Jes?s Villasante o Peter Fatelning (Head and Deputy Head of Unit, respectively) stating that the fact that contents of B.2.3.4 are refining contents of clause 41 is considered valid from a legal perspective by the EC I understand that, regarding point 1, we can clearly state that: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Unless we receive any objection by end of this week, in which case we would have to confirm the position of each partner to send a detailed report on each partner's position to the EC, I will provide this statement in a response to the mail of our PO. Regarding point 2, the solution proposed by our PO it's ok for Telef?nica, but we need to know if anyone objects. Please also express any objection by the end of this week. Please ask your legal representatives about the questions above, if you need to. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: Issue on IPR management of background associated to background of FI-WARE GEis Date: Thu, 9 May 2013 04:34:04 +0000 From: To: , CC: , , Dear Juanjo, Your explanation of the collaboration agreement is surprising. As you know, we don't know the contents. The SAP explanation is a surprise, since it always came across that - SAP did not want to be obliged to provide background to complementary beneficiaries, only to beneficiaries. I always thought that that was in the collaboration agreement, if anything at all. - (since providing background needs to be done and royalty-free) removing the paragraph still keeps the perceived conflict between clause 41 (as you mentioned on Friday, SAP perceives that the clause does not allow any background to be provided to complementary beneficiaries) and the collaboration agreement. That argument is not mentioned anymore??? The second point is also still valid in the Telefonica solution. Perhaps we should start from the beginning. What is it that the FI-WARE consortium want to say about background to complementary beneficiaries? Note that we are not interested in Telefonica's or SAP's position, only the consortium's. Depending on the answer to the question above, I would favour the last option. Peter or Jesus could write an email. "Valid from a legal perspective" can only be tested in a court of law anyway; until then, all is opinion. Best regards, Arian ________________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 07 May 2013 19:24 To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: CNECT-ICT-285248; Javier de Pedro Sanchez; LUIS GARCIA GARCIA; jhierro >> "Juan J. Hierro" Subject: Issue on IPR management of background associated to background of FI-WARE GEis Dear Arian and Ragnar, Following our conversation last friday, I would like to explain the IPR management issue we have potentially identified in the current Grant Agreement which we would like to get solved in amendment 5. In this mail, I will elaborate on: 1. The issue itself 2. The alternative solutions proposed by some of the partners in FI-WARE 3. Some thoughts about next steps trying to find how to solve the issue 1. The issue itself The issue is derived from a contradiction that has been detected by SAP on different places of the Grant Agreement (the contract). On one hand, the B.3.2.4 section on IPR included in the FI-WARE DoW (formally referred as Annex I of the Grant Agreement) states the following: [cid:part1.08040204.00010208 at tid.es] This paragraph was based on what we already stated in our proposal and was also requested by the EC. It was also aligned with clauses related to access rights to FI-WARE GE specifications and implementations in the FI-PPP Collaboration Agreement. However, special clause 41 in article 7 of the Grant Agreement states the following which apparently contradicts what was said in section B.3.2.4 of the DoW: [cid:part2.04080501.01050601 at tid.es] Besides this, there is article of the Grant Agreement that elaborates on what interpretation should prevail in case of conflicts between different parts of the Grant Agreement: [cid:part3.07080809.01050802 at tid.es] That would mean that what was stated in special clause 41 in article 7 would take precedence over what was stated in section B.3.2.4 of the DoW. It seems like it would be worth fixing this contradictions in an amendment of the DoW. 2. The alternative solutions proposed by SAP and Telefonica 2.1 Solution proposed by SAP The solution proposed by SAP is simple: drop the conflicting paragraph on section B.3.2.4. Consequently, just relying on what the Grant Agreement states, users of FI-WARE in the context of the FI-PPP could be charged for the background associated to a FI-WARE GE implementation. However, since the Collaboration Agreement states that access to background associated to FI-WARE GE implementations has to be granted royalty-free, this 'ability' to charge for background associated to a FI-WARE GE implementation would not be executable in practice unless breaking the Collaboration Agreement. Implementing the proposal, the Grant Agreement would become consistent, and the goal to keep access to both background and foreground granted royalty-free would be kept preserved through the Collaboration Agreement. 2.2. Solution proposed by Telefonica Telefonica's proposal was also simple: * Fix special clause 41 so that it reads as follows (changes marked in red): Complementary beneficiaries enjoy the rights and bear the obligations of beneficiaries with regard to Articles II.32, II.33 and II.34 of Annex II {Access Rights}. However, for complementary beneficiaries, these rights and obligations are limited to foreground and background associated only to FI-WARE GE implementations developed in FI-WARE the project. Therefore, they do not extend to background that is not part of FI-WARE GE implementations or required for them to run. Complementary beneficiaries are not members of the consortium for the purpose of this grant agreement * Clarify paragraph in section B.3.2.4 of the DoW for the avoidance of doubt: Access Rights to Foreground and Background associated to FI-WARE GE implementations needed for the execution of the FI-PPP projects and users who carry out experiments in the FI-WARE Open Innovation Lab as long as the FI-WARE project lasts, shall be deemed granted on a Royalty-Free basis. Other than in exceptional circumstances and only for Background specifically identified, no costs shall be charged for granting such Access Rights. The FI-WARE beneficiaries will not charge any such costs to the project. The whole idea would be to fix the Grant Agreement as to reflect what was the spirit of the program since the beginning, without the need to rely on the Collaboration Agreement. Note that the EC is party in the Grant Agreement but not the Collaboration Agreement, therefore this proposal allows the EC to act against any partner that doesn't grant royalty-free access to background and foreground associated to a FI-WARE GE implementation for the execution of projects in the FI-PPP. With SAP's proposal, it is up to partners signing the Collaboration Agreement to decide whether to sue or not any partner who decides to charge for background associated to a FI-WARE GE implementation. Furthermore, the proposal intends to fix any uncertainties regarding usage of background of FI-WARE GE implementations by third parties users of the FI-WARE Open Innovation Lab (could be a party running an experiment on the FI-WARE Open Innovation Lab be considered as a partner of the FI-PPP ? We believe it is not so clear, so better that we make it clear that access to background and foreground associated to FI-WARE GE implementations will be granted royalty-free to third parties users of the FI-WARE Open Innovation Lab 3. Some thoughts about next steps trying to find how to solve the issue It would be important that this issue be solved in amendment 5. Obviously, one potential alternative would be to go for one of the two proposals described in the previous point. At the current moment, the solution proposed by Telefonica was endorsed by more partners within FI-WARE (up to 14 partners). The proposal made by SAP was supported by two partners (one being SAP). The rest of partners seem to abstain. Another possibility would be that the EC makes a formal statement that the special clause 41 doesn't get into contradiction with the mentioned paragraph in section B.3.2.4 of the DoW so the DoW in practice is refining what the clause 41 was stating in a first approach. Note that such statement to be provided by the EC should be formal and valid from a legal perspective. Looking forward your response. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "ATT00001.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00002.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00003.png" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-pcc mailing list Fiware-pcc at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-pcc -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 13 09:49:11 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 May 2013 09:49:11 +0200 Subject: [Fiware-wpl] Link to minutes of meeting Message-ID: <51909AF7.9020604@tid.es> Dear all, I anticipate the link for today's call. It is under edition at this moment and the contents will be ready before the start of the call. https://docs.google.com/document/d/1_HV97Onfsme-3Ss9iFN-rWakKJNLm0kqXkTFI_wWkYk Speak to you later, 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 jhierro at tid.es Mon May 13 10:01:24 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 May 2013 10:01:24 +0200 Subject: [Fiware-wpl] [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis In-Reply-To: References: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> <51908828.3070908@tid.es> Message-ID: <51909DD4.6020202@tid.es> Dear Alex, Regarding access to users of the FI-WARE OIL, I believe that there was agreement, because it has been discussed multiple times, that access rights will be granted royalty-free as well, subject to FI-WARE OIL Terms and Conditions. I agree that we have to add the "subject to FI-WARE OIL Terms and Conditions" would need to be added, but nothing more. Therefore, my proposed revised statement would be: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Users of the FI-WARE OIL refer to third parties that will adhere to the FI-WARE OIL terms and conditions. It's ok then to you and rest of partners ? BTW, it's our intend to provide a first draft of the FI-WARE OIL Terms and Conditions this week as to start the discussion and get it finalized on time. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 13/05/13 09:35, Alex Glikson wrote: Dear Juanjo, Regarding point #1.. IMO, if we want to make progress faster, it might be a good idea to distinguish between Use Cases and OIL. IPR for Use Cases has been discussed many times, including Collaboration Agreement, and it sounds feasible to reach a decision there (maybe with some facilitation from EC). However, the discussion on terms and conditions for OIL only started, and it might be premature at the moment to assume a very specific approach to IPR. Clearly, it should have some sort of alignment with the spirit of the terms and conditions for Use Cases -- but there are many details which yet need to be nailed down and agreed. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-pcc at lists.fi-ware.eu" , Cc: "Theilmann, Wolfgang" , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , "fiware-ga at lists.fi-ware.eu" Date: 13/05/2013 09:27 AM Subject: [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis Sent by: fiware-pcc-bounces at lists.fi-ware.eu ________________________________ Hi, Please find below the response by our PO, Arian Zwegers, to my email describing the issue on IPR management of background associated to FI-WARE GEis. Essentially, our PO: 1. asks us to clearly state what is our position regarding IPRs to background associated to the FI-WARE GEis 2. would go for a solution consisting in a formal letter by Jes?s Villasante o Peter Fatelning (Head and Deputy Head of Unit, respectively) stating that the fact that contents of B.2.3.4 are refining contents of clause 41 is considered valid from a legal perspective by the EC I understand that, regarding point 1, we can clearly state that: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Unless we receive any objection by end of this week, in which case we would have to confirm the position of each partner to send a detailed report on each partner's position to the EC, I will provide this statement in a response to the mail of our PO. Regarding point 2, the solution proposed by our PO it's ok for Telef?nica, but we need to know if anyone objects. Please also express any objection by the end of this week. Please ask your legal representatives about the questions above, if you need to. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: Issue on IPR management of background associated to background of FI-WARE GEis Date: Thu, 9 May 2013 04:34:04 +0000 From: To: , CC: , , Dear Juanjo, Your explanation of the collaboration agreement is surprising. As you know, we don't know the contents. The SAP explanation is a surprise, since it always came across that - SAP did not want to be obliged to provide background to complementary beneficiaries, only to beneficiaries. I always thought that that was in the collaboration agreement, if anything at all. - (since providing background needs to be done and royalty-free) removing the paragraph still keeps the perceived conflict between clause 41 (as you mentioned on Friday, SAP perceives that the clause does not allow any background to be provided to complementary beneficiaries) and the collaboration agreement. That argument is not mentioned anymore??? The second point is also still valid in the Telefonica solution. Perhaps we should start from the beginning. What is it that the FI-WARE consortium want to say about background to complementary beneficiaries? Note that we are not interested in Telefonica's or SAP's position, only the consortium's. Depending on the answer to the question above, I would favour the last option. Peter or Jesus could write an email. "Valid from a legal perspective" can only be tested in a court of law anyway; until then, all is opinion. Best regards, Arian ________________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 07 May 2013 19:24 To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: CNECT-ICT-285248; Javier de Pedro Sanchez; LUIS GARCIA GARCIA; jhierro >> "Juan J. Hierro" Subject: Issue on IPR management of background associated to background of FI-WARE GEis Dear Arian and Ragnar, Following our conversation last friday, I would like to explain the IPR management issue we have potentially identified in the current Grant Agreement which we would like to get solved in amendment 5. In this mail, I will elaborate on: 1. The issue itself 2. The alternative solutions proposed by some of the partners in FI-WARE 3. Some thoughts about next steps trying to find how to solve the issue 1. The issue itself The issue is derived from a contradiction that has been detected by SAP on different places of the Grant Agreement (the contract). On one hand, the B.3.2.4 section on IPR included in the FI-WARE DoW (formally referred as Annex I of the Grant Agreement) states the following: [cid:part1.08040204.00010208 at tid.es] This paragraph was based on what we already stated in our proposal and was also requested by the EC. It was also aligned with clauses related to access rights to FI-WARE GE specifications and implementations in the FI-PPP Collaboration Agreement. However, special clause 41 in article 7 of the Grant Agreement states the following which apparently contradicts what was said in section B.3.2.4 of the DoW: [cid:part2.04080501.01050601 at tid.es] Besides this, there is article of the Grant Agreement that elaborates on what interpretation should prevail in case of conflicts between different parts of the Grant Agreement: [cid:part3.07080809.01050802 at tid.es] That would mean that what was stated in special clause 41 in article 7 would take precedence over what was stated in section B.3.2.4 of the DoW. It seems like it would be worth fixing this contradictions in an amendment of the DoW. 2. The alternative solutions proposed by SAP and Telefonica 2.1 Solution proposed by SAP The solution proposed by SAP is simple: drop the conflicting paragraph on section B.3.2.4. Consequently, just relying on what the Grant Agreement states, users of FI-WARE in the context of the FI-PPP could be charged for the background associated to a FI-WARE GE implementation. However, since the Collaboration Agreement states that access to background associated to FI-WARE GE implementations has to be granted royalty-free, this 'ability' to charge for background associated to a FI-WARE GE implementation would not be executable in practice unless breaking the Collaboration Agreement. Implementing the proposal, the Grant Agreement would become consistent, and the goal to keep access to both background and foreground granted royalty-free would be kept preserved through the Collaboration Agreement. 2.2. Solution proposed by Telefonica Telefonica's proposal was also simple: * Fix special clause 41 so that it reads as follows (changes marked in red): Complementary beneficiaries enjoy the rights and bear the obligations of beneficiaries with regard to Articles II.32, II.33 and II.34 of Annex II {Access Rights}. However, for complementary beneficiaries, these rights and obligations are limited to foreground and background associated only to FI-WARE GE implementations developed in FI-WARE the project. Therefore, they do not extend to background that is not part of FI-WARE GE implementations or required for them to run. Complementary beneficiaries are not members of the consortium for the purpose of this grant agreement * Clarify paragraph in section B.3.2.4 of the DoW for the avoidance of doubt: Access Rights to Foreground and Background associated to FI-WARE GE implementations needed for the execution of the FI-PPP projects and users who carry out experiments in the FI-WARE Open Innovation Lab as long as the FI-WARE project lasts, shall be deemed granted on a Royalty-Free basis. Other than in exceptional circumstances and only for Background specifically identified, no costs shall be charged for granting such Access Rights. The FI-WARE beneficiaries will not charge any such costs to the project. The whole idea would be to fix the Grant Agreement as to reflect what was the spirit of the program since the beginning, without the need to rely on the Collaboration Agreement. Note that the EC is party in the Grant Agreement but not the Collaboration Agreement, therefore this proposal allows the EC to act against any partner that doesn't grant royalty-free access to background and foreground associated to a FI-WARE GE implementation for the execution of projects in the FI-PPP. With SAP's proposal, it is up to partners signing the Collaboration Agreement to decide whether to sue or not any partner who decides to charge for background associated to a FI-WARE GE implementation. Furthermore, the proposal intends to fix any uncertainties regarding usage of background of FI-WARE GE implementations by third parties users of the FI-WARE Open Innovation Lab (could be a party running an experiment on the FI-WARE Open Innovation Lab be considered as a partner of the FI-PPP ? We believe it is not so clear, so better that we make it clear that access to background and foreground associated to FI-WARE GE implementations will be granted royalty-free to third parties users of the FI-WARE Open Innovation Lab 3. Some thoughts about next steps trying to find how to solve the issue It would be important that this issue be solved in amendment 5. Obviously, one potential alternative would be to go for one of the two proposals described in the previous point. At the current moment, the solution proposed by Telefonica was endorsed by more partners within FI-WARE (up to 14 partners). The proposal made by SAP was supported by two partners (one being SAP). The rest of partners seem to abstain. Another possibility would be that the EC makes a formal statement that the special clause 41 doesn't get into contradiction with the mentioned paragraph in section B.3.2.4 of the DoW so the DoW in practice is refining what the clause 41 was stating in a first approach. Note that such statement to be provided by the EC should be formal and valid from a legal perspective. Looking forward your response. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "ATT00001.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00002.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00003.png" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-pcc mailing list Fiware-pcc at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-pcc ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Mon May 13 17:38:29 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Mon, 13 May 2013 15:38:29 +0000 Subject: [Fiware-wpl] deliverable generation triggered on your own Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610838D5@DEWDFEMB11A.global.corp.sap> Dear colleagues, We were discussing to make this more explicit and send it again via the list (from the WPL/WPA meeting last week). Got the content, got the structure, but still you can't submit a deliverable? This will help: Imagine you (or somebody for you) introduced a "front page" for a pending deliverable, and you maintained the "Structure of the Document" section and the related content pages - what should you do then? Former status: we at SAP did spot this and eventually triggered to generate a "zip" file out of it - even on hourly basis. New: YOU are now enabled to trigger this generation on your own, using the deliverable system's "Adminparts" (as everybody in this WPL/WPA-group should have been assigned an account - otherwise please approach me via email) - this will allow more flexibility and less dependability from the schedule of others - so win-win for everybody :) There are two main triggers that you can use: Manually with entering the page-name (and selecting the wiki) as described here https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables.Adminpart#.22Printing.22_a_page Or semi-automatically with the bookmarklet, described here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables.Adminpart#Copy_a_page_Bookmarklet Mind the special paragraph on "Printing with the bookmarklet " This "printing" will work in general on all of the wikis (even on the chapter-specific wikis) - BUT you should not do this for the final submission (as the generated wiki-links in the doc files will be pointing to you chapter-private wiki!) For final deliverable submission it is wise to copy (e.g. with the copy-page functionality) all the pages either in the "fi-ware-review" wiki or the "fiware" public wiki. If you have any additional question, please let me know. Best regards, /Thorsten PS: Overall you should as well keep in mind that you can "combine" only two wiki spaces in the "structure of the document" section. The "guiding" wiki having local [[Page_name]]-links and the other one with the [https://.....index.php/Page_name Page_name]-Syntax -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon May 13 18:16:19 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 May 2013 18:16:19 +0200 Subject: [Fiware-wpl] Thales wide reporting for M13-24 - Message-ID: <18180_1368461787_519111DB_18180_8351_1_7009c8e2-ff4d-431f-8730-c1363fc111a8@THSONEA01HUB06P.one.grp> Dear WPL colleagues, Find attached to this email the Thales consolidated reporting for the period M13-M24. In it you have the reporting of Thales per each of the WPs (except WP4, WP5 and WP6 where this reporting is assumed to have been already reported to WPL by each of the Thales participants - in cc). As for other WPs please use this document has input to complete your reporting. Thanks in advance, Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - M13-M24 reporting per WP THALES 13052013.doc Type: application/msword Size: 270336 bytes Desc: FI-WARE - M13-M24 reporting per WP THALES 13052013.doc URL: From mcp at tid.es Mon May 13 18:44:22 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 May 2013 18:44:22 +0200 Subject: [Fiware-wpl] Assignment of reviewers for SOTA Message-ID: <51911866.4070501@tid.es> Dear all, The assignment of reviewers for the State of the Art document seems to be undefined - I was checking in the minutes of meeting and in all the e-mails sent so far and I cannot see it. No harm done as the reviews have not started yet. My proposal is as follows: ? Data - reviewed by Apps ? Cloud - reviewed by IoT ? Apps - reviewed by I2ND ? IoT - reviewed by Data ? I2ND - reviewed by Security ? Security - reviewed by Cloud I took the liberty of adding it to the minutes of meeting for the sake of traceability. I want a private message from each WPL telling me what people are going to review his part. WP6 does not need to send it (they already did) 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 thierry.nagellen at orange.com Tue May 14 08:39:59 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 14 May 2013 06:39:59 +0000 Subject: [Fiware-wpl] Assignment of reviewers for SOTA In-Reply-To: <51911866.4070501@tid.es> References: <51911866.4070501@tid.es> Message-ID: <18962_1368513600_5191DC40_18962_13693_1_976A65C5A08ADF49B9A8523F7F81925C0E1E37@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, For the peer review of the state of the art of Cloud, I will manage personally the peer review of the Cloud chapter. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : lundi 13 mai 2013 18:44 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Assignment of reviewers for SOTA Dear all, The assignment of reviewers for the State of the Art document seems to be undefined - I was checking in the minutes of meeting and in all the e-mails sent so far and I cannot see it. No harm done as the reviews have not started yet. My proposal is as follows: ? Data - reviewed by Apps ? Cloud - reviewed by IoT ? Apps - reviewed by I2ND ? IoT - reviewed by Data ? I2ND - reviewed by Security ? Security - reviewed by Cloud I took the liberty of adding it to the minutes of meeting for the sake of traceability. I want a private message from each WPL telling me what people are going to review his part. WP6 does not need to send it (they already did) 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue May 14 09:54:19 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 14 May 2013 09:54:19 +0200 Subject: [Fiware-wpl] Thales wide reporting for M13-24 - In-Reply-To: <18180_1368461787_519111DB_18180_8351_1_7009c8e2-ff4d-431f-8730-c1363fc111a8@THSONEA01HUB06P.one.grp> References: <18180_1368461787_519111DB_18180_8351_1_7009c8e2-ff4d-431f-8730-c1363fc111a8@THSONEA01HUB06P.one.grp> Message-ID: <5191EDAB.2010700@tid.es> Dear all, We have specifically addressed this on a number of occassions and we do not want to foster it. Please do not send a global report. You have to send each WPL their part separatedly. The WPLs have enough work already to increase their burden. Best regards, Miguel El 13/05/2013 18:16, BISSON Pascal escribi?: Dear WPL colleagues, Find attached to this email the Thales consolidated reporting for the period M13-M24. In it you have the reporting of Thales per each of the WPs (except WP4, WP5 and WP6 where this reporting is assumed to have been already reported to WPL by each of the Thales participants - in cc). As for other WPs please use this document has input to complete your reporting. Thanks in advance, Best Regards, Pascal _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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: From mcp at tid.es Tue May 14 15:03:21 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 14 May 2013 15:03:21 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Assignment of reviewers for SOTA In-Reply-To: <51911866.4070501@tid.es> References: <51911866.4070501@tid.es> Message-ID: <51923619.1040509@tid.es> Pier reminded me the agreement we reached in a previous confcall - it is not reflected on the minutes, but it was like this as far as we recall: * I2ND will review IoT * Cloud will review Data As there are no WPLs reviewing the SOTA yet, we can change the assigment with no harm done. If someone had requested something in the call, feel free to tell me. These are the only two I remember. Deadline to send me this: today EOB I will send a redistribution by the end of the day changing this. Best regards, Miguel El 13/05/2013 18:44, Miguel Carrillo escribi?: Dear all, The assignment of reviewers for the State of the Art document seems to be undefined - I was checking in the minutes of meeting and in all the e-mails sent so far and I cannot see it. No harm done as the reviews have not started yet. My proposal is as follows: ? Data - reviewed by Apps ? Cloud - reviewed by IoT ? Apps - reviewed by I2ND ? IoT - reviewed by Data ? I2ND - reviewed by Security ? Security - reviewed by Cloud I took the liberty of adding it to the minutes of meeting for the sake of traceability. I want a private message from each WPL telling me what people are going to review his part. WP6 does not need to send it (they already did) 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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 pascal.bisson at thalesgroup.com Tue May 14 15:05:59 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 14 May 2013 15:05:59 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Assignment of reviewers for SOTA In-Reply-To: <51923619.1040509@tid.es> References: <51911866.4070501@tid.es> <51923619.1040509@tid.es> Message-ID: <21741_1368536761_519236B9_21741_603_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E559F416@THSONEA01CMS04P.one.grp> BTW Peer review of Open Specs of I2ND Chapter have been appointed as per WP8 Audio conf of today. I reported them on the peer review cockpit. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 14 mai 2013 15:03 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : Re: [Fiware-wpl] [Fiware-wpa] Assignment of reviewers for SOTA Pier reminded me the agreement we reached in a previous confcall - it is not reflected on the minutes, but it was like this as far as we recall: * I2ND will review IoT * Cloud will review Data As there are no WPLs reviewing the SOTA yet, we can change the assigment with no harm done. If someone had requested something in the call, feel free to tell me. These are the only two I remember. Deadline to send me this: today EOB I will send a redistribution by the end of the day changing this. Best regards, Miguel El 13/05/2013 18:44, Miguel Carrillo escribi?: Dear all, The assignment of reviewers for the State of the Art document seems to be undefined - I was checking in the minutes of meeting and in all the e-mails sent so far and I cannot see it. No harm done as the reviews have not started yet. My proposal is as follows: ? Data - reviewed by Apps ? Cloud - reviewed by IoT ? Apps - reviewed by I2ND ? IoT - reviewed by Data ? I2ND - reviewed by Security ? Security - reviewed by Cloud I took the liberty of adding it to the minutes of meeting for the sake of traceability. I want a private message from each WPL telling me what people are going to review his part. WP6 does not need to send it (they already did) 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-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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 Tue May 14 15:54:20 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 14 May 2013 15:54:20 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Assignment of reviewers for SOTA In-Reply-To: References: <51911866.4070501@tid.es> <51923619.1040509@tid.es> Message-ID: <5192420C.6000809@tid.es> No problem. Now we have this: * I2ND will review IoT * Cloud will review Data * Data will review Cloud In the absence of more reminders I would assign the others today EOB. BR Miguel El 14/05/2013 15:46, Marti Christof (mach) escribi?: > Hi Miguel > > It was "Data will review Cloud", because I was giving this preference. But I/we (WP6) have no problem with your proposal from yesterday, which seems to be the same as for the other manuals. So from our point of view, there is no need to change it. > > Best regards, > Christof > > > Am 14.05.2013 um 15:03 schrieb Miguel Carrillo > > : > > Pier reminded me the agreement we reached in a previous confcall - it is not reflected on the minutes, but it was like this as far as we recall: > > * I2ND will review IoT > * Cloud will review Data > > As there are no WPLs reviewing the SOTA yet, we can change the assigment with no harm done. > > If someone had requested something in the call, feel free to tell me. These are the only two I remember. Deadline to send me this: today EOB > > I will send a redistribution by the end of the day changing this. > > Best regards, > > Miguel > > > El 13/05/2013 18:44, Miguel Carrillo escribi?: > Dear all, > > The assignment of reviewers for the State of the Art document seems to be undefined - I was checking in the minutes of meeting and in all the e-mails sent so far and I cannot see it. No harm done as the reviews have not started yet. > > My proposal is as follows: > ? Data - reviewed by Apps > ? Cloud - reviewed by IoT > ? Apps - reviewed by I2ND > ? IoT - reviewed by Data > ? I2ND - reviewed by Security > ? Security - reviewed by Cloud > I took the liberty of adding it to the minutes of meeting for the sake of traceability. > > I want a private message from each WPL telling me what people are going to review his part. WP6 does not need to send it (they already did) > > 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-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpa > > > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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-wpa mailing list > Fiware-wpa at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpa > -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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 Wed May 15 01:46:56 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 15 May 2013 01:46:56 +0200 Subject: [Fiware-wpl] Review process for State of the Art Message-ID: <5192CCF0.8020405@tid.es> Dear all, After collecting the inputs of the WPLs, the result is as follows: * I2ND will review IoT * Cloud will review Data * Data will review Cloud * IoT will review I2ND * Security will review Apps * Apps will review Security I will be out today. Please send your respective docs to the chapter in charge of the review of your state of the art. 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 jonas.heitto at alcatel-lucent.com Wed May 15 08:46:06 2013 From: jonas.heitto at alcatel-lucent.com (Heitto, Jonas (Jonas)) Date: Wed, 15 May 2013 06:46:06 +0000 Subject: [Fiware-wpl] [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis In-Reply-To: <51909DD4.6020202@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> <51908828.3070908@tid.es> <51909DD4.6020202@tid.es> Message-ID: <127C84805B8CDC4EBA7B1FEB557EC66A02EEFB@FR711WXCHMBA02.zeu.alcatel-lucent.com> Dear Juanjo, when addressing the PO's question relating to Background licensing to complementary beneficiaries, you suggest this response: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Users of the FI-WARE OIL refer to third parties that will adhere to the FI-WARE OIL terms and conditions. As the first sentence refers to the FI-PPP Collaboration Agreement, it might not be accurate to state in this 2nd sentence that "this" also applies to 3rd party users of the OIL. The OIL terms and conditions have to my knowledge not been determined yet, and I doubt they will duplicate those contained in the FI-PPP Collaboration Agreement. Best regards Jonas Dr. Jonas Heitto, LL.M. Senior IP Counsel ALCATEL-LUCENT INTELLECTUAL PROPERTY & STANDARDS * Tel +49 711 821 44561 * Fax +49 711 821 44587 jonas.heitto at alcatel-lucent.com Alcatel-Lucent Deutschland AG Lorenzstra?e 10 70435 Stuttgart Sitz der Gesellschaft/ Domicile of the Company: Stuttgart . Amtsgericht/ District Court Stuttgart HRB 4026 Vorsitzender des Aufsichtsrates/ Chairman of the Board of Directors: Michael Oppenhoff Vorstand/ Board of Management: Alf Henryk Wulf (Vorsitzender/ Chairman) . Hans-J?rg Daub . Dr. Rainer Fechner . Andreas Gehe Note: This e-mail message and any documents accompanying it may contain confidential and/or legally privileged information belonging to Alcatel-Lucent. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the information is strictly prohibited. If you have received this e-mail in error, please immediately notify us and delete all copies of the transmission. ________________________________ From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of JUAN JOSE HIERRO SUREDA Sent: Montag, 13. Mai 2013 10:01 To: Alex Glikson Cc: fiware-wpl at lists.fi-ware.eu; Theilmann, Wolfgang; fiware-wpa at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu; fiware-ga at lists.fi-ware.eu Subject: Re: [Fiware-wpl] [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis Dear Alex, Regarding access to users of the FI-WARE OIL, I believe that there was agreement, because it has been discussed multiple times, that access rights will be granted royalty-free as well, subject to FI-WARE OIL Terms and Conditions. I agree that we have to add the "subject to FI-WARE OIL Terms and Conditions" would need to be added, but nothing more. Therefore, my proposed revised statement would be: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Users of the FI-WARE OIL refer to third parties that will adhere to the FI-WARE OIL terms and conditions. It's ok then to you and rest of partners ? BTW, it's our intend to provide a first draft of the FI-WARE OIL Terms and Conditions this week as to start the discussion and get it finalized on time. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 13/05/13 09:35, Alex Glikson wrote: Dear Juanjo, Regarding point #1.. IMO, if we want to make progress faster, it might be a good idea to distinguish between Use Cases and OIL. IPR for Use Cases has been discussed many times, including Collaboration Agreement, and it sounds feasible to reach a decision there (maybe with some facilitation from EC). However, the discussion on terms and conditions for OIL only started, and it might be premature at the moment to assume a very specific approach to IPR. Clearly, it should have some sort of alignment with the spirit of the terms and conditions for Use Cases -- but there are many details which yet need to be nailed down and agreed. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-pcc at lists.fi-ware.eu" , Cc: "Theilmann, Wolfgang" , "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , "fiware-ga at lists.fi-ware.eu" Date: 13/05/2013 09:27 AM Subject: [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis Sent by: fiware-pcc-bounces at lists.fi-ware.eu ________________________________ Hi, Please find below the response by our PO, Arian Zwegers, to my email describing the issue on IPR management of background associated to FI-WARE GEis. Essentially, our PO: 1. asks us to clearly state what is our position regarding IPRs to background associated to the FI-WARE GEis 2. would go for a solution consisting in a formal letter by Jes?s Villasante o Peter Fatelning (Head and Deputy Head of Unit, respectively) stating that the fact that contents of B.2.3.4 are refining contents of clause 41 is considered valid from a legal perspective by the EC I understand that, regarding point 1, we can clearly state that: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Unless we receive any objection by end of this week, in which case we would have to confirm the position of each partner to send a detailed report on each partner's position to the EC, I will provide this statement in a response to the mail of our PO. Regarding point 2, the solution proposed by our PO it's ok for Telef?nica, but we need to know if anyone objects. Please also express any objection by the end of this week. Please ask your legal representatives about the questions above, if you need to. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: Issue on IPR management of background associated to background of FI-WARE GEis Date: Thu, 9 May 2013 04:34:04 +0000 From: To: , CC: , , Dear Juanjo, Your explanation of the collaboration agreement is surprising. As you know, we don't know the contents. The SAP explanation is a surprise, since it always came across that - SAP did not want to be obliged to provide background to complementary beneficiaries, only to beneficiaries. I always thought that that was in the collaboration agreement, if anything at all. - (since providing background needs to be done and royalty-free) removing the paragraph still keeps the perceived conflict between clause 41 (as you mentioned on Friday, SAP perceives that the clause does not allow any background to be provided to complementary beneficiaries) and the collaboration agreement. That argument is not mentioned anymore??? The second point is also still valid in the Telefonica solution. Perhaps we should start from the beginning. What is it that the FI-WARE consortium want to say about background to complementary beneficiaries? Note that we are not interested in Telefonica's or SAP's position, only the consortium's. Depending on the answer to the question above, I would favour the last option. Peter or Jesus could write an email. "Valid from a legal perspective" can only be tested in a court of law anyway; until then, all is opinion. Best regards, Arian ________________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 07 May 2013 19:24 To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: CNECT-ICT-285248; Javier de Pedro Sanchez; LUIS GARCIA GARCIA; jhierro >> "Juan J. Hierro" Subject: Issue on IPR management of background associated to background of FI-WARE GEis Dear Arian and Ragnar, Following our conversation last friday, I would like to explain the IPR management issue we have potentially identified in the current Grant Agreement which we would like to get solved in amendment 5. In this mail, I will elaborate on: 1. The issue itself 2. The alternative solutions proposed by some of the partners in FI-WARE 3. Some thoughts about next steps trying to find how to solve the issue 1. The issue itself The issue is derived from a contradiction that has been detected by SAP on different places of the Grant Agreement (the contract). On one hand, the B.3.2.4 section on IPR included in the FI-WARE DoW (formally referred as Annex I of the Grant Agreement) states the following: [cid:part1.08040204.00010208 at tid.es] This paragraph was based on what we already stated in our proposal and was also requested by the EC. It was also aligned with clauses related to access rights to FI-WARE GE specifications and implementations in the FI-PPP Collaboration Agreement. However, special clause 41 in article 7 of the Grant Agreement states the following which apparently contradicts what was said in section B.3.2.4 of the DoW: [cid:part2.04080501.01050601 at tid.es] Besides this, there is article of the Grant Agreement that elaborates on what interpretation should prevail in case of conflicts between different parts of the Grant Agreement: [cid:part3.07080809.01050802 at tid.es] That would mean that what was stated in special clause 41 in article 7 would take precedence over what was stated in section B.3.2.4 of the DoW. It seems like it would be worth fixing this contradictions in an amendment of the DoW. 2. The alternative solutions proposed by SAP and Telefonica 2.1 Solution proposed by SAP The solution proposed by SAP is simple: drop the conflicting paragraph on section B.3.2.4. Consequently, just relying on what the Grant Agreement states, users of FI-WARE in the context of the FI-PPP could be charged for the background associated to a FI-WARE GE implementation. However, since the Collaboration Agreement states that access to background associated to FI-WARE GE implementations has to be granted royalty-free, this 'ability' to charge for background associated to a FI-WARE GE implementation would not be executable in practice unless breaking the Collaboration Agreement. Implementing the proposal, the Grant Agreement would become consistent, and the goal to keep access to both background and foreground granted royalty-free would be kept preserved through the Collaboration Agreement. 2.2. Solution proposed by Telefonica Telefonica's proposal was also simple: * Fix special clause 41 so that it reads as follows (changes marked in red): Complementary beneficiaries enjoy the rights and bear the obligations of beneficiaries with regard to Articles II.32, II.33 and II.34 of Annex II {Access Rights}. However, for complementary beneficiaries, these rights and obligations are limited to foreground and background associated only to FI-WARE GE implementations developed in FI-WARE the project. Therefore, they do not extend to background that is not part of FI-WARE GE implementations or required for them to run. Complementary beneficiaries are not members of the consortium for the purpose of this grant agreement * Clarify paragraph in section B.3.2.4 of the DoW for the avoidance of doubt: Access Rights to Foreground and Background associated to FI-WARE GE implementations needed for the execution of the FI-PPP projects and users who carry out experiments in the FI-WARE Open Innovation Lab as long as the FI-WARE project lasts, shall be deemed granted on a Royalty-Free basis. Other than in exceptional circumstances and only for Background specifically identified, no costs shall be charged for granting such Access Rights. The FI-WARE beneficiaries will not charge any such costs to the project. The whole idea would be to fix the Grant Agreement as to reflect what was the spirit of the program since the beginning, without the need to rely on the Collaboration Agreement. Note that the EC is party in the Grant Agreement but not the Collaboration Agreement, therefore this proposal allows the EC to act against any partner that doesn't grant royalty-free access to background and foreground associated to a FI-WARE GE implementation for the execution of projects in the FI-PPP. With SAP's proposal, it is up to partners signing the Collaboration Agreement to decide whether to sue or not any partner who decides to charge for background associated to a FI-WARE GE implementation. Furthermore, the proposal intends to fix any uncertainties regarding usage of background of FI-WARE GE implementations by third parties users of the FI-WARE Open Innovation Lab (could be a party running an experiment on the FI-WARE Open Innovation Lab be considered as a partner of the FI-PPP ? We believe it is not so clear, so better that we make it clear that access to background and foreground associated to FI-WARE GE implementations will be granted royalty-free to third parties users of the FI-WARE Open Innovation Lab 3. Some thoughts about next steps trying to find how to solve the issue It would be important that this issue be solved in amendment 5. Obviously, one potential alternative would be to go for one of the two proposals described in the previous point. At the current moment, the solution proposed by Telefonica was endorsed by more partners within FI-WARE (up to 14 partners). The proposal made by SAP was supported by two partners (one being SAP). The rest of partners seem to abstain. Another possibility would be that the EC makes a formal statement that the special clause 41 doesn't get into contradiction with the mentioned paragraph in section B.3.2.4 of the DoW so the DoW in practice is refining what the clause 41 was stating in a first approach. Note that such statement to be provided by the EC should be formal and valid from a legal perspective. Looking forward your response. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "ATT00001.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00002.png" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00003.png" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-pcc mailing list Fiware-pcc at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-pcc ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed May 15 13:38:07 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 11:38:07 +0000 Subject: [Fiware-wpl] Open Specs and Checkpoint 11a Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> Dear colleagues, While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is: Checkpoint 11a Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers. Status: Not achieved Due date: Urgently needed What will be our positioning here on the next review? Did we achieve this? Analysis In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally. Decision need Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery. ? I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public. Two ways forward 1. If I got it right, this mainly focuses on open specification and the foreground IP around it. In general the statements requested potentially would be: - This Open Spec is exploitable for proprietary 3rd party products - This Open Spec is exploitable for open source 3rd party products - This Open Spec is exploitable for FI-PPP members only But IANAL and I think we would need to start compiling this firstly. SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption. Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki? Options I see: 1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it 1.B. Introduce the information on the Summary pages (linked above) 1.C. Introduce a new page which summarizes this information in "one" list 1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable) I would opt for 1.A. Next steps: - Find a consensus on what statements are requested - Decide on where to put them 2. There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?): [] FI-WARE [] FI-PPP [] planned for OIL [] 3rd party on request [] 3rd party publicly available (free to use) [] commercially exploitable (free to use, exploit and contribute) Or something more specific: [] open source with licence XXXX I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case) ? Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it? Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Wed May 15 17:23:27 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 15 May 2013 15:23:27 +0000 Subject: [Fiware-wpl] Open Specs and Checkpoint 11a In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461087CAA@DEWDFEMB11A.global.corp.sap> Some small additions to point 1 to make it more complete. Dear colleagues, While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is: Checkpoint 11a Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers. Status: Not achieved Due date: Urgently needed What will be our positioning here on the next review? Did we achieve this? Analysis In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally. Decision need Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery. ? I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public. Two ways forward 1. If I got it right, this mainly focuses on open specification and the foreground IP around it. In general the statements requested potentially would be: - This Open Spec is exploitable for FI-PPP members only - This Open Spec is exploitable for proprietary 3rd party products - This Open Spec is exploitable for open source 3rd party products - This Open Spec is exploitable for open source 3rd party products, including open source licenses that require patent pledges (see below) - If the owner of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation But IANAL and I think we would need to start compiling this firstly. SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption. Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki? Options I see: 1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it 1.B. Introduce the information on the Summary pages (linked above) 1.C. Introduce a new page which summarizes this information in "one" list 1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable) I would opt for 1.A. Next steps: - Find a consensus on what statements are requested - Decide on where to put them 2. There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?): [] FI-WARE [] FI-PPP [] planned for OIL [] 3rd party on request [] 3rd party publicly available (free to use) [] commercially exploitable (free to use, exploit and contribute) Or something more specific: [] open source with licence XXXX I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case) ? Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it? Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu May 16 00:03:32 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 May 2013 00:03:32 +0200 Subject: [Fiware-wpl] Shared spreadsheet on planned FI-WARE GEi usage by UC projects Message-ID: <51940634.6060405@tid.es> Dear all, As you know, we updated the shared spreadsheet that was capturing the plans on usage of FI-WARE GEis in Release 1 by UC projects in phase 1, as to include new sheets where UC projects in phase 1 and 2 can state their plans on usage of FI-WARE GEis in Release 2: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing Looking at the sheet titled "FI-WARE GEi (2nd Release) planned usage in Phase 2", it was intended that the column titled "Planned 1st Deployment / Next Update" would contain the next day at which a version of the FI-WARE GEi. However, some of you have annotated there the day from which it was available in Release 1. That was not the intended goal ... Date planned for the 1st deployment or next updated is intended to apply looking at the future. Please fix it. In order to be able to capture what FI-WARE GEis in release 2 may be already available in the FI-WARE Testbed, I have added the column "Available on testbed or for downloading (Y/N)": * If "Already in 1st release (Y/N)" == "Y" * "Available on testbed or for downloading (Y/N)" should be "Y" * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Already in 1st release (Y/N)" = "N" * If "Available on testbed or for downloading (Y/N)" == "Y" * it means that you have already deployed the FI-WARE GEi (after completing some of the minor releases within Release 2 of FI-WARE) * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Available on testbed or for downloading (Y/N)" == "N" * it means that you this FI-WARE GEi was planned for the second release but hasn't been deployed yet * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to deploy the FI-WARE GEi for the 1st time Hope this helps, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu May 16 09:10:38 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 May 2013 09:10:38 +0200 Subject: [Fiware-wpl] Open Specs and Checkpoint 11a In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66461087CAA@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66461087CAA@DEWDFEMB11A.global.corp.sap> Message-ID: <5194866E.7010600@tid.es> Dear Thorsten, Thanks for raising this out. I honestly believe your analysis goes far beyond what needed to be fixed here. In my honest opinion, comments from the reviewers were indeed derived from the fact that the "Legal Notice" that should accompany each Open Specification hadn't been yet finalized and was not homogeneous across GE Open Specifications. In theory, we have managed to produce a Legal Notice that, regarding IPR provisions, takes into account "the potential questions and concerns of would be implementers", therefore we should be able to justify that we cover their comment already. Also in my honest opinion, the text that SAP seems to have added is just redundant with what this new Legal Notice says. Of course, redundancy doesn't hard, but maybe will introduce confusion (how will people interpret it if that "clarification" is not present in other Open Specs ?) so I would try to avoid them or, in any case, I'll put the sentence in an "Introduction" section of the wiki page that gathers all FI-WARE GE Open Specifications. Last but not least, IPRs on FI-WARE GE Open Specifications and IPRs on FI-WARE GE implementations (GEis) should be treated separately. IPRs on FI-WARE GEis should be treated in the FI-WARE Catalogue (Terms and Conditions tab in associated entry) while IPR on FI-WARE GE Open Specifications is covered in the Legal Notice. Strictly speaking, checkpoint 11.a is covered through the Legal Notice. Most probably the reviewers are also concerned about IPRs on FI-WARE GEis so therefore we should make sure that we arrive at the review with that point also covered but not necessarely by the end of this week (though probably by the end of this month :-) The urgent point now is to fix the Legal Notice and provide the instructions to include the reference to that new Legal Notice text. I'll check where we are right now and will get back to you all. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 15/05/13 17:23, Sandfuchs, Thorsten wrote: Some small additions to point 1 to make it more complete. Dear colleagues, While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is: Checkpoint 11a Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers. Status: Not achieved Due date: Urgently needed What will be our positioning here on the next review? Did we achieve this? Analysis In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally. Decision need Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery. ? I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public. Two ways forward 1. If I got it right, this mainly focuses on open specification and the foreground IP around it. In general the statements requested potentially would be: - This Open Spec is exploitable for FI-PPP members only - This Open Spec is exploitable for proprietary 3rd party products - This Open Spec is exploitable for open source 3rd party products - This Open Spec is exploitable for open source 3rd party products, including open source licenses that require patent pledges (see below) - If the owner of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation But IANAL and I think we would need to start compiling this firstly. SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption. Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki? Options I see: 1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it 1.B. Introduce the information on the Summary pages (linked above) 1.C. Introduce a new page which summarizes this information in "one" list 1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable) I would opt for 1.A. Next steps: - Find a consensus on what statements are requested - Decide on where to put them 2. There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?): [] FI-WARE [] FI-PPP [] planned for OIL [] 3rd party on request [] 3rd party publicly available (free to use) [] commercially exploitable (free to use, exploit and contribute) Or something more specific: [] open source with licence XXXX I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case) ? Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it? Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu May 16 09:15:27 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 16 May 2013 07:15:27 +0000 Subject: [Fiware-wpl] [Fiware-wpa] Shared spreadsheet on planned FI-WARE GEi usage by UC projects In-Reply-To: <51940634.6060405@tid.es> References: <51940634.6060405@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461088824@DEWDFEMB11A.global.corp.sap> Hi Juanjo, It is currently only the marketplace and repository GE that e.g. were driving this - and we even recommended this to our partners. And we even clarified this in the WPL/WPA meeting and there was an OK for this back then. Sure we can bring this up again, but keeping the user in mind, I would then reassess the situation: I'm still very much in favor to visualize somehow and within this table that there are already a ton of enablers present _right_ _now_, which the UCs can use (as far as they are able to get the legal stuff sorted). I think the way we setup this table currently implies that there is nothing available and usable prior to the 31-Jul-13 - this potentially withholds people from starting to experiment with it - and we need people to start learning to use us and accessing us. The sooner, the better. This is why I would as well opt _against_ a column "Available on Testbed for download" - it is simply as well implying restrictiveness - _many_ of the GEs (at least in WP3) are publicly downloadable from the fi-ware forge already today. There no restriction whatsoever - some of them even allow very flexible adoption and value-creation on top of the existing implementation and allow commercial exploitation. Therefore I would propose: 1. Change F5 "Planned 1st Deployment/Next update" to something like "Available as SaaS on Testbed since/available from" 2. Change E5 "Available on testbed or for downloading" to more towards "Available for download for PP or PU" and then the options "PU", "PP", "NA" 3. Change B2 "FI-WARE Catalogue" to "FI-WARE Catalog (please visit this link to find system endpoints and downloads)" Hope this helps to clarify this and looking forward for your support in this. Best /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Donnerstag, 16. Mai 2013 00:04 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Shared spreadsheet on planned FI-WARE GEi usage by UC projects Dear all, As you know, we updated the shared spreadsheet that was capturing the plans on usage of FI-WARE GEis in Release 1 by UC projects in phase 1, as to include new sheets where UC projects in phase 1 and 2 can state their plans on usage of FI-WARE GEis in Release 2: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing Looking at the sheet titled "FI-WARE GEi (2nd Release) planned usage in Phase 2", it was intended that the column titled "Planned 1st Deployment / Next Update" would contain the next day at which a version of the FI-WARE GEi. However, some of you have annotated there the day from which it was available in Release 1. That was not the intended goal ... Date planned for the 1st deployment or next updated is intended to apply looking at the future. Please fix it. In order to be able to capture what FI-WARE GEis in release 2 may be already available in the FI-WARE Testbed, I have added the column "Available on testbed or for downloading (Y/N)": * If "Already in 1st release (Y/N)" == "Y" * "Available on testbed or for downloading (Y/N)" should be "Y" * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Already in 1st release (Y/N)" = "N" * If "Available on testbed or for downloading (Y/N)" == "Y" * it means that you have already deployed the FI-WARE GEi (after completing some of the minor releases within Release 2 of FI-WARE) * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Available on testbed or for downloading (Y/N)" == "N" * it means that you this FI-WARE GEi was planned for the second release but hasn't been deployed yet * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to deploy the FI-WARE GEi for the 1st time Hope this helps, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From burkhard.neidecker-lutz at sap.com Wed May 15 14:21:11 2013 From: burkhard.neidecker-lutz at sap.com (Neidecker-Lutz, Burkhard) Date: Wed, 15 May 2013 12:21:11 +0000 Subject: [Fiware-wpl] [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis In-Reply-To: <51908828.3070908@tid.es> References: <69AD1A9684E7184DADBE43806285BA9D06DA87B1@S-DC-ESTF03-B.net1.cec.eu.int> <51908828.3070908@tid.es> Message-ID: Dear Juanjo, dear Arian, Let me try to summarize SAPs position (which seems to be misunderstood) and what we perceive to be the consortium intent after all (and probably several of the proposed solutions will in the end be acceptable). The current DoW indeed does restrict the access to background due to overly broad language (background instead of complimentary background and the override rules between the sections). Note that these changes restricting the access was made at the request of some French consortium partners, not SAP. Despite this restriction, the Collaboration Agreement indeed *does* give the intended royalty free access to all parties to the Collaboration Agreement. The current DoW alone as currently worded, does not. What the consortium *agreement* seems to be is that access to all foreground and background *in GE implementations* (i.e. complementary foreground and background) is always royalty free for all parties to the FI-PPP agreements and while there is an ongoing discussion around this (because that is *not* covered by any of the current agreements is that the parties in the OIL will also be granted royalty free access despite them not being party to any of the FI-PPP contracts. Note that SAPs position on this was that: a) Access to the GE *specifications* needs to be not only open and royalty free but also needs a patent grant allowing conforming open source implementations that are guaranteed not to violate any essential patents of the FI-PPP members (something the SAP owned GE specs are licensed under) b) The GE *implementations* of SAP are all released under a very permissive open source license (BSD) to ensure both royalty free access to the FI-PPP, OIL users or anybody else. c) Where SAP needs to use SAP background IP *outside a GE implementation* (i.e. outside complimentary background) we can maintain control over that. It was point c) that actually prompted our current attempt to clarify the language of the warring provisions of the different paragraphs in the FI-Ware DoW, certainly no desire to charge for any GEs inside or outside the FI-PPP. Burkhard Neidecker-Lutz Fellow | Next Business and Technology AR. Mgmt AG SAP AG | Vincenz-Priessnitz-Strasse 1 | 76131 Karlsruhe | Germany T +49 6227 7-52533 | M +49 160-8896858 | E burkhard.neidecker-lutz at sap.com www.sap.com Please consider the impact on the environment before printing this e-mail. 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. From: fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Montag, 13. Mai 2013 08:29 To: fiware-pcc at lists.fi-ware.eu Cc: Theilmann, Wolfgang; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-ga at lists.fi-ware.eu Subject: [Fiware-pcc] Fwd: RE: Issue on IPR management of background associated to background of FI-WARE GEis Hi, Please find below the response by our PO, Arian Zwegers, to my email describing the issue on IPR management of background associated to FI-WARE GEis. Essentially, our PO: 1. asks us to clearly state what is our position regarding IPRs to background associated to the FI-WARE GEis 2. would go for a solution consisting in a formal letter by Jes?s Villasante o Peter Fatelning (Head and Deputy Head of Unit, respectively) stating that the fact that contents of B.2.3.4 are refining contents of clause 41 is considered valid from a legal perspective by the EC I understand that, regarding point 1, we can clearly state that: The commitment by FI-WARE partners is to grant royalty-free access to background and foreground associated to the FI-WARE GEis for the execution of FI-PPP projects (including FI-WARE), in line with what is stated in the Collaboration Agreement. Note that this not only applies to partners of FI-PPP projects but also third party users of the FI-WARE OIL (since offering FI-WARE GEis royalty-free to them is essential for the execution of FI-WARE and the FI-PPP program). Unless we receive any objection by end of this week, in which case we would have to confirm the position of each partner to send a detailed report on each partner's position to the EC, I will provide this statement in a response to the mail of our PO. Regarding point 2, the solution proposed by our PO it's ok for Telef?nica, but we need to know if anyone objects. Please also express any objection by the end of this week. Please ask your legal representatives about the questions above, if you need to. Best regards, -- Juanjo -------- Original Message -------- Subject: RE: Issue on IPR management of background associated to background of FI-WARE GEis Date: Thu, 9 May 2013 04:34:04 +0000 From: To: , CC: , , Dear Juanjo, Your explanation of the collaboration agreement is surprising. As you know, we don't know the contents. The SAP explanation is a surprise, since it always came across that - SAP did not want to be obliged to provide background to complementary beneficiaries, only to beneficiaries. I always thought that that was in the collaboration agreement, if anything at all. - (since providing background needs to be done and royalty-free) removing the paragraph still keeps the perceived conflict between clause 41 (as you mentioned on Friday, SAP perceives that the clause does not allow any background to be provided to complementary beneficiaries) and the collaboration agreement. That argument is not mentioned anymore??? The second point is also still valid in the Telefonica solution. Perhaps we should start from the beginning. What is it that the FI-WARE consortium want to say about background to complementary beneficiaries? Note that we are not interested in Telefonica's or SAP's position, only the consortium's. Depending on the answer to the question above, I would favour the last option. Peter or Jesus could write an email. "Valid from a legal perspective" can only be tested in a court of law anyway; until then, all is opinion. Best regards, Arian ________________________________________ From: Juanjo Hierro [jhierro at tid.es] Sent: 07 May 2013 19:24 To: ZWEGERS Arian (CNECT); BERGSTROM Ragnar (CNECT) Cc: CNECT-ICT-285248; Javier de Pedro Sanchez; LUIS GARCIA GARCIA; jhierro >> "Juan J. Hierro" Subject: Issue on IPR management of background associated to background of FI-WARE GEis Dear Arian and Ragnar, Following our conversation last friday, I would like to explain the IPR management issue we have potentially identified in the current Grant Agreement which we would like to get solved in amendment 5. In this mail, I will elaborate on: 1. The issue itself 2. The alternative solutions proposed by some of the partners in FI-WARE 3. Some thoughts about next steps trying to find how to solve the issue 1. The issue itself The issue is derived from a contradiction that has been detected by SAP on different places of the Grant Agreement (the contract). On one hand, the B.3.2.4 section on IPR included in the FI-WARE DoW (formally referred as Annex I of the Grant Agreement) states the following: [cid:part1.08040204.00010208 at tid.es] This paragraph was based on what we already stated in our proposal and was also requested by the EC. It was also aligned with clauses related to access rights to FI-WARE GE specifications and implementations in the FI-PPP Collaboration Agreement. However, special clause 41 in article 7 of the Grant Agreement states the following which apparently contradicts what was said in section B.3.2.4 of the DoW: [cid:part2.04080501.01050601 at tid.es] Besides this, there is article of the Grant Agreement that elaborates on what interpretation should prevail in case of conflicts between different parts of the Grant Agreement: [cid:part3.07080809.01050802 at tid.es] That would mean that what was stated in special clause 41 in article 7 would take precedence over what was stated in section B.3.2.4 of the DoW. It seems like it would be worth fixing this contradictions in an amendment of the DoW. 2. The alternative solutions proposed by SAP and Telefonica 2.1 Solution proposed by SAP The solution proposed by SAP is simple: drop the conflicting paragraph on section B.3.2.4. Consequently, just relying on what the Grant Agreement states, users of FI-WARE in the context of the FI-PPP could be charged for the background associated to a FI-WARE GE implementation. However, since the Collaboration Agreement states that access to background associated to FI-WARE GE implementations has to be granted royalty-free, this 'ability' to charge for background associated to a FI-WARE GE implementation would not be executable in practice unless breaking the Collaboration Agreement. Implementing the proposal, the Grant Agreement would become consistent, and the goal to keep access to both background and foreground granted royalty-free would be kept preserved through the Collaboration Agreement. 2.2. Solution proposed by Telefonica Telefonica's proposal was also simple: * Fix special clause 41 so that it reads as follows (changes marked in red): Complementary beneficiaries enjoy the rights and bear the obligations of beneficiaries with regard to Articles II.32, II.33 and II.34 of Annex II {Access Rights}. However, for complementary beneficiaries, these rights and obligations are limited to foreground and background associated only to FI-WARE GE implementations developed in FI-WARE the project. Therefore, they do not extend to background that is not part of FI-WARE GE implementations or required for them to run. Complementary beneficiaries are not members of the consortium for the purpose of this grant agreement * Clarify paragraph in section B.3.2.4 of the DoW for the avoidance of doubt: Access Rights to Foreground and Background associated to FI-WARE GE implementations needed for the execution of the FI-PPP projects and users who carry out experiments in the FI-WARE Open Innovation Lab as long as the FI-WARE project lasts, shall be deemed granted on a Royalty-Free basis. Other than in exceptional circumstances and only for Background specifically identified, no costs shall be charged for granting such Access Rights. The FI-WARE beneficiaries will not charge any such costs to the project. The whole idea would be to fix the Grant Agreement as to reflect what was the spirit of the program since the beginning, without the need to rely on the Collaboration Agreement. Note that the EC is party in the Grant Agreement but not the Collaboration Agreement, therefore this proposal allows the EC to act against any partner that doesn't grant royalty-free access to background and foreground associated to a FI-WARE GE implementation for the execution of projects in the FI-PPP. With SAP's proposal, it is up to partners signing the Collaboration Agreement to decide whether to sue or not any partner who decides to charge for background associated to a FI-WARE GE implementation. Furthermore, the proposal intends to fix any uncertainties regarding usage of background of FI-WARE GE implementations by third parties users of the FI-WARE Open Innovation Lab (could be a party running an experiment on the FI-WARE Open Innovation Lab be considered as a partner of the FI-PPP ? We believe it is not so clear, so better that we make it clear that access to background and foreground associated to FI-WARE GE implementations will be granted royalty-free to third parties users of the FI-WARE Open Innovation Lab 3. Some thoughts about next steps trying to find how to solve the issue It would be important that this issue be solved in amendment 5. Obviously, one potential alternative would be to go for one of the two proposals described in the previous point. At the current moment, the solution proposed by Telefonica was endorsed by more partners within FI-WARE (up to 14 partners). The proposal made by SAP was supported by two partners (one being SAP). The rest of partners seem to abstain. Another possibility would be that the EC makes a formal statement that the special clause 41 doesn't get into contradiction with the mentioned paragraph in section B.3.2.4 of the DoW so the DoW in practice is refining what the clause 41 was stating in a first approach. Note that such statement to be provided by the EC should be formal and valid from a legal perspective. Looking forward your response. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu May 16 09:30:23 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 16 May 2013 07:30:23 +0000 Subject: [Fiware-wpl] Open Specs and Checkpoint 11a In-Reply-To: <5194866E.7010600@tid.es> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66461087CAA@DEWDFEMB11A.global.corp.sap> <5194866E.7010600@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646108888F@DEWDFEMB11A.global.corp.sap> Hi Juanjo, I was as well reassessing it another time, if I got it right, I think the reviewers refer somewhere to "human readable" information and not legal texts, therefore the pointer to the Legal Notice does not apply as you said. The checkpoint itself mentions "IPR provisions of the individual GE Open Specifications" - therefore the focus is on the Spec and not the Implementation. I do agree that we have to separate the two and I would agree that we should firstly focus on the Open Spec in order to address this checkpoint. Yes SAP was already trying to provide this "human readable" format in the first version and this is an attempt that others would adopt it. We even improved this now and added on the open specs/architecture description level: This Open Specification is exploitable for proprietary 3rd party products and is exploitable for open source 3rd party products, including open source licenses that require patent pledges. If the owner (SAP) of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation. We think this addresses exactly this checkpoint: it allows an would-be implementor to understand that he is in a safe harbor concerning implementations based on this Open Spec. For the software part I'm with you that there is already something to submit it - without being blocked by this IPR question. Currently we are gathering at least the information on public availability of binaries in the "FI-WARE SW Release report's. And in the end as part of the catalogue. Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. Mai 2013 09:11 To: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: Open Specs and Checkpoint 11a Dear Thorsten, Thanks for raising this out. I honestly believe your analysis goes far beyond what needed to be fixed here. In my honest opinion, comments from the reviewers were indeed derived from the fact that the "Legal Notice" that should accompany each Open Specification hadn't been yet finalized and was not homogeneous across GE Open Specifications. In theory, we have managed to produce a Legal Notice that, regarding IPR provisions, takes into account "the potential questions and concerns of would be implementers", therefore we should be able to justify that we cover their comment already. Also in my honest opinion, the text that SAP seems to have added is just redundant with what this new Legal Notice says. Of course, redundancy doesn't hard, but maybe will introduce confusion (how will people interpret it if that "clarification" is not present in other Open Specs ?) so I would try to avoid them or, in any case, I'll put the sentence in an "Introduction" section of the wiki page that gathers all FI-WARE GE Open Specifications. Last but not least, IPRs on FI-WARE GE Open Specifications and IPRs on FI-WARE GE implementations (GEis) should be treated separately. IPRs on FI-WARE GEis should be treated in the FI-WARE Catalogue (Terms and Conditions tab in associated entry) while IPR on FI-WARE GE Open Specifications is covered in the Legal Notice. Strictly speaking, checkpoint 11.a is covered through the Legal Notice. Most probably the reviewers are also concerned about IPRs on FI-WARE GEis so therefore we should make sure that we arrive at the review with that point also covered but not necessarely by the end of this week (though probably by the end of this month :-) The urgent point now is to fix the Legal Notice and provide the instructions to include the reference to that new Legal Notice text. I'll check where we are right now and will get back to you all. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 15/05/13 17:23, Sandfuchs, Thorsten wrote: Some small additions to point 1 to make it more complete. Dear colleagues, While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is: Checkpoint 11a Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers. Status: Not achieved Due date: Urgently needed What will be our positioning here on the next review? Did we achieve this? Analysis In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally. Decision need Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery. => I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public. Two ways forward 1. If I got it right, this mainly focuses on open specification and the foreground IP around it. In general the statements requested potentially would be: - This Open Spec is exploitable for FI-PPP members only - This Open Spec is exploitable for proprietary 3rd party products - This Open Spec is exploitable for open source 3rd party products - This Open Spec is exploitable for open source 3rd party products, including open source licenses that require patent pledges (see below) - If the owner of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation But IANAL and I think we would need to start compiling this firstly. SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption. Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki? Options I see: 1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it 1.B. Introduce the information on the Summary pages (linked above) 1.C. Introduce a new page which summarizes this information in "one" list 1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable) I would opt for 1.A. Next steps: - Find a consensus on what statements are requested - Decide on where to put them 2. There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?): [] FI-WARE [] FI-PPP [] planned for OIL [] 3rd party on request [] 3rd party publicly available (free to use) [] commercially exploitable (free to use, exploit and contribute) Or something more specific: [] open source with licence XXXX I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case) => Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it? Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 May 16 10:25:35 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 16 May 2013 10:25:35 +0200 Subject: [Fiware-wpl] Open Specs and Checkpoint 11a In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646108888F@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD664610871DA@DEWDFEMB11A.global.corp.sap> <2981E9D6242FCF47ADC9B5DBA5DFD66461087CAA@DEWDFEMB11A.global.corp.sap> <5194866E.7010600@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646108888F@DEWDFEMB11A.global.corp.sap> Message-ID: <519497FF.2070004@tid.es> I'm fine with providing a "human readable" version. However, I believe it MUST NOT be part of the text in the spec itself. Maybe a general text in an introductory section of the Summary of FI-WARE GE Open Specifications. Besides, you have to take into account that there were two valid Legal Notices that were defined. One elaborates on essential patents, while the other doesn't distinguish between essential or non-essential patents. Last but not least, I believe that the text proposed by SAP could be improved. On: This Open Specification is exploitable for proprietary 3rd party products and is exploitable for open source 3rd party products, including open source licenses that require patent pledges. I believe that the text proposed by SAP is still not so "human readable" :-) I would go for something that many users of standard specs would understand: Any party can implement products that are compliant with a FI-WARE GE Open Specification without paying royalties to their copyright owners for any patent that may be considered essential to the specification. This would also apply for the implementation of products to be distributed under open source licenses that require patent pledges. On: If the owner (SAP) of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation. I believe that patent are deemed granted to "someone" not "an implementation". On the other hand, mentioning "royalty-free" would make things more clear. Bottom line, I would go for the following slight variation: If the copyright owner of a FI-WARE GE Open Specification holds a patent that is essential to create a conforming implementation of that specification (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted royalty-free to any party for the implementation of the specification. Since we have to cope with the two valid Legal Notices, so I would finally add: The above applies to FI-WARE GE Open Specifications bound to the . If the FI-WARE GE Open Specification is bound to the then the above applies for any kind of patent owned by the copyright owner that can be used in implementations of the specification. Best regards, -- Juanjo On 16/05/13 09:30, Sandfuchs, Thorsten wrote: Hi Juanjo, I was as well reassessing it another time, if I got it right, I think the reviewers refer somewhere to "human readable" information and not legal texts, therefore the pointer to the Legal Notice does not apply as you said. The checkpoint itself mentions "IPR provisions of the individual GE Open Specifications" - therefore the focus is on the Spec and not the Implementation. I do agree that we have to separate the two and I would agree that we should firstly focus on the Open Spec in order to address this checkpoint. Yes SAP was already trying to provide this "human readable" format in the first version and this is an attempt that others would adopt it. We even improved this now and added on the open specs/architecture description level: This Open Specification is exploitable for proprietary 3rd party products and is exploitable for open source 3rd party products, including open source licenses that require patent pledges. If the owner (SAP) of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation. We think this addresses exactly this checkpoint: it allows an would-be implementor to understand that he is in a safe harbor concerning implementations based on this Open Spec. For the software part I'm with you that there is already something to submit it - without being blocked by this IPR question. Currently we are gathering at least the information on public availability of binaries in the "FI-WARE SW Release report's. And in the end as part of the catalogue. Best, /Thorsten From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 16. Mai 2013 09:11 To: Sandfuchs, Thorsten Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: Open Specs and Checkpoint 11a Dear Thorsten, Thanks for raising this out. I honestly believe your analysis goes far beyond what needed to be fixed here. In my honest opinion, comments from the reviewers were indeed derived from the fact that the "Legal Notice" that should accompany each Open Specification hadn't been yet finalized and was not homogeneous across GE Open Specifications. In theory, we have managed to produce a Legal Notice that, regarding IPR provisions, takes into account "the potential questions and concerns of would be implementers", therefore we should be able to justify that we cover their comment already. Also in my honest opinion, the text that SAP seems to have added is just redundant with what this new Legal Notice says. Of course, redundancy doesn't hard, but maybe will introduce confusion (how will people interpret it if that "clarification" is not present in other Open Specs ?) so I would try to avoid them or, in any case, I'll put the sentence in an "Introduction" section of the wiki page that gathers all FI-WARE GE Open Specifications. Last but not least, IPRs on FI-WARE GE Open Specifications and IPRs on FI-WARE GE implementations (GEis) should be treated separately. IPRs on FI-WARE GEis should be treated in the FI-WARE Catalogue (Terms and Conditions tab in associated entry) while IPR on FI-WARE GE Open Specifications is covered in the Legal Notice. Strictly speaking, checkpoint 11.a is covered through the Legal Notice. Most probably the reviewers are also concerned about IPRs on FI-WARE GEis so therefore we should make sure that we arrive at the review with that point also covered but not necessarely by the end of this week (though probably by the end of this month :-) The urgent point now is to fix the Legal Notice and provide the instructions to include the reference to that new Legal Notice text. I'll check where we are right now and will get back to you all. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 15/05/13 17:23, Sandfuchs, Thorsten wrote: Some small additions to point 1 to make it more complete. Dear colleagues, While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is: Checkpoint 11a Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers. Status: Not achieved Due date: Urgently needed What will be our positioning here on the next review? Did we achieve this? Analysis In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally. Decision need Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery. => I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public. Two ways forward 1. If I got it right, this mainly focuses on open specification and the foreground IP around it. In general the statements requested potentially would be: - This Open Spec is exploitable for FI-PPP members only - This Open Spec is exploitable for proprietary 3rd party products - This Open Spec is exploitable for open source 3rd party products - This Open Spec is exploitable for open source 3rd party products, including open source licenses that require patent pledges (see below) - If the owner of this GE spec holds a patent that is essential to create a conforming implementation of the GE spec (i.e. it is impossible to write a conforming implementation without violating the patent) then a license to that patent is deemed granted to the implementation But IANAL and I think we would need to start compiling this firstly. SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption. Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki? Options I see: 1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it 1.B. Introduce the information on the Summary pages (linked above) 1.C. Introduce a new page which summarizes this information in "one" list 1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable) I would opt for 1.A. Next steps: - Find a consensus on what statements are requested - Decide on where to put them 2. There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?): [] FI-WARE [] FI-PPP [] planned for OIL [] 3rd party on request [] 3rd party publicly available (free to use) [] commercially exploitable (free to use, exploit and contribute) Or something more specific: [] open source with licence XXXX I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case) => Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it? Best, /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu May 16 12:29:38 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 16 May 2013 12:29:38 +0200 Subject: [Fiware-wpl] FI-WARE WP8 Open Specs (Now uploaded) Message-ID: <6626_1368700181_5194B515_6626_4718_1_189c890e-aaca-444b-b3e0-197110163172@THSONEA01HUB04P.one.grp> Dear All, This just to let you know that I generated D8.1.2 (Open Specs GE V2 + Open API) and provided the link through the Open Specs Peer Review cockpit we all shared. As such peer review from WP4 can now start. Apologize for the delay (especially to Alex and his team who was awaiting to perform the peer review). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri May 17 09:33:08 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 17 May 2013 09:33:08 +0200 Subject: [Fiware-wpl] R: Shared spreadsheet on planned FI-WARE GEi usage by UC projects In-Reply-To: <51940634.6060405@tid.es> References: <51940634.6060405@tid.es> Message-ID: Dear Juanjo, I remind you that the rows concerning the I2ND GEis are not yet in this table, nor in the webinar schedule sheet. Can you please add them so that we can complete the entries as required. If Alex agrees, I would also suggest moving the Cloud Proxy from Cloud to the newly created I2ND section. 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: gioved? 16 maggio 2013 00:04 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Shared spreadsheet on planned FI-WARE GEi usage by UC projects Dear all, As you know, we updated the shared spreadsheet that was capturing the plans on usage of FI-WARE GEis in Release 1 by UC projects in phase 1, as to include new sheets where UC projects in phase 1 and 2 can state their plans on usage of FI-WARE GEis in Release 2: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E&usp=sharing Looking at the sheet titled "FI-WARE GEi (2nd Release) planned usage in Phase 2", it was intended that the column titled "Planned 1st Deployment / Next Update" would contain the next day at which a version of the FI-WARE GEi. However, some of you have annotated there the day from which it was available in Release 1. That was not the intended goal ... Date planned for the 1st deployment or next updated is intended to apply looking at the future. Please fix it. In order to be able to capture what FI-WARE GEis in release 2 may be already available in the FI-WARE Testbed, I have added the column "Available on testbed or for downloading (Y/N)": * If "Already in 1st release (Y/N)" == "Y" * "Available on testbed or for downloading (Y/N)" should be "Y" * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Already in 1st release (Y/N)" = "N" * If "Available on testbed or for downloading (Y/N)" == "Y" * it means that you have already deployed the FI-WARE GEi (after completing some of the minor releases within Release 2 of FI-WARE) * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to update the FI-WARE GEi * If "Available on testbed or for downloading (Y/N)" == "N" * it means that you this FI-WARE GEi was planned for the second release but hasn't been deployed yet * "Planned 1st Deployment / Next Update" should contain the future date at which you plan to deploy the FI-WARE GEi for the 1st time Hope this helps, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jhierro at tid.es Sun May 19 23:48:33 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 19 May 2013 23:48:33 +0200 Subject: [Fiware-wpl] Joint WPLs/WPAs confcalls tomorrow Message-ID: <519948B1.3030604@tid.es> Hi all, Tomorrow I have been invited to a lunch with several representatives of the Spanish Ministry of Industry and Economy as well as Peter Fatelning and other relevant public authorities that will attend a rather relevant event on the FI-PPP here in Spain. Therefore, I'm afraid that I have to cancell the second part (afternoon session) of our joint WPLs/WPAs confcall. The topic we planned to address (follow-up of our discussion on the OAuth2.0-based framework for Access Control to APIs) will be postponed for May 27th. The morning session remains and will be chaired by Miguel. I take advantage of this email to tell you that I plan to send a number of important messages along tomorrow. Please stay tunned because they will require that you take some actions. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Mon May 20 10:38:46 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 20 May 2013 10:38:46 +0200 Subject: [Fiware-wpl] Link to today's minutes of meeting Message-ID: <5199E116.9040308@tid.es> Dear all, I am still editing them. But here it goes in case there are delays with the email. * https://docs.google.com/document/d/1HtuHO5BVH9kfYSWV2zA196u-DGqFRiCGo-OoT9K7wUw/edit?pli=1#heading=h.o7t2a46xt0om Talk to you later 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 stefano.depanfilis at eng.it Mon May 20 11:02:23 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Mon, 20 May 2013 11:02:23 +0200 Subject: [Fiware-wpl] Link to today's minutes of meeting In-Reply-To: <5199E116.9040308@tid.es> References: <5199E116.9040308@tid.es> Message-ID: dear Miguel and all, unfortunately today i cannot attend. anyway you and thorsten can in case answer toand listen about issues concerning wp10. we will have our phc tomorrow morning as scheduled. thank you in advance stefano 2013/5/20 Miguel Carrillo > Dear all, > > I am still editing them. But here it goes in case there are delays with > the email. > > > - > https://docs.google.com/document/d/1HtuHO5BVH9kfYSWV2zA196u-DGqFRiCGo-OoT9K7wUw/edit?pli=1#heading=h.o7t2a46xt0om > > > Talk to you later > > Miguel > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: mcp at tid.es > > Follow FI-WARE on the net > > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: http://twitter.com/Fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 20 12:54:05 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 20 May 2013 12:54:05 +0200 Subject: [Fiware-wpl] IMPORTANT: Delivery of Architecture chapter by chapter Message-ID: <519A00CD.5060308@tid.es> Dear all, There is an important item on today's agenda I forgot to mention. The Architecture document has a word file per chapter so we can deliver chapter by chapter easily. Although it was initially agreed to deliver all together, given the situation and particularly the dates of the review, we think that we it is critical to deliver chapter by chapter as they become available. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From pascal.bisson at thalesgroup.com Mon May 20 14:02:26 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 20 May 2013 14:02:26 +0200 Subject: [Fiware-wpl] IMPORTANT: Delivery of Architecture chapter by chapter In-Reply-To: <519A00CD.5060308@tid.es> References: <519A00CD.5060308@tid.es> Message-ID: <27094_1369051349_519A10D5_27094_3562_1_819e9245-06c9-41c3-b2ed-082448f4c920@THSONEA01HUB01P.one.grp> Possibly Yes but I remain convinced it remains better to get it delivered as a whole. Even more in that case we are only awaiting from Juanjo's review from the Chapter's part not yet reviewed. Meaning we should not be that far to make it happen BR Pascal -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: lundi 20 mai 2013 12:54 ??: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet?: [Fiware-wpl] IMPORTANT: Delivery of Architecture chapter by chapter Dear all, There is an important item on today's agenda I forgot to mention. The Architecture document has a word file per chapter so we can deliver chapter by chapter easily. Although it was initially agreed to deliver all together, given the situation and particularly the dates of the review, we think that we it is critical to deliver chapter by chapter as they become available. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From mcp at tid.es Mon May 20 15:04:33 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 20 May 2013 15:04:33 +0200 Subject: [Fiware-wpl] IMPORTANT: Delivery of Architecture chapter by chapter In-Reply-To: <27094_1369051349_519A10D5_27094_3562_1_819e9245-06c9-41c3-b2ed-082448f4c920@THSONEA01HUB01P.one.grp> References: <519A00CD.5060308@tid.es> <27094_1369051349_519A10D5_27094_3562_1_819e9245-06c9-41c3-b2ed-082448f4c920@THSONEA01HUB01P.one.grp> Message-ID: <519A1F61.7060503@tid.es> Dear Pascal, Reviewings means further iterating and different degrees of quality could result in different timescales. We need to deliver as soon as we can and as much as we can. Best regards, miguel El 20/05/2013 14:02, BISSON Pascal escribi?: > Possibly Yes but I remain convinced it remains better to get it delivered as a whole. > Even more in that case we are only awaiting from Juanjo's review from the Chapter's part not yet reviewed. Meaning we should not be that far to make it happen > > BR > Pascal > > > -----Message d'origine----- > De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo > Envoy? : lundi 20 mai 2013 12:54 > ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu > Objet : [Fiware-wpl] IMPORTANT: Delivery of Architecture chapter by chapter > > Dear all, > > There is an important item on today's agenda I forgot to mention. > > The Architecture document has a word file per chapter so we can deliver chapter by chapter easily. Although it was initially agreed to deliver all together, given the situation and particularly the dates of the review, we think that we it is critical to deliver chapter by chapter as they become available. > > Best regards, > > Miguel > > -- > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telef?nica Distrito Telef?nica > _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 483 26 77 > > e-mail: mcp at tid.es > > Follow FI-WARE on the net > > Website: http://www.fi-ware.eu > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > Twitter: http://twitter.com/Fiware > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > ---------------------------------------------------------------------- > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl > . > -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Tue May 21 06:17:56 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 21 May 2013 06:17:56 +0200 Subject: [Fiware-wpl] VERY IMPORTANT: LEGAL NOTICE to attach to FI-WARE Open Specifications In-Reply-To: <51950D41.3000708@tid.es> References: <51950D41.3000708@tid.es> Message-ID: <519AF574.6020009@tid.es> Dear all, Just to keep you informed about the progress of this matter and keep you aware in case people from your legal department approach you with questions. After quite a long period, we believe at TID that we have managed to finalize the wording of the Legal Notices that will accompany the FI-WARE GE Open Specifications. Please find enclosed the consolidated drafts, reflecting all gathered comments from the different legal representatives, if you are interested. A very final round has been setup to get these legal notices definitively closed by next Wednesday May 22nd. In the meantime, we have created two new pages on the wiki that will contain the final wording for the two valid Legal Notices by EOB May 22nd and currently contain the current draft (which we consider 95% of probabilities final and certainly more polished than the versions being used so far): * FI-WARE Open Specification Legal Notice (essential patents license): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) * FI-WARE Open Specification Legal Notice (implicit patents license): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) It is our intention to start submitting the Open Specifications deliverable immediately after May 22nd (of course, each WP once it has already finished all the planned peer-reviews). As I have said, that day we expect that the wording of the Legal Notices will be actually finished so we will update the contents of the wiki pages above accordingly. We highly encourage you to update the wiki pages associated to your specifications in the meantime, as to point to one of the above legal notices wiki pages, replacing the current links to interim legal notices used up to now. That way, when we start submitting the deliverables, they several FI-WARE GE Open Specifications will be referring to any of the two wiki pages above. Which of the two Legal Notices to use is up to you. For the sake of your information, IBM and Telefonica will use the legal notice with implicit patents license while, as far as I understand, SAP is going to use the legal notice with essential patents license. Telef?nica recommends to use the legal notice with implicit patents license but, again, feel free to use the one that is more suitable to you. We will deal with deliverables this way but after May 22nd and before closing FI-WARE Release 2 (end of June) we will see how to comply with one of the requirements from some of the attorneys that have to do with making the copyright holders and the text of the Legal Notice become an integral part of the FI-WARE Open Specifications (or at least create a dedicated wiki page associated to a personalized Legal Notice per specification with the name of the specification, the name of the copyright holders and the text of the Legal Notice). We will provide detailed instructions about the changes to implement at wiki level to cope with this requirement. But, again, this can wait until after we have submitted the deliverables, which is the very urgent thing now. Last but not least, one detail: as you would be able to see in the attached emails, some attorneys of some partners have surprisingly raised the question about the public and royalty-free nature of FI-WARE GE Open Specifications ... This, I have to confess, has astonished me in the first place because this is a very fundamental principle in FI-WARE that was not only stated in the DoW but also in the Consortium Agreement. Therefore, I have replied to those attorneys that this was not a matter of discussion and if they have any doubt in that respect, they should approach their technical/management representative so that they solve whatever doubt they may have. Just wanted to let you know this in case that they approach you on the matter. As you can see, I have clearly stated that we will have to inform the EC about those who won't comply with this basic rule so they have to balance the consequences. Best regards, -- Juanjo -------- Original Message -------- Subject: Re: [Fiware-legal] FI-WARE LEGAL NOTICE Date: Thu, 16 May 2013 18:45:53 +0200 From: Juanjo Hierro To: LUIS GARCIA GARCIA , "fiware-legal at lists.fi-ware.eu" On 16/05/13 15:48, LUIS GARCIA GARCIA wrote: Dear all, ... No modifications have been introduced affecting the Royalty free character of this Legal Notice. This RF nature is in the essence of this project and in accordance with the FI-WARE Grant Agreement and Consortium Agreement and cannot be a matter of discussion. It's a very fundamental principle of this project that was agreed even at proposal preparation time (i.e., 3 years ago). Hi all, I would like to emphasize this last statement by Luis. Actually, breaking the public and royalty-free nature of FI-WARE GE Open Specifications would be considered a infringement of the FI-WARE contract (Grant Agreement) and would certainly be considered in the approval or rejection of reported costs. Note that neither Luis nor me intend to respond any message from anyone questioning this. It's absolute out of questioning and we will not spend any more minute on the matter and we wouldn't recommend that you spend any minute either. I'm pretty sure that the technical and business managers from every partner are fully aware of this very basic principle in FI-WARE, so if you still have some doubts, you just need to double-check with them. I also want to emphasize that the deadline of Wednesday 22nd is absolutely final. We intend to close the wording of the Legal Notices at that date unless someone finds a big mistake/issue everyone would agree that has to be fixed (honestly, I can't guess which). Actually, we believe that the current draft is perfectly valid and complete. Of course, the path towards absolute perfection never ends, but precisely because we will be able to evolve contents of the Legal Notice in the future if found necessary, it's time to close NOW a first valid version of the Legal Notices that we can attach to the FI-WARE Open Specifications. Immediately afterwards, we will provide instructions as to attach one of the two defined Legal Notices to each of the FI-WARE GE Open Specifications. We will then define a deadline for binding the FI-WARE GE Open Specifications to any of the defined Legal Notices after which we will report to the EC what are the FI-WARE GE Open Specifications for which such request has not been met. The corresponding Copyright Holders will have to measure the consequences of not complying this request by the coordinator and the subsequent reaction by the EC. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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-legal mailing list Fiware-legal at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-legal -------------- next part -------------- An embedded message was scrubbed... From: LUIS GARCIA GARCIA Subject: FI-WARE LEGAL NOTICE Date: Thu, 16 May 2013 15:48:45 +0200 Size: 118688 URL: From jhierro at tid.es Tue May 21 07:30:47 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 21 May 2013 07:30:47 +0200 Subject: [Fiware-wpl] URGENT Action points derived from architecture session on OAuth 2.0-based Access Control framework in FI-WARE Message-ID: <519B0687.60403@tid.es> Hi all, This mail is a reminder of the several APs identified during our architect session on Monday 13th about the OAuth 2.0-based Access Control framework in FI-WARE. The first point had to do with making the GCP IdM GEi API documentation available to all partners. You can now download the GCP IdM GEi API documentation from the following link at the FI-WARE project. Note that access to this link is private, so you will have to login in your FusionForge account (and be registered as member of the FI-WARE project): https://forge.fi-ware.eu/docman/view.php/7/2369/GCP+API+documentation_v0-2.pdf I have also attached to this email an updated version of the presentation that describes the architecture we are aiming to implement. As a follow-up of the technical session we had on Monday May 13th, I would like to remind the following action points: * @UPM to carry out a revision of the RESTful API specification provided in the referred GCP documentation in order to determine if it will allow them to finish developments under way regarding a FI-WARE OIL portal for management of user accounts and user attributes. I remind to UPM that they should also rely on the available APIs from the Access Control GE to deal with definition of roles and access policies from the same portal. * @UPM and @DT: UPM to provide detailed links to the places in the standard OAuth specs where they believe that the complete OAuth 2.0 RESTFul API to be supported by the IdM GE are specified. DT to respond to UPM so that the whole issue about existence of a complete standard RESTful API is clarified. Don't hesitate to carry out this discussion within the fiware-api-cross mailing list so that we can all follow-up the discussions * @Thales to also carry out a revision of the GCP same documentation and design a proposal to present in our next follow-up confcall about how to manage updates of some attributes of users which may imply rejection of some request tokens (check last slide in the attached presentation) * @UPM to confirm whether all the information is available for them to finalize development of the Proxy * @NSN to confirm whether they plan to support a RESTful API in compliance with the GCP RESTful specification. (note: NSN couldn't attend the confcall on May 13th but this issue was raised: there should be a single IdM GE RESTful API specification so either NSN is happy to implement the one provided by DT or both have to agree on one they will both support) You all are called to attend afternoon session during the next joint WPLs/WPAs follow-up confcall (14:30 to 16:00) on May 27th where we will have the opportunity to follow-up all the above APs (we will start the session addressing these points so that you don't need to stay the whole session if we finish earlier, but please book the whole slot in your agendas). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Security 13-05-14.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 187888 bytes Desc: not available URL: From mcp at tid.es Tue May 21 11:32:37 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 21 May 2013 11:32:37 +0200 Subject: [Fiware-wpl] Tips for deliverable generation Message-ID: <519B3F35.3070302@tid.es> Dear all, Pascal was asking for this so let us provide it. We have been working with this for a while, so you must be familiar with it by now. You know that the cockpit is here: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit You have edited covers in the past (there are also general instructions at the end of the cockpit. For specific support for the tool, go to Thorsten and for other matters, come to me. I added a link to the Unit Test Report at the end of the Unit Test manual. Please got there and: * Ensure that there is a row per Unit Test * Ensure that you use short URLs: "wiki-fi.ware.eu/..." * Ensure that you put the result of the tests (supposedly, each GE owner has passed the Unit Testing plan prior to delivery). I guess that each entry will typically have a "Y". This is something that each WPL has to fill in. The idea for the deliverables is: 1) Generate the cover linked from the cockpit 2) Trigger the generation of the deliverable (message by Thorsten with instructions attached) 3) Once you have the doc generated, follow the instructions at the bottom of the cockpit 4) Once you have the document in word format, do not forget to add the TOC, the header and the footer. You can take the header and footer from a good example: * https://forge.fi-ware.eu/docman/view.php/7/2341/D.6.4.2+FI-WARE+User+and+Programmers+Guide.docx This is what you need to create the header/footer (my Word is in Spanish on my PC but you can guess) [cid:part1.05010508.09070904 at tid.es] I choose "blank header"and then do "copy paste" from the example doc. Remember to tick the "1st page different" (this check is only visible when editing the header or footer) [cid:part2.03070101.07020809 at tid.es] Before delivering, check that there are no links to fi-ware-private in the doc. 5) When the doc is ready for delivery, create the pdf file. Upload both, word version and pdf version to FI-WARE -> Docs -> FI-WARE deliverables -> Release 2(public documentation) -> chapter name Make the word version private always - if the manual itself is private in nature, you can make private the pdf file private as well. 6) Send me a message with the links and the info for delivery. At this point we can send it to the EC 7) Update the cockpit with the delivery date, a link to the original file created by the deliverable generation tool and a link to the final deliverable. Just go there and see what we did for the WPs already delivered. IMPORTANT: use the public wiki pages to generate the Architecture and the Open Specs. The wiki must be updated by now. All changes from now on on both should go directly to the public wiki. Hope this clarifies the doubts that still remained there. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 79337 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 56187 bytes Desc: not available URL: -------------- next part -------------- An embedded message was scrubbed... From: "Sandfuchs, Thorsten" Subject: deliverable generation triggered on your own Date: Mon, 13 May 2013 15:38:29 +0000 Size: 18633 URL: From jhierro at tid.es Wed May 22 01:31:56 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 01:31:56 +0200 Subject: [Fiware-wpl] =?windows-1252?q?Fwd=3A_Observations_regarding_rejec?= =?windows-1252?q?tion_of_deliverable_=93D10=2E5=2E1_Report_on_Validation_?= =?windows-1252?q?Process_including_Validation_with_Use_Case_projects=94?= In-Reply-To: <519C03C3.5060408@tid.es> References: <519C03C3.5060408@tid.es> Message-ID: <519C03EC.6080804@tid.es> FYI -------- Original Message -------- Subject: Observations regarding rejection of deliverable ?D10.5.1 Report on Validation Process including Validation with Use Case projects? Date: Wed, 22 May 2013 01:31:15 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu CC: Fatelnig Peter , EC - Jes?s Villasante , Miguel Carrillo , stefano de panfilis , "jhierro >> \"Juan J. Hierro\"" , "subsidies at tid.es" Dear Arian, Ragnar, Peter, Jesus, After careful analysis of the report associated to the M18 review, we would like to submit to you the following observations regarding comments provided in the review report that you provided as justification of the rejection of deliverable ?D10.5.1 Report on Validation Process including Validation with Use Case projects?. Please take them into account in the final assessment of this deliverable during the 2nd year review. Your feedback, of course, is more than welcome. We will be also happy to provide any further clarifications if needed. We leave to you the decision on how/when to share this with the project reviewers. Thanks and best regards, -- Juanjo Hierro 1. ?The validation process described in the document is generally well thought and detailed; however, it has been devised without sufficient consideration of the FI-WARE project and FI-WARE Releases.? Observation by FI-WARE: - The validation process was initially proposed by FI-WARE to the Use-Case projects. This approach was discussed and agreed by representatives of the Use-Case projects within the Architecture Board. - The architecture board recognized the reviewers comments in M6 and FI-WARE proposed a subsequent ?initial feedback survey? to cater for short-term feedback cycle and to allow feedback on the first Testbed instances (therefore being closely aligned with the FI-WARE project and FI-WARE release ? major FI-WARE release end of M17/30.09.2012 - survey send out: Di 02.10.2012 01:03). - Subsequent and proposed validation schedules are by definition of the process to be aligned within the involved stakeholders: FI-WARE and use case projects. There is no defined schedule by the validation process, therefore alignment towards subsequent FI-WARE Release is part of the involved partners and not of the process. The process allows maximum flexibility. 2. ?The validation approach is also considered insufficient, in view of what is envisaged in the DoW in supporting Use Case projects on deployment, execution and validation of the conceptual prototypes in respect of the available GEs. ? Observation by FI-WARE: - FI-WARE Testbed Team including the GE instances owner gave continuous support to the UC projects in the access and use of the GEis of interest. Due to this continuous support FI-WARE provided dedicated webinars for each chapter and sometimes more for the same chapter in order to cover different aspects on different GEis. This continuous support welcomed by the UCs (it can be seen in the answers of the "first initial survey") is not explicitly reported in the deliverable as we intend it more to describe the validation itself rather than the support provided. - FI-WARE agrees with the reviewers comments that the validation process as outlined and executed within the FI-WARE project within Task 10.5 does not completely follow the description of the task in the DoW ? but again as this was decided and discussed within the highest possible technology board (the FI-WARE architecture board) this deviation from the DoW is in line with all related parties and the deviation in general should be acceptable. As changes to the DoW take time, these changes in the process could only be reflected as part of the upcoming amendment 4 to the DoW. 3. ?According to the deliverable, the design phase of FI-WARE incorporates requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters. As the link between Use Case requirements and the actual content of the individual chapters is not readily traceable, this has a significant impact on the validation, and the extent to which the Agile best practices have been embraced. [..]The available questionnaire is presently basic, and is a long way off from providing the validation required to enrich the characterization of Use Case scenarios (as a contribution towards Phase 2 trials) and generally boost GE uptake. Observation by FI-WARE - The D.10.5.1 deliverables states: ?The design phase occurs taking care also requirements that have been successfully communicated from the Use Cases Projects to the FI-WARE chapters.? ? which should imply a given fact that requirements actually were formally communicated and does not imply that these requirements can be tracked throughout the whole process in the current way, agile is implemented and ?lived?. The deliverable in this point may have wrongly lead to the assumption that there were successfully communicated requirements, which the validation team itself couldn?t really judge or imply. As the deliverable outlined later there is no tight linkage between defined requirements and the features provided. - Secondly the decision taken by the Architecture board was bond to the fact that validation based on all relevant features/epics provided by the FI-WARE project was not reasonable for the given amount of time and expected efforts - FI-WARE features do comprise of more than 900 features (please bear in mind that only limited resources were foreseen in the DoW to actually execute on the validation task towards the core platform). - Finally it was decided by the Architecture board that a ?validation questionnaire? to be provided by FI-WARE has to cater for validation and mainly will be based upon questions related to ?validation context? and ?generic enablers? and not based on features and requirements. The use case projects therefore were only bound to give the scenarios and their descriptions to FI-WARE and not their requirements. - Enrichment of the characterization of use case scenarios and boost of GE uptake was not in scope of the validation approach as implied in the reviewer statement. - As the amendment 4 foresees there will be again a reiteration of the validation process towards the phase 2 projects and their trials, where further changes in the process are currently being considered by the architecture board, potentially leading to a tighter linkage between requirements and GEs which might lead to a better validation. E.g. it is foreseen that use case projects will input their requirements to GE-based trackers and not to a common fi-ware tracker any more. One of the feedbacks received by the use case projects almost speaks for itself: As a general impression, the validation questions were quite helpful to provide feedback. The only issue we faced in our case was due to the fact that we evaluated the GEs per prototype component and not for specific scenarios. 4. Additionally, how testing and evaluation would be conducted in relation to the non-functional capabilities that are listed for the first releases in the Technical Roadmap is yet to be described. Observation by FI-WARE - Checking non-functional capabilities was again reiterated within the architecture board and no common consensus could be found towards the validation process. This recommendation will be taken into the next discussion which will redefine the process for FIWARE v2 (but will not be part of the D.10.5.2 deliverable as for time constraints: phase 2 projects did not start to redefine the validation process and potentially won?t do so for the next two month ) ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 May 22 12:35:55 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 12:35:55 +0200 Subject: [Fiware-wpl] IMPORTANT REMINDER: Future Internet Public Private Partnership In-Reply-To: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> References: <04BE08B5CBC6F54AB4B342A70C56474F0230AB6F@S-DC-ESTE04-B.net1.cec.eu.int> Message-ID: <519C9F8B.5080604@tid.es> Hi all, TID didn't want to push that much this AP before because we thought that was better to stay focused on the deliverables that were due end of April as to make sure they get delivered in reasonable time. But now it seems like we are starting to be in a good shape, so that I believe it is now time to push and remind you the AP. I have already got an extension of the deadline in the case of FI-WARE until end of this month due to the fact that we in FI-WARE have many things on the table. That should allow us to deliver a resoable reesponse. Instructions to follow were gathered already in the pre-minutes of the WPLs/WPAs but I'm copy them here for your convenience: The EC has formally asked us to fill a form summarizing achievements of FI-WARE. See mail forwarded on 06/05/13, subject: "Future Internet Public Private Partnership". A shared version of the form for FI-WARE is available at: https://docs.google.com/document/d/1f4lBauFu2Tn1Fs6TiWi19_fI-b1-zyRAlUE3z_-Elvg/edit Juanjo: our take regarding Part A would be to make references to contents of entries in the FI-WARE Catalogue, which indeed should contain complete info answering questions about: * Description of the Generic Enabler * What does this Generic Enabler offer in terms of functionality * What potential use could it have in the development of services and applications Actually, the standard sections on the catalogue titled "What you get" and "Open Specification Reference" should answer the two first questions, while the standard section titled "Why to get it" should answer the third one. We should be able to answer the question on "What is the market position in relation to competitive products? What is the competitive advantage?" based on the contents of the State of the Art deliverable that it is supposed to be under way. AP on all WPLs/WPAs to provide entries associated to FI-WARE GEis of Release 1 in their chapter. Use the google docs provided above for that purpose. AP on all WPLs/WPAs to review contents of the State of the Art deliverable so that it provides clear answers to the questions formulated on benchmarking, not only regarding FI-WARE GEis in Relase 1 but FI-WARE GEis in Release 2 (this will pave the way for an update of the form once Release 2 is delivered) Juanjo: ATOS may try to provide the initial draft to Part C.2) AP on all WPLs/WPAs to provide input to the different sections and review contents of entries in the catalogue to ensure that they can be used for answer to Part A. Deadline: Monday 20, 11:00am. Telefonica will be drafting an answer for the rest of the form. Please keep an eye on what is being drafted in the shared google doc and provide inputs/comments. We shall prepare an update of the form once Release 2 is delivered and entries linked to new FI-WARE GEis are registered in the FI-WARE Catalogue. Try to get this APs done by mid next week. I will be off-line for a while due because travelling to Berlin but supposed to be connected from 17:30 on or so. I will be able to answer any questions you may have by them. Regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Future Internet Public Private Partnership Date: Mon, 6 May 2013 16:18:46 +0000 From: To: , , , , , , , , , , , , , , , , , , CC: , , , , , Dear Project Coordinators, Please find attached a note and the corresponding forms regarding the achievements of the FI-PPP. Regards, Jesus Jesus VILLASANTE Head of Unit [cid:part2.06010704.07010404 at tid.es] European Commission DG Communication Networks, Content and Technology E3: Net Innovation BU25 3/81 B-1049 Brussels/Belgium +32 2 29-63521 Jesus.Villasante at ec.europa.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 1585 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche XIFI.doc Type: application/msword Size: 32768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche USE-CASES.doc Type: application/msword Size: 38912 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche FIWARE.doc Type: application/msword Size: 38400 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Cover Note FI-PPP Fiches (060513).doc.pdf Type: application/pdf Size: 34650 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-PPP Fiche INFINITY.doc Type: application/msword Size: 26112 bytes Desc: not available URL: From mcp at tid.es Wed May 22 13:55:27 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 May 2013 13:55:27 +0200 Subject: [Fiware-wpl] Spam filtering Message-ID: <519CB22F.50903@tid.es> Dear all, This is to briefly report on the status of the spam filters. We have had quite a bit of spamming on some lists in the past weeks (namely, fiware general, wpl, wpa, support and iot). We implemented some filtering that initially seemed to work but now we are back to square one receiving tons of mail every day and we need to see what to do. As I am moderating 4 out of 5, most of you did not even perceive this. Those in IoT have seen just a fifth of the spam in the project. The idea is that we have been testing a mechanism to block this. The support list has been running ok with this for more than a week now and we are goingto extend it to the aforementioned list today if everything goes well. While this is under tests in fiware general, wpl, wpa, support and iot) the moderator of the list will receive a warning each time a message is blocked. After a few days, if all passes the tests ad see that the filtering is good, we will disable this temporary mechanism and we will delete spam not sending any warnings to anyone. Once finished, we will extend it to all the lists of the project. 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 mcp at tid.es Wed May 22 14:27:08 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 May 2013 14:27:08 +0200 Subject: [Fiware-wpl] URGENT: Delivery of Open specs TODAY Message-ID: <519CB99C.1040807@tid.es> Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: [Fiware-pcc] VERY IMPORTANT: LEGAL NOTICE to attach to FI-WARE Open Specifications Date: Tue, 21 May 2013 06:17:56 +0200 Size: 147096 URL: From pierangelo.garino at telecomitalia.it Wed May 22 15:07:38 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 22 May 2013 15:07:38 +0200 Subject: [Fiware-wpl] R: Spam filtering Message-ID: <0d5bf212rvcdpcemv6cyeq2c.1369228058349@email.android.com> Dear Miguel, Please extend the filtering to I2ND list as well. Although I have to manage less than 10 spamming messages per day, removing that at all would be very welcome. Thanks and BR Pier Inviato da Samsung Mobile -------- Original message -------- Subject: [Fiware-wpl] Spam filtering From: Miguel Carrillo To: "fiware-wpa at lists.fi-ware.eu" ,"fiware-wpl at lists.fi-ware.eu" CC: Dear all, This is to briefly report on the status of the spam filters. We have had quite a bit of spamming on some lists in the past weeks (namely, fiware general, wpl, wpa, support and iot). We implemented some filtering that initially seemed to work but now we are back to square one receiving tons of mail every day and we need to see what to do. As I am moderating 4 out of 5, most of you did not even perceive this. Those in IoT have seen just a fifth of the spam in the project. The idea is that we have been testing a mechanism to block this. The support list has been running ok with this for more than a week now and we are goingto extend it to the aforementioned list today if everything goes well. While this is under tests in fiware general, wpl, wpa, support and iot) the moderator of the list will receive a warning each time a message is blocked. After a few days, if all passes the tests ad see that the filtering is good, we will disable this temporary mechanism and we will delete spam not sending any warnings to anyone. Once finished, we will extend it to all the lists of the project. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl 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 pascal.bisson at thalesgroup.com Wed May 22 15:09:53 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 15:09:53 +0200 Subject: [Fiware-wpl] URGENT: Delivery of Open specs TODAY In-Reply-To: <519CB99C.1040807@tid.es> References: <519CB99C.1040807@tid.es> Message-ID: <20567_1369228199_519CC3A7_20567_4164_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E57C0A3A@THSONEA01CMS04P.one.grp> Dear Miguel, Dear Colleagues, To complete Miguel's email and to be precise we (as Security Chapter) can't deliver because we haven't yet received all peer reviews of our Chapter's open-specs. Still some are missing although a few. As for Open-specs review we got. The comments have been addressed (at least the ones on which we could have agreement). Meaning with help of Cloud Chapter delivering us the latest review we could also deliver. So please Miguel/Juanjo consider this. Even more than it would be better for all to deliver altogether. Even more if it is only a matter of a day if not hours. I put in cc the Security team for information. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 22 mai 2013 14:27 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 thorsten.sandfuchs at sap.com Wed May 22 15:20:14 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Wed, 22 May 2013 13:20:14 +0000 Subject: [Fiware-wpl] [Fiware-wpa] URGENT: Delivery of Open specs TODAY In-Reply-To: <519CB99C.1040807@tid.es> References: <519CB99C.1040807@tid.es> Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> Hi Miguel, As I was browsing the other chapters, I found that many chapters still link to "PRELIMINARY" API pages - which we in WP3 did completely dissolve within this release. I vaguely remember that there were actions to do so (otherwise we most probably wouldn't have it implemented) - but I couldn't find the right mail in a quick search. Can somebody comment: did we do something wrong here? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Mittwoch, 22. Mai 2013 14:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 May 22 16:46:35 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 May 2013 16:46:35 +0200 Subject: [Fiware-wpl] [Fiware-wpa] URGENT: Delivery of Open specs TODAY In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> References: <519CB99C.1040807@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> Message-ID: <519CDA4B.2020202@tid.es> Hi I miraculously manged to contact Juanjo (on a plane most of the afternoon) In general, the "PRELIMINARY" should not appear on the pages for R2 anymore. In R1 it was acceptable but our maturity level should be high enough not to have this anymore. There is just one possible exception: when we expect deep changes in R3 (not for most of the cases) So yes, this should be renamed. And renaming mediawiki pages is something that can be done in minutes as you know. Important: please send me word and pdf files. Do not forget the source (document in word format) Best regards, Miguel El 22/05/2013 15:20, Sandfuchs, Thorsten escribi?: Hi Miguel, As I was browsing the other chapters, I found that many chapters still link to "PRELIMINARY" API pages - which we in WP3 did completely dissolve within this release. I vaguely remember that there were actions to do so (otherwise we most probably wouldn't have it implemented) - but I couldn't find the right mail in a quick search. Can somebody comment: did we do something wrong here? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Mittwoch, 22. Mai 2013 14:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 pierangelo.garino at telecomitalia.it Wed May 22 17:08:28 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 22 May 2013 17:08:28 +0200 Subject: [Fiware-wpl] R: [Fiware-wpa] URGENT: Delivery of Open specs TODAY In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> References: <519CB99C.1040807@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> Message-ID: Dear Thorsten and Miguel, Let me provide a comment on this issue, as some of the I2ND API Open Specs are named PRELIMINARY. The release of those API specs reflects the situation of r2.2, and some update might be necessary to include the specs belonging to Features implemented in r2.3. More in general, each of the I2ND GEs is grouping a wide set of Features, which are made available in R2 but will be updated towards R3 as well. We considered therefore better keeping the PRELIMINARY as it was originally defined in the guidelines for R1. My opinion is that, although changing the name is matter of minutes (and I'm back to PC so I could do it quickly enough now), we shouldn't change those names for I2ND Specs. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: mercoled? 22 maggio 2013 15:20 A: Miguel Carrillo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] URGENT: Delivery of Open specs TODAY Hi Miguel, As I was browsing the other chapters, I found that many chapters still link to "PRELIMINARY" API pages - which we in WP3 did completely dissolve within this release. I vaguely remember that there were actions to do so (otherwise we most probably wouldn't have it implemented) - but I couldn't find the right mail in a quick search. Can somebody comment: did we do something wrong here? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Mittwoch, 22. Mai 2013 14:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 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 Wed May 22 17:13:12 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 May 2013 17:13:12 +0200 Subject: [Fiware-wpl] R: [Fiware-wpa] URGENT: Delivery of Open specs TODAY In-Reply-To: References: <519CB99C.1040807@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646108F9F7@DEWDFEMB11A.global.corp.sap> Message-ID: <519CE088.4090404@tid.es> Dear Pier, As I said, if there are plans for radical changes, the "preliminary " can stay. It should disappear by default but it looks like as though in your case it will have to stay. The others should delete it unless there's a good reason to keep it. BR Miguel El 22/05/2013 17:08, Garino Pierangelo escribi?: Dear Thorsten and Miguel, Let me provide a comment on this issue, as some of the I2ND API Open Specs are named PRELIMINARY. The release of those API specs reflects the situation of r2.2, and some update might be necessary to include the specs belonging to Features implemented in r2.3. More in general, each of the I2ND GEs is grouping a wide set of Features, which are made available in R2 but will be updated towards R3 as well. We considered therefore better keeping the PRELIMINARY as it was originally defined in the guidelines for R1. My opinion is that, although changing the name is matter of minutes (and I'm back to PC so I could do it quickly enough now), we shouldn't change those names for I2ND Specs. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: mercoled? 22 maggio 2013 15:20 A: Miguel Carrillo; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] URGENT: Delivery of Open specs TODAY Hi Miguel, As I was browsing the other chapters, I found that many chapters still link to "PRELIMINARY" API pages - which we in WP3 did completely dissolve within this release. I vaguely remember that there were actions to do so (otherwise we most probably wouldn't have it implemented) - but I couldn't find the right mail in a quick search. Can somebody comment: did we do something wrong here? Best, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Mittwoch, 22. Mai 2013 14:27 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 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. -- ---------------------------------------------------------------------- _/ _/_/ 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 Wed May 22 19:01:22 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 19:01:22 +0200 Subject: [Fiware-wpl] Creation of new WP as a result of incorporating beneficiaries of the 2nd Open Call Message-ID: <519CF9E2.3020002@tid.es> Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 22 19:01:36 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 19:01:36 +0200 Subject: [Fiware-wpl] Creation of new WP as a result of incorporating beneficiaries of the 2nd Open Call Message-ID: <519CF9F0.8030502@tid.es> Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Wed May 22 19:54:03 2013 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Wed, 22 May 2013 19:54:03 +0200 Subject: [Fiware-wpl] [Fiware-ga] Creation of new WP as a result of incorporatingbeneficiaries of the 2nd Open Call In-Reply-To: <1369242099348.391269701@boxbe> References: <1369242099348.391269701@boxbe> Message-ID: dear juanjo, i basically do agree, but for the sake of better consistency i do suggest to keep the two ges fi-inmedia and Compressed Domain Video Analysis together. in fact the fi-inmedia was born and agreed at the level of the fi-ppp ab to extend and complement with what already specified and provided by the Compressed Domain Video Analysis ge. keeping them separate, i mean in two different wps, migth generate inconsistencies and/or overlaps. so either both in the data chapter or both in the new wp. the argument of size of a wp you put forward is a bit articial in the sense that if we believe a new chapter needs to be in the overall fi-ware architecture than the size per se does not matter at all while keeping things together in an almost unconsistent way foir sure migth generate incomprehensions as well as communication and exploiation issues. so my proposal is to very much welcome the new wp, but also to keep together the content geis well defined in the data chapter. ciao, stefano 2013/5/22 Juanjo Hierro > [image: Boxbe] You chose to allow > Juanjo Hierro (jhierro at tid.es) even though this message failed > authentication > Click to disallow > > Hi all, > > As you perfectly know, a number of new partners will join the FI-WARE > consortium as a result of the 2nd Open Call. > > I have given a careful thought to the way these new beneficiaries of the > 2nd Open Call could be integrated in FI-WARE. Overall, looking for an > approach that makes sense technically in the first place but also makes > sense from an organizational perspective. > > It is obvious that Advanced Web-based User Interface GEs should fit > within a new WP because existing WPs are not so much related. In a first > approach, one may go for a design where there essentially the activities > devised in the WeX proposal (dealing with the topic on Advanced Web-based > User Interface in the 2nd Open Call) would go to that WP, while activities > addressed in the FI-INMEDIA (dealing with the another topic on > Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context > Management. However, this would lead to a situation which is a bit > unbalanced because the new WP will be very small compare to others. > Besides, the Data/Context Management WP would become rather huge and > difficult to manage. > > The solution that has came to my mind would consist in adding a new WP > devoted to "Advanced Middleware, Web-based User Interface and Multimedia > Enablers". This WP would concentrate tasks linked to specification and > reference implementation of enablers targeted to: > > - support development of Web-based User Interfaces covering 3D and > augmented reality and multimedia aspects > - support multimedia enablers that may help to deal with stream > processing and delivery of multimedia contents > - advanced middleware technologies (i.e., KIARA) intended to help the > above enablers to reach the best performance > > > The Working Package Leader (WPL) would be ZHAW and I believe that the > best idea would be to propose that DKFI becomes the Working Package > Architect (WPA). Of course, all this under the necessary technical and > overall coordination by TID and follow-up through the regular joint > WPLs/WPAs follow-up confcalls. > > I see several advantages on this approach. Among others, moving KIARA > to the new WP would help to better work on the details about how the KIARA > middleware can be used to support the quite challenging requirements on > performance that are expected for the other GEs to be provided by this > WP. Besides, the approach would allow to concentrate the resources of > DFKI in a single WP, thus easing their task as WPA. DFKI would not be > only involved in the KIARA activities but also in the activities dealing > with overall design of the architecture that supports advanced Web-based > User Interfaces covering 3D and augmented reality capabilities and > stream-related enablers dealing with processing and delivery of multimedia > contents, contributing their know-how in both fields and also the fact that > the proposed contributions for the first topic were relying on open source > technologies developed at DFKI. > > I have already discussed this within TID (currently WPL in the > Data/Context Management WP) in addition to ZHAW and DFKI (because they > would become the WPL and WPA of this new WP, respectively) and they agree > with this movement. > > Therefore, we will go for implementing the addition of this new WP in > amendment 5 that for which the negotiation is going to start soon. Note > that we intend to close this new amendment rather soon (targeting end of > this month or first week of June). Therefore, we will proceed with this > approach unless we receive an elaborated objection by any of you. I > cannot imagine about any reason why there may be any objection to this but, > formally, we had to ask :-) > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > ------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > _______________________________________________ > Fiware-ga mailing list > Fiware-ga at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-ga > > -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 22 20:27:36 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 20:27:36 +0200 Subject: [Fiware-wpl] [Fiware-ga] Creation of new WP as a result of incorporatingbeneficiaries of the 2nd Open Call In-Reply-To: References: <1369242099348.391269701@boxbe> Message-ID: <519D0E18.5040703@tid.es> Hi Stefano, Thanks for your input. Indeed we asked Siemens about their opinion. Let me wait until his feedback and then determine what to do. Cheers, -- Juanjo On 22/05/13 19:54, stefano de panfilis wrote: dear juanjo, i basically do agree, but for the sake of better consistency i do suggest to keep the two ges fi-inmedia and Compressed Domain Video Analysis together. in fact the fi-inmedia was born and agreed at the level of the fi-ppp ab to extend and complement with what already specified and provided by the Compressed Domain Video Analysis ge. keeping them separate, i mean in two different wps, migth generate inconsistencies and/or overlaps. so either both in the data chapter or both in the new wp. the argument of size of a wp you put forward is a bit articial in the sense that if we believe a new chapter needs to be in the overall fi-ware architecture than the size per se does not matter at all while keeping things together in an almost unconsistent way foir sure migth generate incomprehensions as well as communication and exploiation issues. so my proposal is to very much welcome the new wp, but also to keep together the content geis well defined in the data chapter. ciao, stefano 2013/5/22 Juanjo Hierro > [Boxbe] [http://www.boxbe.com/stfopen?tc_serial=14203782183&tc_rand=626565837&utm_source=stf&utm_medium=email&utm_campaign=ANNO_AFA&utm_content=001] You chose to allow Juanjo Hierro (jhierro at tid.es) even though this message failed authentication Click to disallow Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-ga mailing list Fiware-ga at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-ga -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed May 22 20:29:09 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 22 May 2013 20:29:09 +0200 Subject: [Fiware-wpl] URGENT: Delivery of Open specs TODAY In-Reply-To: <519CB99C.1040807@tid.es> References: <519CB99C.1040807@tid.es> Message-ID: <519D0E75.80704@tid.es> Dear all, I just realised that Juanjo delivered the WP3 open specs. Congratulations to SAP and the team they lead on being the 1st ones to deliver. Best regards, Miguel El 22/05/2013 14:27, Miguel Carrillo escribi?: Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. 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 pierangelo.garino at telecomitalia.it Wed May 22 22:36:06 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 22 May 2013 22:36:06 +0200 Subject: [Fiware-wpl] R: [Fiware-ga] Creation of new WP as a result of incorporating beneficiaries of the 2nd Open Call In-Reply-To: <519CF9E2.3020002@tid.es> References: <519CF9E2.3020002@tid.es> Message-ID: Hi Juanjo, I basically agree with the proposal you made, I just want to add that, as pointed out by Stefano about the close relationship with GEis of data chapter, another specific connection should be established between the newly created WP and the I2ND one, for what concerns both the CDI and the Cloud Proxy/Edge GEs. In my view it is important that we keep in close contact the developments of this WP which deals with web-based interfaces and the I2ND chapter; as an example the features of the CDI which provide access to device capabilities specifically through JavaScript API can be leveraged in the implementation of those advanced UIs planned in the WP. The same could be envisaged for Cloud Proxy, which can easily host implementations of advanced UIs and related GEs. BR Pier Da: fiware-ga-bounces at lists.fi-ware.eu [mailto:fiware-ga-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 22 maggio 2013 19:01 A: fiware-ga at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-ga] Creation of new WP as a result of incorporating beneficiaries of the 2nd Open Call Hi all, As you perfectly know, a number of new partners will join the FI-WARE consortium as a result of the 2nd Open Call. I have given a careful thought to the way these new beneficiaries of the 2nd Open Call could be integrated in FI-WARE. Overall, looking for an approach that makes sense technically in the first place but also makes sense from an organizational perspective. It is obvious that Advanced Web-based User Interface GEs should fit within a new WP because existing WPs are not so much related. In a first approach, one may go for a design where there essentially the activities devised in the WeX proposal (dealing with the topic on Advanced Web-based User Interface in the 2nd Open Call) would go to that WP, while activities addressed in the FI-INMEDIA (dealing with the another topic on Stream-oriented GEs in the 2nd Open Call) may go to the WP on Data/Context Management. However, this would lead to a situation which is a bit unbalanced because the new WP will be very small compare to others. Besides, the Data/Context Management WP would become rather huge and difficult to manage. The solution that has came to my mind would consist in adding a new WP devoted to "Advanced Middleware, Web-based User Interface and Multimedia Enablers". This WP would concentrate tasks linked to specification and reference implementation of enablers targeted to: * support development of Web-based User Interfaces covering 3D and augmented reality and multimedia aspects * support multimedia enablers that may help to deal with stream processing and delivery of multimedia contents * advanced middleware technologies (i.e., KIARA) intended to help the above enablers to reach the best performance The Working Package Leader (WPL) would be ZHAW and I believe that the best idea would be to propose that DKFI becomes the Working Package Architect (WPA). Of course, all this under the necessary technical and overall coordination by TID and follow-up through the regular joint WPLs/WPAs follow-up confcalls. I see several advantages on this approach. Among others, moving KIARA to the new WP would help to better work on the details about how the KIARA middleware can be used to support the quite challenging requirements on performance that are expected for the other GEs to be provided by this WP. Besides, the approach would allow to concentrate the resources of DFKI in a single WP, thus easing their task as WPA. DFKI would not be only involved in the KIARA activities but also in the activities dealing with overall design of the architecture that supports advanced Web-based User Interfaces covering 3D and augmented reality capabilities and stream-related enablers dealing with processing and delivery of multimedia contents, contributing their know-how in both fields and also the fact that the proposed contributions for the first topic were relying on open source technologies developed at DFKI. I have already discussed this within TID (currently WPL in the Data/Context Management WP) in addition to ZHAW and DFKI (because they would become the WPL and WPA of this new WP, respectively) and they agree with this movement. Therefore, we will go for implementing the addition of this new WP in amendment 5 that for which the negotiation is going to start soon. Note that we intend to close this new amendment rather soon (targeting end of this month or first week of June). Therefore, we will proceed with this approach unless we receive an elaborated objection by any of you. I cannot imagine about any reason why there may be any objection to this but, formally, we had to ask :-) Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jhierro at tid.es Thu May 23 08:56:14 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 23 May 2013 08:56:14 +0200 Subject: [Fiware-wpl] Submission of the FI-WARE Architecture deliverable Message-ID: <519DBD8E.5090104@tid.es> Hi all, There were some contributions that are still pending and now I have to go for a full day meeting of the FI-PPP SB and the Advisory Council. Therefore, I will submit the whole Architecture documents that are part of the deliverable this evening. Please note that I will submit them without further delay. I don't want to delay this anymore. Those who wish to introduce some last-minute change, can do so, but not later than 14:00 today. If you update the document, please leave it accessible in the FI-WARE Architecture deliverable cockpit (column G) of the following Google doc: https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu May 23 10:13:48 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 23 May 2013 10:13:48 +0200 Subject: [Fiware-wpl] clarification on deliverables Message-ID: <519DCFBC.9000407@tid.es> Dear all, The other day I sent clarifications to ease the process of the deliverable generation. These instructions were general. In the case of the Open Specs and the Architecture in particular of course we need to have the cockpit updated. Be aware that if we find something wrong and easy to fix (for instance, a wrong header) we may speed up the process by taking the word doc from the cockpit and changing it. Although you have had a lot of them so far, I remind you where the cockpits are just in case it helps. Open Specs Cockpit(update column E, the one we will use) * https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdHYxYTVOZ3FrNEprZXRBZk80TGRLMGc#gid=0 Architecture cockpit (update column G, the one we will use) * https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Thu May 23 17:05:52 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 23 May 2013 15:05:52 +0000 Subject: [Fiware-wpl] Backlog - Wiki Reviews Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890500E2@EX10-MB2-MAD.hi.inet> Dear Partners, Find linked the reviews of the wiki views of the backlog: @Thorsten - WP3 - Apps: https://forge.fi-ware.eu/docman/view.php/27/2422/FIWARE.backlog.apps.review.20130523-1452.xlsx @ Alex -WP4 - Cloud: https://forge.fi-ware.eu/docman/view.php/27/2423/FIWARE.backlog.cloud.review.20130523-1452.xlsx @Thierry/Carlos - WP5 - IoT: https://forge.fi-ware.eu/docman/view.php/27/2426/FIWARE.backlog.iot.review.20130523-1452.xlsx @ Sergio - WP6 - Data: https://forge.fi-ware.eu/docman/view.php/27/2424/FIWARE.backlog.data.review.20130523-1452.xlsx @ Pier - WP7 - I2ND: https://forge.fi-ware.eu/docman/view.php/27/2425/FIWARE.backlog.i2nd.review.20130523-1452.xlsx @Pascal - WP8 - Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx I hope you find them useful. The purpose is to help by pointing out items which would be improved (potentially). I tried to make them intuitive, but they may well need clarifications. Therefore, please, don't hesitate to contact me or let me know. If you find anything, which could be a mistake, please, let me know. It may help me to improve the scripts. Please, address the issues at your earliest convenience. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thorsten.sandfuchs at sap.com Thu May 23 17:25:48 2013 From: thorsten.sandfuchs at sap.com (Sandfuchs, Thorsten) Date: Thu, 23 May 2013 15:25:48 +0000 Subject: [Fiware-wpl] Template for deliverable generation updated Message-ID: <2981E9D6242FCF47ADC9B5DBA5DFD66461091CBD@DEWDFEMB11A.global.corp.sap> Dear colleagues, you might have noted (or not) that the documents that get generated (zip-files) starting from today around 13:00 get a different layout in some parts. This was introduced to improve readability. Eg. We have now "justified" text in the "Normal" text parts. With the latest fix on 17:17 CEST the last errors were resolved - now the headings (which inherited the justify-paragraph text) will be Left aligned. If you find any problems or have concerns, please let me know in order to fix this. Happy generating, J /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu May 23 20:05:05 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 23 May 2013 20:05:05 +0200 Subject: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Message-ID: <519E5A51.3040609@tid.es> Dear all, We are organizing the webminars in a more informal an hopefully effective manner. We will use twitter to broadcast the details of the webminars * Each webminar will have a dedicated hashtag * The owner of each webminar will tweet messages with the relevant info to @Fiware from their accounts, also using the GEi hashtag. This could happen before , after and during the webminar. * The attendees will be encouraged to make questions to you via twitter during the presentation. They will use the hashtag for the webminar and will send the tweet to @Fiware - of course, in principle you must reply. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (if it the answer is provided later in his presentation, for instance) We keep the details publicly updated here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 All GE owners please : * Immediate action point (for now): Add the hashtag you will use for your GEi in column F * It seems obvious but .... make sure that you have a twitter account ready to broadcast your messages! * Add the logistic details there (if needed) * Make sure that you do not forget to announce your webminar via twitter a number of days in advance * Make sure that you publicise your hashtag and that people know that they have to use it to draw your attention to their questions * Make sure that you are ready to reply to questions via twitter during the webminar We are going to publicly announce this to the PPP shortly. Best regards, Miguel P.S.: before anyone asks, the fi-ware-training list will not be used for now. Let us leave it dormant. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergg at tid.es Fri May 24 12:26:23 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Fri, 24 May 2013 10:26:23 +0000 Subject: [Fiware-wpl] Backlog - Wiki Reviews In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B890500E2@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890500E2@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D8659393A@EX10-MB2-MAD.hi.inet> Dear Manuel, Thanks for the great effort. It will definitively help us to clean up the backlogs. I think it would be useful to spend a slot next Monday to explain it and solve doubts. Miguel, is it feasible? Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Thursday, May 23, 2013 5:06 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Backlog - Wiki Reviews Dear Partners, Find linked the reviews of the wiki views of the backlog: @Thorsten - WP3 - Apps: https://forge.fi-ware.eu/docman/view.php/27/2422/FIWARE.backlog.apps.review.20130523-1452.xlsx @ Alex -WP4 - Cloud: https://forge.fi-ware.eu/docman/view.php/27/2423/FIWARE.backlog.cloud.review.20130523-1452.xlsx @Thierry/Carlos - WP5 - IoT: https://forge.fi-ware.eu/docman/view.php/27/2426/FIWARE.backlog.iot.review.20130523-1452.xlsx @ Sergio - WP6 - Data: https://forge.fi-ware.eu/docman/view.php/27/2424/FIWARE.backlog.data.review.20130523-1452.xlsx @ Pier - WP7 - I2ND: https://forge.fi-ware.eu/docman/view.php/27/2425/FIWARE.backlog.i2nd.review.20130523-1452.xlsx @Pascal - WP8 - Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx I hope you find them useful. The purpose is to help by pointing out items which would be improved (potentially). I tried to make them intuitive, but they may well need clarifications. Therefore, please, don't hesitate to contact me or let me know. If you find anything, which could be a mistake, please, let me know. It may help me to improve the scripts. Please, address the issues at your earliest convenience. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri May 24 12:30:37 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 24 May 2013 12:30:37 +0200 Subject: [Fiware-wpl] Backlog - Wiki Reviews In-Reply-To: <03BE306058976141B4883174DF62D54D8659393A@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890500E2@EX10-MB2-MAD.hi.inet> <03BE306058976141B4883174DF62D54D8659393A@EX10-MB2-MAD.hi.inet> Message-ID: <519F414D.5010201@tid.es> yes, certainly El 24/05/2013 12:26, SERGIO GARCIA GOMEZ escribi?: Dear Manuel, Thanks for the great effort. It will definitively help us to clean up the backlogs. I think it would be useful to spend a slot next Monday to explain it and solve doubts. Miguel, is it feasible? Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Thursday, May 23, 2013 5:06 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Backlog - Wiki Reviews Dear Partners, Find linked the reviews of the wiki views of the backlog: @Thorsten - WP3 - Apps: https://forge.fi-ware.eu/docman/view.php/27/2422/FIWARE.backlog.apps.review.20130523-1452.xlsx @ Alex -WP4 - Cloud: https://forge.fi-ware.eu/docman/view.php/27/2423/FIWARE.backlog.cloud.review.20130523-1452.xlsx @Thierry/Carlos - WP5 - IoT: https://forge.fi-ware.eu/docman/view.php/27/2426/FIWARE.backlog.iot.review.20130523-1452.xlsx @ Sergio - WP6 - Data: https://forge.fi-ware.eu/docman/view.php/27/2424/FIWARE.backlog.data.review.20130523-1452.xlsx @ Pier - WP7 - I2ND: https://forge.fi-ware.eu/docman/view.php/27/2425/FIWARE.backlog.i2nd.review.20130523-1452.xlsx @Pascal - WP8 - Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx I hope you find them useful. The purpose is to help by pointing out items which would be improved (potentially). I tried to make them intuitive, but they may well need clarifications. Therefore, please, don't hesitate to contact me or let me know. If you find anything, which could be a mistake, please, let me know. It may help me to improve the scripts. Please, address the issues at your earliest convenience. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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: From mev at tid.es Fri May 24 12:55:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 24 May 2013 10:55:03 +0000 Subject: [Fiware-wpl] Backlog - Wiki Reviews In-Reply-To: <519F414D.5010201@tid.es> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890500E2@EX10-MB2-MAD.hi.inet> <03BE306058976141B4883174DF62D54D8659393A@EX10-MB2-MAD.hi.inet> <519F414D.5010201@tid.es> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89050403@EX10-MB2-MAD.hi.inet> Thanks for the comment Sergio, and for the time slot Miguel!! Then, I'll prepare a short presentation to explain the underlying scheme, etc, and to give context to your questions and doubts. Kind regards, Manuel From: MIGUEL CARRILLO PACHECO Sent: viernes, 24 de mayo de 2013 12:31 To: SERGIO GARCIA GOMEZ Cc: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: Re: [Fiware-wpl] Backlog - Wiki Reviews yes, certainly El 24/05/2013 12:26, SERGIO GARCIA GOMEZ escribi?: Dear Manuel, Thanks for the great effort. It will definitively help us to clean up the backlogs. I think it would be useful to spend a slot next Monday to explain it and solve doubts. Miguel, is it feasible? Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Thursday, May 23, 2013 5:06 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Backlog - Wiki Reviews Dear Partners, Find linked the reviews of the wiki views of the backlog: @Thorsten - WP3 - Apps: https://forge.fi-ware.eu/docman/view.php/27/2422/FIWARE.backlog.apps.review.20130523-1452.xlsx @ Alex -WP4 - Cloud: https://forge.fi-ware.eu/docman/view.php/27/2423/FIWARE.backlog.cloud.review.20130523-1452.xlsx @Thierry/Carlos - WP5 - IoT: https://forge.fi-ware.eu/docman/view.php/27/2426/FIWARE.backlog.iot.review.20130523-1452.xlsx @ Sergio - WP6 - Data: https://forge.fi-ware.eu/docman/view.php/27/2424/FIWARE.backlog.data.review.20130523-1452.xlsx @ Pier - WP7 - I2ND: https://forge.fi-ware.eu/docman/view.php/27/2425/FIWARE.backlog.i2nd.review.20130523-1452.xlsx @Pascal - WP8 - Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx I hope you find them useful. The purpose is to help by pointing out items which would be improved (potentially). I tried to make them intuitive, but they may well need clarifications. Therefore, please, don't hesitate to contact me or let me know. If you find anything, which could be a mistake, please, let me know. It may help me to improve the scripts. Please, address the issues at your earliest convenience. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://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: From mcp at tid.es Fri May 24 17:55:11 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 24 May 2013 17:55:11 +0200 Subject: [Fiware-wpl] Regeneration of the Technical roadmap Message-ID: <519F8D5F.60400@tid.es> Dear all, This is to announce that I will regenerate the Technical Roadmap based on the info present on the wiki - it will be an extra issue to reflect the current status and I will deliver it to the EC as such. I will regenerate it on Tuesday at 4pm. 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 jhierro at tid.es Mon May 27 07:45:09 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 May 2013 07:45:09 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture In-Reply-To: <51A2EFD2.6040106@tid.es> References: <51A2EFD2.6040106@tid.es> Message-ID: <51A2F2E5.3020101@tid.es> Hi, Please find attached the final official submission of the FI-WARE Architecture deliverable. While carrying out a very final cross-chapter revision, I have identified the need to achieve a better consistency between names of sections in the different chapters and even within chapters: * There were some cases where the section titled "Basic Concepts" within the Architecture Description of a given GE was titled as "Main Concepts". I have changed this wherever I found it * There were some cases where the "Main Interactions" section within the Architecture Description of a given GE was titled as "Main Operations". I have changed this wherever I found it. There were GEs in the Security chapter for which the sections related to Copyright and Legal Notices were missing. This also happens regarding Basic Design Principles. Please add these sections asap. Despite I asked for the names of the companies to be added manually, I got no response. It would be nice that you perform a general review of the structure in your chapters and double-check alignment with the standard structure template we defined. I fixed a lot of the issues but this would be only reflected in the final deliverable so I have produced and already sent to you a version with comments that highlighted the changes you should introduce in the public wiki ASAP (note that this document is marked as private). For your convenience, here it goes the structure of sections that should have been adopted: 1. General Architecture Description of a Chapter: * Introduction * Architecture Overview * * Architecture Description of GEs * Interface to other chapters * References 2. Architecture Description of a given GE: * Copyright * Legal Notice * Overview (Target usage should be inside) * Basic Concepts * Architecture (recommended but optional, sometimes you have put this before "Basic concepts" but it would be nice to keep consistency and place it after) * Main Interactions * Basic Design Principles * Detailed Open Specifications (which should contain the links to the rest of Open Specifications) * References There were also A LOT of inconsistencies regarding level of headings. As an example, there were many chapters where there wasn't a second level heading. This was revealed thanks to the automated generation process and should be fixed in the wiki asap to avoid wrong generation next times. I carried out a final spelling checking to all chapters finding also many typos. I have to confess that I got astonished when I saw still those kind of issues in a so late stage of the peer-review ... Didn't nobody notice that? Despite we incurred in a delay, I have now found that it was worth carrying out this final review. Without giving names, when I have asked "how can we still find this issues?" in the draft I had just reviewed, I got the response "honestly, I believe some people hasn't read the contents in that detail". We honestly have to reconsider how we are carrying out our peer-review processes. I have also carried out several changes to improve overall readability. The detailed Open Specifications where not included in all cases, even within the same chapter, so I have had to put a note to the EC and reviewers explaining that we had decided to keep the inclusion by those GEs that decided to include it, because we will adopt that convention finally. Therefore, please do so. In addition, I also found that the copyright notice in many of the cases was only for 2012. This maybe interpreted by the reviewers as "no single line has been touched by the owners this year" when clearly this doesn't apply. Please fix those Copyright Notices where you have to write 2012-2013 (in the case of new GEs, 2013) Last but not least, there are a number of things that I have detected about which we have to reach a final agreement and adopt a convention across all chapters: * Titles, numbering and format (i.e., centered or not) of figures. I believe that we proposed a convention, and asked to avoid using of figure numbers, but apparently hasn't been followed consistently * Architecture section within a GE Architecture Description * Style for references We should address all of them once we finish with the most urgent things we currently have on our plate, but have them ready at the time we will start disseminating this among the wider community of developers. Please share with members of your respective chapters. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Date: Mon, 27 May 2013 07:32:02 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of deliverable D.2.3.2 FI-WARE Architecture. To ease review of its contents, separate files have been produced for the different chapters that made up the whole document. All of these files can be extracted from the .zip file you can download from the following URL: https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip Note that the FI-WARE Architecture specification is public and its contents become part of the several FI-WARE GE Open Specifications, therefore you can download this file without logging in your FusionForge account. We haven't delivered it earlier to make sure that it was aligned with the contents of FI-WARE GE Open Specifications that will be delivered along this week (some of them have already been delivered to you). The FI-WARE Architecture has beed produced conducting several peer-reviews and a final whole revision by myself, as chief architect, to ensure overall consistency. You will see that the description of the architecture of some GEs ended with a sections that provides the links to the Detailed Specifications. This doesn't happen in all the cases and will be fixed in subsequent releases of the deliverable. However, we thought it was not critical to add them here because you are going to receive them separately. Note that specifications are still provided together with an interim Legal Notice. This is because the Legal Notice accompanying specifications is still going through a final review by legal representatives of the different partners. This process is about to finish, so we don't expect major issues regarding usage by UC projects within the FI-PPP or impact in the launch of the FI-WARE Open Innovation Lab. Furthermore, differences between the final and interim Legal Notices is rather minor. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us in case you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 27 10:26:34 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 27 May 2013 10:26:34 +0200 Subject: [Fiware-wpl] Minutes for today - under edition now Message-ID: <51A318BA.5060509@tid.es> Dear all, The link for today's call: * https://docs.google.com/document/d/1h5fQOSjy5_aDO9pQ7_5Y2GQq-Q5mTv0-CjD_giqk-HU/edit?usp=sharing Work in progress! :) Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon May 27 13:35:40 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 May 2013 13:35:40 +0200 Subject: [Fiware-wpl] Cancelled: afternoon sesion of joint WPLs/WPAs follow-up confcall dealing with Access Control and OAuth framework and other stuff Message-ID: <51A3450C.3070809@tid.es> Hi, We agreed to cancel the afternoon sesion of joint WPLs/WPAs follow-up confcall dealing with Access Control and OAuth framework and other stuff ... but I just wanted to send this email so everyone is aware, even though not attending the morning session. I'm double-checking with the Cloud-UPM team whether they are available for tomorrow 14:30. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From jhierro at tid.es Mon May 27 16:06:37 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 May 2013 16:06:37 +0200 Subject: [Fiware-wpl] IMPORTANT: 1st series of Webinars about FI-WARE GEis In-Reply-To: <519E5A51.3040609@tid.es> References: <519E5A51.3040609@tid.es> Message-ID: <51A3686D.7040709@tid.es> Dear FI-WARE GEi owners, A reminder on the instruction you should follow to organize your webinars and, quite important: the way you have to organized them. Please find attached the original email from Miguel. Please note that the webinars have raised a lot of expectation among the UC projects and they are asking about next steps, logistic info per webinar, etc. We will inform them that they will be able to find all the necessary info on the Twitter @FIware account, so don't let them down !! Cheers, -- Juanjo -------- Original Message -------- Subject: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Date: Thu, 23 May 2013 20:05:05 +0200 From: Miguel Carrillo To: fiware at lists.fi-ware.eu CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, We are organizing the webminars in a more informal an hopefully effective manner. We will use twitter to broadcast the details of the webminars * Each webminar will have a dedicated hashtag * The owner of each webminar will tweet messages with the relevant info to @Fiware from their accounts, also using the GEi hashtag. This could happen before , after and during the webminar. * The attendees will be encouraged to make questions to you via twitter during the presentation. They will use the hashtag for the webminar and will send the tweet to @Fiware - of course, in principle you must reply. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (if it the answer is provided later in his presentation, for instance) We keep the details publicly updated here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 All GE owners please : * Immediate action point (for now): Add the hashtag you will use for your GEi in column F * It seems obvious but .... make sure that you have a twitter account ready to broadcast your messages! * Add the logistic details there (if needed) * Make sure that you do not forget to announce your webminar via twitter a number of days in advance * Make sure that you publicise your hashtag and that people know that they have to use it to draw your attention to their questions * Make sure that you are ready to reply to questions via twitter during the webminar We are going to publicly announce this to the PPP shortly. Best regards, Miguel P.S.: before anyone asks, the fi-ware-training list will not be used for now. Let us leave it dormant. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From jhierro at tid.es Mon May 27 16:19:15 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 May 2013 16:19:15 +0200 Subject: [Fiware-wpl] Fwd: Details about organization of webinars of FI-WARE GEis In-Reply-To: <51A36AE6.3070300@tid.es> References: <51A36AE6.3070300@tid.es> Message-ID: <51A36B63.5070703@tid.es> Hi, Following my previous email on the matter, please find attached the email I have just sent to the whole FI-PPP regarding how we are going to deal with synchronization, announcements, support, etc regarding webinars. Please, FI-WARE GEi owners: act accordingly. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Details about organization of webinars of FI-WARE GEis Date: Mon, 27 May 2013 16:17:10 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu , all at fi-ppp.eu Dear all, Some of you have asked about how to get more details about FI-WARE GEi webinars. We will use our @FIware twitter account to broadcast the details of the webminars as well as handle interaction with you and interested people. In this respect: * Each webminar will have a dedicated hashtag. It should be the one that has already been used in the cockpit we defined for dealing with registration to the webinars: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 * The owner of each webminar will post messages with the relevant info to @Fiware in Twitter, also using the associated GEi hashtag. This could happen before (to announce logistic details), after (e.g., providing link to download slides used during the seminar, etc) and during the webminar (chairing the session) * The attendees to a given webinar are encouraged to make their questions also posting to @FIware and using the associated hashtag. Questions may be sent earlier, during or after the session. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (keep it on hold if the answer is provided later in his presentation, for example) If you have any question, don't hesitate to ask. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From mev at tid.es Mon May 27 19:07:03 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Mon, 27 May 2013 17:07:03 +0000 Subject: [Fiware-wpl] [Fiware-wpa] IMPORTANT: 1st series of Webinars about FI-WARE GEis - webinars for this week and unscheduled Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89050A3B@EX10-MB2-MAD.hi.inet> Dear Partners, In order to help organising this activity, please, have a look at the list of webinars scheduled for this week. Please, notice 3 hashtags are missing from: ? (DATA) Semantic Application by TI ? Allocation of Object Storage - I actually cannot map this enabler. I'd appreciate help ? (DATA) Location by Thales Sergio, since two of them belong to DATA chapter, I'd appreciate your contacting them. Thanks in advance!!! [cid:image001.png at 01CE5B0C.5B7E1D90] Please, be aware there're a number of enablers not scheduled yet. I'd appreciate having dates as soon as possible. >From this set there are enables belonging to CLOUD (@Alex), IOT(@Thierry/Carlos , DATA(@Sergio), I2ND(@Pier)) and SECURITY(@Pascal), I'd appreciate you contacting the corresponding partners so as to fix dates as soon as possible. Thanks in advance!! [cid:image002.png at 01CE5B0D.5D0F0150] If anything, please, let me know. Kind regards, Manuel From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: lunes, 27 de mayo de 2013 16:07 To: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] IMPORTANT: 1st series of Webinars about FI-WARE GEis Dear FI-WARE GEi owners, A reminder on the instruction you should follow to organize your webinars and, quite important: the way you have to organized them. Please find attached the original email from Miguel. Please note that the webinars have raised a lot of expectation among the UC projects and they are asking about next steps, logistic info per webinar, etc. We will inform them that they will be able to find all the necessary info on the Twitter @FIware account, so don't let them down !! Cheers, -- Juanjo -------- Original Message -------- Subject: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Date: Thu, 23 May 2013 20:05:05 +0200 From: Miguel Carrillo To: fiware at lists.fi-ware.eu CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, We are organizing the webminars in a more informal an hopefully effective manner. We will use twitter to broadcast the details of the webminars * Each webminar will have a dedicated hashtag * The owner of each webminar will tweet messages with the relevant info to @Fiware from their accounts, also using the GEi hashtag. This could happen before , after and during the webminar. * The attendees will be encouraged to make questions to you via twitter during the presentation. They will use the hashtag for the webminar and will send the tweet to @Fiware - of course, in principle you must reply. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (if it the answer is provided later in his presentation, for instance) We keep the details publicly updated here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 All GE owners please : * Immediate action point (for now): Add the hashtag you will use for your GEi in column F * It seems obvious but .... make sure that you have a twitter account ready to broadcast your messages! * Add the logistic details there (if needed) * Make sure that you do not forget to announce your webminar via twitter a number of days in advance * Make sure that you publicise your hashtag and that people know that they have to use it to draw your attention to their questions * Make sure that you are ready to reply to questions via twitter during the webminar We are going to publicly announce this to the PPP shortly. Best regards, Miguel P.S.: before anyone asks, the fi-ware-training list will not be used for now. Let us leave it dormant. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 42377 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 32006 bytes Desc: image002.png URL: From jhierro at tid.es Mon May 27 21:18:59 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 27 May 2013 21:18:59 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.6.1.2 Open Specifications (WP6 - Data Chapter) In-Reply-To: <51A3B12A.7020709@tid.es> References: <51A3B12A.7020709@tid.es> Message-ID: <51A3B1A3.8010203@tid.es> Dear all, Please find below he official submission of the FI-WARE GE Open Specifications linked to the Data Chapter. Congratulations to members of the Data Chapter ! (and members of the Apps Chapter who had already submitted days ago) Now starts the competion about who is going to be the last ;-) Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.6.1.2 Open Specifications (WP6 - Data Chapter) Date: Mon, 27 May 2013 21:16:58 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, Sergio Garc?a G?mez , "Marti Christof (mach)" , "jhierro >> \"Juan J. Hierro\"" , FI-WARE project EC mailbox Dear all, This is the official submission of D.6.1.2 Open Specifications (WP6). You can download the corresponding files from the following links: * FI-WARE GE Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2482/D.6.1.2+FI-WARE+GE+Open+Specifications+-+Data+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdps at tid.es Tue May 28 02:11:56 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Tue, 28 May 2013 00:11:56 +0000 Subject: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 Message-ID: <77A22C1085494D48B4018F06A40DB2C72FA3E480@EX10-MB2-MAD.hi.inet> Dear all, First, thank you very much for your contribution. Please find attached the first version of the integrated Periodic Report of M24. I kindly ask you to review it. If you have something in yellow in your WP, please update it. If you see something to be updated of another WP, please contact with the WPL directly. We?ll only accept changes from WPL of each own WP. Please, send your updates before next Thursday 30th of May, EOB. (It is very important to use the activated track change control) Next Friday, it will be update with your last versions and it will be reviewed by the Coordinator in order to deliver the final version next week. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 811122 bytes Desc: D.1.2.4-FI-WARE_Periodic_Peport-M13-M24-v1.docx URL: From jhierro at tid.es Tue May 28 06:59:36 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 06:59:36 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) In-Reply-To: <51A437D2.7050509@tid.es> References: <51A437D2.7050509@tid.es> Message-ID: <51A439B8.6060900@tid.es> New one submitted (Cloud). So we have already delivered Apps, Data and Cloud. We expect to deliver all by EOB today, most probably IoT and I2ND along this morning. Regardig the Security specs, note that you should fix the issue about copyrights holder sections and, most importantly, the REST API specifications associated to the Identity Management GE should be part of it, otherwise we will need to include a note to the EC clarifying they have not been made publicly available. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Date: Tue, 28 May 2013 06:51:30 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, Alex Glikson , "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of D.4.1.2 Open Specifications (WP4 - Cloud Chapter). You can download the corresponding file from the following link: * https://forge.fi-ware.eu/docman/view.php/7/2484/D.4.1.2+FI-WARE+GE+Open+Specifications+-+Cloud+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 28 07:06:37 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 07:06:37 +0200 Subject: [Fiware-wpl] IMPORTANT: 1st series of Webinars about FI-WARE GEis In-Reply-To: <51A3686D.7040709@tid.es> References: <519E5A51.3040609@tid.es> <51A3686D.7040709@tid.es> Message-ID: <51A43B5D.1040509@tid.es> Hi, A request we have received from the UC projects which I believe shouldn't be too hard to accomodate: * Please add slides and other material in the Google Docs (table dedicated to your tag in 'Logistic details" Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/05/13 16:06, Juanjo Hierro wrote: Dear FI-WARE GEi owners, A reminder on the instruction you should follow to organize your webinars and, quite important: the way you have to organized them. Please find attached the original email from Miguel. Please note that the webinars have raised a lot of expectation among the UC projects and they are asking about next steps, logistic info per webinar, etc. We will inform them that they will be able to find all the necessary info on the Twitter @FIware account, so don't let them down !! Cheers, -- Juanjo -------- Original Message -------- Subject: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Date: Thu, 23 May 2013 20:05:05 +0200 From: Miguel Carrillo To: fiware at lists.fi-ware.eu CC: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, We are organizing the webminars in a more informal an hopefully effective manner. We will use twitter to broadcast the details of the webminars * Each webminar will have a dedicated hashtag * The owner of each webminar will tweet messages with the relevant info to @Fiware from their accounts, also using the GEi hashtag. This could happen before , after and during the webminar. * The attendees will be encouraged to make questions to you via twitter during the presentation. They will use the hashtag for the webminar and will send the tweet to @Fiware - of course, in principle you must reply. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (if it the answer is provided later in his presentation, for instance) We keep the details publicly updated here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 All GE owners please : * Immediate action point (for now): Add the hashtag you will use for your GEi in column F * It seems obvious but .... make sure that you have a twitter account ready to broadcast your messages! * Add the logistic details there (if needed) * Make sure that you do not forget to announce your webminar via twitter a number of days in advance * Make sure that you publicise your hashtag and that people know that they have to use it to draw your attention to their questions * Make sure that you are ready to reply to questions via twitter during the webminar We are going to publicly announce this to the PPP shortly. Best regards, Miguel P.S.: before anyone asks, the fi-ware-training list will not be used for now. Let us leave it dormant. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 28 13:15:52 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 13:15:52 +0200 Subject: [Fiware-wpl] REMINDER: follow-up confcall on OAuth 2.0 and Access Control framework in FI-WARE Message-ID: <51A491E8.4070105@tid.es> Dear all, This is just a reminder of the confcall we are goint to have at 14:30, as already agreed yesterday during our regular joint WPLs/WPAs follow-up confcalls. We'll use powwownow. 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) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx From mcp at tid.es Tue May 28 13:34:01 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 28 May 2013 13:34:01 +0200 Subject: [Fiware-wpl] Deletion of old "open Specs" directory Message-ID: <51A49629.5050605@tid.es> Dear all, Some of you may have noticed that I have been rearranging the folders for our deliverables under the project "FI-WARE". They have now a more logical structure (I hope!) The old folder "D.3-8.1 FI-WARE Open Specifications" is deprecated and the open specs are now in the chapter folder withing "Release1" and "Release 2" . The only reason to keep the old folder is that I found files that apparently were used for cross reviews in the past. My view is they have little value now and the they should not be shared with the UCs (also, they may cause confusions). In case someone wants to keep them, I will wait until next week. You can port them before monday to the private docman if you really want to keep them. I refer to these folders marked in red: [cid:part1.04060205.02030802 at tid.es] On Monday, "D.3-8.1 FI-WARE Open Specifications" and all its contents will be deleted unless there is an objection coming from any of the the WPL/WPA or Juanjo. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: cfabfgdh.png Type: image/png Size: 15049 bytes Desc: not available URL: From davide.dallecarbonare at eng.it Tue May 28 13:51:45 2013 From: davide.dallecarbonare at eng.it (Davide Dalle Carbonare) Date: Tue, 28 May 2013 13:51:45 +0200 Subject: [Fiware-wpl] Platform for FI-WARE Webinars Message-ID: <51A49A51.2010703@eng.it> Dear parters, in order to provide FI-WARE webinars I notify you about the possibility of using the MeshMe.tv platform made available by UPM. To understand how this platform works and how to use it, It's possible to attend to a dedicated presentation on these dates: 1) Wednesday 5th of June from 14h to 15h 2) Thursday 6th of June from 14h to 15h To facilitate the organization of these sessions, please, confirm your attendance by sending a message to both: - Juan Quemada Vives - Abel Carril To enter the webinar session click on: http://www.mashme.tv/M/2qvRiO?mode=1 Requirements for accessing the platform: A browser which supports HTML5 must be used. This includes the last versions of Chrome, Firefox, Opera, Internet Explorer 9 or 10, etc. @WPLs, please, circulate this message in your WP mailing lists in order to involve all the potential users. Thank you and Kind Regards, Davide From jhierro at tid.es Tue May 28 14:39:44 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 14:39:44 +0200 Subject: [Fiware-wpl] Presentation on OAuth 2.0 and Access Control Framework in FI-WARE Message-ID: <51A4A590.3080100@tid.es> Hi, Many of you already had this, but just for your convenience so that you don't need to search for it. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Security 13-05-14.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 187888 bytes Desc: not available URL: From mev at tid.es Tue May 28 17:57:39 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 28 May 2013 15:57:39 +0000 Subject: [Fiware-wpl] Webinars scheduled for this week - please, pay attention Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89050E97@EX10-MB2-MAD.hi.inet> Dear Partners, Please, have a look at the webinars scheduled for this week. Please, be aware of a number of things: 1. (SECURITY) Data Handling - please, clarify whether it is CEST time 2. (SECURITY) DB Anonimyzer - please, follow the same time format as other partners. a. I see it advertised for 07.June, but not the one scheduled for 31st.May 3. (ALL) - Don't forget to: a. Advertise your webinar by sending at least a twit to . at FIWARE (I've seen some already sent - GOOD!!) b. Put a hashtag which is not in use, check it beforehand. You can easily do it by adding the FIWARE prefix to your enabler acronym. c. Write the logistic details for accessing your session, don't forget to add a presentation, which can be downloaded and followed by your audience. d. When, you have finished, please, mark the date with "-done," if possible annotate the number of attendees. Please be aware of the dot before @FIWARE, . at FIWARE - when you start your twit this way. Well, if anything, please, let me know. Kind regards, Manuel [cid:image001.png at 01CE5BCB.F83848D0] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37313 bytes Desc: image001.png URL: From mcp at tid.es Tue May 28 19:19:50 2013 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 28 May 2013 19:19:50 +0200 Subject: [Fiware-wpl] Fwd: Submission of extra issue of FI-WARE Technical roadmap (D.2.4.2b) In-Reply-To: <51A4E6B1.1020804@tid.es> References: <51A4E6B1.1020804@tid.es> Message-ID: <51A4E736.5040905@tid.es> Dear all, As announced. I generated the source file shortly after 4pm. Best regards, Miguel -------- Mensaje original -------- Asunto: Submission of extra issue of FI-WARE Technical roadmap (D.2.4.2b) Fecha: Tue, 28 May 2013 19:17:37 +0200 De: Miguel Carrillo Para: Arian.ZWEGERS at ec.europa.eu , Dominic Greenwood , msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com, INFSO-ICT-285248 at ec.europa.eu CC: JUAN JOSE HIERRO SUREDA , "Vanessa.VANHUMBEECK at ec.europa.eu" , MANUEL ESCRICHE VICENTE Dear all, Following our agile methodology, our roadmap is in constant evolution. Although the changes on this occasion are not particularly extensive, we think that it is a good idea to provide you with an extra issue reflecting the current status of the roadmap. This is therefore not on the list of commited deliverables but we thought that you would appreciate it. This is publicly available here: * https://forge.fi-ware.eu/docman/view.php/7/2501/D2.4.2b+FI-WARE+Technical+Roadmap+%28extra+issue%29.pdf You can find the source pages constantly updated under http://wiki.fi-ware.eu/FI-WARE_Technical_Roadmap I also attach it with this message in pdf format. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: D2.4.2b FI-WARE Technical Roadmap (extra issue).pdf Type: application/pdf Size: 1652223 bytes Desc: not available URL: From jhierro at tid.es Tue May 28 19:32:41 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 19:32:41 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.5.1.2 Open Specifications (WP5 - IoT Chapter) In-Reply-To: <51A4E9FD.5040608@tid.es> References: <51A4E9FD.5040608@tid.es> Message-ID: <51A4EA39.2030700@tid.es> Dear all, Please find enclosed official submission of FI-WARE GE Open Specifications associated to the IoT 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) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.5.1.2 Open Specifications (WP5 - IoT Chapter) Date: Tue, 28 May 2013 19:31:41 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, "thierry.nagellen at orange.com" , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of D.5.1.2 Open Specifications (WP5 - IoT Chapter). You can download the corresponding file from the following link: * https://forge.fi-ware.eu/docman/view.php/7/2505/D.5.1.2+FI-WARE+GE+Open+Specifications+-+IoT+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 28 20:23:42 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 20:23:42 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.7.1.2 Open Specifications (WP7 - I2ND Chapter) In-Reply-To: <51A4F5E7.6060003@tid.es> References: <51A4F5E7.6060003@tid.es> Message-ID: <51A4F62E.7040202@tid.es> I2ND chapter delivered. Congratulations ! Only the Security chapter is remaining. I'll take care of that tonight or tomorrow early in the morning. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.7.1.2 Open Specifications (WP7 - I2ND Chapter) Date: Tue, 28 May 2013 20:22:31 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, Garino Pierangelo , "Hans.Einsiedler at telekom.de" , "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of D.7.1.2 Open Specifications (WP7 - I2ND Chapter). You can download the corresponding file from the following link: * https://forge.fi-ware.eu/docman/view.php/7/2497/D.7.1.2+FI-WARE+GE+Open+Specifications+-+I2ND+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 29 08:11:57 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 May 2013 08:11:57 +0200 Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Message-ID: <51A59C2D.90605@tid.es> Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From GLIKSON at il.ibm.com Wed May 29 08:26:50 2013 From: GLIKSON at il.ibm.com (Alex Glikson) Date: Wed, 29 May 2013 09:26:50 +0300 Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: <51A59C2D.90605@tid.es> References: <51A59C2D.90605@tid.es> Message-ID: Thanks for putting this together. I have one comment regarding the catalogue. I know that there are several critical changes (including updated 'Terms and Conditions') which are still pending approval for many months (in fact, we failed to deliver on time on the corresponding checkpoint due to this 4 months delay). Would be good to take care of this early enough. In particular, I would recommend removing the approval process altogether. This is an unnecessary bottleneck, which prevents timely updates, and makes the catalogue less relevant. We don't have any approvals/moderation in all the other information sources -- I don't see why this should be different here. Handling reviews and updates in a regular way might be much more efficient, IMO. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 29/05/2013 09:11 AM Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Sent by: fiware-wpl-bounces at lists.fi-ware.eu Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed May 29 08:57:51 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 May 2013 06:57:51 +0000 Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: References: <51A59C2D.90605@tid.es> Message-ID: <28122_1369810673_51A5A6F1_28122_2928_1_976A65C5A08ADF49B9A8523F7F81925C0EB1E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, Two comments also regarding the rehearsal : 1. I propose to introduce the agenda with collaboration activities: how new projects have been included in the program (Fi-Ware point of view) Architect Weeks + Webinars. We can show that we try to involve them very quickly and we can also give a first feedback on our understanding how they should/would/could use & implement some GEs in their trials. We can add in this part the views for OIL and Campus Party to show that Fi-Ware is launching the ecosystem. 2. Catalogue: I agree with Alex that the approval process is a bottleneck. I think it is better to refine process for the catalogue and how we have to describe things in the catalogue (we have new partners) and use some links to what we have now delivered (first step release 2.2 but in 3 months release 2.3). So we need a clear view today to update regularly the catalogue following the same rules. At least also clarify what is the single entry point for 3rd parties: wiki or catalogue. Focusing last months on our development with are unclear on this critical interface. 3. Legal notice: we do not share the same view currently and we have to clarify this point before the review. EC would strongly ask to finalize that for UC projects in phase 2 but also for OIL BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : mercredi 29 mai 2013 08:27 ? : Juanjo Hierro Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Thanks for putting this together. I have one comment regarding the catalogue. I know that there are several critical changes (including updated 'Terms and Conditions') which are still pending approval for many months (in fact, we failed to deliver on time on the corresponding checkpoint due to this 4 months delay). Would be good to take care of this early enough. In particular, I would recommend removing the approval process altogether. This is an unnecessary bottleneck, which prevents timely updates, and makes the catalogue less relevant. We don't have any approvals/moderation in all the other information sources -- I don't see why this should be different here. Handling reviews and updates in a regular way might be much more efficient, IMO. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro > To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 29/05/2013 09:11 AM Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed May 29 09:24:49 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 May 2013 07:24:49 +0000 Subject: [Fiware-wpl] Fwd: Submission of extra issue of FI-WARE Technical roadmap (D.2.4.2b) In-Reply-To: <51A4E736.5040905@tid.es> References: <51A4E6B1.1020804@tid.es> <51A4E736.5040905@tid.es> Message-ID: <32073_1369812290_51A5AD42_32073_14495_1_976A65C5A08ADF49B9A8523F7F81925C0EB1FB@PEXCVZYM13.corporate.adroot.infra.ftgroup> Thanks a lot Miguel for your efforts. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 28 mai 2013 19:20 ? : fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Submission of extra issue of FI-WARE Technical roadmap (D.2.4.2b) Dear all, As announced. I generated the source file shortly after 4pm. Best regards, Miguel -------- Mensaje original -------- Asunto: Submission of extra issue of FI-WARE Technical roadmap (D.2.4.2b) Fecha: Tue, 28 May 2013 19:17:37 +0200 De: Miguel Carrillo Para: Arian.ZWEGERS at ec.europa.eu , Dominic Greenwood , msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com, INFSO-ICT-285248 at ec.europa.eu CC: JUAN JOSE HIERRO SUREDA , "Vanessa.VANHUMBEECK at ec.europa.eu" , MANUEL ESCRICHE VICENTE Dear all, Following our agile methodology, our roadmap is in constant evolution. Although the changes on this occasion are not particularly extensive, we think that it is a good idea to provide you with an extra issue reflecting the current status of the roadmap. This is therefore not on the list of commited deliverables but we thought that you would appreciate it. This is publicly available here: * https://forge.fi-ware.eu/docman/view.php/7/2501/D2.4.2b+FI-WARE+Technical+Roadmap+%28extra+issue%29.pdf You can find the source pages constantly updated under http://wiki.fi-ware.eu/FI-WARE_Technical_Roadmap I also attach it with this message in pdf format. 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 29 23:50:11 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 May 2013 23:50:11 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: <51A59C2D.90605@tid.es> References: <51A59C2D.90605@tid.es> Message-ID: <51A67813.8060405@tid.es> Dear all, I have update the link so that it is now editable: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing Thanks for raising this. I thought I had already done. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 29/05/13 08:11, Juanjo Hierro wrote: Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu May 30 00:16:09 2013 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 30 May 2013 00:16:09 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: <51A59C2D.90605@tid.es> References: <51A59C2D.90605@tid.es> Message-ID: <51A67E29.7070102@tid.es> I took the liberty of adding a section at the beginning with the participant list Please fill it in, we need your details in advance. Particularly, those not on the list on June,5 may not be able to enter SAP's premises on the second rehearsal day El 29/05/2013 8:11, Juanjo Hierro escribi?: Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 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 May 30 08:45:07 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 May 2013 08:45:07 +0200 Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: <28122_1369810673_51A5A6F1_28122_2928_1_976A65C5A08ADF49B9A8523F7F81925C0EB1E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <51A59C2D.90605@tid.es> <28122_1369810673_51A5A6F1_28122_2928_1_976A65C5A08ADF49B9A8523F7F81925C0EB1E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51A6F573.3020601@tid.es> On 29/05/13 08:57, thierry.nagellen at orange.com wrote: Hi All, Two comments also regarding the rehearsal : 1. I propose to introduce the agenda with collaboration activities: how new projects have been included in the program (Fi-Ware point of view) Architect Weeks + Webinars. We can show that we try to involve them very quickly and we can also give a first feedback on our understanding how they should/would/could use & implement some GEs in their trials. We can add in this part the views for OIL and Campus Party to show that Fi-Ware is launching the ecosystem. This was something I was assuming would be part of the contents of the presentation on major highlights (note this is the first presentation/item in the agenda). Nevertheless, I would kindly ask you to add this comment to the point on comments/feedback regarding this action within the google doc so we don't forget and double-check it is covered in that presentation. 2. Catalogue: I agree with Alex that the approval process is a bottleneck. I think it is better to refine process for the catalogue and how we have to describe things in the catalogue (we have new partners) and use some links to what we have now delivered (first step release 2.2 but in 3 months release 2.3). So we need a clear view today to update regularly the catalogue following the same rules. At least also clarify what is the single entry point for 3rd parties: wiki or catalogue. Focusing last months on our development with are unclear on this critical interface. I have asked Miguel to come with a proposal on this matter. We agree it has became a bottleneck and we have therefore to fix it. 3. Legal notice: we do not share the same view currently and we have to clarify this point before the review. EC would strongly ask to finalize that for UC projects in phase 2 but also for OIL. Do you mean that the fact that we will have two Legal Notices will be seen as an issue by reviewers ? If so, I would be happy to hear about any constructive proposal on how to solve the issue. Telefonica had loved to have one single Legal Notice for obvious reasons ... but so far, the best compromise we were able to reach was that of having two valid alternatives for the Legal Notice and leave owners of a given spec decide what Legal Notice to agree on regarding a given spec. I can elaborate why I believe that the Legal Notice with explicit license on essential patents may become a barrier for potential adopters considering the possibility to implement FI-WARE GE Open Specifications: * The Legal Notice with explicit license on essential patents makes the following explicit statement: we will not sue you if you implement this spec based on an invention we have patented, if WE (the owners of the specs) agree that patent can be considered "essential" (essential meaning that nobody can conceive a reasonable implementation of the spec without relying on the idea/invention protected by the patent). * Therefore, if I were a potential implementer of the spec I would easily think ... "ummm, if they highlight this concept of "essential patent" is because they indeed consider the existence of 'non-essential' patents" ... they may have some of those non-essential patents in their portfolio and may be willing to ask royalties for them if they find that I may have infringed one of those non-essential patents with my implementation ... * Since I cannot see the list of non-essential patents anywhere ... I would tend to think "... should I invest on implementing this spec ? The risk is that I may be sued because I may have broken something that an owner of the spec may consider "non-essential" * because deciding that the invention in question is actually essential or not is a matter of opinion, I would be therefore in risk that they block the delivery of my product to the market until some jury establish that I was right and that invention should be considered essential ... a question that may well take years ... * Bottom line: is too risky so I will give up and look for a more open and less risky standard/specification to implement. The Legal Notice with the implicit license on patents drops any doubts for a potential implementer. It clearly states: Subject to all of the terms and conditions below, the Copyright Holders in this Specification hereby grant you, the individual or legal entity exercising permissions granted by this License, a fully-paid up, non-exclusive, nontransferable, perpetual, worldwide, royalty free (without the right to sublicense) license under its respective copyrights incorporated in the Specification, to copy and modify this Specification and to distribute copies of the modified version, and to use this Specification, to create and distribute special purpose specifications and software that is an implementation of this Specification. without distinguishing between essential and non-essential patents, therefore solving the issues described before. Relevant enough, an organization like the OMG (Object Management Group), widely recognized for producing some of the most widely accepted open standards in the last 20 years, had a Legal Notice which followed the approach of the implicit patent license. That was another reason why we thought it was good to rely on the experience of an organization like OMG when we proposed the initial only version of the Legal Notice. Interestingly, some of the FI-WARE partners seem that they could live with OMG's legal notice in those case where they contributed specs to OMG. I have to confess that I didn't understand why they couldn't adopt the same decision in the case of FI-WARE specifications. I'm very interesting to hear others' feedback on my reasoning. Cheers, -- Juanjo BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : mercredi 29 mai 2013 08:27 ? : Juanjo Hierro Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Thanks for putting this together. I have one comment regarding the catalogue. I know that there are several critical changes (including updated 'Terms and Conditions') which are still pending approval for many months (in fact, we failed to deliver on time on the corresponding checkpoint due to this 4 months delay). Would be good to take care of this early enough. In particular, I would recommend removing the approval process altogether. This is an unnecessary bottleneck, which prevents timely updates, and makes the catalogue less relevant. We don't have any approvals/moderation in all the other information sources -- I don't see why this should be different here. Handling reviews and updates in a regular way might be much more efficient, IMO. Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro > To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 29/05/2013 09:11 AM Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 May 30 08:48:18 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 May 2013 08:48:18 +0200 Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: References: <51A59C2D.90605@tid.es> Message-ID: <51A6F632.3090101@tid.es> On 29/05/13 08:26, Alex Glikson wrote: Thanks for putting this together. I have one comment regarding the catalogue. I know that there are several critical changes (including updated 'Terms and Conditions') which are still pending approval for many months (in fact, we failed to deliver on time on the corresponding checkpoint due to this 4 months delay). Would be good to take care of this early enough. In particular, I would recommend removing the approval process altogether. This is an unnecessary bottleneck, which prevents timely updates, and makes the catalogue less relevant. We don't have any approvals/moderation in all the other information sources -- I don't see why this should be different here. Handling reviews and updates in a regular way might be much more efficient, IMO. As mentioned in my response to Thierry, I have asked Miguel to come with a proposal for avoiding bottlenecks. Cheers, -- Juanjo Regards, Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Juanjo Hierro To: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" , Date: 29/05/2013 09:11 AM Subject: [Fiware-wpl] Cockpit document for REHEARSAL of the 2nd year review Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx_______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu May 30 08:57:43 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 May 2013 08:57:43 +0200 Subject: [Fiware-wpl] [Fiware-wpa] Cockpit document for REHEARSAL of the 2nd year review In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD6646109ACA8@DEWDFEMB11A.global.corp.sap> References: <51A59C2D.90605@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD6646109ACA8@DEWDFEMB11A.global.corp.sap> Message-ID: <51A6F867.70305@tid.es> On 29/05/13 08:28, Sandfuchs, Thorsten wrote: Hi Juanjo, 1. The agenda is not editable - my comment for the chapter specific parts was to have the rough guidance: ? major achievement on external and FI-PPP internal use ? availability of our components (FI-PPP & FI-PPP external) ? changes in FI-WARE v2 ? plans for rest of 2013 (OIL ...) Fixed. Please add this topics as feedback in the proper places. 2. we need the Attendance list (for the SAP premises) - therefore please integrate a list where people can subscribe if they are present on the rehersal part on Tuesday. Miguel has added that. 3. as you mention the catalogue in the Draft agenda, I was just writing an email to Miguel (who is on business trip) I tend to recommend to Markus to push the partners of WP3 to update the catalogue in relation to R2.2 - currently there are only a limited number of GEs presented, which do not match the numbers given in the Testbed Usage Table. But on the other hand you mentioned, that there might be a ton of "moderation" requests pending and that we need to rethink the complete approach. Can you perhaps elaborate to us how to go forward with it? Should we approach the partners? It's easy to agree to the goal: having a reasonable well documented catalogue for the review and the webinars - but how can we make this happen as a group? Our commitment should be to have the entries for GEis in Release 2 ready and perfect in the Catalogue by the end of July. We should explain that at the review to justify we may not have all of them ready at the time of the review. Given said that, it would be nice to show that we are "on the process" and show that this has actually happened for some but not necessarily all of the new GEis in the FI-WARE Catalogue for our next review. I hope that, engaging the WPLs in the task, we will be able to achieve this goal. Summary: let's launch the task force for this regarding all the GEis, but with the commitment from all WPLs to get the task completed for at least one new GEi in their chapter before the review. This should be achievable. Because I believe that your comments are meaningful for the rest, I copy them directly in my response. I hope this is not an issue for you. I'm doing it for the sake of efficiency. Best regards, -- Juanjo Thanks for shedding a light. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Mittwoch, 29. Mai 2013 08:12 To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Cockpit document for REHEARSAL of the 2nd year review Hi all, I have elaborated the following document on Google docs that should help us to prepare our 2nd year project review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/edit?usp=sharing As a first input, you will see a proposed agenda. Please provide comments, etc. PLEASE send any email on discussion, questions, proposals about the reharsal to fiware-wpl and fiware-wpa writing REHEARSAL on the subject. Your constructive comments, feedback, etc. are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 May 30 13:32:10 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 30 May 2013 13:32:10 +0200 Subject: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.8.1.2 Open Specifications (WP8 - Security Chapter) In-Reply-To: <51A73821.4010708@tid.es> References: <51A73821.4010708@tid.es> Message-ID: <51A738BA.2000000@tid.es> FYI, please find attached the official submission of the FI-WARE GE Open Specifications from the Security chapter. I would like to call your attention regarding the issue with the IdM GE. Make sure that you are not facing a similar situation in your chapter/WP. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.8.1.2 Open Specifications (WP8 - Security Chapter) Date: Thu, 30 May 2013 13:29:37 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom 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: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, Pascal Bisson , "daniel.gidoin at thalesgroup.com" , "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of D.8.1.2 Open Specifications (WP8 - Security Chapter). You can download the corresponding file from the following link: * https://forge.fi-ware.eu/docman/view.php/7/2504/D.8.1.2+FI-WARE+GE+Open+Specifications+-+Security+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. We accompany the public open specs above with the following API specifications of the Identity Management GE provided by Deutsche Telekom AG (DT) which are still currently kept private by DT (therefore, you can only download once you have logged in your account in FusionForge): * https://forge.fi-ware.eu/docman/view.php/7/2503/IdM+GE+by+DT+-+GCP+API+documentation_v0-3.docx Regarding this API specification of the IdM GE provided by DT, it is unclear to us whether DT is delivering the IdM GE API specification as a public and royalty-free specification or not. Note that part of the RESTful API to be supported by the IdM GE may comply with some standard specifications (e.g., RESTful API definition for OAuth 2.0), but there are other parts for which such a correspondence with a standard may not exist. Those parts definitively need to be specified and be made public and royalty-free as FI-WARE GE Open Specifications. Consequently: * we have formulated that question to DT and we are still waiting for their answer * we have informed DT that if a FI-WARE GE API is not delivered to be made public and royalty-free, we consider this an infringement of the contract, this unless the EC does have a different interpretation * since we haven't received any response from DT yet, we cannot release the IdM GE API specifications publicly and we are providing it private, in case that reviewers wish to carry out a review of the specs while a definitive answer arrives from DT The above has been made in sync with Thales, as leader of the WP. Last but not least, it is also unclear what the situation is regarding the Identity Management GE implementation provided by NSN. Concretely: * it is unclear whether NSN will align their API specs with those specified by DT * it is also unclear whether NSN will provide their API specs as public and royalty-free We are also working together with Thales, as leader of the WP, to clarify the situation regarding the Identity Management GE implementation provided by NSN. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Thu May 30 17:01:55 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 30 May 2013 15:01:55 +0000 Subject: [Fiware-wpl] webinars - please, status and links Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890516D0@EX10-MB2-MAD.hi.inet> Dear Partners, Let me bother you with some relevant info about the webinars. I hope I'm able to write a guideline with all details next days. Meanwhile, please, take into considerations two additional comments: ? I'll mark green webinars scheduled for today, when you're done please mark them blue, and inform the number of attendees, as shown in the snapshot below. ? Additionally, please, inform the links to the slides and recording on columns T and U, see snapshot below Thanks for nice cooperation!! Kind regards, Manuel [cid:image001.png at 01CE5D57.60A46ED0] [cid:image002.png at 01CE5D57.60A46ED0] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 17893 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 15078 bytes Desc: image002.png URL: From mev at tid.es Thu May 30 17:49:51 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 30 May 2013 15:49:51 +0000 Subject: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8905173D@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: ? Close the backlog items finished during M25 (if not already done) ? Update items under execution not finished to belong to S2.3.3 ? Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: ? Bug is available as entry type - theme isn't available anymore ? You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. ? You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully ? All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdps at tid.es Fri May 31 08:54:45 2013 From: jdps at tid.es (JAVIER DE PEDRO SANCHEZ) Date: Fri, 31 May 2013 06:54:45 +0000 Subject: [Fiware-wpl] FI-WARE: : First version of Periodic Report M13-M24 Message-ID: <77A22C1085494D48B4018F06A40DB2C72FA43384@EX10-MB2-MAD.hi.inet> Dear all, as you know, we are trying to close as soon as possible the periodic report. I've just received updates from SAP (WP1, WP2, WP3, WP8, WP9, WP10, WP11 & WP12) and TRDF (WP2, WP4, WP7 & WP10) about their consolidated effort, so please have a look of the involved WP that have been updated. [cid:image001.png at 01CE5DDC.17AA5430] [cid:image002.png at 01CE5DDC.17AA5430] [cid:image003.png at 01CE5DDC.17AA5430] [cid:image004.png at 01CE5DDC.17AA5430] [cid:image005.png at 01CE5DDC.78BCA3E0] [cid:image006.png at 01CE5DDC.78BCA3E0] [cid:image007.png at 01CE5DDC.78BCA3E0] [cid:image008.png at 01CE5DDC.78BCA3E0] [cid:image009.png at 01CE5DDC.78BCA3E0] [cid:image010.png at 01CE5DDC.78BCA3E0] If it is needed, send me and updated periodic report of your WP today. BR Javier. De: JAVIER DE PEDRO SANCHEZ Enviado el: martes, 28 de mayo de 2013 2:12 Para: 'fiware-wpl at lists.fi-ware.eu' CC: subsidies at tid.es Asunto: FI-WARE: : First version of Periodic Report M13-M24 Importancia: Alta Dear all, First, thank you very much for your contribution. Please find attached the first version of the integrated Periodic Report of M24. I kindly ask you to review it. If you have something in yellow in your WP, please update it. If you see something to be updated of another WP, please contact with the WPL directly. We?ll only accept changes from WPL of each own WP. Please, send your updates before next Thursday 30th of May, EOB. (It is very important to use the activated track change control) Next Friday, it will be update with your last versions and it will be reviewed by the Coordinator in order to deliver the final version next week. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 32093 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 55351 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 37397 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 27958 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 42480 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 31882 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 30760 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 66060 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 53412 bytes Desc: image009.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 62471 bytes Desc: image010.png URL: From mev at tid.es Fri May 31 09:06:21 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 31 May 2013 07:06:21 +0000 Subject: [Fiware-wpl] webinars scheduled today Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89051A22@EX10-MB2-MAD.hi.inet> Dear Partners, Let me remind you of the webinars scheduled today belonging to CLOUD (Alex), DATA(Sergio) and SECURITY(Pascal). Sergio, please, be aware LOCS hashtag is not complete. Please, pay attention to advertise them on twitter by addressing them to FIWARE: . at FIWARE - don't forget neither the leading dot, nor the hashtag in the message. Pascal, I miss information about PPL/SAP, which was scheduled for yesterday. Has taken place? If anything, please, let me know. Kind regards, Manuel [cid:image002.png at 01CE5DDD.3AAC9EB0] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 37037 bytes Desc: image002.png URL: From jhierro at tid.es Fri May 31 11:55:15 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 31 May 2013 11:55:15 +0200 Subject: [Fiware-wpl] IMPORTANT: Dedicated review preparation during afternoon session of our joint WPLs/WPAs confcall this morning Message-ID: <51A87383.7090309@tid.es> Hi all, DT, part of the Security team that we needed for running the follow-up confcall regarding the OAuth2-based Access Control framework, will not be available for joining us this next monday. Therefore, we will devote the whole afternoon session to the work on preparation of the review meeting that is soon approaching. We may also spend some time during the morning session to preparation of the review if we managed to cover the other topics earlier. Therefore, attendance of all WPLs is absolutely mandatory this time for both sessions. As suggested, please bring feedback in the google docs we setup for gathering info about the review: https://docs.google.com/document/d/1oPxdD2fD7RjMH-AuETYY1r2IL3G0_m0kXiYHt5As5g4/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) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Fri May 31 12:11:15 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 31 May 2013 10:11:15 +0000 Subject: [Fiware-wpl] webinar guidelines - first draft Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B89051AF1@EX10-MB2-MAD.hi.inet> Dear Partners, Please, have the link to the webinars guidelines. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_inform_and_adversite_webinars_of_GE This way you have aggregated all relevant information to take into account when informing and advertising the webinars. Please, take into consideration it is the first draft, therefore, feedback or advice on how to improve it is appreciated. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri May 31 15:35:18 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 31 May 2013 15:35:18 +0200 Subject: [Fiware-wpl] Attendee list and ID numbers Message-ID: <51A8A716.8050409@tid.es> Dear all, After receving a complaint from SAP I have decided to delete the column with the ID numbers. I have kept a private copy of the ones already on the table so I do not need to collect those. If anyone else adds his name on the table let me know and send me your ID number (or passport) privately 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