From pierangelo.garino at telecomitalia.it Mon Oct 3 11:28:29 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 3 Oct 2011 11:28:29 +0200 Subject: [Fiware-i2nd] Some detail about I2ND Action Points defined in last confcall Message-ID: Dear All, In our last confcall we defined a number of actions to be performed, some are urgent!, so let me try and explain how to progress more rapidly, according to the clarifications I got from the periodic call I had with Juanjo and Thomas on Friday (maybe with some simplification that I hope doesn't create other concerns and/or doubts), and define what is practically expected to be done by all of us. 1. The Product Vision is what we are going to implement in FI-WARE, split into each FI-WARE Chapter: this is of course our GEs (so our final products!), and this description details the functionality we want to provide for each of them, and their interfacing. The Product Vision is described by the Fi-WARE Wiki page(s) at URL https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision and is 'automatically' translated from the High Level Description (D2.2a) document. 2. Portions of the Product Vision functionality may have been already available, through the Assets each partner is contributing to the project. There will be a place where the assets will be described in the Wiki pages (associated to the Product Vision). For the time being the guidelines to insert the asset descriptions are not yet available. As soon as available I'll tell you how they need to be uploaded; for sure they will derive from the asset descriptions we have already produced or we are (still) producing now. *So please do strictly comply with the rules for asset description we established in our I2ND confcall last week, and provide them urgently (see Action Points from I2ND40 to I2ND42)*. 3. There are further functionalities of our GEs which are not yet available/implemented (e.g. no asset available for them), but they need to be provided to complete the expected functionality of the GE: these are the 'things to do'. We have to 'capture' them through the EPICs descriptions we started to generate in past weeks and insert them in the FI-WARE Backlog (see point 4 below). *This is our main work concerning EPICS to be done right now (see Action Points I2ND43-I2ND45)!* Some more details: o An EPIC should represent mostly work to be done (i.e. developments in the project's lifetime). They can however represent a mix of available functionalities (already available through the assets) and new functionalities. o An EPIC representing more than 75-80% of an assets functionality is not considered an EPIC for FI-WARE; we should therefore try and focus the EPIC on the 'missing' parts. A consistent Chapter EPIC should represent max 25% of available functionality and the remaining description should refer to 'work to be done'. o More clarifications about the EPIC contents and their difference with respect to Features/User Stories can be found in the attached mail (it was a request by one Chapter member to Juanjo for clarifications) and in the Wiki page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology . Remember that the 'hierarchy' is Themes/EPICs/Feature/User Stories. 'Feature' entry is new, and sits in between EPICs and User Stories; it was introduced to provide Use Case Projects more detailed capabilities. o One further rule of thumb: EPICs have to be useful to us that will have to implement the functionality required, remember this when describing them... 4. Once the EPICs comply with the rules explained above, we have to enter them in the FI-WARE Backlog, here is how to do it (this is answer to Action Point I2ND44): o Read carefully the tutorial at Wiki page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_add_the_full_description_of_backlog_entries_to_the_Wiki I believe the explanation is rather clear, and it should not create troubles. o The https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog WIki page contains already some EPICs introduced by other Chapters, you can see how the final result of your insertion should look like. o Please agree with the Task Leader the insertion of the EPICs in the FI-WARE backlog. *We have to urgently target the insertion of the Primary EPICs we defined in our last confcall*. TLs should in turn talk to Hans and me for coordination of this process (and for any further doubt about EPICs insertion). o At a later stage the FI-WARE Backlog entries will be associated to entries in the FI-WARE Tracker (more info on this step asap). Sorry if this mail is rather long, I hope however it can dissipate some of the doubts you might still have about the actions we need to do. For further clarifications please share with all of us the issues you might identify. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro Subject: Re: [Fiware-wpl] FI-WARE - Urgent - delivrables to provide for tomorrow - request for clarification Date: Thu, 29 Sep 2011 19:39:22 +0200 Size: 33860 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From castrucci at dis.uniroma1.it Tue Oct 4 10:23:32 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Tue, 4 Oct 2011 10:23:32 +0200 Subject: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Message-ID: <003001cc826e$e81e3910$d028a8c0@cratr70> Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Tue Oct 4 11:20:32 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 4 Oct 2011 11:20:32 +0200 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) In-Reply-To: <003001cc826e$e81e3910$d028a8c0@cratr70> References: <003001cc826e$e81e3910$d028a8c0@cratr70> Message-ID: Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? - For this reason, is the use of class diagrams limiting us or not? - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From castrucci at dis.uniroma1.it Tue Oct 4 12:55:14 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Tue, 4 Oct 2011 12:55:14 +0200 Subject: [Fiware-i2nd] Proposal for specification conventions (I2ND49) References: <003001cc826e$e81e3910$d028a8c0@cratr70> Message-ID: <00b101cc8284$18caf570$d028a8c0@cratr70> Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From marius-iulian.corici at fokus.fraunhofer.de Tue Oct 4 17:18:16 2011 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Tue, 4 Oct 2011 17:18:16 +0200 Subject: [Fiware-i2nd] Task 7.4 EPICs Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBB27@EXCHSRV.fokus.fraunhofer.de> Hello Task 7.4, Please find the EPICs on the Wiki page with EPICs https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE _Backlog#Network_services coordinated on DT and Fraunhofer input, considering also the Ericsson and the Orange assets and the .xls form at the link: https://forge.fi-ware.eu/docman/view.php/10/454/S3C_EPICs_v0+2_Fraunhofe r_DT.xls Please forgive us, if any information was lost during the process. Any comments and modifications are more than welcomed. Greetings, Marius Corici -- Dipl.-Eng. Marius Corici, Senior Researcher Fraunhofer FOKUS Institute Competence Center for Next Generation Network Infrastructures (NGNI) Phone: +49 30 3463 7271 email: marius-iulian.corici at fokus.fraunhofer.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.woods at intel.com Tue Oct 4 18:08:03 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 4 Oct 2011 17:08:03 +0100 Subject: [Fiware-i2nd] Personal Introduction - Hello All Message-ID: <187F4CC97FD0B6488FAE608A8038FF1439142C9D@irsmsx503.ger.corp.intel.com> Hello All, I am Chris Woods a new researcher with Intel. I am new on this project so, just wanted to introduce myself virtually on the email list. A little bit about me: My background is in software development across both the cloud and mobile devices. I have previously worked as a Program Manager at Microsoft on Windows Azure Infrastructure, delivering software components for Azure, including high availability automated DNS APIs and analysing Microsoft's cloud monitoring and reliability. While at Microsoft I also worked on mobile adaptive rendering for Hotmail, Bing, and MSN. I released one of the few Microsoft Open Source projects, for enabling for mobile device detection. Prior to Microsoft I held development positions in the mobile industry working at Symbian on the PIM database, and designing Wi-Fi APIs, delivering training courses to Nokia on Symbian development, and creating Linux, Windows, and Symbian device drivers for Wi-Fi and NAND devices. More recently I have been involved in Android development, creating mobile and cloud applications for social networking integration, and encountering some of the issues I hope I too able to address here. I am delighted to join the project and look forward to working with you all. All the best, Chris ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 5 10:21:27 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 5 Oct 2011 10:21:27 +0200 Subject: [Fiware-i2nd] R: Personal Introduction - Hello All In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF1439142C9D@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF1439142C9D@irsmsx503.ger.corp.intel.com> Message-ID: Dear Chris, welcome to the I2ND group of FI-WARE! Your background couldn't be better for working with us ;-) Seriously speaking, I'm really pleased that you'll be working in I2ND, the know-how you bring to it will be extremely important, especially concerning the Generic Enabler in Task 7.1 'Connected Device Interfacing'. By following the discussions going on through the mailing list, you'll be able intercept some of the current topics we are working on; I invite you to have a look also at the I2ND doc repository at https://forge.fi-ware.eu/docman/?group_id=10 ; in particular you'll find, in the documents of the folder 'General/Telephone Conference Minutes', the list of latest action points we defined (you have to be logged in on the Forge site to access those documents, as they are private to the project). I also anticipate that we have (periodic) I2ND confcalls scheduled on Wednesday at 10:00 a.m. (CEST): next is on Oct 12th, you'll receive in advance the details to join the call. For any other general clarification on the group activity please don't hesitate to contact me either by mail or by phone (number below). Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Woods, Chris Inviato: marted? 4 ottobre 2011 18:08 A: fiware-i2nd Oggetto: [Fiware-i2nd] Personal Introduction - Hello All Hello All, I am Chris Woods a new researcher with Intel. I am new on this project so, just wanted to introduce myself virtually on the email list. A little bit about me: My background is in software development across both the cloud and mobile devices. I have previously worked as a Program Manager at Microsoft on Windows Azure Infrastructure, delivering software components for Azure, including high availability automated DNS APIs and analysing Microsoft's cloud monitoring and reliability. While at Microsoft I also worked on mobile adaptive rendering for Hotmail, Bing, and MSN. I released one of the few Microsoft Open Source projects, for enabling for mobile device detection. Prior to Microsoft I held development positions in the mobile industry working at Symbian on the PIM database, and designing Wi-Fi APIs, delivering training courses to Nokia on Symbian development, and creating Linux, Windows, and Symbian device drivers for Wi-Fi and NAND devices. More recently I have been involved in Android development, creating mobile and cloud applications for social networking integration, and encountering some of the issues I hope I too able to address here. I am delighted to join the project and look forward to working with you all. All the best, Chris ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Wed Oct 5 10:34:41 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 5 Oct 2011 10:34:41 +0200 Subject: [Fiware-i2nd] R: Task 7.4 EPICs In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBB27@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBB27@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi Marius, thanks for your uploads. A general information to all the Team members. Beware of the Forge uploading mechanism: when you upload a document, by default it will be classified as 'public' and you cannot force it in other ways. You have then to perform a second action: that is go to 'Admin', select your document (which appears in the 'Active', i.e. public list), and force it to be Private. Marius can you please do it now for your EPIC's excel file, and if you don't succeed inform me, thanks. I know this is an annoying procedure: the Forge team is trying to force by default the documents as 'private', but it seems this is not one of the configuration options we can play with in FusionForge... BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: marted? 4 ottobre 2011 17:18 A: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Task 7.4 EPICs Hello Task 7.4, Please find the EPICs on the Wiki page with EPICs https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog#Network_services coor fer input, considering also the Ericsson and the Orange assets and the .xls form at the link: https://forge.fi-ware.eu/docman/view.php/10/454/S3C_EPICs_v0+2_Fraunhofer_DT.xls Please forgive us, if any information was lost during the process. Any comments and modifications are more t /span> Greetings, Marius Corici -- Dipl.-Eng. Marius Corici, Senior Researcher Fraunhofer FOKUS Institute Competence Center for Next Generation Network Infrastructures (NGNI) Phone: +49 30 3463 7271 email: marius-iulian.corici at fokus.fraunhofer.de Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Wed Oct 5 10:58:32 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 5 Oct 2011 10:58:32 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] Instructions on how to proceed with assets soon In-Reply-To: <4E8C1ABC.1020405@tid.es> References: <4E8C1ABC.1020405@tid.es> Message-ID: Dear All, *please suspend for a while* any activity you might be doing on the FI-WARE Wiki, as there is some possible modification going on in the next few minutes. As soon as the operation is complete I'll inform you. BR Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 5 ottobre 2011 10:52 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From pierangelo.garino at telecomitalia.it Thu Oct 6 11:32:26 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 6 Oct 2011 11:32:26 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further In-Reply-To: <4E8C2AFB.2020302@tid.es> References: <4E8C2AFB.2020302@tid.es> Message-ID: Dear All, please find below a description of how the Wiki pages concerning FI-WARE have been modified, to better represent vision, assets and backlog. Please carefully check the instructions, and *follow them* to restart inserting the EPICs and asset description when the definition process is done. You'll see the *current 'FI-WARE backlog' page is deprecated*. You have therefore to insert everything in the page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%2812ND%29_in_FI-WARE For already existing EPICs, you just need to copy from the previous page the link, and insert it in the EPICs section of the corresponding GE in the new page (have a look at the FIWARE.Epic.I2ND.CDI.QoE example: I just edited that CDI section inserting * [[FIWARE.Epic.I2ND.CDI.QoE]] and the link to previous description was ok). For any doubt please contact me. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 5 ottobre 2011 12:02 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From castrucci at dis.uniroma1.it Thu Oct 6 14:51:44 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Thu, 6 Oct 2011 14:51:44 +0200 Subject: [Fiware-i2nd] Proposal for specification conventions (I2ND49) References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> Message-ID: <016501cc8426$b5021ce0$d028a8c0@cratr70> Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ---------------------------------------------------------------------------- ------------------------------------------------------------------------------ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Oct 6 15:03:48 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 6 Oct 2011 15:03:48 +0200 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) In-Reply-To: <016501cc8426$b5021ce0$d028a8c0@cratr70> References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> Message-ID: Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams... If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From castrucci at dis.uniroma1.it Thu Oct 6 15:19:47 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Thu, 6 Oct 2011 15:19:47 +0200 Subject: [Fiware-i2nd] Proposal for specification conventions (I2ND49) References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> Message-ID: <01ad01cc842a$a0147590$d028a8c0@cratr70> Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams. If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------------------------------------------------------------------- ---------------------------------------------------------------------------- _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Oct 7 11:39:51 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 7 Oct 2011 11:39:51 +0200 Subject: [Fiware-i2nd] T7.1: EPICs about CDI GE Message-ID: Dear All, I have prepared a set of EPICs (still in excel format at the moment), you find the file at: https://forge.fi-ware.eu/docman/view.php/10/470/Backlog+entries_CDI-2.xls Basically there's one EPIC per CDI interface category (service) according to the set we defined in the High Level Description, while for User identity, security and privacy there's a separate one, which also implies a link with Security Team activities. I would consider these, along with the QoSQoE one already in the Wiki, the set of Primary EPICs for CDI. Please have a look at them approving or proposing modifications; I'll upload them in the Wiki pages of the project by this afternoon. Feel free of course to add other EPICs you consider 'Primary' for CDI, but I remind you that it must be done by today. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Fri Oct 7 15:09:24 2011 From: chris.woods at intel.com (Woods, Chris) Date: Fri, 7 Oct 2011 14:09:24 +0100 Subject: [Fiware-i2nd] T7.1: EPICs about CDI GE In-Reply-To: References: Message-ID: <187F4CC97FD0B6488FAE608A8038FF143919B376@irsmsx503.ger.corp.intel.com> Hi Pier, Thank you for putting this together. I've reviewed the EPICs and supplied an updated version of the document. https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw2%29.xls Summary of my changes: 1. Reworded EPICs around the requests of an actor (usually a FI-Ware application developer) 2. Added EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.Phone Describing access to phone capabilities; making calls, call log view etc. 3. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceFeatures to focus on the detection of functionality available on the handset 4. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceServices to focus on the utilisation of functionality detected in DeviceFeatures Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, October 07, 2011 10:40 AM To: Vincenzo Suraci; Woods, Chris; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Subject: T7.1: EPICs about CDI GE Dear All, I have prepared a set of EPICs (still in excel format at the moment), you find the file at: https://forge.fi-ware.eu/docman/view.php/10/470/Backlog+entries_CDI-2.xls Basically there's one EPIC per CDI interface category (service) according to the set we defined in the High Level Description, while for User identity, security and privacy there's a separate one, which also implies a link with Security Team activities. I would consider these, along with the QoSQoE one already in the Wiki, the set of Primary EPICs for CDI. Please have a look at them approving or proposing modifications; I'll upload them in the Wiki pages of the project by this afternoon. Feel free of course to add other EPICs you consider 'Primary' for CDI, but I remind you that it must be done by today. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC84F8.056431B0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Fri Oct 7 15:37:05 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 7 Oct 2011 15:37:05 +0200 Subject: [Fiware-i2nd] R: T7.1: EPICs about CDI GE In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143919B376@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143919B376@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris, thanks a lot for your revision, I see we're immediately exploiting your expertise on Agile methodologies :) In relationship to the EPICs, I received this morning a number of mails from Juanjo, and in one of them I recognize it is said what probably is not completely true for those I proposed: indeed, it is not always true that what described in our EPICs corresponds to 'work to be done', as some of the functionality could be already available through our assets (I consider mainly those from TI). Maybe a second revision later will be necessary to avoid this 'discrepancy', but we need to have the description of all assets we are bringing to CDI's development to perform it. Hence I will insert the EPICs in the Wiki pages. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: venerd? 7 ottobre 2011 15:09 A: Garino Pierangelo; Vincenzo Suraci; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: T7.1: EPICs about CDI GE Hi Pier, Thank you for putting this together. I've reviewed the EPICs and supplied an updated version of the document. https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw2%29.xls Summary of my changes: 1. Reworded EPICs around the requests of an actor (usually a FI-Ware application developer) 2. Added EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.Phone Describing access to phone capabilities; making calls, call log view etc. 3. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceFeatures to focus on the detection of functionality available on the handset 4. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceServices to focus on the utilisation of functionality detected in DeviceFeatures Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, October 07, 2011 10:40 AM To: Vincenzo Suraci; Woods, Chris; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Subject: T7.1: EPICs about CDI GE Dear All, I have prepared a set of EPICs (still in excel format at the moment), you find the file at: https://forge.fi-ware.eu/docman/view.php/10/470/Backlog+entries_CDI-2.xls Basically there's one EPIC per CDI interface category (service) according to the set we defined in the High Level Description, while for User identity, security and privacy there's a separate one, which also implies a link with Security Team activities. I would consider these, along with the QoSQoE one already in the Wiki, the set of Primary EPICs for CDI. Please have a look at them approving or proposing modifications; I'll upload them in the Wiki pages of the project by this afternoon. Feel free of course to add other EPICs you consider 'Primary' for CDI, but I remind you that it must be done by today. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8506.F7A78270]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Fri Oct 7 15:42:06 2011 From: chris.woods at intel.com (Woods, Chris) Date: Fri, 7 Oct 2011 14:42:06 +0100 Subject: [Fiware-i2nd] T7.1: EPICs about CDI GE In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143919B376@irsmsx503.ger.corp.intel.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143919B392@irsmsx503.ger.corp.intel.com> Hi Pier, Yes - I think the epics should cover all functionality, some of which may already be delivered by pre-existing assets, and others will need to be constructed. I'll provide a list of the currently known assets - Joe forwarded me a collection of disparate emails form different partners. I'll collate these in one document - this should provide us with an easy overview of what already exists. I'll provide this on the Forge by close of business today. - Hope this helps. Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, October 07, 2011 2:37 PM To: Woods, Chris; Vincenzo Suraci; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: T7.1: EPICs about CDI GE Hi Chris, thanks a lot for your revision, I see we're immediately exploiting your expertise on Agile methodologies :) In relationship to the EPICs, I received this morning a number of mails from Juanjo, and in one of them I recognize it is said what probably is not completely true for those I proposed: indeed, it is not always true that what described in our EPICs corresponds to 'work to be done', as some of the functionality could be already available through our assets (I consider mainly those from TI). Maybe a second revision later will be necessary to avoid this 'discrepancy', but we need to have the description of all assets we are bringing to CDI's development to perform it. Hence I will insert the EPICs in the Wiki pages. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: venerd? 7 ottobre 2011 15:09 A: Garino Pierangelo; Vincenzo Suraci; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: T7.1: EPICs about CDI GE Hi Pier, Thank you for putting this together. I've reviewed the EPICs and supplied an updated version of the document. https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw2%29.xls Summary of my changes: 1. Reworded EPICs around the requests of an actor (usually a FI-Ware application developer) 2. Added EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.Phone Describing access to phone capabilities; making calls, call log view etc. 3. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceFeatures to focus on the detection of functionality available on the handset 4. Redefinition of EPIC.FIWARE.I2ND.ConnectedDeviceInterfacing.DeviceServices to focus on the utilisation of functionality detected in DeviceFeatures Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, October 07, 2011 10:40 AM To: Vincenzo Suraci; Woods, Chris; Butler, Joe M Cc: fiware-i2nd at lists.fi-ware.eu Subject: T7.1: EPICs about CDI GE Dear All, I have prepared a set of EPICs (still in excel format at the moment), you find the file at: https://forge.fi-ware.eu/docman/view.php/10/470/Backlog+entries_CDI-2.xls Basically there's one EPIC per CDI interface category (service) according to the set we defined in the High Level Description, while for User identity, security and privacy there's a separate one, which also implies a link with Security Team activities. I would consider these, along with the QoSQoE one already in the Wiki, the set of Primary EPICs for CDI. Please have a look at them approving or proposing modifications; I'll upload them in the Wiki pages of the project by this afternoon. Feel free of course to add other EPICs you consider 'Primary' for CDI, but I remind you that it must be done by today. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC84FF.48D6DEF0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC84FF.48D6DEF0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Fri Oct 7 16:29:28 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 7 Oct 2011 16:29:28 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] 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: Dear All, Some further clarification on backlog contents, please take them into account when producing your inputs. Have a nice weekend BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 7 ottobre 2011 09:36 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From Thomas-Rolf.Banniza at alcatel-lucent.com Fri Oct 7 16:53:00 2011 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Fri, 7 Oct 2011 16:53:00 +0200 Subject: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: A References: <4E8EABF5.5000206@tid.es> A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> Hi Pier, from the pure AGILE point of view, Junajo might be right. But: Where is the place where it is really described what a customer (other FiWare WP, use case project) can expect from the GE? If the EPIC will describe only what's new (or more exact: what still has to be developed), I have seen no place where a comprehensive description of a functionality (new, still to be developed, function together with the appropriately attached assets). Or did I miss something in this story? Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Freitag, 7. Oktober 2011 16:29 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Dear All, Some further clarification on backlog contents, please take them into account when producing your inputs. Have a nice weekend BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 7 ottobre 2011 09:36 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Fri Oct 7 17:03:14 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 7 Oct 2011 17:03:14 +0200 Subject: [Fiware-i2nd] R: I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> References: <4E8EABF5.5000206@tid.es> A <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi Thomas, According what Juanjo said in his mail, the customer can 'build' the overall picture by doing the three actions below: * 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 Maybe this is a different way to provide this kind of information, but it is probably avoiding us (or at least we were told this ;-) to provide very huge and time consuming requirements + specifications documents. Also for me this is an approach I never used in the past, so I cannot evaluate if it is worth doing it or not: so I rely on who has already some expertise and experience in adopting it. So we should accelerate in the definition of assets to be adopted, and complete the EPICs. On the other hand, some 'mixing' of functionality already available through the assets and some to be developed (work to be done) is possible in the EPIC descriptions. Hope this clarifies the point. Have a nice weekend :) Pier Da: BANNIZA, Thomas-Rolf [mailto:Thomas-Rolf.Banniza at alcatel-lucent.com] Inviato: venerd? 7 ottobre 2011 16:53 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: AW: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Hi Pier, from the pure AGILE point of view, Junajo might be right. But: Where is the place where it is really described what a customer (other FiWare WP, use case project) can expect from the GE? If the EPIC will describe only what's new (or more exact: what still has to be developed), I have seen no place where a comprehensive description of a functionality (new, still to be developed, function together with the appropriately attached assets). Or did I miss something in this story? Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Freitag, 7. Oktober 2011 16:29 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Dear All, Some further clarification on backlog contents, please take them into account when producing your inputs. Have a nice weekend BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 7 ottobre 2011 09:36 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8513.004BC420]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Fri Oct 7 18:08:10 2011 From: chris.woods at intel.com (Woods, Chris) Date: Fri, 7 Oct 2011 17:08:10 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> References: <4E8EABF5.5000206@tid.es> A <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143919B433@irsmsx503.ger.corp.intel.com> Hi Folks, I've some experience as a scrum master, typically an agile project would be described in differing blocks of granularity. Each block describing the project in increasing detail. Where a theme breaks down into many epics, which in turn break down into many user stories, which in turn break down into many implementation tasks, effectively a large tree. I've put together the table below, I hope this helps. - I shows how I've broken down agile projects before. Chris Title Theme Epic User story / features Implementation task Level of detail Very Low Low Medium -functional details provided High - Implementation details provided Description A very high level statement of the project goal. Many epic's or "scenarios" which many result in the project achieving the goal stated in the theme Suggested user stories which Coverage All functionality All functionality All functionality Only the functionality which needs to be implemented. - These are work items. If an asset already implements a feature, then there is no need for an implementation task, as this has already been completed. Examples Change the way the world consumes music John, a music lover, really enjoys having access to great music wherever he travels. Example 1: John, a music lover, packs all of his CDs into a carry case to bring on holiday. (rejected) Example 2: John, a music lover, rips his CDs, converting all of them to mp3s and takes them with him on his iPod (rejected) Example 3: John, a music lover, subscribes to a service and can stream music to his phone anywhere in the world. Access is provided by an easy to use mobile phone application. (accepted) Example 1: Create a cloud music service at (ilovemusic.fiware.com). Provide a UI with a login button on the top left in bright red with yellow text.... (etc.).. Example 2: Produce a design document which outlines the core APIs... (etc) Typical process Many epics or scenarios are created. Each epic or scenario is evaluated by team members against the original theme. Epics are reviewed, some are dropped, others created, and some revised. The result is a set of epics which the team believe will allow the project to succeed. Typically an epic will not include implementation detail (unless strictly needed). This allows various user stories to be evaluated against the epic. For a single epic many user stories will be generated. Each user story will be reviewed against any criteria specified in the epic. E.g. does this allow a developer to achieve their goal? The user stories are updated and reviewed so that only the ones which will best match the epic are accepted by the team. Typically a user story will contain implementation details. This allows various implementation ideas to be discussed and evaluated. A detailed description of the feature, broken down into implementation tasks. These are tracked on the backlog. Tasks here can also include "Use asset X to provide core music playback functionality" etc. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of BANNIZA, Thomas-Rolf Sent: Friday, October 07, 2011 3:53 PM To: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Hi Pier, from the pure AGILE point of view, Junajo might be right. But: Where is the place where it is really described what a customer (other FiWare WP, use case project) can expect from the GE? If the EPIC will describe only what's new (or more exact: what still has to be developed), I have seen no place where a comprehensive description of a functionality (new, still to be developed, function together with the appropriately attached assets). Or did I miss something in this story? Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Freitag, 7. Oktober 2011 16:29 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement Dear All, Some further clarification on backlog contents, please take them into account when producing your inputs. Have a nice weekend BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 7 ottobre 2011 09:36 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC850A.1D6865D0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Mon Oct 10 16:30:04 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 10 Oct 2011 16:30:04 +0200 Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Message-ID: Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jhierro at tid.es Tue Oct 11 10:24:43 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Oct 2011 10:24:43 +0200 Subject: [Fiware-i2nd] R: I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement In-Reply-To: References: <4E8EABF5.5000206@tid.es> A <133D9897FB9C5E4E9DF2779DC91E947C0680DC6C@SLFSNX.rcs.alcatel-research.de> Message-ID: <4E93FD4B.3000408@tid.es> On 07/10/11 17:03, Garino Pierangelo wrote: Hi Thomas, According what Juanjo said in his mail, the customer can ?build? the overall picture by doing the three actions below: * 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 You are right. * Maybe this is a different way to provide this kind of information, but it is probably avoiding us (or at least we were told this ;-) to provide very huge and time consuming requirements + specifications documents. Also for me this is an approach I never used in the past, so I cannot evaluate if it is worth doing it or not: so I rely on who has already some expertise and experience in adopting it. I want to point out that the approach we have put in place is not strictly related to Agile. In a project where we were developing a product we had started from the scratch and we follow Agile, in its pure terms, the overall picture would be build by just reading: * The product vision, which would give the user an overview of what is expected in the product * The product backlog, which describes those functionalities that will be addressed (from Themes through Epics, corresponding to functionalities that are considered but still too high-level to plan, up to Features and User-Stories corresponding to functionalities enough detailed as to be planned in a release or sprint) However, we had to deal with the fact that FI-WARE didn't start from the scratch. We will rely on a number of assets which will be adopted as baseline for creating the reference implementation of GEs. How do we deal with the fact that a relevant amount of work has already been done ? How should/can we document it ? Carrying out a "reverse engineering" process targeted to documenting what has already been done, in the form of backlog entries could have been a choice but we definitively discarded this approach for two reasons: * It had been a great effort that would simply delayed us. * It goes a little bit against "Agile" philosophy: backlogs are a) about what has to be developed and b) producing stuff that useful in driving that development. Of course, as development progress, we will have a history of Epics/Features/User-stories that have been developed and tested but ... Do we need to document the history previous to the FI-WARE Project ? It definitively doesn't add to much value in driving future development (i.e., point b)) * There should be documentation already available and linked to the assets even if they were not developed using Agile: User's/Programmer's Guides, Tutorials, Specifications .... why don't simply use it to document what is our baseline ? That's why we have considered the three points (FI-WARE Product Vision, publicly available documentation of the baseline assets and FI-WARE backlog) as the ingredients that allow to compose a complete vision. It's a matter of pragmatism. We had to be able to provide UC projects as much information as possible of the GEs (how they will look like, what sort of functionality and APIs they will support, etc) and the sooner possible. The adopted approach may not be the most "academic" one, but should work and is more lightweight. Hope it helps, -- 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 pierangelo.garino at telecomitalia.it Tue Oct 11 12:20:54 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 12:20:54 +0200 Subject: [Fiware-i2nd] Asset descriptions in FI-WARE wiki pages Message-ID: Dear All, The insertion of asset description in the wiki pages needs to reflect the understanding of asset's usage to cope with GE functionalities (i.e. a selection process, which is in some case already done, in others it is not so complete yet, so I kindly ask to progress on this steps urgently, mainly coordinated by Task Leaders). Once this step is done, we'll have to insert the assets in the wiki pages (I remind we must finish this process by tomorrow EOB, at least for our primary assets), here are the instructions we were given to proceed in this step: In the 'Materializing the I2ND in FI-WARE' page, you can find a section concerning the Baseline Assets for each Generic Enabler: Here you should enumerate the assets that will be considered for implementing that GE. For each asset, a link to a dedicated Wiki page should be created, describing the asset. In order to do this: o 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) o 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) o The description of assets in the wiki usually exploits the description we produced as Word documents so far, so please use that material to populate the wiki page. If some asset was not yet described in that way, it is probably worth describing it directly in the wiki page. o Please remember that the wiki pages are publicly available, so carefully consider what details you would like to disclose of your assets. Please agree with the Task Leaders the upload of your asset descriptions, according to the rules above, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Tue Oct 11 13:23:48 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 11 Oct 2011 12:23:48 +0100 Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets In-Reply-To: References: Message-ID: <187F4CC97FD0B6488FAE608A8038FF143919BA7D@irsmsx503.ger.corp.intel.com> Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here. Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC880B.3DC06AE0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: functionality to epic map.pdf Type: application/pdf Size: 947187 bytes Desc: functionality to epic map.pdf URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From pierangelo.garino at telecomitalia.it Tue Oct 11 14:00:59 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 14:00:59 +0200 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) In-Reply-To: <01ad01cc842a$a0147590$d028a8c0@cratr70> References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> <01ad01cc842a$a0147590$d028a8c0@cratr70> Message-ID: Dear Marco, yesterday during the WPL/WPA confcall I mentioned that as I2ND we prepared a proposal for specs conventions etc, and I have been invited to submit it through the mailing list, so that we can start the discussion on that basis. Before doing that, I'd like to have your comment about one point: we're proposing the use of UML as modeling language, while I noticed that in other chapters (mainly Security one) there is a proposal to adopt USDL. I'm new to USDL (as to UML in fact...) so could you tell me/us if you had a look at it, and maybe provide some comparison note about the two, e.g. whether they are overlapping or complementary or whatever else, etc? Many thanks BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 15:20 A: Garino Pierangelo Cc: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams... If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Tue Oct 11 14:16:04 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 14:16:04 +0200 Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143919BA7D@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143919BA7D@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris, I'm fine with the new list of EPICs; basically the previous versions were each addressing one functionality group as depicted in the High Level Description of I2ND, along with few more EPICs 'specialised' on specific topics. I believe that the current list is still completing the picture, in particular in conjunction with the nice mapping onto functionality you provided. One comment: the MediaServices EPIC was originated based on the inputs by Joe about additional functionality which can be offered by the CDI: if you agree, I'd put Intel and yourself as stakeholder and owner. If no other comments come, I'll complete the uploading of the EPICs in the wiki. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 11 ottobre 2011 13:24 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: Urgent actions concerning EPICs/Assets Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here. Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8820.11983320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Tue Oct 11 14:30:33 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 14:30:33 +0200 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, please find below the details for the I2ND periodic confcall we?ll have tomorrow (I?d like to strictly stay within one hour of call max). Here is the proposed agenda: * Complete Primary EPICs description and upload to wiki (can Task Leaders briefly report on this) * Complete Primary Asset description and upload to wiki (can Task Leaders briefly report on this) * Reporting and actions from periodic WPL/WPA meeting * General aspects on wiki usage * Use of Chapter?s backlog * Follow-up on conventions to be adopted for specs * Follow-up on Security team interaction * AOB Please take note that this time we?ll use a different bridge! Confcall Details: Time: 10:00 CEST PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com Best Regards Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3911 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USA_en_pwn-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: USA_en_pwn-dial-in-numbers.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From marius-iulian.corici at fokus.fraunhofer.de Tue Oct 11 14:58:07 2011 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Tue, 11 Oct 2011 14:58:07 +0200 Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDDA@EXCHSRV.fokus.fraunhofer.de> Hello, We checked again the security issues in the NetIC (less) and in the S3C (more) and attached is a document including the additions to section 3.3 on our contribution to D2.2. Any comments are more than welcomed. Should we complete this on the wikipage which mirrors the document, or? Greetings, Marius Corici From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Tuesday, October 11, 2011 2:16 PM To: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Chris, I'm fine with the new list of EPICs; basically the previous versions were each addressing one functionality group as depicted in the High Level Description of I2ND, along with few more EPICs 'specialised' on specific topics. I believe that the current list is still completing the picture, in particular in conjunction with the nice mapping onto functionality you provided. One comment: the MediaServices EPIC was originated based on the inputs by Joe about additional functionality which can be offered by the CDI: if you agree, I'd put Intel and yourself as stakeholder and owner. If no other comments come, I'll complete the uploading of the EPICs in the wiki. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 11 ottobre 2011 13:24 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: Urgent actions concerning EPICs/Assets Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here . Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NetIC_S3C_Security_Items.docx Type: application/octet-stream Size: 14800 bytes Desc: NetIC_S3C_Security_Items.docx URL: From pierangelo.garino at telecomitalia.it Tue Oct 11 15:40:36 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 15:40:36 +0200 Subject: [Fiware-i2nd] R: R: Urgent actions concerning EPICs/Assets In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDDA@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDDA@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi Marius, Many thanks for your contribution. Did you consider the added items applicable to the two GEs (NetIC+S3C), or only linked to one of the two GEs? By having a first look, it seems to me that Secure Exposure could be applied to both (well, to all the GEs in I2ND), Secure Control Environment again to both, and Privacy Protection is mainly for S3C (and I'd say to CDI and CE too...). I'm going to insert some update involving CDI, then I'll circulate the new version for further improvements. Then, we'll share it with the Security guys (hopefully by tomorrow). For what concerns the insertion in the wiki, we still have to define how to update the section (or maybe create new ones); this will be done in next days in conjunction with the Security team and the Team Manager. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: marted? 11 ottobre 2011 14:58 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Oggetto: RE: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hello, We checked again the security issues in the NetIC (less) and in the S3C (more) and attached is a document including the additions to section 3.3 on our contribution to D2.2. Any comments are more than welcomed. Should we complete this on the wikipage which mirrors the document, or? Greetings, Marius Corici From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Tuesday, October 11, 2011 2:16 PM To: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Chris, I'm fine with the new list of EPICs; basically the previous versions were each addressing one functionality group as depicted in the High Level Description of I2ND, along with few more EPICs 'specialised' on specific topics. I believe that the current list is still completing the picture, in particular in conjunction with the nice mapping onto functionality you provided. One comment: the MediaServices EPIC was originated based on the inputs by Joe about additional functionality which can be offered by the CDI: if you agree, I'd put Intel and yourself as stakeholder and owner. If no other comments come, I'll complete the uploading of the EPICs in the wiki. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 11 ottobre 2011 13:24 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: Urgent actions concerning EPICs/Assets Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here. Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC882C.1E974370]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC882C.1E974370]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From marius-iulian.corici at fokus.fraunhofer.de Tue Oct 11 16:00:44 2011 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Tue, 11 Oct 2011 16:00:44 +0200 Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets In-Reply-To: References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDDA@EXCHSRV.fokus.fraunhofer.de> Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDE5@EXCHSRV.fokus.fraunhofer.de> Hello Pier, We tried to combine the use cases of the two GEs. As I remember from the meeting in Torino and please correct me if I am wrong the NetIC has most of the security requirements either the same or responded through the S3C. Secure exposure may be for all the communication with other third parties same for the control environment. Privacy protection is more subscriber related and thus only S3C. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Tuesday, October 11, 2011 3:41 PM To: Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Subject: R: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Marius, Many thanks for your contribution. Did you consider the added items applicable to the two GEs (NetIC+S3C), or only linked to one of the two GEs? By having a first look, it seems to me that Secure Exposure could be applied to both (well, to all the GEs in I2ND), Secure Control Environment again to both, and Privacy Protection is mainly for S3C (and I'd say to CDI and CE too...). I'm going to insert some update involving CDI, then I'll circulate the new version for further improvements. Then, we'll share it with the Security guys (hopefully by tomorrow). For what concerns the insertion in the wiki, we still have to define how to update the section (or maybe create new ones); this will be done in next days in conjunction with the Security team and the Team Manager. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: marted? 11 ottobre 2011 14:58 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Oggetto: RE: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hello, We checked again the security issues in the NetIC (less) and in the S3C (more) and attached is a document including the additions to section 3.3 on our contribution to D2.2. Any comments are more than welcomed. Should we complete this on the wikipage which mirrors the document, or? Greetings, Marius Corici From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Tuesday, October 11, 2011 2:16 PM To: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Chris, I'm fine with the new list of EPICs; basically the previous versions were each addressing one functionality group as depicted in the High Level Description of I2ND, along with few more EPICs 'specialised' on specific topics. I believe that the current list is still completing the picture, in particular in conjunction with the nice mapping onto functionality you provided. One comment: the MediaServices EPIC was originated based on the inputs by Joe about additional functionality which can be offered by the CDI: if you agree, I'd put Intel and yourself as stakeholder and owner. If no other comments come, I'll complete the uploading of the EPICs in the wiki. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 11 ottobre 2011 13:24 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: Urgent actions concerning EPICs/Assets Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here . Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From castrucci at dis.uniroma1.it Tue Oct 11 16:34:51 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Tue, 11 Oct 2011 16:34:51 +0200 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> <01ad01cc842a$a0147590$d028a8c0@cratr70> Message-ID: <012101cc8822$efe416b0$d028a8c0@cratr70> Dear Pier, all, I'm also new to USDL, and I have just done a quick look at it. >From my understanding, USDL aims to be a formal modelling language to describe services. With USDL, a system is described in terms of provided services by means of a metmodel including several packages. For each service, the different packages are used to provide a formal description of the input the service needs to work properly, the output it provides to the service's consumer, and also other information that could be useful for a complete description of the service (including interaction information used to define how to interact with a service). In conclusion, USLD seems to me as an alternative to UML, but more Service Oriented Architecture (SOA) oriented. So we may have to choose to use UML or USDL. As a personal comment, I don't see any advantage in using USDL instead of UML or viceversa. For sure, most of us can have already experience in using UML, which is a proven modelling language and it has been used in a big number of projects, included EU funded project, while I don't have figures about the utilization of USDL and maybe we may need to spend too much time in learning how it works. Another possible advantage for UML is that there exist a lot of tools to develop UML diagrams (some of them are even free like StarUML), while I found just one tool to develop USDL descriptions (a tryout version realized as an Eclipse plug-in, but I don't know if it is stable or if it is complete). Perhaps somebody else has much experience with USDL and can add more comments? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Tuesday, October 11, 2011 2:00 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, yesterday during the WPL/WPA confcall I mentioned that as I2ND we prepared a proposal for specs conventions etc, and I have been invited to submit it through the mailing list, so that we can start the discussion on that basis. Before doing that, I'd like to have your comment about one point: we're proposing the use of UML as modeling language, while I noticed that in other chapters (mainly Security one) there is a proposal to adopt USDL. I'm new to USDL (as to UML in fact.) so could you tell me/us if you had a look at it, and maybe provide some comparison note about the two, e.g. whether they are overlapping or complementary or whatever else, etc? Many thanks BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 15:20 A: Garino Pierangelo Cc: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams. If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------------------ -------------------------------------------------------------------------- _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ---------------------------------------------------------------------------- Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Tue Oct 11 16:35:33 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 11 Oct 2011 16:35:33 +0200 Subject: [Fiware-i2nd] R: R: Urgent actions concerning EPICs/Assets In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDE5@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDDA@EXCHSRV.fokus.fraunhofer.de> <804B13F8F3D94A4AB18B9B01ACB68FA1047BBDE5@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi Marius, that's fine thanks. I still believe however that the privacy protection is also related to both CDI and CE, as in both cases there might be personal details in both the connected device and the Cloud Edge which call for proper mechanisms to avoid disclosing this information without control. So I propose small modifications to the text of last point (see attached). I have also included an update dealing with Identity Mgmt and CDI. Other partners who want to comment, please add your contribution to this version. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: marted? 11 ottobre 2011 16:01 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Oggetto: RE: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hello Pier, We tried to combine the use cases of the two GEs. As I remember from the meeting in Torino and please correct me if I am wrong the NetIC has most of the security requirements either the same or responded through the S3C. Secure exposure may be for all the communication with other third parties same for the control environment. Privacy protection is more subscriber related and thus only S3C. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Tuesday, October 11, 2011 3:41 PM To: Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Subject: R: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Marius, Many thanks for your contribution. Did you consider the added items applicable to the two GEs (NetIC+S3C), or only linked to one of the two GEs? By having a first look, it seems to me that Secure Exposure could be applied to both (well, to all the GEs in I2ND), Secure Control Environment again to both, and Privacy Protection is mainly for S3C (and I'd say to CDI and CE too...). I'm going to insert some update involving CDI, then I'll circulate the new version for further improvements. Then, we'll share it with the Security guys (hopefully by tomorrow). For what concerns the insertion in the wiki, we still have to define how to update the section (or maybe create new ones); this will be done in next days in conjunction with the Security team and the Team Manager. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: marted? 11 ottobre 2011 14:58 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; Schulze, Frank Oggetto: RE: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hello, We checked again the security issues in the NetIC (less) and in the S3C (more) and attached is a document including the additions to section 3.3 on our contribution to D2.2. Any comments are more than welcomed. Should we complete this on the wikipage which mirrors the document, or? Greetings, Marius Corici From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Tuesday, October 11, 2011 2:16 PM To: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Urgent actions concerning EPICs/Assets Hi Chris, I'm fine with the new list of EPICs; basically the previous versions were each addressing one functionality group as depicted in the High Level Description of I2ND, along with few more EPICs 'specialised' on specific topics. I believe that the current list is still completing the picture, in particular in conjunction with the nice mapping onto functionality you provided. One comment: the MediaServices EPIC was originated based on the inputs by Joe about additional functionality which can be offered by the CDI: if you agree, I'd put Intel and yourself as stakeholder and owner. If no other comments come, I'll complete the uploading of the EPICs in the wiki. BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 11 ottobre 2011 13:24 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: Urgent actions concerning EPICs/Assets Hello All, RE: WP7.1 EPICs https://forge.fi-ware.eu/docman/view.php/10/470/Backlog%2Bentries_CDI-2%28cw3%29.xls I have updated the WP7.1 epics, the file above contains all epics including the contribution from UNIROMA. The updated included removing epics and inserting new epics. Request for feed back I would like to invite you to review the epics and get back to me with feedback. Mapping EPICs to functionality The attached PDF file is a mind-map which matches each EPIC with concrete functionality, the functionality listed in the mind-map from sourced from the FI-WARE High level description document. This is also available as FreeMind (link to download FreeMind application) document on the forge site here. Thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Monday, October 10, 2011 3:30 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8831.326B0030]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8831.326B0030]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8831.326B0030]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NetIC_S3C_CDI_Security_Items-v2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 16828 bytes Desc: NetIC_S3C_CDI_Security_Items-v2.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From Thomas-Rolf.Banniza at alcatel-lucent.com Tue Oct 11 17:51:15 2011 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Tue, 11 Oct 2011 17:51:15 +0200 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) In-Reply-To: <012101cc8822$efe416b0$d028a8c0@cratr70> References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> <01ad01cc842a$a0147590$d028a8c0@cratr70> <012101cc8822$efe416b0$d028a8c0@cratr70> Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0680DDC0@SLFSNX.rcs.alcatel-research.de> Hi Pier, Marco, others on http://www.heise.de/newsticker/meldung/Dienstbeschreibungssprache-USDL-kommt-in-entscheidende-Phase-1252079.html you can find a story summarizing status of USDL (maturity, acceptance, problems still to solve, ...). Sorry, the text is in German, but in my eyes its a good summary. Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Marco Castrucci Gesendet: Dienstag, 11. Oktober 2011 16:35 An: Garino Pierangelo Cc: fiware-i2nd Betreff: Re: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) Dear Pier, all, I'm also new to USDL, and I have just done a quick look at it. >From my understanding, USDL aims to be a formal modelling language to describe services. With USDL, a system is described in terms of provided services by means of a metmodel including several packages. For each service, the different packages are used to provide a formal description of the input the service needs to work properly, the output it provides to the service's consumer, and also other information that could be useful for a complete description of the service (including interaction information used to define how to interact with a service). In conclusion, USLD seems to me as an alternative to UML, but more Service Oriented Architecture (SOA) oriented. So we may have to choose to use UML or USDL. As a personal comment, I don't see any advantage in using USDL instead of UML or viceversa. For sure, most of us can have already experience in using UML, which is a proven modelling language and it has been used in a big number of projects, included EU funded project, while I don't have figures about the utilization of USDL and maybe we may need to spend too much time in learning how it works. Another possible advantage for UML is that there exist a lot of tools to develop UML diagrams (some of them are even free like StarUML), while I found just one tool to develop USDL descriptions (a tryout version realized as an Eclipse plug-in, but I don't know if it is stable or if it is complete). Perhaps somebody else has much experience with USDL and can add more comments? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Tuesday, October 11, 2011 2:00 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, yesterday during the WPL/WPA confcall I mentioned that as I2ND we prepared a proposal for specs conventions etc, and I have been invited to submit it through the mailing list, so that we can start the discussion on that basis. Before doing that, I'd like to have your comment about one point: we're proposing the use of UML as modeling language, while I noticed that in other chapters (mainly Security one) there is a proposal to adopt USDL. I'm new to USDL (as to UML in fact...) so could you tell me/us if you had a look at it, and maybe provide some comparison note about the two, e.g. whether they are overlapping or complementary or whatever else, etc? Many thanks BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 15:20 A: Garino Pierangelo Cc: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams... If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jozsef.varga at nsn.com Tue Oct 11 18:31:56 2011 From: jozsef.varga at nsn.com (Varga, Jozsef (NSN - HU/Budapest)) Date: Tue, 11 Oct 2011 19:31:56 +0300 Subject: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) In-Reply-To: A<133D9897FB9C5E4E9DF2779DC91E947C0680DDC0@SLFSNX.rcs.alcatel-research.de> References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> <01ad01cc842a$a0147590$d028a8c0@cratr70> <012101cc8822$efe416b0$d028a8c0@cratr70> A<133D9897FB9C5E4E9DF2779DC91E947C0680DDC0@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi all, My two cents is on UML. Already used that, almost everyone indicated StarUML as a tool to be used (although I draw sequence diagrams as Word drawing or as ppt most of the time). Br, Jozsef From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of ext BANNIZA, Thomas-Rolf Sent: Tuesday, October 11, 2011 5:51 PM To: Marco Castrucci; Garino Pierangelo Cc: fiware-i2nd Subject: Re: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) Hi Pier, Marco, others on http://www.heise.de/newsticker/meldung/Dienstbeschreibungssprache-USDL-kommt-in-entscheidende-Phase-1252079.html you can find a story summarizing status of USDL (maturity, acceptance, problems still to solve, ...). Sorry, the text is in German, but in my eyes its a good summary. Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Marco Castrucci Gesendet: Dienstag, 11. Oktober 2011 16:35 An: Garino Pierangelo Cc: fiware-i2nd Betreff: Re: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) Dear Pier, all, I'm also new to USDL, and I have just done a quick look at it. >From my understanding, USDL aims to be a formal modelling language to describe services. With USDL, a system is described in terms of provided services by means of a metmodel including several packages. For each service, the different packages are used to provide a formal description of the input the service needs to work properly, the output it provides to the service's consumer, and also other information that could be useful for a complete description of the service (including interaction information used to define how to interact with a service). In conclusion, USLD seems to me as an alternative to UML, but more Service Oriented Architecture (SOA) oriented. So we may have to choose to use UML or USDL. As a personal comment, I don't see any advantage in using USDL instead of UML or viceversa. For sure, most of us can have already experience in using UML, which is a proven modelling language and it has been used in a big number of projects, included EU funded project, while I don't have figures about the utilization of USDL and maybe we may need to spend too much time in learning how it works. Another possible advantage for UML is that there exist a lot of tools to develop UML diagrams (some of them are even free like StarUML), while I found just one tool to develop USDL descriptions (a tryout version realized as an Eclipse plug-in, but I don't know if it is stable or if it is complete). Perhaps somebody else has much experience with USDL and can add more comments? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Tuesday, October 11, 2011 2:00 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, yesterday during the WPL/WPA confcall I mentioned that as I2ND we prepared a proposal for specs conventions etc, and I have been invited to submit it through the mailing list, so that we can start the discussion on that basis. Before doing that, I'd like to have your comment about one point: we're proposing the use of UML as modeling language, while I noticed that in other chapters (mainly Security one) there is a proposal to adopt USDL. I'm new to USDL (as to UML in fact...) so could you tell me/us if you had a look at it, and maybe provide some comparison note about the two, e.g. whether they are overlapping or complementary or whatever else, etc? Many thanks BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 15:20 A: Garino Pierangelo Cc: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams... If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 12 08:44:46 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 12 Oct 2011 08:44:46 +0200 Subject: [Fiware-i2nd] R: R: Proposal for specification conventions (I2ND49) In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0680DDC0@SLFSNX.rcs.alcatel-research.de> References: <003001cc826e$e81e3910$d028a8c0@cratr70> <00b101cc8284$18caf570$d028a8c0@cratr70> <016501cc8426$b5021ce0$d028a8c0@cratr70> <01ad01cc842a$a0147590$d028a8c0@cratr70> <012101cc8822$efe416b0$d028a8c0@cratr70> <133D9897FB9C5E4E9DF2779DC91E947C0680DDC0@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi Thomas, unfortunately I couldn't catch the essence of the article you pointed at due to my absolute inability to understand german :( Can you tell us what's your opinion in the debate between UML and USDL? Are you supporting the latter or would UML be acceptable? To overcome my bad german knowledge, I searched around and found some other interesting description of USDL in the W3C site, where there is the USDL incubator page: http://www.w3.org/2005/Incubator/usdl/ There are references at the end of the document, also to general presentations, e.g.: http://www.w3.org/2005/Incubator/usdl/wiki/images/f/fa/Kk-usdl-20110516.pdf And I also found pages, like the following, on W3C wiki rather interesting: http://www.w3.org/2005/Incubator/usdl/wiki/USDL_XG_Final_Report There is for instance a table showing the landscapes of existing service description efforts. Discussion to be continued, I would however come to some (at least preliminary) conclusion soon, then involve all the other people in the project to have their opinion. BR Pier Da: BANNIZA, Thomas-Rolf [mailto:Thomas-Rolf.Banniza at alcatel-lucent.com] Inviato: marted? 11 ottobre 2011 17:51 A: Marco Castrucci; Garino Pierangelo Cc: fiware-i2nd Oggetto: AW: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) Hi Pier, Marco, others on http://www.heise.de/newsticker/meldung/Dienstbeschreibungssprache-USDL-kommt-in-entscheidende-Phase-1252079.html you can find a story summarizing status of USDL (maturity, acceptance, problems still to solve, ...). Sorry, the text is in German, but in my eyes its a good summary. Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Marco Castrucci Gesendet: Dienstag, 11. Oktober 2011 16:35 An: Garino Pierangelo Cc: fiware-i2nd Betreff: Re: [Fiware-i2nd] R: Proposal for specification conventions (I2ND49) Dear Pier, all, I'm also new to USDL, and I have just done a quick look at it. >From my understanding, USDL aims to be a formal modelling language to describe services. With USDL, a system is described in terms of provided services by means of a metmodel including several packages. For each service, the different packages are used to provide a formal description of the input the service needs to work properly, the output it provides to the service's consumer, and also other information that could be useful for a complete description of the service (including interaction information used to define how to interact with a service). In conclusion, USLD seems to me as an alternative to UML, but more Service Oriented Architecture (SOA) oriented. So we may have to choose to use UML or USDL. As a personal comment, I don't see any advantage in using USDL instead of UML or viceversa. For sure, most of us can have already experience in using UML, which is a proven modelling language and it has been used in a big number of projects, included EU funded project, while I don't have figures about the utilization of USDL and maybe we may need to spend too much time in learning how it works. Another possible advantage for UML is that there exist a lot of tools to develop UML diagrams (some of them are even free like StarUML), while I found just one tool to develop USDL descriptions (a tryout version realized as an Eclipse plug-in, but I don't know if it is stable or if it is complete). Perhaps somebody else has much experience with USDL and can add more comments? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Tuesday, October 11, 2011 2:00 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, yesterday during the WPL/WPA confcall I mentioned that as I2ND we prepared a proposal for specs conventions etc, and I have been invited to submit it through the mailing list, so that we can start the discussion on that basis. Before doing that, I'd like to have your comment about one point: we're proposing the use of UML as modeling language, while I noticed that in other chapters (mainly Security one) there is a proposal to adopt USDL. I'm new to USDL (as to UML in fact...) so could you tell me/us if you had a look at it, and maybe provide some comparison note about the two, e.g. whether they are overlapping or complementary or whatever else, etc? Many thanks BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 15:20 A: Garino Pierangelo Cc: fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Sure, you are correct. I missed the word "case". BR Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci Cc: fiware-i2nd Sent: Thursday, October 06, 2011 3:03 PM Subject: R: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Marco, thanks for the update. One minor note, I modified point 2 of the final summary in the following way (the word 'case' was missing): 2. UML Component diagrams to specify the structure of the system. Starting from the UML Use case diagrams... If this is the meaning for you too, I can upload the modified document replacing the original one. BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 6 ottobre 2011 14:52 A: Garino Pierangelo; fiware-i2nd Oggetto: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, I uploaded an updated version following your comments. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.2.docx Ciao Marco ----- Original Message ----- From: Marco Castrucci To: Garino Pierangelo ; fiware-i2nd Sent: Tuesday, October 04, 2011 12:55 PM Subject: Re: [Fiware-i2nd] Proposal for specification conventions (I2ND49) Dear Pier, find my comments in line in red. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: Marco Castrucci ; fiware-i2nd Sent: Tuesday, October 04, 2011 11:20 AM Subject: R: Proposal for specification conventions (I2ND49) Dear Marco, thanks a lot for your contribution. I have some comments/questions/doubts which I try to summarise here: - I'm not familiar with UML (it might sound strange, but I never had to use it in the past), so when you specify it is a modeling language 'mainly' used for design and specs of Object Oriented software systems, do you mean that its use is not tied to that kind of programming paradigms/languages, but it can be adopted in a broader sense? Exactly: it can be used to model any sw (or even hw) system, and do not impose constraints on the programming paradigm/language to be used for the development of the system - For this reason, is the use of class diagrams limiting us or not? The concept of class is derived from the object-oriented programming paradigm. Anyway, I don't see problems in developing a system described by means of class diagram, using another programming paradigm. In fact, in our case Class diagrams can be used to describe the interfaces of the system, detailing the functionalities exposed, with its needed input and the provided output. There are no limitations then on the implementation methodology of such interface. - Don't we risk to adopt a top-down modeling approach which is not optimized for FI-WARE, where we already deal with existing portions of the system (i.e. the assets)? In case of specification of already available assets, we will have to perform a "reverse engineering" activity, as we will have to create specifications starting from the already available system. - Concerning point 1 in the suggested use of UML (summary at page 4): in the Agile methodology adopted by FI-WARE, EPICs mean 'work to be done' (see also my yesterday's mail). I wouldn't propose to use them as basis for the creation of Use case diagrams. I would rather start from the 'Product vision', i.e. the High Level Description of our GEs to create such diagrams. OK. I'll change the document according and I will upload an updated version soon. As a general comment, I proposed the use of UML as it was also proposed by many of WP7 partners when collecting information about tool for design and specification last week. Of course, if there are other proposals for instruments to be used, we can discuss them and find out the best alternative. Any further input by other partners to this discussion is of course welcome! BR Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: marted? 4 ottobre 2011 10:24 A: fiware-i2nd Cc: Garino Pierangelo Oggetto: Proposal for specification conventions (I2ND49) Dear I2ND partners, as decided during our last conf call, we have to make a joint proposal for the conventions to be adopted for FIWARE specifications (action point I2ND49). Please find here https://forge.fi-ware.eu/docman/view.php/10/452/I2ND+proposal+for+convention+to+be+used+for+specifications_v0.1.docx our proposal. In brief, we propose to use the folowing 4 UML diagrams: - Use case diagrams - Component diagrams - Sequence diagrams - Class diagrams In addition, we also propose the use of StarUML as a free tool to depict UML diagrams. Comments and feedbacks are welcome so that we can finalize our proposal by next Friday (7 October) and then Pier can discuss it at project level. Best regards Marco ----------------------------------------------- Dr. Ing. Castrucci Marco University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From serge.defrance at technicolor.com Wed Oct 12 09:57:23 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 12 Oct 2011 09:57:23 +0200 Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0103815EC7@MOPESMBX01.eu.thmulti.com> Dear All, Please find attached a list of assets and Epics concerning the Cloud Edge. This list corresponds to what we already circulated for the Torino meeting. It may be updated if the decision is taken that we move all our effort from WP4 to WP7 in order to cope with the technical discussion we had in the Torino meeting that the Cloud Edge is not really part of the Cloud infrastructure in the sense that it is not directly managed by the Cloud Hosting functions. Hear you soon in the confcall. Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: lundi 10 octobre 2011 16:30 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC88C5.0A4DAFA0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TechnicolorAssetsWP7revised_v1.docx.zip Type: application/x-zip-compressed Size: 54061 bytes Desc: TechnicolorAssetsWP7revised_v1.docx.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CloudProxyWP7EPICrevised_v01.xls.zip Type: application/x-zip-compressed Size: 30748 bytes Desc: CloudProxyWP7EPICrevised_v01.xls.zip URL: From thomas.michael.bohnert at sap.com Wed Oct 12 11:22:12 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Wed, 12 Oct 2011 11:22:12 +0200 Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Message-ID: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An embedded message was scrubbed... From: "Friesen, Andreas" Subject: [Fiware-apps] End-2-end scenarios from SAP for T3.3 Date: Tue, 23 Aug 2011 15:38:21 +0200 Size: 216891 URL: From pierangelo.garino at telecomitalia.it Wed Oct 12 12:00:56 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 12 Oct 2011 12:00:56 +0200 Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Message-ID: Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Wed Oct 12 12:32:45 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 12 Oct 2011 11:32:45 +0100 Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes In-Reply-To: References: Message-ID: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC88D2.A98C5DC0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jeanpierre.lerouzic at orange.com Wed Oct 12 14:00:57 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 12 Oct 2011 14:00:57 +0200 Subject: [Fiware-i2nd] Urgent actions concerning EPICs/Assets In-Reply-To: References: Message-ID: Hi all, Please find at the link below Orange's EPICs. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%28I2ND%29_in_FI-WARE#Service.2C_Capability.2C_Connectivity_and_Control The EPICS are: # EPIC.FIWARE.I2ND.S3C.SMS+MMS ENABLERS (study what means OneAPI's API for SMS/MMS for API mediation) # EPIC.FIWARE.I2ND.S3C.Telecom platform 1 (A simple Telecom AS/New paradigm in Network API command) # EPIC.FIWARE.I2ND.S3C.API_mediation_1 (Publishing/Exposing/Managing network APIs) # EPIC.FIWARE.I2ND.S3C.WSC 1 (Enabling SP to interact with set of devices) The overall idea is to provide the upper part of S3C that exposes network features through simple APIs to services. It should complement Fokus' EPICS perhaps by interacting with: FIWARE.Epic.I2ND.S3C.ExposedNetworkInformation We will develop them from scratch but taking as basis the Orange assets which are proprietary products. Features will be added (for example the WSC asset works only on IMS, now it will work with more networks and more terminals). Any comment is welcomed. Best regards, Jean-Pierre De?: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy??: lundi 10 octobre 2011 16:30 ??: fiware-i2nd at lists.fi-ware.eu Objet?: [Fiware-i2nd] Urgent actions concerning EPICs/Assets Dear All, Some points coming out from today's WPL/WPA confcall: - As the formal deadline was last Friday, I committed to complete the insertion of EPICs (and relative 'tickets' in the i2nd tracker Backlog) by Wednesday Oct 12th o This refers to what we called the Primary EPICs in our last i2nd confcall o Most of Tasks did already the job: I personally copied from the original FI-WARE backlog page to the new 'Materializing the FI-WARE vision' (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision) the EPICs for S3C, while the others have been inserted already in the new structure. o Remember that use of FI-WARE backlog page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog) is now deprecated and we must use the 'Materializing' one. o Please *T7.2 TL to insert their EPICs* o I'll provide further notes on how to insert the tickets in the Tracker tomorrow morning - We were also asked to complete by the same date the asset descriptions: I agreed to postpone to Wednesday 14th this action, but this means that all Tasks should complete their asset description (and select those which will be retained in the GE implementation!). I kindly ask the *TLs to urge the completion* of this, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments?is?confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. From pierangelo.garino at telecomitalia.it Wed Oct 12 14:08:36 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 12 Oct 2011 14:08:36 +0200 Subject: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> Message-ID: Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC88E8.6F50FAB0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From castrucci at dis.uniroma1.it Wed Oct 12 16:02:37 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Wed, 12 Oct 2011 16:02:37 +0200 Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> Message-ID: <01b601cc88e7$99705300$d028a8c0@cratr70> Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ------------------------------------------------------------------------------ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 12 16:07:20 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 12 Oct 2011 16:07:20 +0200 Subject: [Fiware-i2nd] Table of all Action Points defined in I2ND Message-ID: Dear All, As follow-up of an activity initiated by Chris last week, I have uploaded the following document on the Forge i2nd project site: https://forge.fi-ware.eu/docman/view.php/10/484/Action+List_20111012.xlsx It is an Excel table containing the list of all action points defined so far (well, starting from I2ND40 onward... if someone wants to add the previous ones please do it ;-), so that you have a simple table with all the scheduled deadlines visible at a glance. The document will be regularly updated after the periodic confcalls. Please also check those items we didn't touch in today's confcall, and try to provide an answer to them (e.g. I2ND51, 52). BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From thomas.michael.bohnert at sap.com Wed Oct 12 16:10:00 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Wed, 12 Oct 2011 16:10:00 +0200 Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE In-Reply-To: <01b601cc88e7$99705300$d028a8c0@cratr70> References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> <01b601cc88e7$99705300$d028a8c0@cratr70> Message-ID: <771C9B001456D64783596DDC3801C6EA28171B58F0@DEWDFECCR09.wdf.sap.corp> Marco, USDL is NOT for modeling processes and interactions. It is a language for describing services (in the most general sense). For modeling, in either UML, BPM, Nassi-Shneiderman, etc you may use any respective tool. The Apps Chapter uses yED. Best - Thomas From: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Sent: Mittwoch, 12. Oktober 2011 16:03 To: Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten; garino pierangelo Subject: Re: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasquale.donadio at alcatel-lucent.com Wed Oct 12 16:37:58 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Wed, 12 Oct 2011 16:37:58 +0200 Subject: [Fiware-i2nd] R: USDL and Modelling in FI-WARE In-Reply-To: <01b601cc88e7$99705300$d028a8c0@cratr70> References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> <01b601cc88e7$99705300$d028a8c0@cratr70> Message-ID: Dear all, >From an industrial point of view, and personal experience, Unified Modeling Language is considered the standard de facto for the design of each kind of software component, packages platforms and services. The set of diagrams, also named "Use case diagrams", "State diagrams", "Sequence diagrams" etc...provides a general purpose set of design tools useful to describe each kind of software systems. UML design is moreover supported by many software tools (e.g. StarUML, ArgoUML, Rational/IBM products, etc) On the other hand, USDL seems a service oriented design language only, containing a subset of the UML formalisms. Finally USDL tools seems not yet mature respect the UML tools listed above So, in my opinion, the UML language should be considered the best choice for our software design. Best Regards Pasquale ________________________________ Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Marco Castrucci Inviato: mercoled? 12 ottobre 2011 16.03 A: Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten Oggetto: Re: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeanpierre.lerouzic at orange.com Wed Oct 12 16:56:47 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 12 Oct 2011 16:56:47 +0200 Subject: [Fiware-i2nd] R: USDL and Modelling in FI-WARE In-Reply-To: References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> <01b601cc88e7$99705300$d028a8c0@cratr70> Message-ID: Hi all, I think there is some misunderstanding here. Thomas said these two tools can't be compared or are not interchangeable: ? It seems to me USDL is about large business process modeling, which means much larger conceptual realms than the much simpler simple services that are modelized with UML. I may be wrong about USDL actual possibilities but UML is not a universal solution: How do you quickly model non functional properties such as security, business or operation in UML? How can you share requirements with people that have expertise that you don't have (for example marketing) in UML? How to integrate in a UML model apparently contradictory requirements made by separate team of experts such as security team asking for closed devices and marketing team asking of opened devices? ? Probably it's the whole of Fi-ware that should be modeled in USDL, where each WPs and tasks should use UML. Indeed I am not a specialist of both tools. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de DONADIO, PASQUALE (PASQUALE) Envoy? : mercredi 12 octobre 2011 16:38 ? : Marco Castrucci; Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc : Kadner, Kay; Heller, Markus; Leidig, Torsten Objet : [Fiware-i2nd] R: USDL and Modelling in FI-WARE Dear all, >From an industrial point of view, and personal experience, Unified Modeling Language is considered the standard de facto for the design of each kind of software component, packages platforms and services. The set of diagrams, also named "Use case diagrams", "State diagrams", "Sequence diagrams" etc...provides a general purpose set of design tools useful to describe each kind of software systems. UML design is moreover supported by many software tools (e.g. StarUML, ArgoUML, Rational/IBM products, etc) On the other hand, USDL seems a service oriented design language only, containing a subset of the UML formalisms. Finally USDL tools seems not yet mature respect the UML tools listed above So, in my opinion, the UML language should be considered the best choice for our software design. Best Regards Pasquale ________________________________ Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Marco Castrucci Inviato: mercoled? 12 ottobre 2011 16.03 A: Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten Oggetto: Re: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.leidig at sap.com Wed Oct 12 17:20:02 2011 From: torsten.leidig at sap.com (Leidig, Torsten) Date: Wed, 12 Oct 2011 17:20:02 +0200 Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE In-Reply-To: <771C9B001456D64783596DDC3801C6EA28171B58F0@DEWDFECCR09.wdf.sap.corp> References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> <01b601cc88e7$99705300$d028a8c0@cratr70> <771C9B001456D64783596DDC3801C6EA28171B58F0@DEWDFECCR09.wdf.sap.corp> Message-ID: Dear all, FI-WARE WP3 uses yEd to draw BPMN Collaboration diagrams (not UML). ?We basically sketched two end-to-end usage scenarios (themes). One is about an aggregator creating a composite service and publish that to a store. The second one is from the consumer perspective, who wants to discover buy and use a service. These diagrams have nothing to do with USDL. For the technical interface of a service USDL just links to a technical service description (e.g. WSDL) and does some mapping of high-level service interactions to the technical interface. No dedicated tooling is provided to actually describe WSDL services. USDL tries to be agnostic according the concrete service technology (REST, SOAP, WSDL, ATOM, etc.). USDL is not for software modelling. Best regards, Torsten Dr. Torsten Leidig SAP Research Center CEC Karlsruhe SAP AG Vincenz-Prie?nitz-Str. 1 76131 Karlsruhe T +49 6227 7 52535 F +49 6227 78 29753 E torsten.leidig at sap.com http://www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. From: Bohnert, Thomas Michael Sent: Mittwoch, 12. Oktober 2011 16:10 To: Marco Castrucci; fiware-i2nd at lists.fi-ware.eu; Kadner, Kay Cc: Heller, Markus; Leidig, Torsten; garino pierangelo Subject: RE: [Fiware-i2nd] USDL and Modelling in FI-WARE Marco, USDL is NOT for modeling processes and interactions. It is a language for describing services (in the most general sense). For modeling, in either UML, BPM, Nassi-Shneiderman, etc you may use any respective tool. The Apps Chapter uses yED. Best - Thomas From: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Sent: Mittwoch, 12. Oktober 2011 16:03 To: Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten; garino pierangelo Subject: Re: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From kay.kadner at sap.com Wed Oct 12 17:20:53 2011 From: kay.kadner at sap.com (Kadner, Kay) Date: Wed, 12 Oct 2011 17:20:53 +0200 Subject: [Fiware-i2nd] R: USDL and Modelling in FI-WARE In-Reply-To: References: <771C9B001456D64783596DDC3801C6EA28171B53DD@DEWDFECCR09.wdf.sap.corp> <01b601cc88e7$99705300$d028a8c0@cratr70> Message-ID: Hi guys, let me try to clarify what USDL is good for. As you already said, USDL is for describing services, as it is the Unified Service Description Language. One of its intentions is to extend current service descriptions (e.g., WSDL) by other information that becomes necessary when looking at services from a business service network. In such a network, you need business and operational information like contact data of provider, pricing models for service execution, etc. USDL is by no means meant to replace WSDL. It's an addition to it and to some extent independent from it. This means two things: we do not reinvent the wheel (WSDL is quite mature) and we do not necessarily need a technical description. This is because USDL is intended to also cover service description of non-technical services like car repair or package handling. So, in the end, UML is not comparable to USDL, they both have a totally different purpose. If you like, you can compare USDL to WSDL. I like to state that USDL could be for the Internet of Services what HTML was for the Web. Best Regards, Kay Dr. Kay Kadner Senior Researcher I Chair of W3C USDL XG I SAP Research Dresden SAP AG I SAP Research I Chemnitzer Str. 48 I 01187 Dresden I Germany T +49 351 4811-6127 I F +49 6227 78-44576 I M +49 172 4639220 I mailto:kay.kadner at sap.com www.sap.com/research Please consider the impact on the environment before printing this e-mail. Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notifi ed that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Mittwoch, 12. Oktober 2011 16:57 To: pasquale.donadio at alcatel-lucent.com; castrucci at dis.uniroma1.it; Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten Subject: RE: [Fiware-i2nd] R: USDL and Modelling in FI-WARE Hi all, I think there is some misunderstanding here. Thomas said these two tools can't be compared or are not interchangeable: ? It seems to me USDL is about large business process modeling, which means much larger conceptual realms than the much simpler simple services that are modelized with UML. I may be wrong about USDL actual possibilities but UML is not a universal solution: How do you quickly model non functional properties such as security, business or operation in UML? How can you share requirements with people that have expertise that you don't have (for example marketing) in UML? How to integrate in a UML model apparently contradictory requirements made by separate team of experts such as security team asking for closed devices and marketing team asking of opened devices? ? Probably it's the whole of Fi-ware that should be modeled in USDL, where each WPs and tasks should use UML. Indeed I am not a specialist of both tools. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de DONADIO, PASQUALE (PASQUALE) Envoy? : mercredi 12 octobre 2011 16:38 ? : Marco Castrucci; Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc : Kadner, Kay; Heller, Markus; Leidig, Torsten Objet : [Fiware-i2nd] R: USDL and Modelling in FI-WARE Dear all, >From an industrial point of view, and personal experience, Unified Modeling Language is considered the standard de facto for the design of each kind of software component, packages platforms and services. The set of diagrams, also named "Use case diagrams", "State diagrams", "Sequence diagrams" etc...provides a general purpose set of design tools useful to describe each kind of software systems. UML design is moreover supported by many software tools (e.g. StarUML, ArgoUML, Rational/IBM products, etc) On the other hand, USDL seems a service oriented design language only, containing a subset of the UML formalisms. Finally USDL tools seems not yet mature respect the UML tools listed above So, in my opinion, the UML language should be considered the best choice for our software design. Best Regards Pasquale ________________________________ Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Marco Castrucci Inviato: mercoled? 12 ottobre 2011 16.03 A: Bohnert, Thomas Michael; fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay; Heller, Markus; Leidig, Torsten Oggetto: Re: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear Thomas, thanks for your input! In addition, I'd like to suggest also to have a look to this paper: Cardoso, Winkler, Voigt "A service description language for the Internet of Services": http://eden.dei.uc.pt/~jcardoso/Research/Papers/ISSS-2009-Serv-Desc-Lang-for-the-IoS.pdf. What is still not so clear to me is how to model technical aspects with USDL. In the email you attached, I see that WP3 is using yEd tool for that. I had a look at yEd and I see that it also offers some utilities to draw UML diagrams (even if it is not so complete compared to other tools like StarUML). Thus, is it right to conclude that, for the modelling of technical aspects, we don't need to use the USDL tool but we shall use other tools (like for example yEd or StarUML)? This means that we can use USDL for the global description of the service (business, legal aspects, etc.) and UML for its technical description? Thank you in advance. Best regards Marco ----- Original Message ----- From: Bohnert, Thomas Michael To: fiware-i2nd at lists.fi-ware.eu Cc: Kadner, Kay ; Heller, Markus ; Leidig, Torsten Sent: Wednesday, October 12, 2011 11:22 AM Subject: [Fiware-i2nd] USDL and Modelling in FI-WARE Dear I2ND Members, With reference to the call this morning here are some infos about USDL and general process/program design/modeling. USDL: Landing page: www.internet-of-services.com Short intro: M. Heller, T. M. Bohnert, A. Friesen, "A Unified Service Description Language (USDL) (slides)", 3rd FI-PPP Usage Area Workshop", Brussels, Belgium, Jun 2011 http://dl.dropbox.com/u/43706589/USDL_Heller_tmb.pdf Technical contact: M. Heller (WPL) / T. Leidig (WPA) / K Kadner (USDL W3C IC Chair). I suggest to schedule a USDL-briefing very soon. Also in order to address you concerns with respect to the stability and maturity of USDL in particular. Modeling: USDL is NO alternative to UML. Instead, for modeling your technical aspects you may consider the approach and tooling adopted in the Apps chapter. Precise info with real examples are attached. Questions/Comments welcome. Best - Thomas -- Thomas Michael Bohnert Technical Director SAP (Schweiz) AG, Kreuzplatz 20, 8008 Zurich, Switzerland T +41 58 871 7801, M +41 79 7018941, F +41 58 871 7812 email: thomas.michael.bohnert at sap.com web: tmb.nginet.de, twitter: tmbohnert Please consider the impact on the environment before printing this e-mail. ________________________________ _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Oct 13 09:40:53 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 13 Oct 2011 09:40:53 +0200 Subject: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> Message-ID: Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC898C.32E7CAA0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC898C.32E7CAA0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From marius-iulian.corici at fokus.fraunhofer.de Thu Oct 13 10:07:44 2011 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Thu, 13 Oct 2011 10:07:44 +0200 Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBEA7@EXCHSRV.fokus.fraunhofer.de> Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris J BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Thu Oct 13 10:22:54 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 13 Oct 2011 10:22:54 +0200 Subject: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBEA7@EXCHSRV.fokus.fraunhofer.de> References: <187F4CC97FD0B6488FAE608A8038FF14391E7B00@irsmsx503.ger.corp.intel.com> <804B13F8F3D94A4AB18B9B01ACB68FA1047BBEA7@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8990.B8D89780]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8990.B8D89780]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8990.B8D89780]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jeanpierre.lerouzic at orange.com Fri Oct 14 14:59:00 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Fri, 14 Oct 2011 14:59:00 +0200 Subject: [Fiware-i2nd] TR: [Fiware-security] Asset Information Message-ID: Hi all, This is probably a work in progress in WP8 about USDL and Fi-Ware but I find it interesting. Best regards, Jean-Pierre De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de Antonio Garcia Vazquez Envoy? : vendredi 14 octobre 2011 14:30 ? : TRABELSI, Slim Cc : Fiware-security at lists.fi-ware.eu Objet : [Fiware-security] Asset Information 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT10181072.txt URL: From marius-iulian.corici at fokus.fraunhofer.de Mon Oct 17 17:15:38 2011 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Mon, 17 Oct 2011 17:15:38 +0200 Subject: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris J BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Security Chapter Evaluation from the i2nd Perspective.docx Type: application/octet-stream Size: 17068 bytes Desc: Security Chapter Evaluation from the i2nd Perspective.docx URL: From pierangelo.garino at telecomitalia.it Tue Oct 18 09:49:50 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 18 Oct 2011 09:49:50 +0200 Subject: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi Marius, actually as first attempt I expected to gather some comment to the Security chapter description (to understand what they propose and this could impact I2ND), while you did a more detailed analysis about what contribution could come from the I2ND side to those GEs. The two options are of course not alternative but rather complementary, so I propose we keep both of them, and provide by today their contents to the Security people. My input is attached to this mail, I kindly ask the other delegates of the Security Task Force (Henk/Serge, Chris ) to add their comments in any of the two documents (this one or the one sent by Marius yesterday) *by today early afternoon*, thanks. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8D79.F5306310]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8D79.F5306310]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8D79.F5306310]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8D79.F5306310]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE High-Level Description -Security-v1.0 11-08-15-I2ND.doc Type: application/msword Size: 823296 bytes Desc: FI-WARE High-Level Description -Security-v1.0 11-08-15-I2ND.doc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jeanpierre.lerouzic at orange.com Tue Oct 18 10:11:48 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Tue, 18 Oct 2011 10:11:48 +0200 Subject: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP In-Reply-To: References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hi all, Here are a few thoughts about security. There are standards in security such as ISO 27000, in fact there are many security standards but this one in independent of security technologies. The main recommendations are: ? To preserve: o confidentiality (ensuring that information is accessible only to those authorised to have access), o integrity (safeguarding the accuracy and completeness of information and processing methods) o availability (ensuring that authorised users have access to information and associated assets when required). ? To assert the security situation at regular intervals ? To put in place actions to mitigate risks. ? To make it possible to audit the situation. Obviously in I2ND we don't deal with security but we have to make it possible that the people of the art can do his own stuff. It's my understanding that we should provide: ? Classical means to protect: o confidentiality which means authenticating users/networks/devices/services with WP8 Identity enabler. o Integrity mostly by using encryption (I don't know if WP8 has some recommendation here) o Availability by detecting anomalous situation when an authorized user wants to access its service/device/network (kinda exception management) ? We have to provide to WP8 some information to make them able to assert (review) WP7 security situation. The best is probably to ask them their requirements in this area. ? We have to provide some programmability in our own enablers (the contrary to hard wired architecture) to make it possible for WP8 guys to put in place mitigating actions, again we should ask them about what they intend to do. ? We have to provide WP8 a secured access to some WP7 general indicators about deviations to normal situations (anomaly detection). It's only some random ideas, don't hesitate to comment them. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mardi 18 octobre 2011 09:50 ? : Corici, Marius-Iulian Cc : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP Hi Marius, actually as first attempt I expected to gather some comment to the Security chapter description (to understand what they propose and this could impact I2ND), while you did a more detailed analysis about what contribution could come from the I2ND side to those GEs. The two options are of course not alternative but rather complementary, so I propose we keep both of them, and provide by today their contents to the Security people. My input is attached to this mail, I kindly ask the other delegates of the Security Task Force (Henk/Serge, Chris ) to add their comments in any of the two documents (this one or the one sent by Marius yesterday) *by today early afternoon*, thanks. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris J BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Wolfgang.Steigerwald at telekom.de Tue Oct 18 16:42:21 2011 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Tue, 18 Oct 2011 16:42:21 +0200 Subject: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP In-Reply-To: References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Message-ID: Hello Pier, the document you send in your mail regarding the security assets is outdated, please use the document https://forge.fi-ware.eu/docman/view.php/19/518/WP8+Description+of+the+Security+Asset+v10.docx it's the latest version. Best regards Wolfgang Deutsche Telekom AG T-Labs (Research & Development) 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. ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Dienstag, 18. Oktober 2011 09:50 An: Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP Hi Marius, actually as first attempt I expected to gather some comment to the Security chapter description (to understand what they propose and this could impact I2ND), while you did a more detailed analysis about what contribution could come from the I2ND side to those GEs. The two options are of course not alternative but rather complementary, so I propose we keep both of them, and provide by today their contents to the Security people. My input is attached to this mail, I kindly ask the other delegates of the Security Task Force (Henk/Serge, Chris ) to add their comments in any of the two documents (this one or the one sent by Marius yesterday) *by today early afternoon*, thanks. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:174053814 at 18102011-177B]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:174053814 at 18102011-177B]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:174053814 at 18102011-177B]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:174053814 at 18102011-177B]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:174053814 at 18102011-1782]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From serge.defrance at technicolor.com Tue Oct 18 16:43:27 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Tue, 18 Oct 2011 16:43:27 +0200 Subject: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP In-Reply-To: References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E010F4FD9A4@MOPESMBX01.eu.thmulti.com> Hi Pier, We have nothing to add to the document you have circulated this morning. Best Regards, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: mardi 18 octobre 2011 09:50 To: Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP Hi Marius, actually as first attempt I expected to gather some comment to the Security chapter description (to understand what they propose and this could impact I2ND), while you did a more detailed analysis about what contribution could come from the I2ND side to those GEs. The two options are of course not alternative but rather complementary, so I propose we keep both of them, and provide by today their contents to the Security people. My input is attached to this mail, I kindly ask the other delegates of the Security Task Force (Henk/Serge, Chris ) to add their comments in any of the two documents (this one or the one sent by Marius yesterday) *by today early afternoon*, thanks. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8DB5.0F529890]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8DB5.0F529890]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8DB5.0F529890]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8DB5.0F529890]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8DB5.0F529890]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Wed Oct 19 09:40:37 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 19 Oct 2011 09:40:37 +0200 Subject: [Fiware-i2nd] I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: <4E9DB5ED.5090906@tid.es> References: <4E9DB5ED.5090906@tid.es> Message-ID: Dear All, We are asked to make the asset description in the I2ND wiki page more in line with the original template, I report below a list of comments received, along with the assets whose description has to be updated (the description of non mentioned assets is ok). According to what specified below, can you make the necessary changes to (or add) the assets *by today*, thanks. BR Pier General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don't. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... Particular comments (specific to your WP) * Connected Device Interfacing * Meego - "Runtime pre-requisites"empty. IPR should be more explicit. * Reinforcement Learning - "IPR" & "Publicly available documentation" should be explicitly filled in. * Cloud Edge * No assets! * Network Information and Control * Network Element Virtualizer - IPR empty * Service, Capability, Connectivity and Control The names of the partner should be removed from titles (inconsistent with the rest of the assets in other WPs) * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. * Ericsson Device Connection Platform - part of the fields are empty * Orange WSC - wrong template (not using any at all) * Orange API mediation - wrong template (not using any at all) * Orange Telecom enabler - wrong template (not using any at all) * Orange voicemail enabler - wrong template (not using any at all) * Telekom Network Identity Management IPR empty. * Telekom Resource Management - ok * Telekom Seamless Network Connectivity - ok Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From vincenzo.suraci at dis.uniroma1.it Wed Oct 19 09:53:14 2011 From: vincenzo.suraci at dis.uniroma1.it (Vincenzo Suraci) Date: Wed, 19 Oct 2011 09:53:14 +0200 Subject: [Fiware-i2nd] R: I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: References: <4E9DB5ED.5090906@tid.es> Message-ID: <002701cc8e34$27d4c1c0$777e4540$@dis.uniroma1.it> Dear Pier, we accomplished to finalize the UoR ?Reinforcement Learning? under the CDI GE, resolving all the issues raised up from the comments. Best Regards, Vincenzo Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 19 ottobre 2011 09:41 A: chris.woods at intel.com; 'Marco Castrucci'; 'Defrance Serge'; pasquale.donadio at alcatel-lucent.com; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); sascha.smets at ericsson.com; jeanpierre.lerouzic at orange.com; Dmitry.Sivchenko at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, We are asked to make the asset description in the I2ND wiki page more in line with the original template, I report below a list of comments received, along with the assets whose description has to be updated (the description of non mentioned assets is ok). According to what specified below, can you make the necessary changes to (or add) the assets *by today*, thanks. BR Pier General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don?t. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source? Particular comments (specific to your WP) * Connected Device Interfacing * Meego ? ?Runtime pre-requisites?empty. IPR should be more explicit. * Reinforcement Learning ? ?IPR? & ?Publicly available documentation? should be explicitly filled in. * Cloud Edge * No assets! * Network Information and Control * Network Element Virtualizer ? IPR empty * Service, Capability, Connectivity and Control The names of the partner should be removed from titles (inconsistent with the rest of the assets in other WPs) * OpenEPC Platform ? partially wrong template. The IPR section should comply with the usual format. * Ericsson Device Connection Platform ? part of the fields are empty * Orange WSC ? wrong template (not using any at all) * Orange API mediation ? wrong template (not using any at all) * Orange Telecom enabler ? wrong template (not using any at all) * Orange voicemail enabler ? wrong template (not using any at all) * Telekom Network Identity Management IPR empty. * Telekom Resource Management - ok * Telekom Seamless Network Connectivity - ok Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: not available URL: From pasquale.donadio at alcatel-lucent.com Wed Oct 19 09:58:45 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Wed, 19 Oct 2011 09:58:45 +0200 Subject: [Fiware-i2nd] R: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: References: <4E9DB5ED.5090906@tid.es> Message-ID: Dear Pier, please find in the wiki the minor modifications related to the Network Element Virtualizer IPR section. Best Regards, Pasquale ________________________________ Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: mercoled? 19 ottobre 2011 9.41 A: chris.woods at intel.com; 'Marco Castrucci'; 'Defrance Serge'; DONADIO, PASQUALE (PASQUALE); Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); sascha.smets at ericsson.com; jeanpierre.lerouzic at orange.com; Dmitry.Sivchenko at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, We are asked to make the asset description in the I2ND wiki page more in line with the original template, I report below a list of comments received, along with the assets whose description has to be updated (the description of non mentioned assets is ok). According to what specified below, can you make the necessary changes to (or add) the assets *by today*, thanks. BR Pier General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don't. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... Particular comments (specific to your WP) * Connected Device Interfacing * Meego - "Runtime pre-requisites"empty. IPR should be more explicit. * Reinforcement Learning - "IPR" & "Publicly available documentation" should be explicitly filled in. * Cloud Edge * No assets! * Network Information and Control * Network Element Virtualizer - IPR empty * Service, Capability, Connectivity and Control The names of the partner should be removed from titles (inconsistent with the rest of the assets in other WPs) * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. * Ericsson Device Connection Platform - part of the fields are empty * Orange WSC - wrong template (not using any at all) * Orange API mediation - wrong template (not using any at all) * Orange Telecom enabler - wrong template (not using any at all) * Orange voicemail enabler - wrong template (not using any at all) * Telekom Network Identity Management IPR empty. * Telekom Resource Management - ok * Telekom Seamless Network Connectivity - ok Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E45.B07B25D0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Wed Oct 19 10:28:24 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 19 Oct 2011 10:28:24 +0200 Subject: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP In-Reply-To: References: <804B13F8F3D94A4AB18B9B01ACB68FA1047BBFEE@EXCHSRV.fokus.fraunhofer.de> Message-ID: Dear Wolfgang, We assumed to start our investigation from the Generic Enablers functionality rather than the assets, although of course the latter will be part of the former. Now I see that the original HLD (D2.2a) section on Security inserted in the Product Vision wiki pages was updated, so we should consider this latter as reference. Maybe by reporting to you our current feedback on the security section of HLD and its GEs (it's not a long list of comments and doubts there) you can help us to point to the assets dealing with those aspects we highlight? We're going soon to send you and Vania (as Security reference contacts for I2ND as mentioned by Pascal) our documents for a joint analysis. Then we'll agree together the most effective way to interact on the topic. BR Pier Da: Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Inviato: marted? 18 ottobre 2011 16:42 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; robert.seidl at nsn.com Oggetto: AW: I2ND S3C and NetIC vs. Security WP Hello Pier, the document you send in your mail regarding the security assets is outdated, please use the document https://forge.fi-ware.eu/docman/view.php/19/518/WP8+Description+of+the+Security+Asset+v10.docx it's the latest version. Best regards Wolfgang Deutsche Telekom AG T-Labs (Research & Development) 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. ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Dienstag, 18. Oktober 2011 09:50 An: Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] R: I2ND S3C and NetIC vs. Security WP Hi Marius, actually as first attempt I expected to gather some comment to the Security chapter description (to understand what they propose and this could impact I2ND), while you did a more detailed analysis about what contribution could come from the I2ND side to those GEs. The two options are of course not alternative but rather complementary, so I propose we keep both of them, and provide by today their contents to the Security people. My input is attached to this mail, I kindly ask the other delegates of the Security Task Force (Henk/Serge, Chris ) to add their comments in any of the two documents (this one or the one sent by Marius yesterday) *by today early afternoon*, thanks. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E3D.1F44BED0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E3D.1F44BED0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E3D.1F44BED0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E3D.1F44BED0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E3D.1F44BED0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From jeanpierre.lerouzic at orange.com Wed Oct 19 10:34:42 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 19 Oct 2011 10:34:42 +0200 Subject: [Fiware-i2nd] Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: References: <4E9DB5ED.5090906@tid.es> Message-ID: Dear Pier and all, Please find in the wiki the modifications related to the following assets: ? Web session Controller ? API mediation ? Fast Telecom Service helper ? Voicemail enabler Best Regards, Jean-Pierre ________________________________ Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: mercoled? 19 ottobre 2011 9.41 A: chris.woods at intel.com; 'Marco Castrucci'; 'Defrance Serge'; DONADIO, PASQUALE (PASQUALE); Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); sascha.smets at ericsson.com; jeanpierre.lerouzic at orange.com; Dmitry.Sivchenko at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, We are asked to make the asset description in the I2ND wiki page more in line with the original template, I report below a list of comments received, along with the assets whose description has to be updated (the description of non mentioned assets is ok). According to what specified below, can you make the necessary changes to (or add) the assets *by today*, thanks. BR Pier General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don't. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... Particular comments (specific to your WP) * Connected Device Interfacing * Meego - "Runtime pre-requisites"empty. IPR should be more explicit. * Reinforcement Learning - "IPR" & "Publicly available documentation" should be explicitly filled in. * Cloud Edge * No assets! * Network Information and Control * Network Element Virtualizer - IPR empty * Service, Capability, Connectivity and Control The names of the partner should be removed from titles (inconsistent with the rest of the assets in other WPs) * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. * Ericsson Device Connection Platform - part of the fields are empty * Orange WSC - wrong template (not using any at all) * Orange API mediation - wrong template (not using any at all) * Orange Telecom enabler - wrong template (not using any at all) * Orange voicemail enabler - wrong template (not using any at all) * Telekom Network Identity Management IPR empty. * Telekom Resource Management - ok * Telekom Seamless Network Connectivity - ok Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From chris.woods at intel.com Wed Oct 19 17:56:38 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 19 Oct 2011 16:56:38 +0100 Subject: [Fiware-i2nd] Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: References: <4E9DB5ED.5090906@tid.es> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B0B86B3@irsmsx503.ger.corp.intel.com> Hi Pier, Please find an updated set of details on MeeGo IPR, and runtime prerequisites. Thanks, Chris From: DONADIO, PASQUALE (PASQUALE) [mailto:pasquale.donadio at alcatel-lucent.com] Sent: Wednesday, October 19, 2011 8:59 AM To: Garino Pierangelo; Woods, Chris; 'Marco Castrucci'; 'Defrance Serge'; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); sascha.smets at ericsson.com; jeanpierre.lerouzic at orange.com; Dmitry.Sivchenko at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier, please find in the wiki the minor modifications related to the Network Element Virtualizer IPR section. Best Regards, Pasquale ________________________________ Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: mercoled? 19 ottobre 2011 9.41 A: chris.woods at intel.com; 'Marco Castrucci'; 'Defrance Serge'; DONADIO, PASQUALE (PASQUALE); Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); sascha.smets at ericsson.com; jeanpierre.lerouzic at orange.com; Dmitry.Sivchenko at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: I: Assets in Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, We are asked to make the asset description in the I2ND wiki page more in line with the original template, I report below a list of comments received, along with the assets whose description has to be updated (the description of non mentioned assets is ok). According to what specified below, can you make the necessary changes to (or add) the assets *by today*, thanks. BR Pier General comments (for all WPs) * There are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * In the general page of each WP, some provide a very short description together with the asset name and other don't. The page with the list of your assets has to have a short description for each one (e.g.: http://tinyurl.com/5snfngy) * IPRs are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... Particular comments (specific to your WP) * Connected Device Interfacing * Meego - "Runtime pre-requisites"empty. IPR should be more explicit. * Reinforcement Learning - "IPR" & "Publicly available documentation" should be explicitly filled in. * Cloud Edge * No assets! * Network Information and Control * Network Element Virtualizer - IPR empty * Service, Capability, Connectivity and Control The names of the partner should be removed from titles (inconsistent with the rest of the assets in other WPs) * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. * Ericsson Device Connection Platform - part of the fields are empty * Orange WSC - wrong template (not using any at all) * Orange API mediation - wrong template (not using any at all) * Orange Telecom enabler - wrong template (not using any at all) * Orange voicemail enabler - wrong template (not using any at all) * Telekom Network Identity Management IPR empty. * Telekom Resource Management - ok * Telekom Seamless Network Connectivity - ok Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC8E80.1170B960]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From castrucci at dis.uniroma1.it Fri Oct 21 18:42:47 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Fri, 21 Oct 2011 18:42:47 +0200 Subject: [Fiware-i2nd] Problem with our mail server Message-ID: <002001cc9010$77b419b0$d028a8c0@cratr70> Dear Pier, all, due to a very heavy storm occurring in Rome on Thursday morning which has flooded the Eleboration Data Center of our University, we have been disconnected from Internet the whole day of yesterday (20/10) and today (21/10) up to 12:00 AM . So, I would be very grateful if you could forward to me all emails sent to us in that period (if any). Thank you very much. Marco ----------------------------------------------- Dr. Ing. Castrucci Marco CRAT - Consortium for the Research in Automation and Telecommunication University of Rome "Sapienza" V. Ariosto 25, 00185 Rome, Italy Tel (+39) 06 77274039 (037) Fax (+39) 06 77274033 Mob (+39) 348 7709997 email: castrucci at dis.uniroma1.it -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Sat Oct 22 23:23:17 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Sat, 22 Oct 2011 23:23:17 +0200 Subject: [Fiware-i2nd] R: [Fiware-wpl] WP9 Questionnaire In-Reply-To: <4E8032BF.8040703@eng.it> References: <4E8032BF.8040703@eng.it> Message-ID: Dear Davide, please find attached the questionnaire comments produced by the I2ND team. Best Regards Pier -----Messaggio originale----- Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Davide Dalle Carbonare Inviato: luned? 26 settembre 2011 10:07 A: fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-wpl] WP9 Questionnaire Dear WP leaders, as you know in WP9 we have produced a first version of "FI-WARE DevComE Technical description" document and some parts of it has been discussed during the last plenary meeting in Turin. At the moment we are updating the document with the comments received during that discussion, and in order to better take into account the various WP needs we kindly ask you to answer to the attached questionnaire (very short) by October 3rd. I'm at your disposal for questions and comments ... thank you and Best Regards, Davide Dalle Carbonare Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE WP9 Questionnaire-I2ND.doc Type: application/msword Size: 41984 bytes Desc: FI-WARE WP9 Questionnaire-I2ND.doc URL: From pierangelo.garino at telecomitalia.it Tue Oct 25 11:03:19 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 25 Oct 2011 11:03:19 +0200 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, please find below the details for the I2ND periodic confcall we?ll have tomorrow. Here is the proposed agenda: * Status of activities * Product Vision wiki page updates * ?Materialising I2ND in FI-WARE? updates * Security team interaction * Description of Features and User Stories for first Development sprint * 6-months Review meeting (Nov 22) ? Requirements * First Open Call ? Contributions * I2ND meeting in Berlin ? Planning * AOB (please circulate in advance the topics you?d like to address in the call) Confcall Details: Time: 10:00 CEST PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com Best Regards Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3790 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USA_en_pwn-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: USA_en_pwn-dial-in-numbers.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Tue Oct 25 11:55:38 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 25 Oct 2011 11:55:38 +0200 Subject: [Fiware-i2nd] Clarification on I2ND confcall Agenda Message-ID: Hi All, I realized that the structure of the agenda items was not maintained once the message was sent. Correct structuring is as follows: - Status of activities . Product Vision wiki page updates . "Materialising I2ND in FI-WARE" updates . Security team interaction - Description of Features and User Stories for first Development sprint - 6-months Review meeting (Nov 22) - Requirements - First Open Call - Contributions - I2ND meeting in Berlin - Planning - AOB (please circulate in advance the topics you'd like to address in the call) BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Wed Oct 26 10:26:24 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 26 Oct 2011 09:26:24 +0100 Subject: [Fiware-i2nd] Security: URGENT Action Point In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B1E95B3@irsmsx503.ger.corp.intel.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B1E968E@irsmsx503.ger.corp.intel.com> Hello All, Please find attached my first draft of the security Epic for Privacy Protection of Subscriber Information toward Applications. This is a first draft - I'd really appreciate your feedback. I am still getting up to speed with all the security requirements - all of your input would be most gratefully received. Many thanks in advance, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Wednesday, October 26, 2011 8:00 AM To: Woods, Chris Subject: R: Security: URGENT Action Point Dear Chris, this looks really a good example of EPIC for the Privacy issue. I propose that, before uploading to the wiki, we share with the other partners in the group (at least those involved in T7.1/CDI). BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: marted? 25 ottobre 2011 20:30 A: Garino Pierangelo Oggetto: RE: Security: URGENT Action Point Hi Pier, Please find attached my first attempt at creating an Epic description of the Privacy protect of subscriber information. It would be great if we could discuss this tomorrow - I'd really appreciate your feedback. If you agree with my description I can upload it to the Wiki tomorrow. Many thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Monday, October 24, 2011 3:28 PM To: Hans.Einsiedler at telekom.de; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Woods, Chris Subject: Security: URGENT Action Point Importance: High Dear All, by reviewing the actions we are requested to do I found the revision of I2ND question marks section (Security topics) in the product vision, and this is exactly what we provided in the document attached. Actually the request was to handle this section the same as done by the Data and the Apps chapters (see their 'Question Marks' section in their FI-WARE Product Vision pages) but I believe that our revision is already in good shape. Now, being this done, we are requested to generate Themes/Epics to be inserted in the Question marks section of the 'Materializing the Interface to Networks and Devices (I2ND) in FI-WARE' page, as done by those chapters. This is an action we need to complete by Wednesday 26th. We need to start creating these entries, and insert in the wiki, I believe we can consider to create an Epic for each of the paragraphs we have in the document, that is at the end four Epics. I suggest the following split of the activity: - I take myself care of entries for 'Identity Management' - Marius might take care of Epic for 'Secure Exposure of Network Services Control Functionality towards Application Platforms' and 'Secure Control Environment for Open Networking and Network Services' (maybe for this latter you could get some contribution from Klaus/Thomas at ALU?) - Chris might take care of Privacy Protection of Subscriber Information towards Applications Please let me know if this is ok for you, or propose alternative solutions, thanks. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: venerd? 21 ottobre 2011 12:51 A: Garino Pierangelo Cc: Schulze, Frank Oggetto: RE: I2ND S3C and NetIC vs. Security WP Hello, We tried to reformulate the paragraph for the exposure of control interfaces from the S3c towards whatever is on top although we think that a complete removal of the paragraph may be better suited. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 20, 2011 11:08 AM To: Corici, Marius-Iulian Subject: R: I2ND S3C and NetIC vs. Security WP Dear Marius, I tried to merge into your document (attached) the one we provided earlier (attached as well) for internal evaluation of our question marks. I believe in fact they contain more or less the same information, and we can share this final joint version with Security people. Can you have a final look and tell me if you agree, there are still a few points (highlighted) which do not fit very well, maybe you can adapt this. Thanks and BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC93C1.54B3C320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Privacy Protection of Subscriber Information towards Applications.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 51052 bytes Desc: Privacy Protection of Subscriber Information towards Applications.docx URL: -------------- next part -------------- ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From chris.woods at intel.com Wed Oct 26 11:11:20 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 26 Oct 2011 10:11:20 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B1E96DD@irsmsx503.ger.corp.intel.com> Hello All, Re: Mind-Map tool ? Freemind As discussed during our call there is a great free (open source), mind-map tool available from the following location: http://freemind.sourceforge.net/wiki/index.php/Download Thanks, Chris -----Original Appointment----- From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Tuesday, October 25, 2011 10:03 AM To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Periodic Confcall When: 26 October 2011 09:00-10:30 (UTC) Dublin, Edinburgh, Lisbon, London. Where: Audioconference Dear All, please find below the details for the I2ND periodic confcall we?ll have tomorrow. Here is the proposed agenda: ? Status of activities ? Product Vision wiki page updates ? ?Materialising I2ND in FI-WARE? updates ? Security team interaction ? Description of Features and User Stories for first Development sprint ? 6-months Review meeting (Nov 22) ? Requirements ? First Open Call ? Contributions ? I2ND meeting in Berlin ? Planning ? AOB (please circulate in advance the topics you?d like to address in the call) Confcall Details: Time: 10:00 CEST PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com Best Regards Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001..txt >> << File: logo Ambiente_foglia.jpg >> ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 26 11:19:45 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 26 Oct 2011 11:19:45 +0200 Subject: [Fiware-i2nd] I: [Fiware-administrative] FI-WARE: first official review report (M1-M6) In-Reply-To: <8EE61BA0CAEDBD4E9DA928D1206463D2E0D681C0D4@EXCLU2K7.hi.inet> References: <8EE61BA0CAEDBD4E9DA928D1206463D2E0D681C0D4@EXCLU2K7.hi.inet> Message-ID: Da: fiware-administrative-bounces at lists.fi-ware.eu [mailto:fiware-administrative-bounces at lists.fi-ware.eu] Per conto di JAVIER DE PEDRO SANCHEZ Inviato: venerd? 21 ottobre 2011 15:44 A: fiware-administrative at lists.fi-ware.eu Oggetto: [Fiware-administrative] FI-WARE: first official review report (M1-M6) Dear all First official review is around the corner and the following approach is going to be followed: Technical issues: 1.- All partners to write out their report describing the technical activities carried out during the last six months. Please, use enclosed word file called: "FI-WARE - technical activities -name_partner" Deadline: October 28th 2.- TID to compile activities per WP and send to every WP leader a file containing all technical activities carried out in their WP. Deadline: November 3st 3.- WP leaders to integrate these activities in a readable section. WP leaders submit their section to TID Deadline: November 8th Administrative issues: 4. All partners to send actual costs during this period. Please, use enclosed excel file called: "FI-WARE - actual costs -name_partner" Deadline: October 28th 5.- TID to send to each partner excel file of follow-up of real effort (done until M5) Deadline: November 3st 6. All partners to send real effort filling out the previous follow-up file. Deadline: November 8th 7. TID to integrate all WP technical activities description, costs and efforts in the first semester report. Please, keep subsidies at tid.es in the recipient list. We would appreciate an email from you to indicate that you have received this e-mail. Thank you very much. Best regards Javier [cid:image001.jpg at 01CC9005.61581320] ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19427 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - technical activities -name_partner.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 230106 bytes Desc: FI-WARE - technical activities -name_partner.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE - actual costs -name_partner.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 42010 bytes Desc: FI-WARE - actual costs -name_partner.xlsx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001..txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Wed Oct 26 15:04:49 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 26 Oct 2011 15:04:49 +0200 Subject: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes Message-ID: Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/542/I2ND_Confcall_20111026_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From lorant.nemeth at nsn.com Wed Oct 26 15:55:25 2011 From: lorant.nemeth at nsn.com (Lorant Nemeth) Date: Wed, 26 Oct 2011 15:55:25 +0200 Subject: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes In-Reply-To: References: Message-ID: <4EA8114D.20200@nsn.com> Hi Pier, I was wondering, if we could set up a 'backlog'/tasklist/tracker for administration issues like 'report technical work done in the past 6 months', 'put this or that into the wiki'..., because after a while it's going to be quite hard to follow them only by checking the minutes. I know, that everybody could do this on his own, but I think a centralized solution would provide better visibility. Br, Loci On 10/26/2011 03:04 PM, ext Garino Pierangelo wrote: > > Dear Partners, > > you can find the minutes of today's confcall here: > > https://forge.fi-ware.eu/docman/view.php/10/542/I2ND_Confcall_20111026_minutes.doc > > Best Regards > > Pier > > ------------------------------------------------------------------ > *Telecom Italia > *Pierangelo Garino > Innovation & Industry Relations -- Research & Prototyping > > Via G. Reiss Romoli 274, I-10148 TORINO > > Tel: +39 011 228 7142 > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra azione > derivante dalla conoscenza di queste informazioni sono rigorosamente > vietate. Qualora abbiate ricevuto questo documento per errore siete > cortesemente pregati di darne immediata comunicazione al mittente e di > provvedere alla sua distruzione, Grazie. > > /This e-mail and any attachments//is //confidential and may contain > privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is > unauthorised. If you are not the intended recipient, please delete > this message and any attachments and advise the sender by return > e-mail, Thanks./ > > *rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se > non ? necessario.* > > > _______________________________________________ > Fiware-i2nd mailing list > Fiware-i2nd at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth Nokia Siemens Networks R&D Team Leader Tel.: +36209849340 Fax: +3612154766 Email: lorant.nemeth at nsn.com Nokia Siemens Networks Kft. Koztelek str. 6 1092, Budapest HUNGARY -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Oct 26 16:44:21 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 26 Oct 2011 16:44:21 +0200 Subject: [Fiware-i2nd] I: Security: URGENT Action Point In-Reply-To: References: Message-ID: Hi All, Here is the picture we mentioned this morning during the confcall (got by Hans during his talk to Security people at DT), concerning the Security Chapter analysis on the interaction with our GEs. This shall be used to complete AP I2ND68 defined in the minutes. BR Pier Da: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Inviato: mercoled? 26 ottobre 2011 06:17 A: Garino Pierangelo; marius-iulian.corici at fokus.fraunhofer.de; chris.woods at intel.com Cc: Wolfgang.Steigerwald at telekom.de; Dmitry.Sivchenko at telekom.de; Nico.Bayer at telekom.de Oggetto: RE: Security: URGENT Action Point Priorit?: Alta Dear all, We had today a discussion using the following picture. It was provided by Wolfgang. Are you aware about this picture? The picture is uncompleted! Cheers, Hans Message Classification: [ ] Public [ ] Private [X] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary ________________________________ From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Montag, 24. Oktober 2011 16:28 To: Einsiedler, Hans; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); chris.woods at intel.com Subject: Security: URGENT Action Point Importance: High Dear All, by reviewing the actions we are requested to do I found the revision of I2ND question marks section (Security topics) in the product vision, and this is exactly what we provided in the document attached. Actually the request was to handle this section the same as done by the Data and the Apps chapters (see their 'Question Marks' section in their FI-WARE Product Vision pages) but I believe that our revision is already in good shape. Now, being this done, we are requested to generate Themes/Epics to be inserted in the Question marks section of the 'Materializing the Interface to Networks and Devices (I2ND) in FI-WARE' page, as done by those chapters. This is an action we need to complete by Wednesday 26th. We need to start creating these entries, and insert in the wiki, I believe we can consider to create an Epic for each of the paragraphs we have in the document, that is at the end four Epics. I suggest the following split of the activity: - I take myself care of entries for 'Identity Management' - Marius might take care of Epic for 'Secure Exposure of Network Services Control Functionality towards Application Platforms' and 'Secure Control Environment for Open Networking and Network Services' (maybe for this latter you could get some contribution from Klaus/Thomas at ALU?) - Chris might take care of Privacy Protection of Subscriber Information towards Applications Please let me know if this is ok for you, or propose alternative solutions, thanks. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: venerd? 21 ottobre 2011 12:51 A: Garino Pierangelo Cc: Schulze, Frank Oggetto: RE: I2ND S3C and NetIC vs. Security WP Hello, We tried to reformulate the paragraph for the exposure of control interfaces from the S3c towards whatever is on top although we think that a complete removal of the paragraph may be better suited. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 20, 2011 11:08 AM To: Corici, Marius-Iulian Subject: R: I2ND S3C and NetIC vs. Security WP Dear Marius, I tried to merge into your document (attached) the one we provided earlier (attached as well) for internal evaluation of our question marks. I believe in fact they contain more or less the same information, and we can share this final joint version with Security people. Can you have a final look and tell me if you agree, there are still a few points (highlighted) which do not fit very well, maybe you can adapt this. Thanks and BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Corici, Marius-Iulian Inviato: luned? 17 ottobre 2011 17:16 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND S3C and NetIC vs. Security WP Hello, Attached is a document trying to respond with the expected information which is offered by S3C and NetIC to the Security GEs. This comes as an addition to the previous document with the functionality requested from the Security GEs. Please let us know on your comments on the document. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 10:23 AM To: Corici, Marius-Iulian; BANNIZA, Thomas-Rolf; pasquale.donadio at alcatel-lucent.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Hi All, I apologise it was my mistake: I had a search filter set, so I couldn't see all the entries in the tracker... Marius, I have made small modification in your tickets to comply with the naming convention for the summary field (inverting FIWARE and EPIC position). I also modified the entry by Pasquale to comply with same rule as well. BR Pier Da: Corici, Marius-Iulian [mailto:marius-iulian.corici at fokus.fraunhofer.de] Inviato: gioved? 13 ottobre 2011 10:08 A: Garino Pierangelo; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes Hello, I've added the epics from S3C on the given link. Please let us know if its ok. https://forge.fi-ware.eu/tracker/index.php?group_id=10&atid=192 Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, October 13, 2011 9:41 AM To: 'BANNIZA, Thomas-Rolf'; Corici, Marius-Iulian Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: I2ND Confcall - 12 Oct - Minutes Marius, Thomas, Do you have troubles in inserting the tickets in the i2nd 'Backlog management' tracker for NetIC and S3C, as I don't see them there? If needed, please let me know and I can help you completing the insertion. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: mercoled? 12 ottobre 2011 14:09 A: Woods, Chris Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] R: I2ND Confcall - 12 Oct - Minutes Great Chris :) BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: mercoled? 12 ottobre 2011 12:33 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: I2ND Confcall - 12 Oct - Minutes RE: I2ND57 - Backlog tracker entries per EPIC for CDI are now available: https://forge.fi-ware.eu/tracker/?atid=192&group_id=10&func=browse From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Wednesday, October 12, 2011 11:01 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 12 Oct - Minutes Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/483/I2ND_Confcall_20111012_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC9366.9FD00860]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Security-and-I2ND.ppt Type: application/vnd.ms-powerpoint Size: 225792 bytes Desc: Security-and-I2ND.ppt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Wed Oct 26 16:58:00 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 26 Oct 2011 16:58:00 +0200 Subject: [Fiware-i2nd] R: I2ND Confcall - 26 Oct - Minutes In-Reply-To: <4EA8114D.20200@nsn.com> References: <4EA8114D.20200@nsn.com> Message-ID: Hi Lorant, Do you mean having a 'living' system, that is a specific tracker used to manage the activities to be done (e.g. one entry per action point, or something like this) and, as soon as they are over, the 'ticket' could be used later to document the activity done? Or do you refer to a simpler solution, like a way to keep track of the work when complete, sort of summary to be used for the reporting as well? In one of the past confcalls (or f2f meetings?) we preliminarly considered not to use a tracker system to manage the activities to be done inside the WP; maybe now that we are little bit more familiar with the tracker system inside FusionForge, we could re-analyse the possibility to setup such a system (we can create e.g. a private tracker inside i2nd project). First of all however it is to be understood better what's the purpose: if it's to be used to keep track of the action points we periodically define, then the Excel sheet available in the same folder of the confcall minutes should be probably enough. If you envisage other, more structured, purposes then we should plan a thread of discussion (maybe a call?) about this where we gather the opinions on the topic and then decide how to proceed. BR Pier Da: Lorant Nemeth [mailto:lorant.nemeth at nsn.com] Inviato: mercoled? 26 ottobre 2011 15:55 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes Hi Pier, I was wondering, if we could set up a 'backlog'/tasklist/tracker for administration issues like 'report technical work done in the past 6 months', 'put this or that into the wiki'..., because after a while it's going to be quite hard to follow them only by checking the minutes. I know, that everybody could do this on his own, but I think a centralized solution would provide better visibility. Br, Loci On 10/26/2011 03:04 PM, ext Garino Pierangelo wrote: Dear Partners, you can find the minutes of today's confcall here: https://forge.fi-ware.eu/docman/view.php/10/542/I2ND_Confcall_20111026_minutes.doc Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth Nokia Siemens Networks R&D Team Leader Tel.: +36209849340 Fax: +3612154766 Email: lorant.nemeth at nsn.com Nokia Siemens Networks Kft. Koztelek str. 6 1092, Budapest HUNGARY Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From chris.woods at intel.com Wed Oct 26 19:10:05 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 26 Oct 2011 18:10:05 +0100 Subject: [Fiware-i2nd] FW: Executing on Task 7.1 In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B1E91B9@irsmsx503.ger.corp.intel.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> Hi All, As discussed on our call I've uploaded the generic version of the execution document I have been discussing with Pier. You can find this generic document here: https://forge.fi-ware.eu/docman/view.php/10/543/Generic+Execution+I2ND.docx For completeness, and openness - I've included the link to my original document, and Pier's comments below. This is a work in progress. I'd really appreciate any improvements you may suggest. Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Wednesday, October 26, 2011 8:55 AM To: Woods, Chris Subject: R: Executing on Task 7.1 Hi Chris, at last I could have a look to your very good document, reflecting in some aspects what we defined and tried to do in the past months (but we never described in a document...), I have added some comment in it from my side, and updated the doc on the Forge site at https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface-pg.docx Generally speaking, I do entirely agree with your proposal, the main concern I have is however that some of the proposed steps should have been already performed in the past months of project activity (and some were actually more or less done, please check the document https://forge.fi-ware.eu/docman/view.php/10/538/CDI_status_2.doc ), so we need to understand whether we can 'skip' (or assume as done) some of them to stay aligned with the overall project timeline (we'll discuss today in the call), or rather we decide to take our time to face all the steps in a more consistent way, causing however some delay to the whole project. My suggestion at the moment would be that we attempt to 'survive' with current not perfectly linear situation, where e.g. some assets are already available even though a real assessment was not done, and for the first release (expected by April) we identify a minimum set of functionality to be implemented which doesn't require too many detailed analysis (and maybe matching some functionality already available...); then we'll restart with next iteration (e.g. including those requirements/epics coming from the other FI-PPP Use Case Projects) with a more complete and organized process as you propose. I propose we share this document with all the CDI partners, and define together how to proceed. We can tell about this in the call in few minutes time... BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: luned? 24 ottobre 2011 18:15 A: Garino Pierangelo Oggetto: Executing on Task 7.1 Hi Pier, As discussed on the phone last week I've converted our previous email discussion (attached) into a discussion document. It is available on the forge at the following location: https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface.docx Thanks, Chris ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From lorant.nemeth at nsn.com Thu Oct 27 09:22:48 2011 From: lorant.nemeth at nsn.com (Lorant Nemeth) Date: Thu, 27 Oct 2011 09:22:48 +0200 Subject: [Fiware-i2nd] R: I2ND Confcall - 26 Oct - Minutes In-Reply-To: References: <4EA8114D.20200@nsn.com> Message-ID: <4EA906C8.6040805@nsn.com> Hi, I wrote a longer letter yesterday, but my laptop crashed so I'll be short this time :) The excel sheet is fine, but it contains short term action points only (1-2 week). On the other hand we have some milestones in the project plan with requirements still to be refined (what/how should things be integrated in the testlab, what does a minor/major SW release mean...). These refined requirements (or questions regarding existing requirements) could be collected in the same tool (i don't really care what tool), so that we could work on/plan with them in advance. Br, Loci On 10/26/2011 04:58 PM, ext Garino Pierangelo wrote: > > Hi Lorant, > > Do you mean having a 'living' system, that is a specific tracker used > to manage the activities to be done (e.g. one entry per action point, > or something like this) and, as soon as they are over, the 'ticket' > could be used later to document the activity done? Or do you refer to > a simpler solution, like a way to keep track of the work when > complete, sort of summary to be used for the reporting as well? > > > In one of the past confcalls (or f2f meetings?) we preliminarly > considered not to use a tracker system to manage the activities to be > done inside the WP; maybe now that we are little bit more familiar > with the tracker system inside FusionForge, we could re-analyse the > possibility to setup such a system (we can create e.g. a private > tracker inside i2nd project). > > First of all however it is to be understood better what's the purpose: > if it's to be used to keep track of the action points we periodically > define, then the Excel sheet available in the same folder of the > confcall minutes should be probably enough. If you envisage other, > more structured, purposes then we should plan a thread of discussion > (maybe a call?) about this where we gather the opinions on the topic > and then decide how to proceed. > > BR > > Pier > > *Da:*Lorant Nemeth [mailto:lorant.nemeth at nsn.com] > *Inviato:* mercoled? 26 ottobre 2011 15:55 > *A:* Garino Pierangelo > *Cc:* fiware-i2nd at lists.fi-ware.eu > *Oggetto:* Re: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes > > Hi Pier, > > I was wondering, if we could set up a 'backlog'/tasklist/tracker for > administration issues like 'report technical work done in the past 6 > months', 'put this or that into the wiki'..., because after a while > it's going to be quite hard to follow them only by checking the minutes. > > I know, that everybody could do this on his own, but I think a > centralized solution would provide better visibility. > > Br, > Loci > > On 10/26/2011 03:04 PM, ext Garino Pierangelo wrote: > > Dear Partners, > > you can find the minutes of today's confcall here: > > https://forge.fi-ware.eu/docman/view.php/10/542/I2ND_Confcall_20111026_minutes.doc > > Best Regards > > Pier > > ------------------------------------------------------------------ > *Telecom Italia > *Pierangelo Garino > Innovation & Industry Relations -- Research & Prototyping > > Via G. Reiss Romoli 274, I-10148 TORINO > > Tel: +39 011 228 7142 > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra azione > derivante dalla conoscenza di queste informazioni sono rigorosamente > vietate. Qualora abbiate ricevuto questo documento per errore siete > cortesemente pregati di darne immediata comunicazione al mittente e di > provvedere alla sua distruzione, Grazie. > > /This e-mail and any attachments is confidential and may contain > privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is > unauthorised. If you are not the intended recipient, please delete > this message and any attachments and advise the sender by return > e-mail, Thanks./ > > *rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se > non ? necessario.* > > > > _______________________________________________ > Fiware-i2nd mailing list > Fiware-i2nd at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-i2nd > > > > -- > L?r?nt N?meth > > Nokia Siemens Networks > R&D Team Leader > Tel.: +36209849340 > Fax: +3612154766 > Email:lorant.nemeth at nsn.com > > Nokia Siemens Networks Kft. > Koztelek str. 6 > 1092, Budapest > HUNGARY > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra azione > derivante dalla conoscenza di queste informazioni sono rigorosamente > vietate. Qualora abbiate ricevuto questo documento per errore siete > cortesemente pregati di darne immediata comunicazione al mittente e di > provvedere alla sua distruzione, Grazie. > > /This e-mail and any attachments//is //confidential and may contain > privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is > unauthorised. If you are not the intended recipient, please delete > this message and any attachments and advise the sender by return > e-mail, Thanks./ > > *rispetta l'ambienteRispetta l'ambiente. Non stampare questa mail se > non ? necessario.* > -- L?r?nt N?meth Nokia Siemens Networks R&D Team Leader Tel.: +36209849340 Fax: +3612154766 Email: lorant.nemeth at nsn.com Nokia Siemens Networks Kft. Koztelek str. 6 1092, Budapest HUNGARY -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeanpierre.lerouzic at orange.com Thu Oct 27 11:01:32 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 27 Oct 2011 11:01:32 +0200 Subject: [Fiware-i2nd] FW: Executing on Task 7.1 In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B1E91B9@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris and all, Thanks for sharing this document. I understand that you proposed a process to assess the Epics and user stories, vs. the assets and resources. My feeling is that a very concrete step, thanks Chris. What I don't understand is on which description you want to base this process because I don't think the current assets and epics give a lot of information about I2ND. If we can't describe what I2ND does in a very concrete and easy to understand way, all efforts to write user stories are moot IMO. Let me try first to look at the DoW and second to look at the Epics, and finally provide some suggestions about what is I2ND and what is missing. ? In the DoW introduction it's written that: "Interface to the Network and Devices - the open interfaces to networks and devices, harmonizing the connectivity needs of services built on top of the platform." So in my personal picture of I2ND it consists of specifications for network and devices interfaces. ? Later in the DoW (B.1.1.4.5) it's mentioned that: A fundamental challenge for the implementation of the required interfaces is that the network functionality is typically distributed over different elements potentially implemented internally in different ways (in multi-vendor environments), and that the interfaces have to take into account the constraints of different providers (in multi-network service scenarios) as well as legal and regulatory requirements. Which makes sense for me if I2ND is about interfaces. ? This is further enforced with the following text (1) Interfaces to end devices (addressed by connected device), (2) interfaces to gateways (cloud proxy), (3) interfaces to connectivity functions inside the network (open networking), and (4) interfaces to services offered by the network operators (network services). When I look at the Epics I can see: ? FIWARE.Epic.I2ND.S3C.ExposedNetworkInformation defines the exposure API for information from the access and core network towards applications such as location, device status, user activity, network events. (mostly an event API). ? EPIC.FIWARE.I2ND.S3C.CoreNetworkControl customizes the IP connectivity according to the requirements of the applications (mostly security features) ? EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement enables the core network to remotely manage connection of devices to the network (A network to device API) ? EPIC.FIWARE.I2ND.S3C.NetworkLevelDataDelivery optimizes the data delivery through network for specific services e.g. unicast, time tolerant communication, groups, multicast and/or broadcast, small messages (a content transport API) ? FIWARE.Epic.I2ND.S3C.SMS+MMS ENABLERS is basically a subset of GSMA's OneAPI ? FIWARE.Epic.I2ND.S3C.Telecom platform_1 manages Telecom calls, conference, voice interaction through a very high level API ? FIWARE.Epic.I2ND.S3C.API mediation_1 deals with publishing, discovering and exposing APIs to stakeholders as well as managing some non functional aspects such as provisioning and monitoring. ? FIWARE.Epic.I2ND.S3C.WSC_1 provides seamless integration of Telco services in devices Now let's draw some conclusions and a rough picture of I2ND : ? Conclusion: o I can't see an EPIC that makes it possible for a Fi-Ware service to deal with devices. But there are two candidates; ? EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement but it is described as a network to device API, so probably we miss a service to network on top of this EPIC. ? WSC_1 probably could be this missing API on top of CoreNetworkDeviceManagement. o Where are interfaces to gateways in EPICS? Orange proposed to work on that depending on requirements from Technicolor, but there is no requirements at the moment. o About Open Networking APIs probably there is no EPIC about it at the moment as "The open networking functional component deals with interfaces that provide open access to the forwarding functions of network nodes and thus enable a certain level of programmability within the network, e.g., concerning flow processing, routing, addressing, and resource management." o When it come to network services APIs I think there are several APIs that cover that: ? At a low level (ExposedNetworkInformation, CoreNetworkControl, NetworkLevelDataDelivery) ? At a higher level: SMS+MMS ENABLERS, Telecom platform_1, API mediation_1, WSC_1 ? Rough picture Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Woods, Chris Envoy? : mercredi 26 octobre 2011 19:10 ? : Garino Pierangelo (pierangelo.garino at telecomitalia.it) Cc : fiware-i2nd (fiware-i2nd at lists.fi-ware.eu) Objet : [Fiware-i2nd] FW: Executing on Task 7.1 Hi All, As discussed on our call I've uploaded the generic version of the execution document I have been discussing with Pier. You can find this generic document here: https://forge.fi-ware.eu/docman/view.php/10/543/Generic+Execution+I2ND.docx For completeness, and openness - I've included the link to my original document, and Pier's comments below. This is a work in progress. I'd really appreciate any improvements you may suggest. Thanks, Chris From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Wednesday, October 26, 2011 8:55 AM To: Woods, Chris Subject: R: Executing on Task 7.1 Hi Chris, at last I could have a look to your very good document, reflecting in some aspects what we defined and tried to do in the past months (but we never described in a document...), I have added some comment in it from my side, and updated the doc on the Forge site at https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface-pg.docx Generally speaking, I do entirely agree with your proposal, the main concern I have is however that some of the proposed steps should have been already performed in the past months of project activity (and some were actually more or less done, please check the document https://forge.fi-ware.eu/docman/view.php/10/538/CDI_status_2.doc ), so we need to understand whether we can 'skip' (or assume as done) some of them to stay aligned with the overall project timeline (we'll discuss today in the call), or rather we decide to take our time to face all the steps in a more consistent way, causing however some delay to the whole project. My suggestion at the moment would be that we attempt to 'survive' with current not perfectly linear situation, where e.g. some assets are already available even though a real assessment was not done, and for the first release (expected by April) we identify a minimum set of functionality to be implemented which doesn't require too many detailed analysis (and maybe matching some functionality already available...); then we'll restart with next iteration (e.g. including those requirements/epics coming from the other FI-PPP Use Case Projects) with a more complete and organized process as you propose. I propose we share this document with all the CDI partners, and define together how to proceed. We can tell about this in the call in few minutes time... BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: luned? 24 ottobre 2011 18:15 A: Garino Pierangelo Oggetto: Executing on Task 7.1 Hi Pier, As discussed on the phone last week I've converted our previous email discussion (attached) into a discussion document. It is available on the forge at the following location: https://forge.fi-ware.eu/docman/view.php/10/530/Executing+on+the+Connected+Device+Interface.docx Thanks, Chris ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 12241 bytes Desc: image002.png URL: From Hans.Einsiedler at telekom.de Thu Oct 27 15:05:42 2011 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 27 Oct 2011 15:05:42 +0200 Subject: [Fiware-i2nd] Telephone conference for the cooperation between Task 7.3, 7.4 abd Task 8.2 Message-ID: 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: not available Type: text/calendar Size: 2278 bytes Desc: not available URL: