From pascal.bisson at thalesgroup.com Mon Oct 3 09:02:40 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 3 Oct 2011 09:02:40 +0200 Subject: [Fiware-security] FI-WARE WP8 Audio-conf (30-09-2011) Minutes Message-ID: <8159_1317625366_4E895E16_8159_5086_1_d02ae7f7-edfb-43c8-ab30-727d80c3b928@THSONEA01HUB01P.one.grp> Dear All, Short minutes of our audio conf of last Friday. Thanks to Michael (IBM), Robert (NSN), Slim (SAP), Richard (TRT-UK), Wolfgang (DT) , Antonio (ATOS) to have attended it. ? FI-WARE wiki has now been moved to the Fusion Forge (see Wikimedia button on upper right when accessing the FI-WARE Project on the Forge) o As such Wiki media is now accessible to all. In case of any problems accessing it please drop and email to Pascal and Daniel o Access was checked for participants to our audio. ? Features backlog o Features backlog per Generic Enabler has now to be entered on the Wiki (accessible from the Forge - aka Wikimedia). ? This has to be performed (based on entries collected so far) by each of the task leads and under their control as well as the one of WPL and Caretakers ? Security Monitoring GE backlog -> Daniel ? Core Generic Enablers backlog -> Robert ? Context-based Security & Compliance -> Antonio ? Optional Generic Enablers -> Slim ? For each of the backlog we should end up with a number of EPICS and some initial user-stories. o Features backlogs for each of the WP8 Generic enablers (so T8.1, T8.2, T8.3 and T8.4) is due on the wiki by Monday 3rd (EOB). ? [Pascal: to drop an email to Juanjo for Robert and Slim to have rights requested to edit their entries to the features backlog for what concerns their enablers] ? Update of Security Chapter o Each of the task leads should proceed with update of their session (related to GE in scope of their task) as soon as possible and whenever it becomes to have it addressed (i.e. as soon as M2 deliverable security chapter content would have been moved to the Wiki on the Forge) ? Each of some would have to proceed here with the changes & updates requested with respect to previous version of their section (as per M2 deliverable - aka 1st release of HLA description) and contribute new content/elements requested for M5 update of Product Vision document (mainly information about the assets identified and selected to become part of the initial software baseline for Year 1 reference implementation of FI-WARE platform) o Initial update of the various sections performed by GEs' owners and task leads is expected by Monday 3rd (EOB) and supposed to be completed if not that day, the day after Tuesday 4th (EOB). This being said all elements have already been produced by each of the task leads (including now T8.2) to have it done. This is just a matter to report this content to the Wiki. o WPL/WPA together with full support of their caretakers to Caretakers to check, assess the update work performed and proceed to any additional changes which might be requested for M5. ? Update of the text for M5 on Core Generic enablers o Text has been produced and released by NSN (Robert) together with IBM (Micahel) and distributed to the WP8 mailing list. o Being said this would be the one to be reported for M5 regarding T8.2 Generic enablers it is requested that each of the partners reviews that text and provide to Robert any comments/suggested changes he may have. This has to be done asap and by Monday 3rd (12am at the latest). So far only Thales (ThereSIS) provided some feedback... ? Next audios o Audio next Friday confirmed so October 7th (10am-12am) o Pascal may organize an audio conf mid of next week in case work for M5 update of HLA (Product Vision Document) and/or Security GEs' backlogs wouldn't have been achieved as expected. ? REMINDER: for INRIA and FT-Orange o It is important for you to join our weekly audios on WP8. I can understand you miss some of them but not all of them. So please take necessary steps to join or find a replacement in case you couldn't attend. Also inform me and Daniel in that case. ? Virtual meeting between WP8 and Use Case projects to discuss enablers in scope of T8.2 (aka Generic enablers on Idmgt, Privacy, Data control) o Pascal waiting for T8.2 availability dates to have them communicated to Juanjo (CA) to set final date and make announcement ? Robert to organize a doodle for that ? Apart from T8.2 Lead and task partners, Pascal call also for each of the other task leads to be present at this Virtual meeting. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sarah.Pennington at uk.thalesgroup.com Mon Oct 3 17:30:34 2011 From: Sarah.Pennington at uk.thalesgroup.com (Pennington, Sarah) Date: Mon, 3 Oct 2011 16:30:34 +0100 Subject: [Fiware-security] FI-WARE T8.4 Backlog Message-ID: Slim, Please find attached the basic backlog entry for the Content-based Security Asset from Thales. Do you need any thing else from us? Do you need any input for the architecture document? Regards, Sarah <> Sarah Pennington Senior Engineer, Research & Technology Thales UK Worton Drive, Reading, Berkshire, RG2 0SB www.thalesgroup.com/uk Tel: +44 (0)118 923 8248. Fax: +44 (0) 118 923 8399. e-mail: sarah.pennington at thalesgroup.com Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Backlog entries_content-based_security.xls Type: application/vnd.ms-excel Size: 44032 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Tue Oct 4 09:16:06 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 4 Oct 2011 09:16:06 +0200 Subject: [Fiware-security] TR: Security chapter within FI-WARE Product Vision available on the Wiki Message-ID: <10128_1317712570_4E8AB2BA_10128_15070_1_d1faaaef-fe8d-4e6a-8f23-a04f611d026b@THSONEA01HUB03P.one.grp> FYI. Please ALL task leads proceed now with the update of your sections this with support of member of your teams and especially Generic Enablers owners. Will review updated content once done. This together with Security Caretakers. Will also provide you with the template for the description of assets as soon as I get it from Juajno. Best Regards, Pascal -----Message d'origine----- De?: Juanjo Hierro [mailto:jhierro at tid.es] Envoy??: mardi 4 octobre 2011 08:29 ??: BISSON Pascal; GIDOIN Daniel Objet?: Security chapter within FI-WARE Product Vision available on the Wiki Hi, I have finished uploading contents of the Security Chapter in the Product Vision chapter of the FI-WARE public Wiki You are now allowed to update its contents. I will send a template for the description of assets during today. Cheers, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Oct 4 09:20:01 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 04 Oct 2011 09:20:01 +0200 Subject: [Fiware-security] TR: Security chapter within FI-WARE Product Vision available on the Wiki In-Reply-To: <10128_1317712570_4E8AB2BA_10128_15070_1_d1faaaef-fe8d-4e6a-8f23-a04f611d026b@THSONEA01HUB03P.one.grp> References: <10128_1317712570_4E8AB2BA_10128_15070_1_d1faaaef-fe8d-4e6a-8f23-a04f611d026b@THSONEA01HUB03P.one.grp> Message-ID: <4E8AB3A1.2000500@tid.es> Hi, In order to avoid collisions, please update each section by clicking on the "Edit" button you will see at the right hand side of the Wiki page for each section. Do not edit the entire Wiki page for the Chapter because that would collide with people editing a specific section. Just standard Wiki rules you probably already know but always is worth reminding. Thanks, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 04/10/11 09:16, BISSON Pascal wrote: > FYI. > > Please ALL task leads proceed now with the update of your sections this with support of member of your teams and especially Generic Enablers owners. > > Will review updated content once done. This together with Security Caretakers. > > Will also provide you with the template for the description of assets as soon as I get it from Juajno. > > > Best Regards, > > Pascal > > -----Message d'origine----- > De : Juanjo Hierro [mailto:jhierro at tid.es] > Envoy? : mardi 4 octobre 2011 08:29 > ? : BISSON Pascal; GIDOIN Daniel > Objet : Security chapter within FI-WARE Product Vision available on the Wiki > > Hi, > > I have finished uploading contents of the Security Chapter in the > Product Vision chapter of the FI-WARE public Wiki > > You are now allowed to update its contents. > > I will send a template for the description of assets during today. > > Cheers, > > -- > Juanjo Hierro > Chief Technologist on Software Technologies > Telefonica R&D Labs > > email: jhierro at tid.es > phone: +34 91 48 32932 > www.tid.es > twitter.com/JuanjoHierro > > Oeste 1, Planta 5. Distrito C > Ronda de la Comunicacion s/n > Madrid 28050 > Spain > > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its 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 From pascal.bisson at thalesgroup.com Tue Oct 4 13:59:38 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 4 Oct 2011 13:59:38 +0200 Subject: [Fiware-security] Security Wiki Update (Features backlog + update of content for M5) Message-ID: <1450_1317729582_4E8AF52E_1450_11456_1_26cf079e-590b-4b92-9722-519d5cd0a2fa@THSONEA01HUB04P.one.grp> Dear WP8 task leads, Could you please urgently add your entries to the Security features backlog you can access from the Wiki on the Forge. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog So far I see only entries coming from T8.3 and attached to Context-based and compliance GE. Thanks Antonio ! Remember that Security entries to the Features backlog were expected to be already performed (since deadline was set 03/10/11 EOB). So please Daniel, Robert and Slim upload entries attached to you enablers (don't forget to precise their type and remember we should go for EPICS, features and User-Stories) Regarding M2 update for M5 I would also urge you to have it performed. Being said M2 content is there https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security and you can proceed with your changes/updates you want to be implemented for M5 to reflect progress achieved. Regarding description of assets attached to each of the GEs I'm still waiting for the template promised by Juanjo and will forward it to you once received. Presumably this afternoon. So stay tuned. Last but not least please drop me an email when * Entries to the features backlog for GEs attached to your task have been performed, * You have finished to update M2 content on the Wiki for M5 Hearing from and waiting for your notifications. Best Regards, PAscal -------------- next part -------------- An HTML attachment was scrubbed... URL: From slim.trabelsi at sap.com Tue Oct 4 14:08:10 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Tue, 4 Oct 2011 14:08:10 +0200 Subject: [Fiware-security] Security Wiki Update (Features backlog + update of content for M5) In-Reply-To: <1450_1317729582_4E8AF52E_1450_11456_1_26cf079e-590b-4b92-9722-519d5cd0a2fa@THSONEA01HUB04P.one.grp> References: <1450_1317729582_4E8AF52E_1450_11456_1_26cf079e-590b-4b92-9722-519d5cd0a2fa@THSONEA01HUB04P.one.grp> Message-ID: Hi Pascal, I Already started adding the Task8.4 entries BR Slim From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mardi 4 octobre 2011 14:00 To: Antonio Garcia Vazquez; GIDOIN Daniel; Seidl, Robert (NSN - DE/Munich); TRABELSI, Slim Cc: BISSON Pascal; Michael Osborne; Fiware-security at lists.fi-ware.eu Subject: Security Wiki Update (Features backlog + update of content for M5) Importance: High Dear WP8 task leads, Could you please urgently add your entries to the Security features backlog you can access from the Wiki on the Forge. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog So far I see only entries coming from T8.3 and attached to Context-based and compliance GE. Thanks Antonio ! Remember that Security entries to the Features backlog were expected to be already performed (since deadline was set 03/10/11 EOB). So please Daniel, Robert and Slim upload entries attached to you enablers (don't forget to precise their type and remember we should go for EPICS, features and User-Stories) Regarding M2 update for M5 I would also urge you to have it performed. Being said M2 content is there https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security and you can proceed with your changes/updates you want to be implemented for M5 to reflect progress achieved. Regarding description of assets attached to each of the GEs I'm still waiting for the template promised by Juanjo and will forward it to you once received. Presumably this afternoon. So stay tuned. Last but not least please drop me an email when * Entries to the features backlog for GEs attached to your task have been performed, * You have finished to update M2 content on the Wiki for M5 Hearing from and waiting for your notifications. Best Regards, PAscal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Oct 4 14:09:20 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 4 Oct 2011 14:09:20 +0200 Subject: [Fiware-security] Security Wiki Update (Features backlog + update of content for M5) In-Reply-To: References: <1450_1317729582_4E8AF52E_1450_11456_1_26cf079e-590b-4b92-9722-519d5cd0a2fa@THSONEA01HUB04P.one.grp> Message-ID: <1450_1317730162_4E8AF772_1450_12022_1_875bdf8b-0033-4ea4-ba53-ab8535f97848@THSONEA01HUB01P.one.grp> Yes I noticed things were engaged from your side ... so thanks ! De : TRABELSI, Slim [mailto:slim.trabelsi at sap.com] Envoy? : mardi 4 octobre 2011 14:08 ? : BISSON Pascal; Antonio Garcia Vazquez; GIDOIN Daniel; Seidl, Robert (NSN - DE/Munich) Cc : Michael Osborne; Fiware-security at lists.fi-ware.eu Objet : RE: Security Wiki Update (Features backlog + update of content for M5) Hi Pascal, I Already started adding the Task8.4 entries BR Slim From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mardi 4 octobre 2011 14:00 To: Antonio Garcia Vazquez; GIDOIN Daniel; Seidl, Robert (NSN - DE/Munich); TRABELSI, Slim Cc: BISSON Pascal; Michael Osborne; Fiware-security at lists.fi-ware.eu Subject: Security Wiki Update (Features backlog + update of content for M5) Importance: High Dear WP8 task leads, Could you please urgently add your entries to the Security features backlog you can access from the Wiki on the Forge. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog So far I see only entries coming from T8.3 and attached to Context-based and compliance GE. Thanks Antonio ! Remember that Security entries to the Features backlog were expected to be already performed (since deadline was set 03/10/11 EOB). So please Daniel, Robert and Slim upload entries attached to you enablers (don't forget to precise their type and remember we should go for EPICS, features and User-Stories) Regarding M2 update for M5 I would also urge you to have it performed. Being said M2 content is there https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security and you can proceed with your changes/updates you want to be implemented for M5 to reflect progress achieved. Regarding description of assets attached to each of the GEs I'm still waiting for the template promised by Juanjo and will forward it to you once received. Presumably this afternoon. So stay tuned. Last but not least please drop me an email when ? Entries to the features backlog for GEs attached to your task have been performed, ? You have finished to update M2 content on the Wiki for M5 Hearing from and waiting for your notifications. Best Regards, PAscal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Oct 5 10:53:13 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 5 Oct 2011 10:53:13 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Instructions on how to proceed with assets soon Message-ID: <11808_1317804794_4E8C1AFA_11808_3304_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AAEB0AE@THSONEA01CMS04P.one.grp> FYI. Stay tuned ! -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy??: mercredi 5 octobre 2011 10:52 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] Instructions on how to proceed with assets soon Hi all, In less than one hour, I will provide detailed instructions on how to incorporate information about the assets and continue with the task regarding recording of entries the FI-WARE Backlogs. It will imply certain re-arrangements on the Wiki, so maybe it's worth that you stop any editing on the Wiki until the detailed instructions come. Apologize for any inconvenience this may cause. Please, be patient. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From pascal.bisson at thalesgroup.com Wed Oct 5 13:48:48 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 5 Oct 2011 13:48:48 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Message-ID: <27199_1317815333_4E8C4425_27199_18223_1_dea46dee-b516-459a-86ba-f1b9635cd5d2@THSONEA01HUB03P.one.grp> Hi all, Please find below the detailed instructions I got from TID (Juanjo) on how to proceed regarding description of assets. Note that they have also decided to change the structure based on which references to Wiki pages containing full description of entries in the backlogs will be found. So first please check. Second, I urge each of the task leads to complete asap update of their sections of the Security Chapter according to enablers they cover. This has to be done with full support of GE owners and member of their teams. As requested yesterday I also ask them to drop me an email once done. So counting on you and them catch up on this requests asap. Regarding description of assets, I'd like also each of the team leaders to drive the process at the level of their team to get everything done by Thursday (tomorrow) EOB. Please be aware that info you upload to the Wiki will be publicly available in the meantime bear in mind it has to be meaningful to the reader (and first and foremost Use Case Project). For information necessary to our shared understanding and that you don't want to expose to rest of the world let me inform you that there should be another wiki to be set-up for that. We will review status on our WP8 weekly audio-conf this Friday (10am-12am) . Those who are unable to attend should send an email reporting what the status of their task with respect to uploading info on the Wiki (contribution to Features backlog + contribution to the update of the Security chapter changes + assets description) 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 Juanjo Hierro Envoy? : mercredi 5 octobre 2011 12:02 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Thu Oct 6 09:58:49 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 6 Oct 2011 09:58:49 +0200 Subject: [Fiware-security] [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <4E8C887F.5040300@tid.es> References: <4E8C2AFB.2020302@tid.es> <4E8C887F.5040300@tid.es> Message-ID: <25065_1317887930_4E8D5FBA_25065_8613_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AB37AC7@THSONEA01CMS04P.one.grp> Dear Juanjo, This just to confirm that I have received your email and instructed the Security team accordingly. At tomorrow's WP8 follow-up audio conf I will assess progress achieved by the Security Team according to new instructions given. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 5 octobre 2011 18:41 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi, I would like that each and every WPL send me an email confirm that he has received and processed the email I sent this morning and has planned the corresponding actions. So far, I haven't seen any change on the Wiki and I still see people working in the old (to be deprecated) "FI-WARE Backlog" chapter. Looking forward your responses, Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain On 05/10/11 12:01, Juanjo Hierro wrote: Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 antonio.garcia at atosresearch.eu Thu Oct 6 17:58:48 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Thu, 6 Oct 2011 17:58:48 +0200 Subject: [Fiware-security] [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <27199_1317815333_4E8C4425_27199_18223_1_dea46dee-b516-459a-86ba-f1b9635cd5d2@THSONEA01HUB03P.one.grp> References: <27199_1317815333_4E8C4425_27199_18223_1_dea46dee-b516-459a-86ba-f1b9635cd5d2@THSONEA01HUB03P.one.grp> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033613A6@INTMAIL02.es.int.atosorigin.com> Hello, I?ve already update FI-WARE Wiki with the information about Assets and Backlog (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Security_in_FI-WARE) Please have a look to check everything is Ok Additionally there are some pending subchapters that I need your help (Daniel & Slim) to fill them: 1) Fragmento asset: Details in ?Programming artifacts? and ?Runtime pre-requisites? 2) Governance Dashboard: Details in ?Programming artifacts? 3) CRLT: Details in ?Programming artifacts? and ?Runtime pre-requisites? 4) USDL-SEC: Details in: ?Programming artifacts?, ?Technologies used? and ?Runtime pre-requisites? Best Regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mi?rcoles, 05 de octubre de 2011 13:49 To: Fiware-security at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); GIDOIN Daniel; LELEU Philippe Subject: TR: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Importance: High Hi all, Please find below the detailed instructions I got from TID (Juanjo) on how to proceed regarding description of assets. Note that they have also decided to change the structure based on which references to Wiki pages containing full description of entries in the backlogs will be found. So first please check. Second, I urge each of the task leads to complete asap update of their sections of the Security Chapter according to enablers they cover. This has to be done with full support of GE owners and member of their teams. As requested yesterday I also ask them to drop me an email once done. So counting on you and them catch up on this requests asap. Regarding description of assets, I?d like also each of the team leaders to drive the process at the level of their team to get everything done by Thursday (tomorrow) EOB. Please be aware that info you upload to the Wiki will be publicly available in the meantime bear in mind it has to be meaningful to the reader (and first and foremost Use Case Project). For information necessary to our shared understanding and that you don?t want to expose to rest of the world let me inform you that there should be another wiki to be set-up for that. We will review status on our WP8 weekly audio-conf this Friday (10am-12am) . Those who are unable to attend should send an email reporting what the status of their task with respect to uploading info on the Wiki (contribution to Features backlog + contribution to the update of the Security chapter changes + assets description) 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 Juanjo Hierro Envoy? : mercredi 5 octobre 2011 12:02 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonio.garcia at atosresearch.eu Thu Oct 6 18:19:59 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Thu, 6 Oct 2011 18:19:59 +0200 Subject: [Fiware-security] [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <27199_1317815333_4E8C4425_27199_18223_1_dea46dee-b516-459a-86ba-f1b9635cd5d2@THSONEA01HUB03P.one.grp> References: <27199_1317815333_4E8C4425_27199_18223_1_dea46dee-b516-459a-86ba-f1b9635cd5d2@THSONEA01HUB03P.one.grp> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033613BB@INTMAIL02.es.int.atosorigin.com> Robert, See attached STORK information (Backlog-EPIC and Asset) to be uploaded in WP8.2 FI-WARE Wiki. Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mi?rcoles, 05 de octubre de 2011 13:49 To: Fiware-security at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); GIDOIN Daniel; LELEU Philippe Subject: TR: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Importance: High Hi all, Please find below the detailed instructions I got from TID (Juanjo) on how to proceed regarding description of assets. Note that they have also decided to change the structure based on which references to Wiki pages containing full description of entries in the backlogs will be found. So first please check. Second, I urge each of the task leads to complete asap update of their sections of the Security Chapter according to enablers they cover. This has to be done with full support of GE owners and member of their teams. As requested yesterday I also ask them to drop me an email once done. So counting on you and them catch up on this requests asap. Regarding description of assets, I?d like also each of the team leaders to drive the process at the level of their team to get everything done by Thursday (tomorrow) EOB. Please be aware that info you upload to the Wiki will be publicly available in the meantime bear in mind it has to be meaningful to the reader (and first and foremost Use Case Project). For information necessary to our shared understanding and that you don?t want to expose to rest of the world let me inform you that there should be another wiki to be set-up for that. We will review status on our WP8 weekly audio-conf this Friday (10am-12am) . Those who are unable to attend should send an email reporting what the status of their task with respect to uploading info on the Wiki (contribution to Features backlog + contribution to the update of the Security chapter changes + assets description) 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 Juanjo Hierro Envoy? : mercredi 5 octobre 2011 12:02 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Stork.zip Type: application/x-zip-compressed Size: 52880 bytes Desc: Stork.zip URL: From daniel.gidoin at thalesgroup.com Fri Oct 7 10:02:50 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 7 Oct 2011 10:02:50 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <4E8EABF5.5000206@tid.es> References: <4E8EABF5.5000206@tid.es> Message-ID: <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: * read the FI-WARE Product Vision, in order to understand what is overall expected for the GE * read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there * read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 7 11:22:02 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 11:22:02 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> Message-ID: <4E8EC4BA.7020602@tid.es> Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: * read the FI-WARE Product Vision, in order to understand what is overall expected for the GE * read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there * read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 robert.seidl at nsn.com Fri Oct 7 11:27:44 2011 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 7 Oct 2011 11:27:44 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <4E8EC4BA.7020602@tid.es> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: * read the FI-WARE Product Vision, in order to understand what is overall expected for the GE * read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there * read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 pedro.soria at atosresearch.eu Fri Oct 7 11:29:44 2011 From: pedro.soria at atosresearch.eu (Pedro Soria Rodriguez) Date: Fri, 7 Oct 2011 11:29:44 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> Message-ID: <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> Hello, I?d like to support Robert and Daniel. In WP8, we at Atos are also concerned about the public visibility of the backlog. The backlog aids development, but development is a task of the consortium, and public visibility is not needed. -- Pedro Soria-Rodriguez Head of Sector Atos Research & Innovation Albarrac?n, 25 28037 Madrid, Spain Email: pedro.soria at atosresearch.eu From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: Friday, October 07, 2011 11:28 To: ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: 1. read the FI-WARE Product Vision, in order to understand what is overall expected for the GE 2. read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there 3. read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From slim.trabelsi at sap.com Fri Oct 7 11:35:26 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Fri, 7 Oct 2011 11:35:26 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> Message-ID: Dear all, I agree with Daniel?s issue. As far as I know according to the consortium agreement SAP development information is not public. Thank you Best regards Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Pedro Soria Rodriguez Sent: vendredi 7 octobre 2011 11:30 To: Seidl, Robert (NSN - DE/Munich); ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hello, I?d like to support Robert and Daniel. In WP8, we at Atos are also concerned about the public visibility of the backlog. The backlog aids development, but development is a task of the consortium, and public visibility is not needed. -- Pedro Soria-Rodriguez Head of Sector Atos Research & Innovation Albarrac?n, 25 28037 Madrid, Spain Email: pedro.soria at atosresearch.eu From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: Friday, October 07, 2011 11:28 To: ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: 1. read the FI-WARE Product Vision, in order to understand what is overall expected for the GE 2. read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there 3. read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Fri Oct 7 11:44:27 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 7 Oct 2011 11:44:27 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> Message-ID: <4393_1317980669_4E8EC9FD_4393_14639_1_bb8e0cd1-62e4-4d3c-855d-4846b7869f98@THSONEA01HUB04P.one.grp> Thank a lot Pedro and Robert! We cannot let a major problem for industrial partners. Daniel De : Pedro Soria Rodriguez [mailto:pedro.soria at atosresearch.eu] Envoy? : vendredi 7 octobre 2011 11:30 ? : Seidl, Robert (NSN - DE/Munich); ext Juanjo Hierro; GIDOIN Daniel Cc : fiware-security at lists.fi-ware.eu Objet : RE: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hello, I?d like to support Robert and Daniel. In WP8, we at Atos are also concerned about the public visibility of the backlog. The backlog aids development, but development is a task of the consortium, and public visibility is not needed. -- Pedro Soria-Rodriguez Head of Sector Atos Research & Innovation Albarrac?n, 25 28037 Madrid, Spain Email: pedro.soria at atosresearch.eu From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: Friday, October 07, 2011 11:28 To: ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: 1. read the FI-WARE Product Vision, in order to understand what is overall expected for the GE 2. read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there 3. read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 7 12:01:59 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 07 Oct 2011 12:01:59 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> Message-ID: <4E8ECE17.5000509@tid.es> Dear folks, Let me start making one thing clear: the FI-WARE Backlog is setup as a PUBLIC deliverable in the DoW. So I'm afraid you are wrong. Nevertheless, as I have explained, you can deal with managing private and public info in the detailed description of backlogs entries. So I don't see any issue. Please take into account that the backlog itself, as well as some info in the detail description of each entry has to be shared with users. That's a fundamental principle setup for this program (in different parts of the DoW) but also a fundamental principle in Agile (which was agreed in the DoW as method to manage the development process). How the hell are they otherwise going to know what you intend to provide as functionality to them so that they can confirm it covers their needs or provide comments? Take into account, in addition, that the aim of the program is that not just UC projects may join to provide requirements and try to use FI-WARE but other Application Developer Communities as well. Again, this is in the DoW. As per description of the asset, what we are proposing is a pragmatic approach to avoid that partners had to develop too much paperwork. Since we do not start from the scratch but really rely on already developed assets, we have to create a snapshot where we provide to the users the following information: * Detailed description of what we already have developed regarding a given GE (i.e., it is implemented in the assets) * What our current roadmap in terms of development is regarding the GE: this is what goes as backlog Point was how to deal with the first point without creating too much paperwork. Partners bringing assets didn't want to deal with all the burden of documenting something they have ... documented before, in the project where the asset considered as baseline was developed. Nothing to say about dealing with the useless task of translating documents they may have into "FI-WARE branded" documents. That would be rather painful. So we agreed on a trade off, quite straightforward to implement while still useful: We will provide publicly available info of each asset that is already bring the implementation of part of the functionality of the GE (programmers manuals, publicly available documentation, etc.) and then the user shall be able to figure out what is the full functionality of the GE in more detail by combining the pieces: the info you provide about the baseline assets, the backlog entries declaring the developments you plan on those assets, and the high-level description in the FI-WARE product vision in order to not miss the overall picture. Of course, if you don't want to disclose any documentation about the baseline assets, you will have to provide the detail description of the functionality that has already been developed and comes with the asset you bring to FI-WARE. And you have to provide it before mid October (that is the extension on the deadline I could live with) ... Is it what you prefer ? This approach has already been discussed since long time and agreed so I don't know what do we come with this sort of surprises at this time. Please confirm whether you will stay with the guidelines or whether you are going to produce a full detailed description of the functionality that is already implemented with regards to each GE based on your asset as commented before. Best regards, -- Juanjo On 07/10/11 11:27, Seidl, Robert (NSN - DE/Munich) wrote: Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: * read the FI-WARE Product Vision, in order to understand what is overall expected for the GE * read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there * read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 daniel.gidoin at thalesgroup.com Fri Oct 7 12:02:13 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 7 Oct 2011 12:02:13 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> <76BD4E6231F77947B6885C75E5214FA5062BF46E@INTMAIL01.es.int.atosorigin.com> Message-ID: <6284_1317981736_4E8ECE28_6284_11004_1_8F1D40232A0E68409E3FC23A30C326620167010BB328@THSONEA01CMS04P.one.grp> Thank you. SAP can escalate the issue to the PCC? Daniel De : TRABELSI, Slim [mailto:slim.trabelsi at sap.com] Envoy? : vendredi 7 octobre 2011 11:35 ? : Pedro Soria Rodriguez; Seidl, Robert (NSN - DE/Munich); ext Juanjo Hierro; GIDOIN Daniel Cc : fiware-security at lists.fi-ware.eu; Bohnert, Thomas Michael Objet : RE: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear all, I agree with Daniel?s issue. As far as I know according to the consortium agreement SAP development information is not public. Thank you Best regards Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Pedro Soria Rodriguez Sent: vendredi 7 octobre 2011 11:30 To: Seidl, Robert (NSN - DE/Munich); ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hello, I?d like to support Robert and Daniel. In WP8, we at Atos are also concerned about the public visibility of the backlog. The backlog aids development, but development is a task of the consortium, and public visibility is not needed. -- Pedro Soria-Rodriguez Head of Sector Atos Research & Innovation Albarrac?n, 25 28037 Madrid, Spain Email: pedro.soria at atosresearch.eu From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: Friday, October 07, 2011 11:28 To: ext Juanjo Hierro; GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: 1. read the FI-WARE Product Vision, in order to understand what is overall expected for the GE 2. read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there 3. read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.michael.bohnert at sap.com Fri Oct 7 18:10:22 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Fri, 7 Oct 2011 18:10:22 +0200 Subject: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <4E8ECE17.5000509@tid.es> References: <4E8EABF5.5000206@tid.es> <4393_1317974574_4E8EB22E_4393_8879_1_862d0756-f225-4bff-8de3-4a4c3ff9a55b@THSONEA01HUB06P.one.grp> <4E8EC4BA.7020602@tid.es> <9739B018F0466A4CAB10A9DABBEBF5A621FC1E@DEMUEXC027.nsn-intra.net> <4E8ECE17.5000509@tid.es> Message-ID: <771C9B001456D64783596DDC3801C6EA2817099F79@DEWDFECCR09.wdf.sap.corp> Dear all, Upfront, let's try to avoid escalations when possible. Transparency is a key indicator for FI-Ware to succeed. Please mind that we are part of a program and Usage Areas have justified needs and some level of expectations/rights to know what's ongoing within FI-WARE. The FI-WARE backlog is one tool to provide evidence that FI-WARE is working towards a common goal within the PPP. As I understood the Agile approach is a "work organization" methodology and it should be possible to plan work item (user stories, epics) via Agile without disclosing deep technical, and IPR relevant aspects of our technology (assets). I sense that the current issue is also related to the quite intense overhead we all have to deal with at the moment. FI-WARE is on center stage and has to deal with multi-stakeholder expectations. A structured approach with sound processes and capable tooling is therefore absolutely vital to avoid major havoc in such a comprehensive project. Being aware that this means many many emails and a very steep learning curve I hope that we, as a team, can get over this period very soon by keeping level head and discussing issues constructively. Please keep telling your concerns but bear the above in mind. It is not always possible to find good compromises and we therefore need some flexibility at all ends. At the end of the day we all want to turn FI-WARE into a successful project and the many effort we are putting into is promising! Best - Thomas From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 7. Oktober 2011 12:02 To: Seidl, Robert (NSN - DE/Munich) Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear folks, Let me start making one thing clear: the FI-WARE Backlog is setup as a PUBLIC deliverable in the DoW. So I'm afraid you are wrong. Nevertheless, as I have explained, you can deal with managing private and public info in the detailed description of backlogs entries. So I don't see any issue. Please take into account that the backlog itself, as well as some info in the detail description of each entry has to be shared with users. That's a fundamental principle setup for this program (in different parts of the DoW) but also a fundamental principle in Agile (which was agreed in the DoW as method to manage the development process). How the hell are they otherwise going to know what you intend to provide as functionality to them so that they can confirm it covers their needs or provide comments? Take into account, in addition, that the aim of the program is that not just UC projects may join to provide requirements and try to use FI-WARE but other Application Developer Communities as well. Again, this is in the DoW. As per description of the asset, what we are proposing is a pragmatic approach to avoid that partners had to develop too much paperwork. Since we do not start from the scratch but really rely on already developed assets, we have to create a snapshot where we provide to the users the following information: * Detailed description of what we already have developed regarding a given GE (i.e., it is implemented in the assets) * What our current roadmap in terms of development is regarding the GE: this is what goes as backlog Point was how to deal with the first point without creating too much paperwork. Partners bringing assets didn't want to deal with all the burden of documenting something they have ... documented before, in the project where the asset considered as baseline was developed. Nothing to say about dealing with the useless task of translating documents they may have into "FI-WARE branded" documents. That would be rather painful. So we agreed on a trade off, quite straightforward to implement while still useful: We will provide publicly available info of each asset that is already bring the implementation of part of the functionality of the GE (programmers manuals, publicly available documentation, etc.) and then the user shall be able to figure out what is the full functionality of the GE in more detail by combining the pieces: the info you provide about the baseline assets, the backlog entries declaring the developments you plan on those assets, and the high-level description in the FI-WARE product vision in order to not miss the overall picture. Of course, if you don't want to disclose any documentation about the baseline assets, you will have to provide the detail description of the functionality that has already been developed and comes with the asset you bring to FI-WARE. And you have to provide it before mid October (that is the extension on the deadline I could live with) ... Is it what you prefer ? This approach has already been discussed since long time and agreed so I don't know what do we come with this sort of surprises at this time. Please confirm whether you will stay with the guidelines or whether you are going to produce a full detailed description of the functionality that is already implemented with regards to each GE based on your asset as commented before. Best regards, -- Juanjo On 07/10/11 11:27, Seidl, Robert (NSN - DE/Munich) wrote: Dear Juanjo, I agree with Daniel and do NOT agree with your point of view. This approach you are refering to was not agreed with all partners and is also not part of the DOW. I support Daniel for this topic. Please Juanjo find a solution for this issue! Same holds for asset description. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks GmbH & Co. KG CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Friday, October 07, 2011 11:22 AM To: GIDOIN Daniel Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Dear Daniel, Your opinion maybe, but nothing that has to do with how we decided to approach this cooperative, open and Agile project. Please stay with the guidelines. Best regards, -- Juanjo On 07/10/11 10:02, GIDOIN Daniel wrote: Dear Juanjo, in my opinion, the backlog cannot be public; otherwise we would not put very technical information. Daniel De : fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : vendredi 7 octobre 2011 09:36 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpa] The Backlog is not about describing features that assets being adopted as baseline already implement Hi all, As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product. Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality. On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects. And most of them hadn't been developed using Agile so far. If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE. But this is not the case. You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed. It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE. Someone who wants to have a detailed picture of all target functionality should: 1. read the FI-WARE Product Vision, in order to understand what is overall expected for the GE 2. read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there 3. read the backlog, to understand what's going on and is somehow on the roadmap The exercise we are doing is about setting the Agile backlogs that will drive our future developments. It's not about documenting what he have done during many years in our respective labs. A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project. That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste. What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course). This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker. You may create another "Backlog" trackers for additional activities (like documentation, etc.). That's why I created a "Task Force Management" tracker in addition. Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers. Regards, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Mon Oct 10 09:24:48 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 10 Oct 2011 09:24:48 +0200 Subject: [Fiware-security] FI-WARE - Security - Audio-conference 07/10/2011 - 10am-12am (Minutes) Message-ID: <26314_1318231491_4E929DC3_26314_10376_1_96315ff6-b8f0-4f26-a17b-5544d106a24a@THSONEA01HUB03P.one.grp> Dear All, Short minutes of WP8 audio conference of last Friday: Present: Antonio (ATOS) Slim (SAP) Robert (NSN) Francesco (SAP) Daniel (Thales) Pascal (Thales Alexandra (DT/T-Systems) 1. Production Vision for M5 / Security Features backlog * T8.1 (Thales) Security monitoring GE section has been updated. Accordingly glossary of terms and question marks sections have been updated Assets description attached to that GE have not been yet entered. Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process. Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Thales: to add the descriptions of entries. Deadline: 10/10/2011 EOB. * T8.2 (Thales) Core Generic enablers section has not been yet updated on the wiki but content has been produced, checked and agreed. Actions set for NSN (deadline 10/10/2011 EOB): * to upload new content of that section on the wiki. * to enter description of assets attached to each of the 3 GEs (IdMgt, Privacy, Data Control) * to add typed (Themes, EPICS, Features, User Stories) entries attached to these Core Generic enablers to the Security Features backlog ISSUE RAISED with respect to INRIA asset - Action NSN Robert to organize an audio with INRIA (Daniel) and Pascal to discuss the issue and find a way out being the INRIA asset is not mature enough to be selected. Audio-conf with Use Case projects to introduce them to Core Generic Enablers as per today: Action NSN to send a reminder for a date to be announced by Pascal to Juanjo. * T8.3 (ATOS) Descriptions of assets attached to T8.3 GE have been uploaded. Actions set for ATOS (deadline 10/10/2011 EOB): * to check/update on the wiki the section devoted to T8.3 GE aka context-based security & compliance * to revisit entries attached to this Generic enabler and entered to the Security Features backlog since some of them do not perfectly fit with the Agile type category announced and/or are too close of asset description. * T8.4 (SLIM) Descriptions of assets attached to T8.3 GE have been uploaded. Actions set for SAP (deadline 10/10/2011 EOB): * to check/update on the wiki the section devoted to T8.4 GE aka optional generic security enablers * to move entries attached to this Generic enabler (EPICS, Features and User-stories) and entered them to the Security Features backlog to the right place (Materializing Security in FI-WARE ...) * to upload the description of each of the assets attached to T8.4 GE. NB: Slim announced a internal meeting to come between FI-WARE and FINEST SAP teams. * since some of them do not perfectly fit with the Agile type category announced and/or are too close of asset description. Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process. Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Thales: to add the descriptions of entries. Deadline: 10/10/2011 EOB. 2. Meetings * Virtual meeting with Usage Areas - date to be announced soon. * No WP8 physical planned so far 3. Update on the security requirements (question marks) coming from the other Chapters * So far no official update was provided to WP8 team but deadline was 07/10/2011 EOB. * According to report provided Pascal and Daniel may organize a Call during the week * In the meantime it is important that each of the representatives of this team appointed to follow-up activities of other teams to contact their counterparts, liaise with them on the topic in order to have an update and textual proposal to be discussed asap and at the latest at our next audio conference. i. Action: Slim, Daniel, Xavier and Wolfgang/Alexandra to report at next meeting for what concerns respectively update of the security requirements/questions marks section of WP3, WP4&WP6, WP5 and WP7 4. ISSUES FACED BY THIS TEAM * Issues are mainly due to the fact that all content uploaded on the wiki would be made public. This has raised a number of serious concerns at the level of members of this team and called for a public and private wiki thus causing double work (decide on what to expose as public whereas still meaningful whereas to keep private to our team). Furthermore the tooling offered to upload content on the wiki was not in favor of performance ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Mon Oct 10 13:04:27 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Mon, 10 Oct 2011 13:04:27 +0200 Subject: [Fiware-security] FI-WARE: wiki update Message-ID: <20287_1318244670_4E92D13E_20287_2261_1_589b1d3f-699a-4e6c-8385-271977d0e17e@THSONEA01HUB06P.one.grp> Dear Partners, Thank a lot to update the FI-Ware wiki as below: - Materializing Security in FI-WARE : o Base line assets o Features and User Stories using your assets. After this work, the update of the backlog is very easy. It's very urgent. Thank you for agreeing to do this work for noon tomorrow, at the latest Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From slim.trabelsi at sap.com Mon Oct 10 17:24:19 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Mon, 10 Oct 2011 17:24:19 +0200 Subject: [Fiware-security] FI-WARE - Security - Audio-conference 07/10/2011 - 10am-12am (Minutes) In-Reply-To: <26314_1318231491_4E929DC3_26314_10376_1_96315ff6-b8f0-4f26-a17b-5544d106a24a@THSONEA01HUB03P.one.grp> References: <26314_1318231491_4E929DC3_26314_10376_1_96315ff6-b8f0-4f26-a17b-5544d106a24a@THSONEA01HUB03P.one.grp> Message-ID: Hi Pascal, I updated the Wiki according to the last procedure https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Security_in_FI-WARE#Optional_Security_Enabler Thank you BR Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: lundi 10 octobre 2011 09:25 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - Security - Audio-conference 07/10/2011 - 10am-12am (Minutes) Dear All, Short minutes of WP8 audio conference of last Friday: Present: Antonio (ATOS) Slim (SAP) Robert (NSN) Francesco (SAP) Daniel (Thales) Pascal (Thales Alexandra (DT/T-Systems) =MsoNormal> 1. Production Vision for M5 / Security Features backlog * T8.1 (Thales) Security monitoring GE section has been updated. Accordingly glossary of terms and question marks sections ha > Assets description attached to that GE have not been yet entered. Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process. Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Th escriptions of entries. Deadline: 10/10/2011 EOB. * T8.2 (Thales) Core Generic enablers section has not been yet updated on the wiki but content has been produced, checked and agreed. Actions set for NSN (deadline 10/10/2011 EOB): * to upload new content of that section on the wiki. * to enter description of assets attached to each of the 3 GEs (IdMgt, Privacy, Data Control) * to add typed (Themes, EPICS, Features, User Stories) entries attached to these Core Generic enablers to the Security Features backlog ISSUE RAISED with respect to INRIA asset - Action NSN Robert to organize an audio with INRIA (Daniel) and Pascal to discuss the issue and find a way out being the INRIA asset is not mature enough to be selected. &nbs p; Audio-conf with Use Case projects to introduce them to Core Generic Enablers as per today: Action NSN to send a reminder for a date to be announced by Pascal to Juanjo. * T8.3 (ATOS) Descriptions of assets attached to T8.3 GE have been uploaded. Actions set for ATOS (deadline 10/1 > * to check/update on the wiki the section devoted to T8.3 GE aka context-based security & compliance * to revisit entries attached to this Generic enabler and entered to the Security Features backlog since some of them do not perfectly fit w ry announced and/or are too close of asset description. * T8.4 (SLIM) Descriptions of assets attached to T8.3 GE have been uploaded. Actions set for SAP (deadline 10/10/2011 EOB): * to check/update on the wiki the section devoted to T8.4 GE aka optional generic security enablers * to move entries attached to this Generic enabler (EPICS, Features and User-stories) and entered them to the Security Features backlog to the right place (Materializing Security in FI-WARE ...) * to upload the description of each of the assets attached to T8.4 GE. NB: Slim announced a internal meeting to come between FI-WARE and FINEST SAP teams. * since some of them do not perfectly fit with the Agile type category announced and/or are too close of asset description. Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process. Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Thales: to add the descriptions of entries. Deadline: 10/10/2011 EOB. 2. Meetings * Virtual meeting with Usage Areas - date to be announced soon. * No WP8 physical planned so far Update on the security requirements (question marks) coming from the other Chapters * So far no official update was provided to WP8 team but deadline was 07/10/2011 EOB. * According to report provided Pascal and Daniel may organize a Call during the week * In the meantime it is important that each of the representatives of this team appointed to follow-up activities of other teams to contact their counterparts, liaise with them on the topic in order to have an update and textual proposal to be discussed asap and at the latest at our next audio conference. Action: Slim, Daniel, Xavier and Wolfgang/Alexandra to report at next meeting for what concerns respectively update of the security requirements/questions marks section of WP3, WP4&WP6, WP5 and WP7 3. ISSUES FACED BY THIS TEAM * Issues are mainly due to the fact that all content uploaded on the wiki would be made public. This has raised a number of serious concerns at the level of members of this team and called for a public and private wiki thus causing double work (decide on what to expose as public whereas still meaningful whereas to keep private to our team). Furthermore the tooling off the wiki was not in favor of performance ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Mon Oct 10 18:11:30 2011 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Mon, 10 Oct 2011 18:11:30 +0200 Subject: [Fiware-security] FI-WARE T8.2 Generic Enabler Description In-Reply-To: References: Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A626C5AC@DEMUEXC027.nsn-intra.net> Hi Sarah, please find my answers to your comments in the document. I added them inside your comments. I think most of the issues were solved in our telco today. Greetings Robert ________________________________ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Pennington, Sarah Sent: Friday, September 30, 2011 11:08 AM To: Fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] FI-WARE T8.2 Generic Enabler Description Dear all, Attached are Thales's comments on the architecture. Regards, Sarah <> Sarah Pennington Senior Engineer, Research & Technology Thales UK Worton Drive, Reading, Berkshire, RG2 0SB www.thalesgroup.com/uk Tel: +44 (0)118 923 8248. Fax: +44 (0) 118 923 8399. e-mail: sarah.pennington at thalesgroup.com Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Security Architecture New V0 6 clean TRT_NSN.doc Type: application/msword Size: 1092608 bytes Desc: Security Architecture New V0 6 clean TRT_NSN.doc URL: From antonio.garcia at atosresearch.eu Mon Oct 10 18:41:58 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Mon, 10 Oct 2011 18:41:58 +0200 Subject: [Fiware-security] (no subject) Message-ID: <0385F69C47D8694EA885D34BE18BCCC403361A0B@INTMAIL02.es.int.atosorigin.com> Pascal, I?ve already updated ?Context-based security and compliance Generic Enabler? description at ?FI-WARE Product Vision + FI-WARE Security section?: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security#Context-based_security_and_compliance Best Regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 10 19:00:58 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 10 Oct 2011 19:00:58 +0200 Subject: [Fiware-security] (no subject) In-Reply-To: <0385F69C47D8694EA885D34BE18BCCC403361A0B@INTMAIL02.es.int.atosorigin.com> References: <0385F69C47D8694EA885D34BE18BCCC403361A0B@INTMAIL02.es.int.atosorigin.com> Message-ID: <16910_1318266060_4E9324CC_16910_12252_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AC518D2@THSONEA01CMS04P.one.grp> Thanks Antonio. De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu] Envoy? : lundi 10 octobre 2011 18:42 ? : BISSON Pascal Cc : Fiware-security at lists.fi-ware.eu Objet : Pascal, I?ve already updated ?Context-based security and compliance Generic Enabler? description at ?FI-WARE Product Vision + FI-WARE Security section?: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Security#Context-based_security_and_compliance Best Regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Tue Oct 11 01:10:26 2011 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 11 Oct 2011 01:10:26 +0200 Subject: [Fiware-security] FI-WARE T8.2 Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A626C5D3@DEMUEXC027.nsn-intra.net> Hi Pascal, I updated the sections for Generic Security Enablers (Identity, Privacy and Data Handling). You will find the changes here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE _Security#Generic_Enablers The overall architecture still needs some updates. I also restructured the order on the Wiki for the Security WP. Hope this reflects now the structure of WP8 in the DoW. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Oct 11 10:12:00 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 11 Oct 2011 10:12:00 +0200 Subject: [Fiware-security] FI-WARE T8.2 In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A626C5D3@DEMUEXC027.nsn-intra.net> References: <9739B018F0466A4CAB10A9DABBEBF5A626C5D3@DEMUEXC027.nsn-intra.net> Message-ID: <17982_1318320726_4E93FA56_17982_1242_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AC98A77@THSONEA01CMS04P.one.grp> Thanks for the update. Let me know when the update of the overall architectures regarding changes you need has been performed. If other tasks lead need to change the overall architecture please report as well and we will proceed one by one. But for the time being let's first start with the update requested by T8.2 lead according to newly uploaded description of assets. Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : mardi 11 octobre 2011 01:10 ? : BISSON Pascal Cc : Fiware-security at lists.fi-ware.eu Objet : FI-WARE T8.2 Hi Pascal, I updated the sections for Generic Security Enablers (Identity, Privacy and Data Handling). You will find the changes here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Security#Generic_Enablers The overall architecture still needs some updates. I also restructured the order on the Wiki for the Security WP. Hope this reflects now the structure of WP8 in the DoW. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Tue Oct 11 19:19:52 2011 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 11 Oct 2011 19:19:52 +0200 Subject: [Fiware-security] FI-WARE T8.2 Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A626C8A1@DEMUEXC027.nsn-intra.net> Hi Pascal, I updated the overall architecture diagram to the actual status of our discussions. I also updated the backlog and asset description, but still some partner input is missing. Greetings Robert > _____________________________________________ > From: Seidl, Robert (NSN - DE/Munich) > Sent: Tuesday, October 11, 2011 1:10 AM > To: ext BISSON Pascal > Cc: Fiware-security at lists.fi-ware.eu > Subject: FI-WARE T8.2 > > Hi Pascal, > I updated the sections for Generic Security Enablers (Identity, > Privacy and Data Handling). > You will find the changes here: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WA > RE_Security#Generic_Enablers > The overall architecture still needs some updates. > > I also restructured the order on the Wiki for the Security WP. > Hope this reflects now the structure of WP8 in the DoW. > > Greetings > Robert > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Oct 12 08:41:39 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 12 Oct 2011 08:41:39 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Maintenance in the wiki on Thursday Message-ID: <27354_1318401701_4E9536A5_27354_18132_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063ACE89E8@THSONEA01CMS04P.one.grp> FYI -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mardi 11 octobre 2011 16:32 ??: fiware-wpl at lists.fi-ware.eu Objet?: [Fiware-wpl] Maintenance in the wiki on Thursday Dear all, We are doing some maintenance works on the wiki on Thursday from 4pm onwards. It will be available by Friday at 9am. We are basically making changes in the templates and restructuring contents. Please make your sure that your teams aware of this. Sorry for the inconveniences this may cause. Best regards Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 Mobile: (+34) 616 213 607 e-mail: mcp at 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 _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From pascal.bisson at thalesgroup.com Wed Oct 12 08:53:56 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 12 Oct 2011 08:53:56 +0200 Subject: [Fiware-security] FI-WARE T8.2 In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A626C8A1@DEMUEXC027.nsn-intra.net> References: <9739B018F0466A4CAB10A9DABBEBF5A626C8A1@DEMUEXC027.nsn-intra.net> Message-ID: <21312_1318402435_4E953983_21312_17587_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063ACE8A61@THSONEA01CMS04P.one.grp> Thanks Robert. Could you put on the Security project repository the file on the overall architecture that you updated. For the missing input from partners please send urgently a reminder to the one who have still not yet delivered (uploaded their stuff on the wiki). Regards , Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : mardi 11 octobre 2011 19:20 ? : BISSON Pascal Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE T8.2 Hi Pascal, I updated the overall architecture diagram to the actual status of our discussions. I also updated the backlog and asset description, but still some partner input is missing. Greetings Robert _____________________________________________ From: Seidl, Robert (NSN - DE/Munich) Sent: Tuesday, October 11, 2011 1:10 AM To: ext BISSON Pascal Cc: Fiware-security at lists.fi-ware.eu Subject: FI-WARE T8.2 Hi Pascal, I updated the sections for Generic Security Enablers (Identity, Privacy and Data Handling). You will find the changes here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Security#Generic_Enablers The overall architecture still needs some updates. I also restructured the order on the Wiki for the Security WP. Hope this reflects now the structure of WP8 in the DoW. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonio.garcia at atosresearch.eu Fri Oct 14 12:31:05 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Fri, 14 Oct 2011 12:31:05 +0200 Subject: [Fiware-security] Asset information Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B72FA@INTMAIL02.es.int.atosorigin.com> Daniel, I need you to completed the some information from Thales assets in ?Materializing Security in FI-WARE + Context-based security and compliance + Baseline Assets?. The details to be filled are: 1) Fragmento: Details in ?Programming artifacts? and ?Runtime pre-requisites? 2) Governance Dashboard: Details in ?Programming artifacts? 3) CRLT: Details in ?Programming artifacts? and ?Runtime pre-requisites? Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonio.garcia at atosresearch.eu Fri Oct 14 14:26:05 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Fri, 14 Oct 2011 14:26:05 +0200 Subject: [Fiware-security] FI-WARE Wiki: Security chapter overview Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B73CF@INTMAIL02.es.int.atosorigin.com> Hi all, For me it is could be Ok as an introduction, but I believe that we could update the architecture image in order to get it close to the implementation we are describing in detail chapters. See attached a first revision (I?ve already used it in Turin?s meeting) where I?ve updated Task 8.3 schema and the names of the GE/components to be implemented in your tasks. If you are agree we can use it instead of the older one On the other hand and also regarding with images I feel most of the pictures we?ve included are so big that could make page reading difficult Why don?t we use the image attributes wiki provides? See help page on: http://simple.wikipedia.org/wiki/Help:How_to_use_images You can take as examples the images I?ve included both in Context-based security and compliance chapter and backlog asset description Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Arquitecture.JPG Type: image/jpeg Size: 102189 bytes Desc: Arquitecture.JPG URL: From antonio.garcia at atosresearch.eu Fri Oct 14 14:30:12 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Fri, 14 Oct 2011 14:30:12 +0200 Subject: [Fiware-security] Asset Information Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B73D4@INTMAIL02.es.int.atosorigin.com> Slim, I need you to check the information from your USDL asset: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/USDL_Language I guest most of the items that are not filled do not apply in this case; but I would like you review them. Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 17 09:18:51 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 17 Oct 2011 09:18:51 +0200 Subject: [Fiware-security] FI-WARE - Security - Minutes of our last audio (14-10-2011) Message-ID: <3547_1318835938_4E9BD6E2_3547_9174_1_ef43820a-3e6b-4eb5-86d3-d17e5fbdbd4b@THSONEA01HUB01P.one.grp> Dear All, This just to let you know that I uploaded on our Security Project (private) wiki the minutes of our last WP8 audio conf. https://forge.fi-ware.eu/docman/view.php/19/505/Minutes+of+WP8+weekly+audio+14102011.docx Please double-check since a number of actions need still be performed to close our work on M5 and Features backlog. Counting on those who still have actions to perform them according to the set deadlines. Next audio-conf is planned this Friday 21 from 10am-12am - Same details as usual. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Oct 18 18:58:14 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 18 Oct 2011 18:58:14 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Overview of status Message-ID: <3429_1318957099_4E9DB02A_3429_14428_1_f8cb2369-95c3-4c56-8fa4-dcf1cff73d0f@THSONEA01HUB02P.one.grp> FYI and check ! De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 18 octobre 2011 16:10 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Overview of status Hi all, End of October is approaching and I want to remind you the major goals we have to meet by the end of the month: * Update of the FI-WARE Product Vision. We should address: * as many of the comments on the first release of the FI-WARE Product Vision by the reviewers as possible * what we committed to do as delta against the first version of this deliverable according to the DoW : "?what are the baseline projects whose results will be considered for integration in FI-WARE together with an explanation on what results may be used why and how they plan to be integrated together. It also will include a description of projects whose progress will be monitored to determine their further adoption in planned releases of FI-WARE. * Creation of the backlog linked to each chapter and GE, including: * Epics describing functionality still at high level, thus requiring further analysis in parallel to sprints * Features, including those we commit to address during first minor release of FI-WARE (starting November 1st and scheduled to end mid February) * User-Stories, including those we plan to develop during first Sprint (starting November 1st, lasting one month) Regarding second bullet of the first point, that is the description of assets, Miguel Carrillo will send to each of you a detailed report on things we are missing or things we will request you to fix in order to achieve a minimum of homogeneity regarding contents published on the Wiki. Please review Miguel's requests carefully and try to implement them as soon as possible. Bear in mind that we should have all this done by end of September and we are running late. Regarding the backlog, apart from finishing the uploading of all the identified Epics associated to chapters/GEs, you should work trying to refine them up to produce the first set of features and user-stories. You should also take a look in parallel to requests made by the UC projects. Thomas and me will take a look at them and assign them to you when we find them suitable for your analysis. Don't hesitate to ask any question. Please share this info with your teams. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 Spain ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Wed Oct 19 11:23:02 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 19 Oct 2011 11:23:02 +0200 Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets Message-ID: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware From antonio.garcia at atosresearch.eu Wed Oct 19 15:32:07 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Wed, 19 Oct 2011 15:32:07 +0200 Subject: [Fiware-security] (WP8.3 assets) RE: TR: [Fiware] Contents under the IPR sections in the assets In-Reply-To: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> Daniel, Slim. As requested on this e-mail from Pascal, please check the IPR information of your Task 8.3 assets an update it. Thanks in advance. ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From antonio.garcia at atosresearch.eu Wed Oct 19 15:48:31 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Wed, 19 Oct 2011 15:48:31 +0200 Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets In-Reply-To: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B7E75@INTMAIL02.es.int.atosorigin.com> Robert, I've Updated Stork IPR information following this directions. I've also changed: 1) The picture position and size to be close to the asset description 2) Updated the missing text under "Runtime pre-requisites" section Best regards ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From antonio.garcia at atosresearch.eu Wed Oct 19 16:46:03 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Wed, 19 Oct 2011 16:46:03 +0200 Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections inthe assets In-Reply-To: <4E9ED81A.2040105@tid.es> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> <0385F69C47D8694EA885D34BE18BCCC4033B7E75@INTMAIL02.es.int.atosorigin.com> <4E9ED81A.2040105@tid.es> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B7ED7@INTMAIL02.es.int.atosorigin.com> Miguel , I?ve updated again the asset IPR description in order to correct the ambiguity you said. The fact is that the main and core components of Stork will be under EUPL 1.1 license and some ancillary ones will have another Open Source ones Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ From: Miguel Carrillo [mailto:mcp at tid.es] Sent: mi?rcoles, 19 de octubre de 2011 16:01 To: Antonio Garcia Vazquez Subject: Re: [Fiware-security] TR: [Fiware] Contents under the IPR sections inthe assets Antonio, Una cosilla: "In general the STORK software can be licensed EUPL 1.1 ". "In general" es un poco ambiguo, no aclara el marco de IPR. Mira si lo puedes aquilatar un poco para que no quede abierto. Gracias Miguel El 19/10/2011 15:48, Antonio Garcia Vazquez escribi?: Robert, I've Updated Stork IPR information following this directions. I've also changed: 1) The picture position and size to be close to the asset description 2) Updated the missing text under "Runtime pre-requisites" section Best regards ************************************ * Antonio Garc?a V?zquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 19 octobre 2011 10:37 ? : fiware at lists.fi-ware.eu Objet : [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 ------------------------------------------------------------------ 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: From daniel.gidoin at thalesgroup.com Wed Oct 19 16:47:02 2011 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 19 Oct 2011 16:47:02 +0200 Subject: [Fiware-security] (WP8.3 assets) RE: TR: [Fiware] Contents under the IPR sections in the assets In-Reply-To: <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> Message-ID: <16093_1319035624_4E9EE2E8_16093_2117_1_8F1D40232A0E68409E3FC23A30C326620167013D91CA@THSONEA01CMS04P.one.grp> Dear Antonio, I'm going to find out because I have no other information than open source license. Best regard -----Message d'origine----- De?: Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu] Envoy??: mercredi 19 octobre 2011 15:32 ??: GIDOIN Daniel; TRABELSI, Slim Cc?: Fiware-security at lists.fi-ware.eu Objet?: (WP8.3 assets) RE: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets Daniel, Slim. As requested on this e-mail from Pascal, please check the IPR information of your Task 8.3 assets an update it. Thanks in advance. ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From slim.trabelsi at sap.com Wed Oct 19 16:52:41 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Wed, 19 Oct 2011 16:52:41 +0200 Subject: [Fiware-security] (WP8.3 assets) RE: TR: [Fiware] Contents under the IPR sections in the assets In-Reply-To: <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> Message-ID: Hi Antonio, Sorry for answering late. I'v updated the usdl-sec section, let me know if it is fine with you. BR Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com -----Original Message----- From: Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu] Sent: mercredi 19 octobre 2011 15:32 To: GIDOIN Daniel; TRABELSI, Slim Cc: Fiware-security at lists.fi-ware.eu Subject: (WP8.3 assets) RE: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets Daniel, Slim. As requested on this e-mail from Pascal, please check the IPR information of your Task 8.3 assets an update it. Thanks in advance. ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From slim.trabelsi at sap.com Wed Oct 19 17:21:25 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Wed, 19 Oct 2011 17:21:25 +0200 Subject: [Fiware-security] Fi-WARE - Security AT - Virtual Workshop with Use Case In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A62AF887@DEMUEXC027.nsn-intra.net> References: <9857_1319029504_4E9ECB00_9857_8900_1_d1cb7053-30b2-4937-b333-7892acf70acb@THSONEA01HUB05P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A62AF887@DEMUEXC027.nsn-intra.net> Message-ID: Dear all, As it was announced during the last confcall. A Task 8.2 workshop will be hosted at SAP Sophia-Antipolis in November 16th. For those who are interested to attend the meeting please let us know. @Robert and @Anja I have to book the rooms know 9:00 to 17:30 is it ok ? Thank you Best regards Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Sent: mercredi 19 octobre 2011 16:39 To: ext BISSON Pascal; TRABELSI, Slim; Antonio Garcia Vazquez; Michael Osborne Cc: GIDOIN Daniel Subject: RE: Fi-WARE - Security AT - Virtual Workshop with Use Case Hi Pascal, just a quick info. The entire week of 3rd November I'm on vacation. 8th November I'm in principle available, but have already some meetings. 17th and 18th November there is the reference group meeting with the TAS3 project. At the 16th we will have the T8.2 architecture meeting (the day before the TAS3 meeting) and maybe we have to travel at the 15th. So these dates are also not possible from my side (we announced this in our WP8 telco last week). Please mention this to Telefonica. Greetings Robert ________________________________ From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Wednesday, October 19, 2011 3:05 PM To: Seidl, Robert (NSN - DE/Munich); ext TRABELSI, Slim; Antonio Garcia Vazquez; Michael Osborne Cc: BISSON Pascal; GIDOIN Daniel Subject: Fi-WARE - Security AT - Virtual Workshop with Use Case Importance: High Dear All, Find hereafter the actions decided at the last WPL/WPA audio conf I had with Juanjo on Monday. Regarding the virtual workshop on Identity, Access Control, Privacy Management: * AP on Juanjo: To setup doodle for virtual workshop either on Nov 3 or Nov 8. Assumption is that virtual workshop will last 3 hours so doodle will help to select both date and starting time. Juanjo will distribute doodle link to WPLs/WPAs and Pascal to the Security team * AP on Juanjo: Propose UC projects virtual workshop either on Nov 15, Nov 16 or Nov 17. * AP on Pascal: Send soon an email to Security team to make them aware that virtual workshop with UC projects will take place most probably some day during Nov 15-17 period. I'd like here to draw your attention to the fact that: * first meeting (i.e. meeting between Security Team and other ATs focusing on Core GEs so T8.2 GEs) is planned to occur either on Nov 3 or Nov 8. Juanjo will set a doodle that I will communicate you onceestablised. At least and for the time being I'd like each of you to book those dates and especially Robert and T8.2 GE owners. * Second (virtual) meeting even more important since with Use Case projects which demanded it, is planned either on Nov 15, Nov 16 or Nov 17. Same applies here please book those dates especially Robert and T8.2 GE owners and be prepared to fill in the doodle I will forward you once established by Juanjo. That's all for the AP on my side. Keep you posted regarding AP put on Juanjo's side. Best Regards, Pascal PS: Of course and if some of the dates proposed are not possible for you please let me know -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonio.garcia at atosresearch.eu Wed Oct 19 17:24:01 2011 From: antonio.garcia at atosresearch.eu (Antonio Garcia Vazquez) Date: Wed, 19 Oct 2011 17:24:01 +0200 Subject: [Fiware-security] (WP8.3 assets) RE: TR: [Fiware] Contents under the IPR sections in the assets In-Reply-To: <16093_1319035624_4E9EE2E8_16093_2117_1_8F1D40232A0E68409E3FC23A30C326620167013D91CA@THSONEA01CMS04P.one.grp> References: <6068_1319016184_4E9E96F8_6068_8082_1_CBBCD6C304123F4AB23FAAE3055C8C0E02063AE8291B@THSONEA01CMS04P.one.grp> <0385F69C47D8694EA885D34BE18BCCC4033B7E5B@INTMAIL02.es.int.atosorigin.com> <16093_1319035624_4E9EE2E8_16093_2117_1_8F1D40232A0E68409E3FC23A30C326620167013D91CA@THSONEA01CMS04P.one.grp> Message-ID: <0385F69C47D8694EA885D34BE18BCCC4033B7F1A@INTMAIL02.es.int.atosorigin.com> Thanks Daniel, In the meantime please check also the missing sections ( tags). From my side I've also updated Task 8.1 SIEM asset IPR. Regards ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: GIDOIN Daniel [mailto:daniel.gidoin at thalesgroup.com] Sent: mi?rcoles, 19 de octubre de 2011 16:47 To: Antonio Garcia Vazquez; TRABELSI, Slim Cc: Fiware-security at lists.fi-ware.eu Subject: RE: (WP8.3 assets) RE: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets Dear Antonio, I'm going to find out because I have no other information than open source license. Best regard -----Message d'origine----- De?: Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu] Envoy??: mercredi 19 octobre 2011 15:32 ??: GIDOIN Daniel; TRABELSI, Slim Cc?: Fiware-security at lists.fi-ware.eu Objet?: (WP8.3 assets) RE: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets Daniel, Slim. As requested on this e-mail from Pascal, please check the IPR information of your Task 8.3 assets an update it. Thanks in advance. ************************************ *????? Antonio Garc?a V?zquez???? * *??????? (+34) 91 214 9384???????? * * antonio.garcia at atosresearch.eu * ************************************ -----Original Message----- From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mi?rcoles, 19 de octubre de 2011 11:23 To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware] Contents under the IPR sections in the assets FYI -----Message d'origine----- De?: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy??: mercredi 19 octobre 2011 10:37 ??: fiware at lists.fi-ware.eu Objet?: [Fiware] Contents under the IPR sections in the assets Dear all, There is an agreement within the PPP that all the contributions will be available to the rest of the partners free of charge for the duration of the PPP. So the information we have to provide in the asset description is the IPR in a wide sense. This means that we have to clearly express how we are going to license each one of the pieces. In other words, the IPR section can express that a given product will be licensed as Open source (explicitly mentioning which one), or alternative that the IPR belong to a company and that the product will be licensed under FRAND Terms. We have reflected this in the tutorial recently created, to make sure that we have a uniform wiki http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations Best, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at 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 _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security ------------------------------------------------------------------ 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. ------------------------------------------------------------------ From slim.trabelsi at sap.com Thu Oct 20 14:56:09 2011 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Thu, 20 Oct 2011 14:56:09 +0200 Subject: [Fiware-security] Finest use case project Message-ID: Dear all, Last Monday we has an internal meeting at SAP with the contributors of the use case project PPP FINEST. If you are interested you can find in the attached PPT their architectures and their requirement mappings with the different fi-ware WP including the security one. We can have further discussion during the Friday call. Thank you BR Slim -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FInest_HLA+GEM6_ABmeetingParis_20110921.ppt Type: application/vnd.ms-powerpoint Size: 1351168 bytes Desc: FInest_HLA+GEM6_ABmeetingParis_20110921.ppt URL: From pascal.bisson at thalesgroup.com Sun Oct 23 17:59:15 2011 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Sun, 23 Oct 2011 17:59:15 +0200 Subject: [Fiware-security] FI-WARE - Security - Audio-conference 21/10/2011 - 10am-12am (Minutes) Message-ID: <22771_1319385678_4EA43A4E_22771_704_1_b9463eb4-2819-479a-8a02-12a145cc6aa6@THSONEA01HUB05P.one.grp> Dear All, Short minutes of WP8 audio conference of last Friday: Present: Richard (TRT-UK) Wolfgang (DT) Antonio (ATOS) Francesco (SAP) Robert (NSN) Daniel (Thales) Pascal (Thales Alexandra (DT/T-Systems) 1. Product Vision for M5 / Security Features backlog * Overall security architecture has been updated by each of the task leads and uploaded on the Wiki by WP Lead (see Overview section of Security Chapter) * The Security Team has been working on addressing comments received from TID on the assets description to make all WP inputs consistent in format. * Reminder: All to take Samson and Hadoop (from Data/Context Mgt Chapter leaded by TID) as the references templates for assets description. * T8.1 (Thales/Daniel) * Comments on Thales assets have been addressed (correct template was used and assets description was reviewed and extended) 1. Action point for other T8.1 partners (i.e. TRT-UK, TAI, ATOS, INRIA ...) to proceed immediately with update of their assets. Deadline to have it done: by 24/10/2011 EOB at the latest!. 2. AP Thales (Daniel): to send a reminder! * Entries to the features backlog (entries provided by TS, to be checked and completed by other partners) 1. 2 EPICS (topics still under discussion at high level) have been added to call for joint work to be engaged between both WP8 & WP4 and WP8 & WP3 (this as previously discussed) * T8.2 (NSN/Robert) * T8.2 Lead busy addressing Miguel comments. Waiting update from IBM and answer from FT-Orange. Work expected to be done according to the set deadline 24/10/11 (EOB) 1. Action Point: NSN to urge IBM to complete the work and urge FT-Orange to answer to them and perform the work requested. 2. Action Point THA: to drop an email to FT-Orange (E. Mayer, X. Aghina) and contact them over the phone on the topic * Entries to the features backlog (no additional update) * T8.3 (ATOS/Antonio) * T8.3 Lead busy addressing Miguel comments. Assets description to be put under proper template. Work expected to be done by 24/10/11 EOB. 1. Action Point: THA to complete description of assets with missing information. * Entries to the features backlog 1. Action Point ATOS: to complete with some User stories. * T8.4 (SAP/Francesco) * T8.4 lead working on addressing Miguel comments. Expected to be done by Monday 24/10/11 EOB. * Entries to the features backlog (work done). 2. Meetings * Past meetings: i. Internal SAP meeting with FINEST. FINEST slides of this meeting have been distributed by SAP. Very interesting from the specific viewpoint of their security requirements. Need to align terminology between us and them. Also need to clarify specific issues. Additional calls have been scheduled to see how FI-WARE (WP8) could work with them on the basis of the EPICS (9) they have specified). * Meeting to come i. FIA/ServiceWave Poznan (Thales/Pascal, ATOS/Antonio to attend and represent FI-WARE Security project). Presentation to be uploaded on the Wiki (AP - Antonio+Pascal) ii. FI-WARE(T8.2)-TAS3 Meeting at SAP on Nov 16 - See invitation from Slim - Robert, Anja, Daniel (possibly also Pascal) to attend. iii. Virtual meeting with other ATs / Virtual meeting with UC Projects * Wiki has been set-up by Juanjo to come up with dates of the meeting targeted (one between WP8 and other Chapters, another one between WP8 and the UC Projects - focusing on Core Generic Enablers (T8.2)). 3. Update on the security requirements (question marks) coming from the other Chapters * Other chapters haven't delivered they security requirements as requested and expected, except for what concerns IoT team where things have been engaged regarding update of their question mark section on security aspects. * It is important for WP8 representatives appointed to follow up activities of each of the other WPs to be pro-active on this in order to urgently call (other WPs) for this update work to shared, discussed, agreed (with us) and closed asap. * Action Point (SAP/Slim/Francesco) * To contact WP3 and interact with them to finalize update for M5 release of Product Vision document of the question mark section on security aspects of App & Service ecosystem chapter. Update expected to be complete to be presented and discussed at next audio. * Action Point (THA/Daniel/Pascal) * To contact WP4 and interact with them to finalize update for M5 release of Product Vision document of the question mark section on security aspects of Cloud Hosting chapter. Update expected to be complete to be presented and discussed at next audio. * Action Point (THA/Pascal/Daniel) * To contact WP6 and interact with them to finalize update for M5 release of Product Vision document of the question mark section on security aspects of Data/Context Management chapter. Update expected to be complete to be presented and discussed at next audio. * Action Point (DT/Wolfang/Alexandra) * To contact WP7 and interact with them to finalize update for M5 release of Product Vision document of the question mark section on security aspects of I2N chapter. Update expected to be complete to be presented and discussed at next audio. 4. Wiki * AP Pascal: Information on private Wiki announced and set-up by TID to be distributed by Pascal. 5. Other * Audio-conf: * Cancelled next week * Next audio conf: November 4th 10am-12am -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Mon Oct 24 11:56:42 2011 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Mon, 24 Oct 2011 11:56:42 +0200 Subject: [Fiware-security] Fi-WARE - Security AT - Virtual Workshop with Use Case In-Reply-To: References: <9857_1319029504_4E9ECB00_9857_8900_1_d1cb7053-30b2-4937-b333-7892acf70acb@THSONEA01HUB05P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A62AF887@DEMUEXC027.nsn-intra.net> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A62B0075@DEMUEXC027.nsn-intra.net> Hi all, during the meeting we could address the following topics: - WP8 overall architecture (depending on Daniel) - Interworking between WP8 tasks (some tasks have dependencies here) - Detailed discussion on T8.2 architecture - Integration of T8.2 partner assets - Discussion on T8.2 Epics and how to bring them down to Features and User Stories - Any other topics ??? This mainly depends on who will participate. So please indicate if you intend to participate or not. Please also propose additional topics which should be addressed at this meeting. Many thanks in advance Robert From: ext TRABELSI, Slim [mailto:slim.trabelsi at sap.com] Sent: Wednesday, October 19, 2011 5:21 PM To: Seidl, Robert (NSN - DE/Munich); ext BISSON Pascal; Antonio Garcia Vazquez; Michael Osborne Cc: GIDOIN Daniel; fiware-security at lists.fi-ware.eu Subject: RE: Fi-WARE - Security AT - Virtual Workshop with Use Case Dear all, As it was announced during the last confcall. A Task 8.2 workshop will be hosted at SAP Sophia-Antipolis in November 16th. For those who are interested to attend the meeting please let us know. @Robert and @Anja I have to book the rooms know 9:00 to 17:30 is it ok ? Thank you Best regards Slim ===================================== Dr Slim Trabelsi Researcher Security & Trust SAP Labs France 805, Avenue du Docteur Maurice Donat BP 1216 - 06254 Mougins Cedex, France T +33 4 92 28 63 45 M + 33 6 11 99 85 79 www.sap.com From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Sent: mercredi 19 octobre 2011 16:39 To: ext BISSON Pascal; TRABELSI, Slim; Antonio Garcia Vazquez; Michael Osborne Cc: GIDOIN Daniel Subject: RE: Fi-WARE - Security AT - Virtual Workshop with Use Case Hi Pascal, just a quick info. The entire week of 3rd November I'm on vacation. 8th November I'm in principle available, but have already some meetings. 17th and 18th November there is the reference group meeting with the TAS3 project. At the 16th we will have the T8.2 architecture meeting (the day before the TAS3 meeting) and maybe we have to travel at the 15th. So these dates are also not possible from my side (we announced this in our WP8 telco last week). Please mention this to Telefonica. Greetings Robert ________________________________ From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Wednesday, October 19, 2011 3:05 PM To: Seidl, Robert (NSN - DE/Munich); ext TRABELSI, Slim; Antonio Garcia Vazquez; Michael Osborne Cc: BISSON Pascal; GIDOIN Daniel Subject: Fi-WARE - Security AT - Virtual Workshop with Use Case Importance: High Dear All, Find hereafter the actions decided at the last WPL/WPA audio conf I had with Juanjo on Monday. Regarding the virtual workshop on Identity, Access Control, Privacy Management: * AP on Juanjo: To setup doodle for virtual workshop either on Nov 3 or Nov 8. Assumption is that virtual workshop will last 3 hours so doodle will help to select both date and starting time. Juanjo will distribute doodle link to WPLs/WPAs and Pascal to the Security team * AP on Juanjo: Propose UC projects virtual workshop either on Nov 15, Nov 16 or Nov 17. * AP on Pascal: Send soon an email to Security team to make them aware that virtual workshop with UC projects will take place most probably some day during Nov 15-17 period. I'd like here to draw your attention to the fact that: * first meeting (i.e. meeting between Security Team and other ATs focusing on Core GEs so T8.2 GEs) is planned to occur either on Nov 3 or Nov 8. Juanjo will set a doodle that I will communicate you onceestablised. At least and for the time being I'd like each of you to book those dates and especially Robert and T8.2 GE owners. * Second (virtual) meeting even more important since with Use Case projects which demanded it, is planned either on Nov 15, Nov 16 or Nov 17. Same applies here please book those dates especially Robert and T8.2 GE owners and be prepared to fill in the doodle I will forward you once established by Juanjo. That's all for the AP on my side. Keep you posted regarding AP put on Juanjo's side. Best Regards, Pascal PS: Of course and if some of the dates proposed are not possible for you please let me know -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wolfgang.Steigerwald at telekom.de Thu Oct 27 13:48:23 2011 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Thu, 27 Oct 2011 13:48:23 +0200 Subject: [Fiware-security] Task 8.2 and I2ND Message-ID: Hello Robert, we had this week an internal meeting between task 8.2 (Alexandra and me) and 7.4 (Hans, Dimitri and Nico). We looked where are the relevant interface in the architecture are and what is missing. As a first result we marked it in architecture picture (see attachment). We should discuss this as soon as possible. Maybe you could set up an audio conf call? Best regards Wolfgang Deutsche Telekom AG T-Labs (Research & Innovation) Wolfgang Steigerwald Winterfeldtstra?e 21, 10781 Berlin +49 30 8353 54287 (Tel.) +49 171 5664350 (Mobil) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Edward R. Kozel, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft Bonn Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Security-and-I2ND.ppt Type: application/vnd.ms-powerpoint Size: 227840 bytes Desc: Security-and-I2ND.ppt URL: From Hans.Einsiedler at telekom.de Thu Oct 27 15:29:02 2011 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 27 Oct 2011 15:29:02 +0200 Subject: [Fiware-security] FW: Telephone conference for the cooperation between Task 7.3, 7.4 abd Task 8.2 Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A62EBDFA@DEMUEXC027.nsn-intra.net> When: Dienstag, 8. November 2011 16:00-18:00 (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: will be provided Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* FYI, please attend, especially task leaders, WPL and WPA also someone from IBM would be nice to have on the call @Hans: Do you provide a telco bridge, or should I do it? -----Original Appointment----- From: Hans.Einsiedler at telekom.de Sent: Thursday, October 27, 2011 3:06 PM To: Hans.Einsiedler at telekom.de; Wolfgang.Steigerwald at telekom.de; Seidl, Robert (NSN - DE/Munich); fiware-i2nd at lists.fi-ware.eu; Alexandra.Mikityuk at t-systems.com; Nico.Bayer at telekom.de; Dmitry.Sivchenko at telekom.de Subject: Telephone conference for the cooperation between Task 7.3, 7.4 abd Task 8.2 When: Dienstag, 8. November 2011 16:00-18:00 (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: will be provided Importance: High Dear all, I just had a shat with Robert Seidl. He is the Task leader of Task 8.2. We propose a telephone conference to discuss common issues related to the mentioned tasks. Please let me know, if you are available to join the call. Many thanks and cheers, Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 3023 bytes Desc: not available URL: From daniel.le-metayer at inrialpes.fr Sun Oct 30 11:57:16 2011 From: daniel.le-metayer at inrialpes.fr (Daniel Le-Metayer) Date: Sun, 30 Oct 2011 11:57:16 +0100 (CET) Subject: [Fiware-security] Fi-WARE - Security AT - Virtual Workshop with Use Case In-Reply-To: Message-ID: <1570257246.147045.1319972236197.JavaMail.root@zmbs1.inria.fr> Dear Slim, I would very much have liked to attend but I will be in South America all that week. I will try to catch up asap. Best, __ D. ----- Mail original ----- > De: "Slim TRABELSI" > ?: "Robert Seidl (NSN - DE/Munich)" , "ext > BISSON Pascal" , "Antonio Garcia > Vazquez" , "Michael Osborne" > > Cc: fiware-security at lists.fi-ware.eu > Envoy?: Mercredi 19 Octobre 2011 17:21:25 > Objet: Re: [Fiware-security] Fi-WARE - Security AT - Virtual Workshop > with Use Case > Dear all, > As it was announced during the last confcall. A Task 8.2 workshop will > be hosted at SAP Sophia-Antipolis in November 16 th . For those who > are interested to attend the meeting please let us know. > @Robert and @Anja I have to book the rooms know 9:00 to 17:30 is it ok > ? > Thank you > Best regards > Slim > ===================================== > Dr Slim Trabelsi < > nt-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Researcher > Security & Trust > SAP Labs France > 805, Avenue du Docteur Maurice Donat > BP 1216 - 06254 Mougins Cedex, France > T +33 4 92 28 63 45 > M + 33 6 11 99 85 79 > www.sap.com > From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] > Sent: mercredi 19 octobre 2011 16:39 > To: ext BIS SON Pasc io Garcia Vazquez; Michael Osborne > Cc: GIDOIN Daniel > Subject: RE: Fi-WARE - Security AT - Virtual Workshop with Use Case > Hi Pascal, > just a quick info. > The entire week of 3rd November I'm on vacation. > 8th November I'm in prin already some meetings. > 17th and 18th November there is the reference group meeting with the > TAS3 project. > At the 16th we will have the T8.2 architecture meeting (the day before > the TAS3 meeting) and maybe we have to travel at the 15th. > So these dates are also not possible from my side (we announced this > in our WP8 telco last week). > Please mention this to Telefonica. > Greetings > Robert > From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] > Sent: Wednesday, October 19, 2011 3:05 PM > To: Seidl, Robert (NSN - DE/Munich); ext TRABELSI, Slim; Antonio > Garcia Vazquez; Michael Osborne > Cc: BISSON Pascal; GIDOIN Daniel > Subject: Fi-WARE - Security AT - Virtual Workshop with Use Case > Importance: High > Dear All, > Find hereafter the actions decided at the last WPL/WPA audio conf I > had with Juanjo on Monday. > Regarding the virtual workshop on Identity, Access Control, Privacy > Management: > ? AP on Juanjo: To setup doodle for virtual workshop either on Nov 3 > or Nov 8. Assumption is that virtual workshop will last 3 hours so > doodle will help to select both date and starting time. Juanjo will > distribute doodle link to WPLs/WPAs and Pascal to the Security team > ? AP on Juanjo: Propose UC projects virtual workshop either on Nov 15, > Nov 16 or Nov 17. > ? AP on Pascal: Send soon an email to Security team to make them aware > that virtual workshop with UC projects will take place most probably > some day during Nov 15-17 period. > < ang=EN-US> > I?d like here to draw your attention to the fact that: > ? first meeting (i.e. meeting between Security Team and other ATs > focusing on Core GEs so T8.2 GEs) is planned to occur either on Nov 3 > or Nov 8. Juanjo will set a doodle that I will communicate you > onceestablised. At least and for the time being I?d like each of you > to book those dates and especially Robert and T8.2 GE owners. > ? > That?s all for the AP on my side. > Keep you posted regarding AP put on Juanjo?s side. > Best Regards, > PS: Of course and if some of the dates proposed are not possible for > you please let me know > _______________________________________________ > Fiware-security mailing list > Fiware-security at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: