From chris.woods at intel.com Tue Nov 1 18:25:33 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 1 Nov 2011 17:25:33 +0000 Subject: [Fiware-i2nd] FW: Executing on Task 7.1 In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B1E91B9@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2539F1@irsmsx503.ger.corp.intel.com> Hi Jean-Pierre, You are concerned that some of the functionality stated in the DoW has not been captured in the epics for I2ND? Specifically, from your email I understood that you are concerned about two major points: A. There are no epics related to 3 functional areas: 1. Service to Device communication ( possible answer below ) 2. Gateway functionality 3. Open network APIs B. There is ambiguity as the Network Service API functional is covered by several epics: ? ExposedNetworkInformation ? CoreNetworkControl ? NetworkLevelDataDelivery ? SMS+MMS ENABLERS ? Telecom platform_1 ? API mediation_1 ? WSC_1 Functional area to Epic relationship It is acceptable for a large functional area to represented by several epics. However if this is the case then we must ensure that the entirety of the original vision is adequately covered in all of the related epics implementations. This will mean that related epic implementers need to meet and work together to ensure that the key functional areas are addressed. With this in mind, do you think that (B, above) the Network Service API can be addressed by each of the epics you listed? Service to Device Communication The remote management epic within Connected Device Interfaces specifically covers services reaching out to devices. Whoever implements this epic will need to liaise with the epic owners for EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement and WSC_1. I think that this (A 1 , above) is addressed. Open Questions I think there is two remaining issues to address 1. Is the Gateway functionality addressed by any of the epics? 2. Is the Open network API functional items addressed by any of the epics? Easy Epic Overview For my own edification I composed the attached mind-map of all epics within I2ND (I've included SVG format - for those recipients without freemind). Thanks, Chirs From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Thursday, October 27, 2011 10:02 AM To: Woods, Chris; pierangelo.garino at telecomitalia.it Cc: fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] FW: Executing on Task 7.1 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: ? 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. ? 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. ? 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." ? 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 [cid:image002.png at 01CC98B1.1BE186A0] 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. [cid:image003.gif at 01CC98B1.1BE186A0]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: image002.png Type: image/png Size: 12241 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 677 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: all epics.mm Type: application/octet-stream Size: 16541 bytes Desc: all epics.mm URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: all epics.svg Type: application/octet-stream Size: 107249 bytes Desc: all epics.svg 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 Tue Nov 1 19:17:48 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 1 Nov 2011 18:17:48 +0000 Subject: [Fiware-i2nd] Security: URGENT Action Point References: <187F4CC97FD0B6488FAE608A8038FF143B1E95B3@irsmsx503.ger.corp.intel.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2539F6@irsmsx503.ger.corp.intel.com> Hello All, I've created a version of this security epic on the Wiki. You can find it at the following address: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.I2ND.CDI.Security.SubscriberPrivacyProtection Chris From: Woods, Chris Sent: Wednesday, October 26, 2011 9:26 AM To: 'Garino Pierangelo'; Wolfgang.Steigerwald at telekom.de; Dmitry.Sivchenko at telekom.de; Nico.Bayer at telekom.de; pierangelo.garino at telecomitalia.it; marius-iulian.corici at fokus.fraunhofer.de; 'Hans.Einsiedler at telekom.de' Cc: fiware-i2nd at lists.fi-ware.eu Subject: RE: Security: URGENT Action Point 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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 01CC98C2.8F890220]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 Nov 2 10:47:33 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 2 Nov 2011 10:47:33 +0100 Subject: [Fiware-i2nd] FW: Executing on Task 7.1 In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B2539F1@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B1E91B9@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B2539F1@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris and all, Yes you summarized perfectly what I wrote clumsily. About your question "do you think that (B, above) the Network Service API can be addressed by each of the epics you listed?" I have no answer but I am open to any suggestion. Best regards, Jean-Pierre De : Woods, Chris [mailto:chris.woods at intel.com] Envoy? : mardi 1 novembre 2011 18:26 ? : LE ROUZIC Jean-Pierre RD-MAPS-REN; pierangelo.garino at telecomitalia.it Cc : fiware-i2nd at lists.fi-ware.eu Objet : RE: [Fiware-i2nd] FW: Executing on Task 7.1 Hi Jean-Pierre, You are concerned that some of the functionality stated in the DoW has not been captured in the epics for I2ND? Specifically, from your email I understood that you are concerned about two major points: A. There are no epics related to 3 functional areas: 1. Service to Device communication ( possible answer below ) 2. Gateway functionality 3. Open network APIs B. There is ambiguity as the Network Service API functional is covered by several epics: ? ExposedNetworkInformation ? CoreNetworkControl ? NetworkLevelDataDelivery ? SMS+MMS ENABLERS ? Telecom platform_1 ? API mediation_1 ? WSC_1 Functional area to Epic relationship It is acceptable for a large functional area to represented by several epics. However if this is the case then we must ensure that the entirety of the original vision is adequately covered in all of the related epics implementations. This will mean that related epic implementers need to meet and work together to ensure that the key functional areas are addressed. With this in mind, do you think that (B, above) the Network Service API can be addressed by each of the epics you listed? Service to Device Communication The remote management epic within Connected Device Interfaces specifically covers services reaching out to devices. Whoever implements this epic will need to liaise with the epic owners for EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement and WSC_1. I think that this (A 1 , above) is addressed. Open Questions I think there is two remaining issues to address 1. Is the Gateway functionality addressed by any of the epics? 2. Is the Open network API functional items addressed by any of the epics? Easy Epic Overview For my own edification I composed the attached mind-map of all epics within I2ND (I've included SVG format - for those recipients without freemind ). Thanks, Chirs From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Thursday, October 27, 2011 10:02 AM To: Woods, Chris; pierangelo.garino at telecomitalia.it Cc: fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] FW: Executing on Task 7.1 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: ? 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. ? 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. ? 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." ? 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.png Type: image/png Size: 12241 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From pierangelo.garino at telecomitalia.it Wed Nov 2 14:45:45 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 2 Nov 2011 14:45:45 +0100 Subject: [Fiware-i2nd] R: FW: Executing on Task 7.1 In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B1E91B9@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B1E98D4@irsmsx503.ger.corp.intel.com> <187F4CC97FD0B6488FAE608A8038FF143B2539F1@irsmsx503.ger.corp.intel.com> Message-ID: Dear Jean-Pierre, Dear Chris, just to add my bit of comments on the topics discussed (hopefully not creating confusions...). I confirm that I2ND will consist of interface specifications, both for network and devices. These will be part of the open specifications of FI-WARE. The execution proposal by Chris was originally prepared for T7.1, while now it has been generalized for all the Tasks in I2ND, that is to the four GEs: CDI, CE, NetIC, S3C. I expect all the Task Coords will have a look and provide a feedback and/or refine if this is felt necessary. I believe your concerns mainly refer to S3C and its relationship with the other GEs, is this right? If not, I don't think there are issues in not having S3C epics describing e.g. the gateway functionality (and for this specific item we have to consider also the work going on inside IoT chapter), because this should be a topic for Cloud Edge epics mainly. In my opinion, the picture you propose provides a possible interpretation of interaction between S3C and the other GEs, although it's not perfectly in line with the original vision of the 4 GEs in our chapter (see below); maybe we can refine this latter according to the valuable insights in your mail. [cid:image003.png at 01CC996E.1A8C8210] Finally, I perfectly agree that a liaison, as suggested by Chris, is necessary between the different GEs in our chapter, to make sure e.g. the remote management within CDI will be matching the expected 'service to device communication' in S3C. BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: mercoled? 2 novembre 2011 10:48 A: chris.woods at intel.com; Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] FW: Executing on Task 7.1 Hi Chris and all, Yes you summarized perfectly what I wrote clumsily. About your question "do you think that (B, above) the Network Service API can be addressed by each of the epics you listed?" I have no answer but I am open to any suggestion. Best regards, Jean-Pierre De : Woods, Chris [mailto:chris.woods at intel.com] Envoy? : mardi 1 novembre 2011 18:26 ? : LE ROUZIC Jean-Pierre RD-MAPS-REN; pierangelo.garino at telecomitalia.it Cc : fiware-i2nd at lists.fi-ware.eu Objet : RE: [Fiware-i2nd] FW: Executing on Task 7.1 Hi Jean-Pierre, You are concerned that some of the functionality stated in the DoW has not been captured in the epics for I2ND? Specifically, from your email I understood that you are concerned about two major points: A. There are no epics related to 3 functional areas: 1. Service to Device communication ( possible answer below ) 2. Gateway functionality 3. Open network APIs B. There is ambiguity as the Network Service API functional is covered by several epics: ? ExposedNetworkInformation ? CoreNetworkControl ? NetworkLevelDataDelivery ? SMS+MMS ENABLERS ? Telecom platform_1 ? API mediation_1 ? WSC_1 Functional area to Epic relationship It is acceptable for a large functional area to represented by several epics. However if this is the case then we must ensure that the entirety of the original vision is adequately covered in all of the related epics implementations. This will mean that related epic implementers need to meet and work together to ensure that the key functional areas are addressed. With this in mind, do you think that (B, above) the Network Service API can be addressed by each of the epics you listed? Service to Device Communication The remote management epic within Connected Device Interfaces specifically covers services reaching out to devices. Whoever implements this epic will need to liaise with the epic owners for EPIC.FIWARE.I2ND.S3C.CoreNetworkDeviceManagement and WSC_1. I think that this (A 1 , above) is addressed. Open Questions I think there is two remaining issues to address 1. Is the Gateway functionality addressed by any of the epics? 2. Is the Open network API functional items addressed by any of the epics? Easy Epic Overview For my own edification I composed the attached mind-map of all epics within I2ND (I've included SVG format - for those recipients without freemind). Thanks, Chirs From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Thursday, October 27, 2011 10:02 AM To: Woods, Chris; pierangelo.garino at telecomitalia.it Cc: fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] FW: Executing on Task 7.1 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: ? 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. ? 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. ? 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." ? 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 [cid:image001.png at 01CC9959.93FB22B0] 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. [cid:image002.gif at 01CC9959.93FB22B0]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.png Type: image/png Size: 12241 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 29619 bytes Desc: image003.png 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 Nov 2 15:53:43 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 2 Nov 2011 14:53:43 +0000 Subject: [Fiware-i2nd] Sharing Webinos Meeting Notes Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B253D0A@irsmsx503.ger.corp.intel.com> Hello All, Myself and Pier reached out to the Webinos Project to explore areas of co-operation. I would like to share the meeting notes from our phone conversation. There appears to be several areas of overlap, including: 1. Connected Devices - Connected Device API implementation 2. Security - Managing access to information, User profile etc 3. Internet of Things - Access to device sensors, Access to local radio (Bluetooth / WiFi) I hope this is of interest, Chris Meeting Notes: Webinos / FI-Ware Intro Attendees: FI-Ware Intel: Chris, Joe Telecom Italia: Pier, Stephen Webinos Nquiringminds: Nick Allott High level synopsis ? The two projects share a lot of similar technical goals ? Co-operation on the following areas is possible: o connected devices o Security and authentication ? Best way to achieve this is for Intel to join as an affiliate member Overview of FI-Ware FI-Ware is EU PPP project which aims to deliver a reference implementation of a platform for future internet development. FI-Ware postulates that the future of the internet will consist of a series of inter connected services. These services will be implemented by GE ( Generic Enablers ). Companies and organisations will offer new services and products by implementing either brand new Generic Enablers, or by create generic enablers which aggregate the output from multiple other generic enablers. The project covers both cloud implementations of a GE structure, "connected" (mobile) devices, and networking technologies. There are 30+ industrial partners involved, including: Telefonica Telecom Italia IBM Technicolor (set to box ) Intel's Involvement Intel is involved in two key areas: o Cloud o Connected devices Connected devices The Connected Device "task" envisions the creation of a platform on a range of devices, from mobile handsets through to in car infotainment systems, that would support the FI-Ware GE model, and enable quick application development and delivery. It is envisioned that this platform will be a HTML5 + JavaScript access to native device functionality. This platform will implement core functionality required to support some of the core functional elements suggested as part of FI-Ware - including: o Supporting the Internet of Things (additional sensor information) o Interfacing with a cloud proxy ( in house cloud edge infrastructure) o Being remotely accessed from the cloud o QoS and Network QoS Technically this direction overlaps with a lot of the great work already preformed by Webinos. Connected Devices Platform creation The connected devices task will try to create the platform by utilising existing technologies, and projects. This includes co-ordinating with other EU funded projects, such as Webinos. Webinos o Inherits from WAC, BONDI, W3C o Intends to push back all results to w3c o Open source project ? Ensuring that contributions can be patent free, and open to use without royalty is important o Significant investment in security solutions including ? Creation of a Personal zone hub (runs in cloud) ? Personal Zone Proxy (agent, runs on device) o Enables headless - "screen zero" javascript o Allows remote access to local resources -2 devices sharing sensors (camera on device A, accessed by javascript on device B) o Target devices: ? TV ? Car ? Laptop / Desktop Implementation in nodes.js ? Windows ? Linux (Ubuntu) ? Mac ? Mobile Implementation in nodes.js ? Android ? Tizen Limited implementations ? Windows Phone 7 ? iOS ? Future platform: Micro (Embedded / Sensor) Implemented as a native 'c' implementation of PZP APIS o 22 core APIS. 18 have been allocated and are being implemented o Has local radio access and control APIS (Bluetooth, WiFi) o APIS are specified in WIDL Co-Operation o Nick attended a prior co-operation meeting in Brussels., 2 months ago o Work in progress to open code base up to non-affiliate members, but not likely to completed until December 2011 / start of 2012. ------------------------------------------------------------- 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 serge.defrance at technicolor.com Thu Nov 3 08:41:01 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 3 Nov 2011 08:41:01 +0100 Subject: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E010FED26DA@MOPESMBX01.eu.thmulti.com> Hello everybody, Is there any conf call planned this morning (9h30 CET) to discuss agenda item of our coming meeting ? 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: mercredi 26 octobre 2011 15:05 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND Confcall - 26 Oct - Minutes 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:image001.gif at 01CC9A04.50E62AF0]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 pasquale.donadio at alcatel-lucent.com Thu Nov 3 09:26:52 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Thu, 3 Nov 2011 09:26:52 +0100 Subject: [Fiware-i2nd] Telco and I2ND meeting in Berlin Message-ID: Hi Pier, Any news about the next meeting in DT (15-16 Nov) ? Have you scheduled a meeting this morning? Best Regards, Pasquale _____________________________________________ Da: DONADIO, PASQUALE (PASQUALE) Inviato: mercoled? 2 novembre 2011 12.45 A: Hans.Einsiedler at telekom.de Oggetto: I2ND meeting in Berlin Hi Hans, I will confirm our participation to the meeting scheduled on 15th, 16th November in DT. Two attendants from ALUI: - Pasquale Donadio, - Giorgio Parladori. Please could you provide some additional information about recommended Hotels? Thanks in advance. Best Regards, Pasquale Pasquale Donadio Alcatel-Lucent Italy Optics PTN System Engineer F: +390828398694 M:+393491264572 W: https://engage.alcatel-lucent.com/people/pdonadio W: http://it.linkedin.com/pub/pasquale-donadio/11/973/297 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Nov 3 09:30:35 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 3 Nov 2011 09:30:35 +0100 Subject: [Fiware-i2nd] R: Telco and I2ND meeting in Berlin In-Reply-To: References: Message-ID: Hi All, we're going to discuss with the Task Leaders the agenda for the meeting this morning. As soon as complete, we'll distribute it to the whole group. BR Pier Da: DONADIO, PASQUALE (PASQUALE) [mailto:pasquale.donadio at alcatel-lucent.com] Inviato: gioved? 3 novembre 2011 09:27 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Telco and I2ND meeting in Berlin Hi Pier, Any news about the next meeting in DT (15-16 Nov) ? Have you scheduled a meeting this morning? Best Regards, Pasquale _____________________________________________ Da: DONADIO, PASQUALE (PASQUALE) Inviato: mercoled? 2 novembre 2011 12.45 A: Hans.Einsiedler at telekom.de Oggetto: I2ND meeting in Berlin Hi Hans, I will confirm our participation to the meeting scheduled on 15th, 16th November in DT. Two attendants from ALUI: * Pasquale Donadio, * Giorgio Parladori. Please could you provide some additional information about recommended Hotels? Thanks in advance. Best Regards, Pasquale Pasquale Donadio Alcatel-Lucent Italy Optics PTN System Engineer F: +390828398694 M:+393491264572 W: https://engage.alcatel-lucent.com/people/pdonadio W: http://it.linkedin.com/pub/pasquale-donadio/11/973/297 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 Thu Nov 3 11:06:44 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 3 Nov 2011 11:06:44 +0100 Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Message-ID: Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Connected Device Interfacing * WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? * Meego - ok * Web API - be more specific in the IPR section * Reinforcement Learning - ok. * Cloud Edge * Network Organizer - IPR- please be more explicit * Network Information and Control * NOX based OpenFlow controller - ok * Network Element Virtualizer - ok * DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) * Service, Capability, Connectivity and Control * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored * Device Connection Platform - part of the fields are empty. IPR must be more specific * Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) * API mediation - not compliant with the official template. Poorly populated. * Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. * Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case * Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Nov 3 11:26:59 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Thu, 3 Nov 2011 11:26:59 +0100 Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE References: Message-ID: <00a701cc9a13$1ed71510$d028a8c0@cratr70> Dear Miguel, for the description of 3rd party assets we are going to use in FI-WARE, can you confirm me that it is enough to use the Hadoop template? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: fiware-i2nd at lists.fi-ware.eu Sent: Thursday, November 03, 2011 11:06 AM Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= a.. Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets b.. IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source". To end with this situation change all assets and put this: a.. Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". a.. If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") b.. Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. c.. If you rephrase this or use variants it's ok as long as the additions are properly explained. c.. Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) d.. Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS a.. Connected Device Interfacing a.. WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? b.. Meego - ok c.. Web API - be more specific in the IPR section d.. Reinforcement Learning - ok. b.. Cloud Edge a.. Network Organizer - IPR- please be more explicit c.. Network Information and Control a.. NOX based OpenFlow controller - ok b.. Network Element Virtualizer - ok c.. DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) d.. Service, Capability, Connectivity and Control a.. OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored b.. Device Connection Platform - part of the fields are empty. IPR must be more specific c.. Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) d.. API mediation - not compliant with the official template. Poorly populated. e.. Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. f.. Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. g.. Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. h.. Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case i.. Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG a.. I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es---------------------------------------------------------------------- ------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 mcp at tid.es Thu Nov 3 12:25:15 2011 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 03 Nov 2011 12:25:15 +0100 Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: <00a701cc9a13$1ed71510$d028a8c0@cratr70> References: <00a701cc9a13$1ed71510$d028a8c0@cratr70> Message-ID: <4EB27A1B.4030205@tid.es> Dear Marco, I assume everyone is using the online tutorials: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_and_configure_trackers_in_FusionForge http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_describe_assets_adopted_as_baseline_for_development_of_FI-WARE_GE_reference_implementations The last one gives you the answer, whis is ... yes! Regards Miguel El 03/11/2011 11:26, Marco Castrucci escribi?: Dear Miguel, for the description of 3rd party assets we are going to use in FI-WARE, can you confirm me that it is enough to use the Hadoop template? Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: fiware-i2nd at lists.fi-ware.eu Sent: Thursday, November 03, 2011 11:06 AM Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely ?urge? the relevant partners to complete their ?homework?. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. ?This product has IPR associated to it?, ?Open source?? To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Connected Device Interfacing * WEB Runtime Engine ? please be more specific in the IPR section. Is it offered under FRAND terms? * Meego ? ok * Web API - be more specific in the IPR section * Reinforcement Learning ? ok. * Cloud Edge * Network Organizer - IPR- please be more explicit * Network Information and Control * NOX based OpenFlow controller - ok * Network Element Virtualizer ? ok * DRAGON ? it looks like a 3rd party asset, in this case it should follow a different template (short one) * Service, Capability, Connectivity and Control * OpenEPC Platform ? partially wrong template. The IPR section should comply with the usual format. ? comments ignored * Device Connection Platform ? part of the fields are empty. IPR must be more specific * Web session Controller ? the extra section ?Known software requirements? breaks the template. Please amend. ?As far I know there are no IPR attached to the FIWARE WSC asset? must be improved (a more formal and accurate remark is needed) * API mediation ? not compliant with the official template. Poorly populated. * Fast Telecom Service helper ? not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Voicemail enabler ? not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. * Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( ?Patent is pending for Deutsche Telekom AG?) ? insufficient. We miss a ?and it will be offered to the rest of the partners under a FRAND scheme? or whatever that applies in this case * Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( ?EU/US patents issued for Telekom?) ? insufficient. We miss a ?and it will be offered to the rest of the partners under a FRAND scheme? or whatever that applies to this case 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas-Rolf.Banniza at alcatel-lucent.com Thu Nov 3 13:22:49 2011 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Thu, 3 Nov 2011 13:22:49 +0100 Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: A References: A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0693A471@SLFSNX.rcs.alcatel-research.de> Dear Pier, do you care for the follwing sub task from Miguel's list? * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Or schould each task leader do this for its own task? 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: Donnerstag, 3. November 2011 11:07 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Wichtigkeit: Hoch Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory ) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Connected Device Interfacing * WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? * Meego - ok * Web API - be more specific in the IPR section * Reinforcement Learning - ok. * Cloud Edge * Network Organizer - IPR- please be more explicit * Network Information and Control * NOX based OpenFlow controller - ok * Network Element Virtualizer - ok * DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) * Service, Capability, Connectivity and Control * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored * Device Connection Platform - part of the fields are empty. IPR must be more specific * Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) * API mediation - not compliant with the official template. Poorly populated. * Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. * Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case * Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 castrucci at dis.uniroma1.it Thu Nov 3 14:19:58 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Thu, 3 Nov 2011 14:19:58 +0100 Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE References: Message-ID: <019c01cc9a2b$491f48c0$d028a8c0@cratr70> Dear Pier and Thomas, due to the fact that the NOX based controller asset is provided by a 3rd party, I've corrected its description according to the proper template to be used. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: fiware-i2nd at lists.fi-ware.eu Sent: Thursday, November 03, 2011 11:06 AM Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= a.. Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets b.. IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source". To end with this situation change all assets and put this: a.. Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". a.. If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") b.. Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. c.. If you rephrase this or use variants it's ok as long as the additions are properly explained. c.. Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) d.. Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS a.. Connected Device Interfacing a.. WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? b.. Meego - ok c.. Web API - be more specific in the IPR section d.. Reinforcement Learning - ok. b.. Cloud Edge a.. Network Organizer - IPR- please be more explicit c.. Network Information and Control a.. NOX based OpenFlow controller - ok b.. Network Element Virtualizer - ok c.. DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) d.. Service, Capability, Connectivity and Control a.. OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored b.. Device Connection Platform - part of the fields are empty. IPR must be more specific c.. Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) d.. API mediation - not compliant with the official template. Poorly populated. e.. Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. f.. Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. g.. Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. h.. Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case i.. Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG a.. I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es---------------------------------------------------------------------- ------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Nov 3 14:22:26 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 3 Nov 2011 14:22:26 +0100 Subject: [Fiware-i2nd] R: URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0693A471@SLFSNX.rcs.alcatel-research.de> References: A <133D9897FB9C5E4E9DF2779DC91E947C0693A471@SLFSNX.rcs.alcatel-research.de> Message-ID: Dear Thomas, yes I'll take care of this item, maybe in the evening or tomorrow early morning to avoid possible conflicts in editing the wiki page. BR Pier Da: BANNIZA, Thomas-Rolf [mailto:Thomas-Rolf.Banniza at alcatel-lucent.com] Inviato: gioved? 3 novembre 2011 13:23 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: AW: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier, do you care for the follwing sub task from Miguel's list? * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Or schould each task leader do this for its own task? 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: Donnerstag, 3. November 2011 11:07 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Wichtigkeit: Hoch Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Connected Device Interfacing * WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? * Meego - ok * Web API - be more specific in the IPR section * Reinforcement Learning - ok. * Cloud Edge * Network Organizer - IPR- please be more explicit * Network Information and Control * NOX based OpenFlow controller - ok * Network Element Virtualizer - ok * DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) * Service, Capability, Connectivity and Control * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored * Device Connection Platform - part of the fields are empty. IPR must be more specific * Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) * API mediation - not compliant with the official template. Poorly populated. * Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. * Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case * Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 01CC9A34.029EA4F0]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 pasquale.donadio at alcatel-lucent.com Thu Nov 3 14:26:24 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Thu, 3 Nov 2011 14:26:24 +0100 Subject: [Fiware-i2nd] R: URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: <019c01cc9a2b$491f48c0$d028a8c0@cratr70> References: <019c01cc9a2b$491f48c0$d028a8c0@cratr70> Message-ID: Dear Pier and Thomas, Also DRAGON asset is provided by a 3rd party. On the wiki you can find the new version of the description, in short format. 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: gioved? 3 novembre 2011 14.20 A: Garino Pierangelo; Banniza, Thomas-Rolf (Thomas-Rolf) Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier and Thomas, due to the fact that the NOX based controller asset is provided by a 3rd party, I've corrected its description according to the proper template to be used. Best regards Marco ----- Original Message ----- From: Garino Pierangelo To: fiware-i2nd at lists.fi-ware.eu Sent: Thursday, November 03, 2011 11:06 AM Subject: [Fiware-i2nd] URGENT ACTION: MODIFICATIONS to Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, Below you can find another feedback by Miguel concerning the wiki pages we have produced so far, with a request for harmonization of specific items like asset descriptions etc. I remind you that some of the actions requested here were already requested in the past, so please *take the necessary actions without further delay*. On the other hand, the deadline is Nov 4th, that is tomorrow! Please read carefully the instructions, identify the items that you have in charge and do the modifications: *Task Leaders* are required to supervise, and timely 'urge' the relevant partners to complete their 'homework'. BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: mercoled? 2 novembre 2011 18:28 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear Pier & Hans, I am sending private emails to all WPLs with further comments to the "Materializing the Interface to Networks and Devices (I2ND) in FI-WARE" section on the wiki. There are general comments (applicable to most WPs) and other that apply to your WP in particular. We have prepared a simple and friendly tutorial to make sure that we go in the same direction (http://tinyurl.com/6gueb5t) . General comments (for all WPs) ============================================================= * Still there are heterogeneous templates for assets. Take Samson and Hadoop as the reference templates for assets * IPRs in Assets are very frequently expressed in a vague manner. "This product has IPR associated to it", "Open source"... To end with this situation change all assets and put this: * Assets with patents/IPRs. Use this text: "This product will be licensed under FRAND (Fair Reasonable and Non-Discriminatory) Terms according to pre-requisites of the FI-PPP program". * If needed, you can add sentences like the one in SAMSON ("Licensing of the software under an Open Source license is currently under consideration. ") * Open source: see Hadoop and use it as template. The text is: "This product is licensed under the open source XXX" where "xxx" will be replaced with the license that applies and a link to the detailed terms where possible. * If you rephrase this or use variants it's ok as long as the additions are properly explained. * Programming Artefacts. I see that this is frequently removed. This is part of the template, it is mandatory and has to stay there. I am not sure if everyone is understanding this. This field elaborates on what we are providing to a developer(an API?, a tool? ... ) * Delete empty sections. I see many blocks of "Themes", "Features" and "User Stories" (for instance) that are empty. This gives a poor impression and will cause trouble in the review. Please remove blank sections, they will have to be re-created when the first entry is added to the wiki Particular comments (specific to your WP) ============================================================= If I say "ok" to one of them, do not relax. It means that there is no particular remark. But the general comments still apply to it and it may need changes. 1) COMMENTS ON ASSETS * Connected Device Interfacing * WEB Runtime Engine - please be more specific in the IPR section. Is it offered under FRAND terms? * Meego - ok * Web API - be more specific in the IPR section * Reinforcement Learning - ok. * Cloud Edge * Network Organizer - IPR- please be more explicit * Network Information and Control * NOX based OpenFlow controller - ok * Network Element Virtualizer - ok * DRAGON - it looks like a 3rd party asset, in this case it should follow a different template (short one) * Service, Capability, Connectivity and Control * OpenEPC Platform - partially wrong template. The IPR section should comply with the usual format. - comments ignored * Device Connection Platform - part of the fields are empty. IPR must be more specific * Web session Controller - the extra section "Known software requirements" breaks the template. Please amend. "As far I know there are no IPR attached to the FIWARE WSC asset" must be improved (a more formal and accurate remark is needed) * API mediation - not compliant with the official template. Poorly populated. * Fast Telecom Service helper - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Voicemail enabler - not compliant with the official template. Poorly populated. IPR are not specific enough At least, express FRAND terms. * Telekom Network Identity Management - The name is not correct, the partner name must be removed. IPR empty. * Telekom Resource Management - The name is not correct, the partner name must be removed. IPR ( "Patent is pending for Deutsche Telekom AG") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies in this case * Telekom Seamless Network Connectivity - The name is not correct, the partner name must be removed. IPR ( "EU/US patents issued for Telekom") - insufficient. We miss a "and it will be offered to the rest of the partners under a FRAND scheme" or whatever that applies to this case 2) COMMENTS ON BACKLOG * I will send you this first thing in the morning Please make sure that this is properly looked at by all the concerned members of the WP under your supervision. Deadline: Friday, 4 EOB. Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- size=2 width="100%" align=center> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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. ________________________________ [CID:00000000000000000000000000000001 at TI.Disclaimer] ________________________________ _______________________________________________ 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 Nov 3 15:01:26 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 3 Nov 2011 15:01:26 +0100 Subject: [Fiware-i2nd] NEW URGENT ACTION: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Message-ID: Dear All, below you can find the second part of requests to make the wiki pages, as well as project trackers, more uniform across the different chapters. Main work for us is to go inside each epic and, according to the guidelines page mentioned in the mail, complete the missing fields (except the 'Theme' field, as we do not have upper layer entities for our epics). Second main item is to manage the discrepancy between the FIWARE.Epic.I2ND.NetIC.DeviceReachability epic and the tracker, i.e. missing entry in the latter for that epic (Thomas can you check this point and take necessary action, thanks). As for previous actions, the deadline is tomorrow... BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: gioved? 3 novembre 2011 13:49 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Re: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Hello again, As promised, my comments to the backlog follow. General comments (for all WPs) ============================= You should review the full description of your backlog entries in the Wiki to make sure all fields are properly filled in. Despite we provided a spreadsheet explaining how to fill each fields and some examples when we started this exercise (the spreadsheet was distributed in mid August) we have found that that guidelines haven't been followed in many cases. We have enhanced the tutorial on the Wiki to include all the explanations now and to make sure that there is a place on the Wiki that you can check out in case of doubt. You can find it at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki Particularly important is the style used for the text provided as "Goal" field. Please try to align with the patterns provided in the description of this field. Do not forget to visit the pages with instructions to handle the trackers: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_and_configure_trackers_in_FusionForge * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter Particular comments (for this WP) ============================= * Backlog entries on the Wiki and tracker fully aligned except for: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.I2ND.NetIC.DeviceReachability The deadline is tomorrow, Friday 4 EOB Best regards, Miguel 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 Thu Nov 3 16:37:35 2011 From: chris.woods at intel.com (Woods, Chris) Date: Thu, 3 Nov 2011 15:37:35 +0000 Subject: [Fiware-i2nd] NEW URGENT ACTION: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE In-Reply-To: References: Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2540FC@irsmsx503.ger.corp.intel.com> Hi Pier, Miguel, I need some clarity on the clarity on the priority numeric system: ? Question: Does a low number represent a high priority, or a low priority? o (0...n) Where: 0 = very high priority & n = low priority OR o (n...0) Where: n = high priority & 0 = low priority? ? Question: Is the priority numbering system zero based? Or based on 1? (is 0 high, or 1 high?) ? Question: What are the numeric mappings for the MoSCoW textual values? MoSCoW Numeric Value? Alternative? Must 0 (high)? 3? Should 1? 2? Could 2? 1? Wont 3 (low)? 0? The details on the wiki (table under "Edit the backlog entry details") are ambiguous on these points. - Have you guys addressed these points before? Perhaps I've missed the information Thanks in advance for your help, 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: Thursday, November 03, 2011 2:01 PM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] NEW URGENT ACTION: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Dear All, below you can find the second part of requests to make the wiki pages, as well as project trackers, more uniform across the different chapters. Main work for us is to go inside each epic and, according to the guidelines page mentioned in the mail, complete the missing fields (except the 'Theme' field, as we do not have upper layer entities for our epics). Second main item is to manage the discrepancy between the FIWARE.Epic.I2ND.NetIC.DeviceReachability epic and the tracker, i.e. missing entry in the latter for that epic (Thomas can you check this point and take necessary action, thanks). As for previous actions, the deadline is tomorrow... BR Pier Da: Miguel Carrillo [mailto:mcp at tid.es] Inviato: gioved? 3 novembre 2011 13:49 A: Garino Pierangelo; hans.einsiedler at telekom.de Cc: JUAN JOSE HIERRO SUREDA Oggetto: Re: Materializing the Interface to Networks and Devices (I2ND) in FI-WARE Hello again, As promised, my comments to the backlog follow. General comments (for all WPs) ============================= You should review the full description of your backlog entries in the Wiki to make sure all fields are properly filled in. Despite we provided a spreadsheet explaining how to fill each fields and some examples when we started this exercise (the spreadsheet was distributed in mid August) we have found that that guidelines haven't been followed in many cases. We have enhanced the tutorial on the Wiki to include all the explanations now and to make sure that there is a place on the Wiki that you can check out in case of doubt. You can find it at: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki Particularly important is the style used for the text provided as "Goal" field. Please try to align with the patterns provided in the description of this field. Do not forget to visit the pages with instructions to handle the trackers: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_and_configure_trackers_in_FusionForge * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter Particular comments (for this WP) ============================= * Backlog entries on the Wiki and tracker fully aligned except for: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.I2ND.NetIC.DeviceReachability The deadline is tomorrow, Friday 4 EOB Best regards, Miguel 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 01CC9A3E.82A764C0]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 chris.woods at intel.com Thu Nov 3 17:01:55 2011 From: chris.woods at intel.com (Woods, Chris) Date: Thu, 3 Nov 2011 16:01:55 +0000 Subject: [Fiware-i2nd] Hotel Recommendations for Berlin Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B254125@irsmsx503.ger.corp.intel.com> Hi Folks, Is there any recommendations for hotel accommodations for the meeting in Berlin on the 15-16th? 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hans.Einsiedler at telekom.de Thu Nov 3 23:51:46 2011 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 3 Nov 2011 23:51:46 +0100 Subject: [Fiware-i2nd] Logistic information for the WP7 meeting Message-ID: Dear all, Please find attached the map to reach us and some recommendations for hotels. Please note: We do not need ID card numbers etc. Please have you ID card with you to show it at the reception (if needed). We will prepare a list of attendances. Cheers, Hams Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary Please note, my signature has changed! ================================================================ Hans Joachim Einsiedler Project manager/Team leader Deutsche Telekom Laboratories, Innovation Development Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423 Fax: +49 391 53475795 Mobile: +49 170 22 74 682 hans.einsiedler at telekom.de ================================================================ 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, Guido Kerkhoff, Edward R. Kozel, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr.: DE50478376 -------------- next part -------------- A non-text attachment was scrubbed... Name: DeutscheTelekom-SC-Winterfeldtstrasse-short-v3.pdf Type: application/pdf Size: 710481 bytes Desc: DeutscheTelekom-SC-Winterfeldtstrasse-short-v3.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: list of hotels close to winterfeldtstra?e.pdf Type: application/pdf Size: 12832 bytes Desc: list of hotels close to winterfeldtstra?e.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Hotel-Quentin.pdf Type: application/pdf Size: 472558 bytes Desc: Hotel-Quentin.pdf URL: From pasquale.donadio at alcatel-lucent.com Fri Nov 4 10:31:46 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Fri, 4 Nov 2011 10:31:46 +0100 Subject: [Fiware-i2nd] R: NetIC interface - Torino discussion summary In-Reply-To: <01e001cc76e6$19b83500$d028a8c0@cratr70> References: <01e001cc76e6$19b83500$d028a8c0@cratr70> Message-ID: Dear Marco, all Please find @ https://forge.fi-ware.eu/docman/view.php/10/568/Task+7.3+-+Torino+meeting+discussion_v2.0.ppt A new version containing the additional example presented in Turin, about the Network Element Virtualizer case It should be used as basis for future discussions 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: luned? 19 settembre 2011 18.06 A: fiware-i2nd Oggetto: [Fiware-i2nd] NetIC interface - Torino discussion summary Dear Task 7.3 partners, I prepared a short presentation with a summary of the internal discussion we had in Torino regarding the NetIC interface. You can find it here: https://forge.fi-ware.eu/docman/view.php/10/392/Task+7.3+-+Torino+meeting+discussion.ppt Please consider it as a working file, so please fell free to add further comments or details. 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 Mon Nov 7 08:34:05 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 7 Nov 2011 08:34:05 +0100 Subject: [Fiware-i2nd] I2ND Meeting: proposed agenda Message-ID: Dear All, You can find below the agenda defined for the I2ND meeting taking place next week in Berlin (Hans already provided in a separate mail the logistic info about it). Please provide any suggestion for modifications and improvements by Thursday (10) at the latest, thanks. ----------------------------------------------------- I2ND Meeting - Berlin 15-16 Nov 2011 Nov 15th - Tuesday * 11-15 - Plenary session: Refinement of execution and processes within WP/Tasks/GEs (3h+lunch) * Revise proposal by Chris * Provide final strategy for the WP * Tools to keep track of work done and to be done (Lorant's N. mail)? * Security aspects * Elaboration on picture provided by Security team about interaction with I2ND GEs * 15-17 - Parallel sessions per Task/GE (2h) (maybe extended up to 18 if required) Nov 16th - Wednesday * 9-11 - Plenary session: Alignment of Functionality among the GEs in the chapter (2h) * Discussion of contact points, overlaps, gaps, epics, etc (Task Coords) * Setting next interaction steps * 11-13 - Parallel sessions per Task/GE (2h) * 14-15 - (cont) Parallel sessions per Task/GE (1h) * Any specific request per Task? * 15-16 - Plenary session: other topics (1h) * GE Development strategies/Alignment with Sprint Phases o (To be checked with ProjMgr too) * Managing Interaction with other WPs and Projects * 16-17 - Wrap up and actions 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 pierangelo.garino at telecomitalia.it Mon Nov 7 10:46:18 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 7 Nov 2011 10:46:18 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint In-Reply-To: <4EB3E27B.5070906@tid.es> References: <4EB3E27B.5070906@tid.es> Message-ID: Hi All, We are (too) slowly completing our activity in refining the contents of the wiki page 'Materialising I2ND in Fi-WARE', in particular concerning the following items: a) Refine the assets description according to the guidelines distributes a number of times b) Insert the Features for each GE which will be selected for 1st Minor Release of FI-WARE (I remind this could be either turning an epic into a Feature, or a refinement on epic that generate specific feature(s)). In the mail sent by Juanjo below, you can find further explanations on how to define Features. It is however recognized that doubts can still be present which prevent us to safely define the Features for our GEs, e.g. not a sufficiently refined stage of epics analysis to identify clearly the items which can turn into a Feature, or because it is not sure whether they can be implemented in the first minor release or not. On the other hand we have to show how things are progressing in our work, and how we manage them. For this reason, 'Work Items' have been introduced, which in my view also provide to some extent a possible (maybe still partial) way to create the overall picture of what we have to achieve (i.e. the issue raised by Lorant in one of his mails a few days ago). The Work Items (see again the full explanation below by Juanjo) will be used to keep track of what we have to do, not in terms of "functionality supported by the product", but rather as activity to be done, e.g. to refine epics, to identify the relevant Features, etc. I personally interpret it as a list of 'to-do' things in the chapter. c) Work Items will be: - entries (tickets) in the i2nd tracker, - they are private, i.e. not visible to others than FI-WARE partners, - and will not need any wiki page associated to them. The hard deadline we have to meet in providing items a), b) earlier listed, and c) the 'Work Items' just introduced, is November 10th: this is the date by which Project Officer will check the presence of complete wiki and Forge site of FI-WARE. I would therefore suggest that we progress in the following way: 1. Complete in max 2 days the asset descriptions (Task Leaders to monitor!) 2. If feasible, provide Features for first minor release by Nov 8 (Task Leaders to monitor!) 3. If no Feature feasible, joint effort between WPL/WPA and Task Leaders to provide entries in the 'Work Items', again by Nov 10. Concerning point 3 above, I propose to have a confcall with TLs either today afternoon (15:30-16:30), tomorrow morning (10:00-11:00) or tomorrow afternoon (15:30-16:30). Discussion item will be how to manage 'Work Items' for I2ND, and what entries we should provide by the deadline. Please WPA and TLs let me have your preference asap, thanks. 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? 4 novembre 2011 14:03 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Hi all, We definitively need to close the selection of Features for the 1st Minor Release of FI-WARE as well as the planning of the 1st Sprint. We should have closed it by end of October but unfortunately we are delayed. Therefore, we have to take the necessary corrective actions. This mail is intended to put this actions in place so that we can recover these few days of delay and get back on track. Everything should be fixed by Nov 10th at the latest. We will do this at the price of making the first sprint a bit shorter, still planning it to finish by end of November. On Nov 10th, it should be clear what are the Features selected for the 1st Minor Release of FI-WARE and what are the backlog entries to be addressed in the 1st Sprint. That information should be visible on your tracker. Note that November 10th is the date at which we have told our PO that everything should be available on the Wiki and FusionForge environment. Now, following the actions/recommendations to implement/follow (some have already been tackled by some of you, but I'm summarizing them here for the convenience of all). Don't hesitate to raise any question or doubt that you may have. Please share them with your teams. Regarding Selection of Features for a given GE: Features may be considered just as a kind of Epic you believe you understand enough (i.e., you own enough detailed info describing the functionality of the Epic) as to feel confident that can be addressed in the duration of a release (duration of releases, also named as minor releases, are three months, don't confuse with usage of the term "release" in the DoW that comprises several releases and we have started to name as "major release"). You may hay identified a number of Features following the above criteria. However, some of you have only identified entries that you have labeled as Epic so far. If so, the first exercise I would ask you to do is to review the list of Epics you have and try to ask yourself the following question ... "Is this a functionality I really understand and have enough information about as to feel confident that could be addressed in 3 months ?" If your answer is "yes", then simply label the Epic as Feature and change the entry both at the Wiki and the tracker accordingly. It may happen that the Epics you have identified are still at a very high-level though. Therefore, you cannot guarantee that you will be able to address them in any. Thus, you need to refine them and this will be work to be done. Those Epics cannot be selected as Features, of course. I would suggest that you try to make some progress refining them until November 10th and try to find out whether you can derive more detailed entries from them and check whether some of them can be labeled as Features. But those entries you believe cannot qualify as Feature because they are still too high-level should be kept as Epics. The first minor release is scheduled to finish by end of January. I know that we have considered finishing it by end of February but after feedback from some of you, let's keep it to finish by end of January. Once you identify a number of Features, it's a matter of deciding whether you feel confident enough to assign it to a particular minor release within the first major release. If so, you should assign it a ReleaseId to the ticket associated to the Feature on the tracker. We will adopt the following convention for identifying minor releases in FI-WARE (i.e., for the values of ReleasesId fields on the tracker): FIWARE.Release.. Where is the number of the major release the minor release is associated to Where is the number of the minor release, within the major release Note that you may not yet feel confident about what release will be the release in which you will address a particular Feature. If so, simply don't assign a ReleaseId to the corresponding ticket. Anyway, bear in mind that, when referring to Features in releases other than the current minor release, you are just setting up an expectation. Expectations may change a bit and we may decide to update the list of Features we plan to address in the second minor release while developing the first minor release. Adapting the planning over time is what Agile is all about. If by November 10th you haven't identified any Feature and you still only have Epics, don't panic. See next section. Regarding planning of 1st Sprint: Some people have shared the feedback that they feel like they are not still in the position to identify a relevant list of User Stories or even Features. They still need to work on the set of Epics they had currently identified. How can we show we are doing some work in the course of the first sprint and be able to follow-up progress ? After thinking a bit on the matter, I have decided to introduce the concept of "Work Item". Work items refer to work to be done in the course of a sprint, trying to meet a concrete goal. It may relate to work to be done in order to refine an Epic (or a feature) and derive actual Features (or User-stories) derived from it. In general, any work you need to address to progress development but may be difficult to express in terms of "functionality supported by the product". This I hope will help you to declare things to be addressed in the first sprint (and subsequent sprints) in a more natural/intuitive way. "Work Items" is not something I had invented myself. It was already identified as a special kind of backlog entries by some Agile authors. Indeed was identified by Dean Leffingwell in the paper I had already sent to you some time ago. The reason why I feel reluctant to introduce these kind of entries in our definition of Backlog was that I was afraid about the explosion of entries in the Wiki. Besides, some of these work items may relate to activities that we may wish to keep at confidential level, just shared among FI-WARE partners. At the end of the day, users (application developers in our case) should just need to know about functionality we plan to develop in GEs. Now I see the advantages that introducing these "Work Items" will bring to some chapters, and definitively they will help us to move things forward and monitor progress. So let's go for their introduction. However, trying to minimize overhead what I believe we can adopt as a formula is that these Work Items just need to be registered on the tracker and we don't need to create a detailed entry on the Wiki. I feel like this is a good compromise and have the following advantages: * We will keep on the public Wiki only that information that is relevant in terms of description of the functionality to be supported by GEs. At the end of the day, this is what is relevant from an user (app developer) perspective, so there is no need to overflown the Wiki with additional, so fine-grained info. * Work Items would exist on the trackers (which is the place where you can get the complete view of a backlog) and trackers linked to chapters are private to chapter members. This will be helpful Given said the above, the task to be done until Nov 10th is to get a good list of User-Stories and Work Items that help to describe what you will do during the first sprint (ending Nov 30th). Hope that this will mean a more clear goal and then you will be able to provide some "meat to eat" by then. We will adopt the following convention for identifying Sprints in FI-WARE (i.e., for the values of SprintId fields on the tracker): FIWARE.Sprint... Where is the number of the major release where the sprint is planned Where is the number of the minor release, within the major release, where the sprint is planned Where is the number of the sprint ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: a-lean-and-scalable-requirements-information-model-for-agile-enterprises.pdf Type: application/pdf Size: 1463988 bytes Desc: a-lean-and-scalable-requirements-information-model-for-agile-enterprises.pdf 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 jeanpierre.lerouzic at orange.com Mon Nov 7 12:58:55 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Mon, 7 Nov 2011 12:58:55 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint In-Reply-To: References: <4EB3E27B.5070906@tid.es> Message-ID: Dear Pier, Hans and all, I am currently on a business trip and it will be difficult for me to modify or insert new content. 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 7 novembre 2011 10:46 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Hi All, We are (too) slowly completing our activity in refining the contents of the wiki page 'Materialising I2ND in Fi-WARE', in particular concerning the following items: a) Refine the assets description according to the guidelines distributes a number of times b) Insert the Features for each GE which will be selected for 1st Minor Release of FI-WARE (I remind this could be either turning an epic into a Feature, or a refinement on epic that generate specific feature(s)). In the mail sent by Juanjo below, you can find further explanations on how to define Features. It is however recognized that doubts can still be present which prevent us to safely define the Features for our GEs, e.g. not a sufficiently refined stage of epics analysis to identify clearly the items which can turn into a Feature, or because it is not sure whether they can be implemented in the first minor release or not. On the other hand we have to show how things are progressing in our work, and how we manage them. For this reason, 'Work Items' have been introduced, which in my view also provide to some extent a possible (maybe still partial) way to create the overall picture of what we have to achieve (i.e. the issue raised by Lorant in one of his mails a few days ago). The Work Items (see again the full explanation below by Juanjo) will be used to keep track of what we have to do, not in terms of "functionality supported by the product", but rather as activity to be done, e.g. to refine epics, to identify the relevant Features, etc. I personally interpret it as a list of 'to-do' things in the chapter. c) Work Items will be: - entries (tickets) in the i2nd tracker, - they are private, i.e. not visible to others than FI-WARE partners, - and will not need any wiki page associated to them. The hard deadline we have to meet in providing items a), b) earlier listed, and c) the 'Work Items' just introduced, is November 10th: this is the date by which Project Officer will check the presence of complete wiki and Forge site of FI-WARE. I would therefore suggest that we progress in the following way: 1. Complete in max 2 days the asset descriptions (Task Leaders to monitor!) 2. If feasible, provide Features for first minor release by Nov 8 (Task Leaders to monitor!) 3. If no Feature feasible, joint effort between WPL/WPA and Task Leaders to provide entries in the 'Work Items', again by Nov 10. Concerning point 3 above, I propose to have a confcall with TLs either today afternoon (15:30-16:30), tomorrow morning (10:00-11:00) or tomorrow afternoon (15:30-16:30). Discussion item will be how to manage 'Work Items' for I2ND, and what entries we should provide by the deadline. Please WPA and TLs let me have your preference asap, thanks. 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? 4 novembre 2011 14:03 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] IMPORTANT UPDATE/HINTS on Selection of Features for the 1st Minor Release and planning of 1st Sprint Hi all, We definitively need to close the selection of Features for the 1st Minor Release of FI-WARE as well as the planning of the 1st Sprint. We should have closed it by end of October but unfortunately we are delayed. Therefore, we have to take the necessary corrective actions. This mail is intended to put this actions in place so that we can recover these few days of delay and get back on track. Everything should be fixed by Nov 10th at the latest. We will do this at the price of making the first sprint a bit shorter, still planning it to finish by end of November. On Nov 10th, it should be clear what are the Features selected for the 1st Minor Release of FI-WARE and what are the backlog entries to be addressed in the 1st Sprint. That information should be visible on your tracker. Note that November 10th is the date at which we have told our PO that everything should be available on the Wiki and FusionForge environment. Now, following the actions/recommendations to implement/follow (some have already been tackled by some of you, but I'm summarizing them here for the convenience of all). Don't hesitate to raise any question or doubt that you may have. Please share them with your teams. Regarding Selection of Features for a given GE: Features may be considered just as a kind of Epic you believe you understand enough (i.e., you own enough detailed info describing the functionality of the Epic) as to feel confident that can be addressed in the duration of a release (duration of releases, also named as minor releases, are three months, don't confuse with usage of the term "release" in the DoW that comprises several releases and we have started to name as "major release"). You may hay identified a number of Features following the above criteria. However, some of you have only identified entries that you have labeled as Epic so far. If so, the first exercise I would ask you to do is to review the list of Epics you have and try to ask yourself the following question ... "Is this a functionality I really understand and have enough information about as to feel confident that could be addressed in 3 months ?" If your answer is "yes", then simply label the Epic as Feature and change the entry both at the Wiki and the tracker accordingly. It may happen that the Epics you have identified are still at a very high-level though. Therefore, you cannot guarantee that you will be able to address them in any. Thus, you need to refine them and this will be work to be done. Those Epics cannot be selected as Features, of course. I would suggest that you try to make some progress refining them until November 10th and try to find out whether you can derive more detailed entries from them and check whether some of them can be labeled as Features. But those entries you believe cannot qualify as Feature because they are still too high-level should be kept as Epics. The first minor release is scheduled to finish by end of January. I know that we have considered finishing it by end of February but after feedback from some of you, let's keep it to finish by end of January. Once you identify a number of Features, it's a matter of deciding whether you feel confident enough to assign it to a particular minor release within the first major release. If so, you should assign it a ReleaseId to the ticket associated to the Feature on the tracker. We will adopt the following convention for identifying minor releases in FI-WARE (i.e., for the values of ReleasesId fields on the tracker): FIWARE.Release.. Where is the number of the major release the minor release is associated to Where is the number of the minor release, within the major release Note that you may not yet feel confident about what release will be the release in which you will address a particular Feature. If so, simply don't assign a ReleaseId to the corresponding ticket. Anyway, bear in mind that, when referring to Features in releases other than the current minor release, you are just setting up an expectation. Expectations may change a bit and we may decide to update the list of Features we plan to address in the second minor release while developing the first minor release. Adapting the planning over time is what Agile is all about. If by November 10th you haven't identified any Feature and you still only have Epics, don't panic. See next section. Regarding planning of 1st Sprint: Some people have shared the feedback that they feel like they are not still in the position to identify a relevant list of User Stories or even Features. They still need to work on the set of Epics they had currently identified. How can we show we are doing some work in the course of the first sprint and be able to follow-up progress ? After thinking a bit on the matter, I have decided to introduce the concept of "Work Item". Work items refer to work to be done in the course of a sprint, trying to meet a concrete goal. It may relate to work to be done in order to refine an Epic (or a feature) and derive actual Features (or User-stories) derived from it. In general, any work you need to address to progress development but may be difficult to express in terms of "functionality supported by the product". This I hope will help you to declare things to be addressed in the first sprint (and subsequent sprints) in a more natural/intuitive way. "Work Items" is not something I had invented myself. It was already identified as a special kind of backlog entries by some Agile authors. Indeed was identified by Dean Leffingwell in the paper I had already sent to you some time ago. The reason why I feel reluctant to introduce these kind of entries in our definition of Backlog was that I was afraid about the explosion of entries in the Wiki. Besides, some of these work items may relate to activities that we may wish to keep at confidential level, just shared among FI-WARE partners. At the end of the day, users (application developers in our case) should just need to know about functionality we plan to develop in GEs. Now I see the advantages that introducing these "Work Items" will bring to some chapters, and definitively they will help us to move things forward and monitor progress. So let's go for their introduction. However, trying to minimize overhead what I believe we can adopt as a formula is that these Work Items just need to be registered on the tracker and we don't need to create a detailed entry on the Wiki. I feel like this is a good compromise and have the following advantages: * We will keep on the public Wiki only that information that is relevant in terms of description of the functionality to be supported by GEs. At the end of the day, this is what is relevant from an user (app developer) perspective, so there is no need to overflown the Wiki with additional, so fine-grained info. * Work Items would exist on the trackers (which is the place where you can get the complete view of a backlog) and trackers linked to chapters are private to chapter members. This will be helpful Given said the above, the task to be done until Nov 10th is to get a good list of User-Stories and Work Items that help to describe what you will do during the first sprint (ending Nov 30th). Hope that this will mean a more clear goal and then you will be able to provide some "meat to eat" by then. We will adopt the following convention for identifying Sprints in FI-WARE (i.e., for the values of SprintId fields on the tracker): FIWARE.Sprint... Where is the number of the major release where the sprint is planned Where is the number of the minor release, within the major release, where the sprint is planned Where is the number of the sprint ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Hans.Einsiedler at telekom.de Mon Nov 7 16:03:07 2011 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Mon, 7 Nov 2011 16:03:07 +0100 Subject: [Fiware-i2nd] Telephone conference for the cooperation between Task 7.3, 7.4 abd Task 8.2 - figure - cheers, Hans Message-ID: Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423??????? Fax: +49 391 53475795 Mobile: +49 170 22 74 682 hans.einsiedler at telekom.de www.telekom.com ================================================================ Erleben, was verbindet. ? Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Chairman) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Edward Kozel, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- 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: From Hans.Einsiedler at telekom.de Mon Nov 7 16:03:04 2011 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Mon, 7 Nov 2011 16:03:04 +0100 Subject: [Fiware-i2nd] Telephone conference for the cooperation between Task 7.3, 7.4 abd Task 8.2 Message-ID: Dear all, Sorry for not sending the dial in number. Agenda: - Short introduction round - Description of the needs of Task 8.2 (interfaces) - Description of the needs of Task 7.3 and 7.4 (interfaces) - Discussion I will send around shortly the figure we have used for the previous discussion. 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: 3584 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Tue Nov 8 12:51:58 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 8 Nov 2011 12:51:58 +0100 Subject: [Fiware-i2nd] I2ND periodic confcall Message-ID: Dear All, here is the provisional agenda for our periodic confcall: - Review of pending action points - Backlog and wiki Wiki entries Assets Features/User stories New proposal for tracker entries Work Items - Finalisation of agenda for I2ND meeting - Updates on Review meeting - Updates on Open Calls - AOB Call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [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: 3482 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 serge.defrance at technicolor.com Tue Nov 8 15:00:27 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Tue, 8 Nov 2011 15:00:27 +0100 Subject: [Fiware-i2nd] I2ND periodic confcall In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0121C9BC13@MOPESMBX01.eu.thmulti.com> Dear All, I updated our media wiki chapter devoted to Cloud Edge with a ?Feature? (Home Resource Abstraction layer). Regards, Serge. -----Original Appointment----- From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: mardi 8 novembre 2011 12:52 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] I2ND periodic confcall When: mercredi 9 novembre 2011 10:00-11:00 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Where: audioconference Dear All, here is the provisional agenda for our periodic confcall: - Review of pending action points - Backlog and wiki Wiki entries Assets Features/User stories New proposal for tracker entries Work Items - Finalisation of agenda for I2ND meeting - Updates on Review meeting - Updates on Open Calls - AOB Call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001.txt >> << File: logo Ambiente_foglia.jpg >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasquale.donadio at alcatel-lucent.com Tue Nov 8 18:13:28 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Tue, 8 Nov 2011 18:13:28 +0100 Subject: [Fiware-i2nd] R: I2ND periodic confcall In-Reply-To: References: Message-ID: Dear Pier, We apologize but none of us will be able to join the telco planned tomorrow. We'll keep track of the minutes and email discussion. Best Regards, Pasquale -----Appuntamento originale----- Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: marted? 8 novembre 2011 12.52 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND periodic confcall Data: mercoled? 9 novembre 2011 10.00-11.00 (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Percorso: audioconference Dear All, here is the provisional agenda for our periodic confcall: - Review of pending action points - Backlog and wiki Wiki entries Assets Features/User stories New proposal for tracker entries Work Items - Finalisation of agenda for I2ND meeting - Updates on Review meeting - Updates on Open Calls - AOB Call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001.txt >> << File: logo Ambiente_foglia.jpg >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeanpierre.lerouzic at orange.com Tue Nov 8 18:15:56 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Tue, 8 Nov 2011 18:15:56 +0100 Subject: [Fiware-i2nd] R: I2ND periodic confcall In-Reply-To: References: Message-ID: I am sorry but I also won't be able to attend this conference. 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? : mardi 8 novembre 2011 18:13 ? : Garino Pierangelo Cc : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: I2ND periodic confcall Dear Pier, We apologize but none of us will be able to join the telco planned tomorrow. We'll keep track of the minutes and email discussion. Best Regards, Pasquale -----Appuntamento originale----- Da: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Inviato: marted? 8 novembre 2011 12.52 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I2ND periodic confcall Data: mercoled? 9 novembre 2011 10.00-11.00 (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Percorso: audioconference Dear All, here is the provisional agenda for our periodic confcall: - Review of pending action points - Backlog and wiki Wiki entries Assets Features/User stories New proposal for tracker entries Work Items - Finalisation of agenda for I2ND meeting - Updates on Review meeting - Updates on Open Calls - AOB Call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. << File: USA_en_pwn-dial-in-numbers.pdf >> Rispetta l'ambiente. Non stampare questa mail se non ? necessario. << File: ATT00001.txt >> << File: logo Ambiente_foglia.jpg >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Nov 9 14:54:45 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 9 Nov 2011 14:54:45 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall - Minutes (9 Nov) Message-ID: Dear All, you can find here https://forge.fi-ware.eu/docman/view.php/10/581/I2ND_Confcall_20111109_minutes.doc the minutes of today's confcall, along with the updated list of APs (https://forge.fi-ware.eu/docman/view.php/10/484/Action+List_20111109.xlsx ). 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 pierangelo.garino at telecomitalia.it Wed Nov 9 15:09:20 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 9 Nov 2011 15:09:20 +0100 Subject: [Fiware-i2nd] WP/ Review report contribution Message-ID: Dear All, this is the WP7 contribution prepared in conjunction with the TLs, sent to the Project Coord yesterday for inclusion in the technical report for first project review. I expect that some refinement will be necessary, due to the harmonization with other contributions. 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: FI-WARE - technical activities - M1-M6 - (WP7)-v1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 53523 bytes Desc: FI-WARE - technical activities - M1-M6 - (WP7)-v1.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 pierangelo.garino at telecomitalia.it Wed Nov 9 15:39:10 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 9 Nov 2011 15:39:10 +0100 Subject: [Fiware-i2nd] Features/User Stories naming convention Message-ID: Hi All, as said this morning in the call, if you are going to insert Features or User Stories in the wiki pages, please follow the naming convention defined in the last WPL/WPA confcall, that is: New page name == . Where is the name of upper granularity, and is the name for new entry. Example applied to CDI GE in the 'Materialising ...' I2ND page - There you can find an epic whose id (and corresponding wiki page name) is: o FIWARE.Epic.I2ND.CDI.DeviceConnectivity - We might create a Feature related to this epics, concerning the AvailableConnectivity, so the Feature id (and corresponding wiki page) would be: o FIWARE.Epic.I2ND.CDI.DeviceConnectivity.AvailableConnectivity In this example: - FIWARE.Epic.I2ND.CDI.DeviceConnectivity is the - AvailableConnectivity is the If we add a User Story to the newly created Feature (e.g. ActiveConnection), then the new page would be: - FIWARE.Epic.I2ND.CDI.DeviceConnectivity.AvailableConnectivity. ActiveConnection Please notice that this naming convention applies only to new entries: those pages already inserted will not be affected at the moment, even if they have a different naming structure. 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-Rolf.Banniza at alcatel-lucent.com Wed Nov 9 15:59:16 2011 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Wed, 9 Nov 2011 15:59:16 +0100 Subject: [Fiware-i2nd] 'work item' for T.7.3 Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0693A7CB@SLFSNX.rcs.alcatel-research.de> Dear Pier, to deal with the needed work on our northbound interface, we would like to introduce a 'work item' with the name 'design of the NetIC northbound interface protocol'. By this, this important work item (not in the sense of AGILE but in the sense of the work we have in fact to do!) will be formally introduced. Following our latest discussions on what an AGILE work item might be, it seems that the AGILE work item is something like a WP-private EPIC or feature. This would mean, that we can structure our work item further (what we will have to do, probably after the Berlin meeting). As I don't know how to introduce the work item into our backlog tracker (by the way: if the work item is not a backlog element why then introduce into the backlog tracker?? -->TID), would you please be so kind to do this for me or give advice how to do it? Best regards, Thomas P.S.: maybe, the other tasks might choose a similar way for their interface (or did they find another way to ensure common design of their interface?) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Thomas R. Banniza Alcatel-Lucent Deutschland AG Bell Labs Germany Dept. ZFZ/N Lorenzstrasse 10 70435 Stuttgart, Germany Phone: +49 711 821-32232 Fax: +49 711 821-32185 email: Thomas-Rolf.Banniza at alcatel-lucent.com Web: www.alcatel-lucent.com Alcatel-Lucent Deutschland AG Sitz der Gesellschaft: Stuttgart ? Amtsgericht Stuttgart HRB 4026 Vorsitzender des Aufsichtsrates: Michael Oppenhoff Vorstand: Alf Henryk Wulf (Vorsitzender) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Peter Kury ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Alcatel-Lucent : At the Speed of Ideas ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Diese E-Mail-Nachricht und ihre etwaigen Anlagen k?nnen vertrauliche Informationen enthalten. Wenn Sie diese E-Mail-Nachricht irrt?mlich erhalten haben, bitten wir Sie, uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon gefertigte Kopien umgehend zu vernichten. Die irrt?mlich erhaltene E-Mail und ihre etwaigen Anlagen d?rfen weder weitergeleitet noch anderweitig verwendet werden. This e-mail and its attachments, if any, may contain confidential information. If you have received this e-mail in error, please notify us and delete or destroy the e-mail and its attachments, if any, immediately. If you have received this e-mail in error, you must not forward or make use of the e-mail and its attachments, if any. From pierangelo.garino at telecomitalia.it Wed Nov 9 16:20:55 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 9 Nov 2011 16:20:55 +0100 Subject: [Fiware-i2nd] R: 'work item' for T.7.3 In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0693A7CB@SLFSNX.rcs.alcatel-research.de> References: <133D9897FB9C5E4E9DF2779DC91E947C0693A7CB@SLFSNX.rcs.alcatel-research.de> Message-ID: Dear Thomas, I think your example is perfectly in line with what I assume a Work Item (Agile) could be. Introducing a Work Item in the backlog is not yet a possibility at the moment, as no 'entry type' has been defined for it, we're waiting the input from TID. However I expect this will be available by tomorrow (I'll urge for having it available). About structuring it further: yes in principle this could be feasible, however we should introduce new 'entry types' for this, and don't think could be a good idea, but I'll check also this possibility. On the other hand, I think it would be nice to create Tasks linked to a Work Item, the same which can be done for any other ticket type (features, user stories, etc). This is possible when you open a ticket, by clicking on the link 'Build Task Relation'. Yes you're right: the Work Item is not a 'real' backlog entry so why inserting it in the backlog? However this can be used to keep track of work in progress (the main reason for having it); I also thought we could create another tracker in our WP, and use it for the work items only, but again this would reduce (or make it somehow trickier) that 'visibility' expected so I didn't propose it. For the time being, please prepare all what you want to put inside your Work Item(s), and wait for insertion until we have the information on how to proceed for doing it. Hope this is clarifying the point. BR Pier -----Messaggio originale----- Da: BANNIZA, Thomas-Rolf [mailto:Thomas-Rolf.Banniza at alcatel-lucent.com] Inviato: mercoled? 9 novembre 2011 15:59 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: 'work item' for T.7.3 Dear Pier, to deal with the needed work on our northbound interface, we would like to introduce a 'work item' with the name 'design of the NetIC northbound interface protocol'. By this, this important work item (not in the sense of AGILE but in the sense of the work we have in fact to do!) will be formally introduced. Following our latest discussions on what an AGILE work item might be, it seems that the AGILE work item is something like a WP-private EPIC or feature. This would mean, that we can structure our work item further (what we will have to do, probably after the Berlin meeting). As I don't know how to introduce the work item into our backlog tracker (by the way: if the work item is not a backlog element why then introduce into the backlog tracker?? -->TID), would you please be so kind to do this for me or give advice how to do it? Best regards, Thomas P.S.: maybe, the other tasks might choose a similar way for their interface (or did they find another way to ensure common design of their interface?) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Thomas R. Banniza Alcatel-Lucent Deutschland AG Bell Labs Germany Dept. ZFZ/N Lorenzstrasse 10 70435 Stuttgart, Germany Phone: +49 711 821-32232 Fax: +49 711 821-32185 email: Thomas-Rolf.Banniza at alcatel-lucent.com Web: www.alcatel-lucent.com Alcatel-Lucent Deutschland AG Sitz der Gesellschaft: Stuttgart ? Amtsgericht Stuttgart HRB 4026 Vorsitzender des Aufsichtsrates: Michael Oppenhoff Vorstand: Alf Henryk Wulf (Vorsitzender) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Peter Kury ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Alcatel-Lucent : At the Speed of Ideas ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Diese E-Mail-Nachricht und ihre etwaigen Anlagen k?nnen vertrauliche Informationen enthalten. Wenn Sie diese E-Mail-Nachricht irrt?mlich erhalten haben, bitten wir Sie, uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon gefertigte Kopien umgehend zu vernichten. Die irrt?mlich erhaltene E-Mail und ihre etwaigen Anlagen d?rfen weder weitergeleitet noch anderweitig verwendet werden. This e-mail and its attachments, if any, may contain confidential information. If you have received this e-mail in error, please notify us and delete or destroy the e-mail and its attachments, if any, immediately. If you have received this e-mail in error, you must not forward or make use of the e-mail and its attachments, if any. 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 pasquale.donadio at alcatel-lucent.com Thu Nov 10 11:37:56 2011 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Thu, 10 Nov 2011 11:37:56 +0100 Subject: [Fiware-i2nd] NetworkResourceControl: Feature and User Story Message-ID: Dear Thomas, Please find @ https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_(I2ND)_in_FI-WARE#Network_Information_and_Control the first feature/user story extracted from the NetworResourceControl EPIC, formatted accordingly Best Regards, Pasquale Pasquale Donadio Alcatel-Lucent Italy Optics PTN System Engineer F: +390828398694 M:+393491264572 W: https://engage.alcatel-lucent.com/people/pdonadio W: http://it.linkedin.com/pub/pasquale-donadio/11/973/297 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Nov 10 13:50:04 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 10 Nov 2011 13:50:04 +0100 Subject: [Fiware-i2nd] Final Berlin meeting agenda Message-ID: Dear All, Following the feedback received, I send you the final agenda for next week's meeting. In red you can find the modified/added items. See you in Berlin! Pier ----------------------------------------------------- I2ND Meeting - Berlin 15-16 Nov 2011 Nov 15th - Tuesday * 11-15 - Plenary session: Refinement of execution and processes within WP/Tasks/GEs (3h+lunch) * Revise proposal by Chris * Provide final strategy for the WP * Tools to keep track of work done and to be done (Lorant's N. mail)? * Security aspects * Elaboration on picture provided by Security team about interaction with I2ND GEs * 15-17 - Parallel sessions per Task/GE (2h) (maybe extended up to 18 if required) Nov 16th - Wednesday * 9-11 - Plenary session: Alignment of Functionality among the GEs in the chapter (2h) * Discussion of contact points, overlaps, gaps, epics, etc (Task Coords) * Setting next interaction steps * Review Meeting: Slides revision * 11-13 - Parallel sessions per Task/GE (2h) * 14-15 - (cont) Parallel sessions per Task/GE (1h) * Any specific request per Task? * 15-16 - Plenary session: other topics (1h) * GE Development strategies/Alignment with Sprint Phases o (To be checked with ProjMgr too) * Managing Interaction with other WPs and Projects * 16-17 - Wrap up and actions ------------------------------------------------------------------ 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 pierangelo.garino at telecomitalia.it Fri Nov 11 10:35:27 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 11 Nov 2011 10:35:27 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Selection of features for 1st minor release and planning of 1st sprint In-Reply-To: <4EBCDB45.9060904@tid.es> References: <4EBCDB45.9060904@tid.es> Message-ID: Hi All, today there will be a revision of wiki pages, particularly for Features and User Stories (unfortunately no news yet about Work Items!), which might require some adjustement. I'll forward you such requests asap, if any. I kindly ask the Task Leaders to verify that each GE has at least one Features and/or User Story, and also make sure they refer to what will be available at the end of first minor release. Thanks and 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: venerd? 11 novembre 2011 09:22 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Selection of features for 1st minor release and planning of 1st sprint Hi, We will devote the whole day to review that everything is Ok and you have actually finished your work regarding selection of features for the first minor release (scheduled to finish by end of January) and planning of 1st sprint (scheduled to finish by end of November). Please stay tunned and react promptly to any request we may ask. Thanks, -- 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 _______________________________________________ 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 Fri Nov 11 10:43:31 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 11 Nov 2011 10:43:31 +0100 Subject: [Fiware-i2nd] R: I: [Fiware-wpl] Selection of features for 1st minor release and planning of 1st sprint In-Reply-To: References: <4EBCDB45.9060904@tid.es> Message-ID: .. And don't forget to insert the corresponding i2nd tracker entry (ticket) for those Features and User Stories added... Pier -----Messaggio originale----- Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: venerd? 11 novembre 2011 10:35 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] I: [Fiware-wpl] Selection of features for 1st minor release and planning of 1st sprint Hi All, today there will be a revision of wiki pages, particularly for Features and User Stories (unfortunately no news yet about Work Items!), which might require some adjustement. I'll forward you such requests asap, if any. I kindly ask the Task Leaders to verify that each GE has at least one Features and/or User Story, and also make sure they refer to what will be available at the end of first minor release. Thanks and 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: venerd? 11 novembre 2011 09:22 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Selection of features for 1st minor release and planning of 1st sprint Hi, We will devote the whole day to review that everything is Ok and you have actually finished your work regarding selection of features for the first minor release (scheduled to finish by end of January) and planning of 1st sprint (scheduled to finish by end of November). Please stay tunned and react promptly to any request we may ask. Thanks, -- 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 _______________________________________________ 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. _______________________________________________ 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. From pierangelo.garino at telecomitalia.it Mon Nov 14 22:20:16 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 14 Nov 2011 22:20:16 +0100 Subject: [Fiware-i2nd] I: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker In-Reply-To: <8CE42417C139684CA4AB55DE1C6A2CFC2079A488B0@GRFMBX707BA020.griffon.local> References: <4EC0AD12.7060204@tid.es> <4EC0C0D6.6030603@tid.es> <8CE42417C139684CA4AB55DE1C6A2CFC2079A488B0@GRFMBX707BA020.griffon.local> Message-ID: Hi Juanjo, here is the status of activity about modifications to be done today. You can find my comments below in Green (look for P.G.). Hope everything is sufficient for producing the expected docs. BR Pier Da: Garino Pierangelo Inviato: luned? 14 novembre 2011 09:10 A: 'BANNIZA, Thomas-Rolf'; Woods, Chris; Hans.Einsiedler at telekom.de; 'Defrance Serge'; pasquale.donadio at alcatel-lucent.com Cc: Heijnen Henk (henk.heijnen at technicolor.com); 'WUENSTEL, Klaus'; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de) Oggetto: I: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker Dear All, As announced on Friday, here is a list of actions we have to perform to complete the I2ND backlog (tracker + wiki pages wherever required), in order to finalise the second release of FI-WARE product vision. First of all, you'll see that introduction of Work Items is suggested in some case, so below are the instructions on how to enter WorkItems in the tracker: - First of all, I have added the 'WorkItem' as new value available for the field 'Entry type'; you can select it when creating a new ticket. - Then, here is the contents of a mail by Juanjo explaining the naming convention (this is an evolution of the naming convention we introduced last week): Regarding the Id for these backlog entries, you should follow the convention: FIWARE.WorkItem... It is recommended that the follows a format like [.]. so that the original Epic/Feature the WorkItem relates to can be easily traced. I remind you that Work Items do not need to have a full detailed description on the Wiki. Just a ticket on the tracker, with all fields properly filled. Back to the list of actions to be performed, you can find it below: I have added a responsible for each of them (yellow highlight), please let me know if this creates troubles to complete by today, and we'll find an alternative solution. Despite what said in the mail, I'd like that ALL the points are done (both blue and red items) so that we complete once for all the modifications. Please let me know asap if you have troubles to perform the modifications, thanks. BR Pier Da: Juanjo Hierro [mailto:jhierro at tid.es] Inviato: luned? 14 novembre 2011 08:19 A: Hans.Einsiedler at telekom.de; Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker Dear Pier and Hans, Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter. You have to review them and take the necessary corrective measure. Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed. Many of the issues are rather easy to address. With the exception of those market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel. I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section). Please forward them to members of your team as soon as possible. I copy the rest of the WPLs and WPAs because I haven't sent my detailed comments to all of them and it might be worth that they review your comments to find out what may apply to them as well. This may help them to anticipate any issue on their respective chapters. Best regards, -- Juanjo I2ND: * General comments: * Regarding entries linked to Features, you should verify that the "FI-WARE Release Id" field on the tracker is properly filled for all Features you plan to address in the 1st minor release. This field should also be filled in Features you believe will be addressed in the second minor release P.G.: This is basically done. For all GEs there is at least one entry scheduled for first minor release, plus some (few!) scheduled for first sprint. * You have used "User-Stories" in the Id of entries linked to some of the User-Stories instead of "Story" as suggested in the template and tutorial. Since it only applies to two entries, I would encourage you to fix it. Unfortunately, you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page that corresponds to the backlog entry description) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. P.G.: Done. * Connected Device Interfacing: * I miss the tickets linked to the FIWARE.Feature.I2ND.CDI.Phone.* functionalities as well as P.G.: Temporarily removed Feature entries from wiki (saved names for re-insertion later). * The FIWARE.User-Stories.I2ND.CDI.DeviceFeatures.CommonDeviceInterface.FrameWorkAndPlatform User-story may probably map better as a WorkItem but you may keep it as a User-Story ... However, I sincerely have some doubts that you can address it during the course of the first sprint (i.e., get it finished by end of November) ... I would go for replacing it by a set of Work-Items that you can tackle in subsequent Sprints ... Similar comment applies to some other User Stories ... P.G.: This is not modified (yet), none scheduled for Sprint ID 1.1.1. * Cloud Edge: * Is the FIWARE.Feature.I2ND.CE.HomeResourceAbstractionLayer Feature planned for the first minor release ? If so, please add the Release Id in the corresponding ticket on the tracker * What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... P.G.: Done some adjustments, maybe a consistency check will be required (people involved currently unavailable, traveling to Berlin, as tomorrow we have the I2ND meeting). * Network Information & Control: * You should replace "EPIC" by "Epic" in the Id of the FIWARE.EPIC.I2ND.NetIC.NetworkResourceControl entry. Unfortunately, you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page that corresponds to the backlog entry description) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker. P.G.: Done. * There are some tickets on the tracker (537, 795, 907, 908) which don't map any entry description on the Wiki and are not linked to Work Items ... Check if you have to delete them. P.G.: Done. * I miss the tickets linked to the two features listed on the Wiki. Apparently, one of them maps to a ticket on the tracker but that ticket doesn't follow the convention of using the entry id as the "summary" field of the ticket. Once you fix this and get the features, don't forget to declare what release they are planned for. P.G.: Done. * What do you plan to do in the first Sprint (scheduled to finish by end of November) ? Need to see some User-Stories or WorkItems planned ... P.G.: WorkItem inserted FIWARE.WorkItem.I2ND.General.AssetRevision to cope with all GEs in the chapter, scheduled for first Sprint. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 chris.woods at intel.com Tue Nov 15 09:02:25 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 15 Nov 2011 08:02:25 +0000 Subject: [Fiware-i2nd] FI-WARE Forge site certificate Errors Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2FCA5C@irsmsx503.ger.corp.intel.com> Hi Folks, Can we get the certificate on the FI-WARE site updated? - I'm having connectivity issues because of this. I believe that Intel's IT security does not allow me to access to FI-WARE site. The certificate used on the site appears to be out of date / untrusted / doesn't match the domain. Thanks, Chris [cid:image001.png at 01CCA36C.E9A03D50] ------------------------------------------------------------- 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.png Type: image/png Size: 261733 bytes Desc: image001.png URL: From pierangelo.garino at telecomitalia.it Tue Nov 15 15:24:31 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 15 Nov 2011 15:24:31 +0100 Subject: [Fiware-i2nd] Process Steps in I2ND Message-ID: Hi All, for those at the parallel sessions in Berlin, this is the link to the Process steps document: https://forge.fi-ware.eu/docman/view.php/10/593/Process_flow_wp7.docx 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 castrucci at dis.uniroma1.it Tue Nov 15 16:30:44 2011 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Tue, 15 Nov 2011 16:30:44 +0100 Subject: [Fiware-i2nd] T7.3 process flow Message-ID: <012901cca3ab$8aebb520$3137750a@cratr70> Dear T7.3 collegues, please find attached a presentation summarizing the discussion had today, following the process flow agreed at WP level. Tomorrow we can refine it and proceed with the discussion about the NetIC northbound interface design. Best regards 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: T7.3 process flow.ppt Type: application/vnd.ms-powerpoint Size: 595968 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Wed Nov 16 12:23:34 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 16 Nov 2011 12:23:34 +0100 Subject: [Fiware-i2nd] Draft slides for review Message-ID: https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v2.pptx ------------------------------------------------------------------ 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 jeanpierre.lerouzic at orange.com Wed Nov 16 12:35:28 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 16 Nov 2011 12:35:28 +0100 Subject: [Fiware-i2nd] Draft slides for review In-Reply-To: References: Message-ID: Hi all, Please is it possible to add a bullet in slide 12? Something like the line in red below: * It provides an extended interfacing for service platforms dynamically adapting their requirements to the packet core network * Service, Capability, Connectivity, and Control elements > Network Event Management > Resource Management (computation, QoS, ...) > Operator's Authentication, Authorisation, Accounting, Auditing and Charging > Connectivity Management > Network Context Data Management > API mediation * Based on 3GPP EPC architecture Otherwise I have no comments, please let me know if you need some input from Orange. 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? : mercredi 16 novembre 2011 12:24 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] Draft slides for review https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v2.pptx ------------------------------------------------------------------ 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. -------------- 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 Nov 16 14:30:50 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 16 Nov 2011 13:30:50 +0000 Subject: [Fiware-i2nd] Mind Map of All Epics in WP7 Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2FD06D@irsmsx503.ger.corp.intel.com> Folks, Please find attached a mind-map of all WP7 epics. Best viewed with FreeMind. Attached PDF for those without the application. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP7 Internal EPICS.mm Type: application/octet-stream Size: 20354 bytes Desc: WP7 Internal EPICS.mm URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP7 Internal EPICS.pdf Type: application/pdf Size: 1190072 bytes Desc: WP7 Internal EPICS.pdf URL: From chris.woods at intel.com Wed Nov 16 16:06:32 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 16 Nov 2011 15:06:32 +0000 Subject: [Fiware-i2nd] Could we ask for a timeline? Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B2FD10E@irsmsx503.ger.corp.intel.com> [cid:image003.png at 01CCA479.B4D81580] ------------------------------------------------------------- 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: oledata.mso Type: application/octet-stream Size: 157790 bytes Desc: oledata.mso URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 21435 bytes Desc: image003.png URL: From pierangelo.garino at telecomitalia.it Wed Nov 16 23:31:01 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 16 Nov 2011 23:31:01 +0100 Subject: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review References: <4EBBB0FA.3020007@tid.es> <4EC046E6.6020408@tid.es> Message-ID: FYI BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:30 A: 'Juanjo Hierro' Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review Dear Juanjo, please find attached the draft presentation for I2ND chapter. Best Regards 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: domenica 13 novembre 2011 23:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Draft agenda for the review Hi all, Please find enclosed the draft agenda of the first official review meeting that will take place on November 22nd in Brussels. As you see, we have booked a 30 mins presentation for each of the WPs linked to FI-WARE chapters. I would recommend that you prepare a maximum of 10-12 slides. I already provide some hints about how to structure these presentations last Friday. Don't hesitate to make any question or share any doubt you may have. A first complete draft of the presentation for your chapter is expected by EOB this Wednesday. Again, following is the index you should develop in your presentations (please follow the titles): * " Vision (/)" (follow the convention 1/3, 2/3, 3/3 on the title to distinguish among the several slides). These should be 3 slides to elaborate on the vision and the description of the most important GEs. * "Focus for the first release". This is one, maximum two slides elaborating on what you expect FI-WARE to deliver for the first major release (planned to be delivered by end of April 2012 and available on the FI-WARE testbed by end of July 2012. * "Response to comments by reviewers". These should be slides addressing reviewers' comments to their revision of the first release of the FI-WARE Product Vision deliverable (check my email also sent last Friday) Thomas: I would ask you to prepare a presentation about FI-WARE in the context of the FI-PPP (part of introduction timeslot at the beginning of the review). There, you have to elaborate on the relationship between UC projects in FI-WARE, how we are approaching the interaction with them, etc. Nuria: You have to prepare a few slides (3-4) on collaboration activities. They should align with contents of the report on Collaboration activities that Miguel has already asked you to complete on the Wiki (note there was a report on Collaboration activities deliverable that was due end of October) Matteo/Stephano: the presentation on developers tools will not contain a "response to comments by reviewers", therefore you may not need the 30 mins. Miguel: the slides reporting on resources consumption and whatever else may be relevant about the management report will go in the last timeslot. Best regards, -- Juanjo -------- Original Message -------- Subject: Draft agenda for the review Date: Thu, 10 Nov 2011 12:09:46 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Jose Jimenez , Miguel Carrillo , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find a proposed agenda for the review meeting on November 22nd Comments/feedback is welcome. Don't hesitate to ask any question you may have. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Nov 16 23:33:35 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 16 Nov 2011 23:33:35 +0100 Subject: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review References: <4EBBB0FA.3020007@tid.es> <4EC046E6.6020408@tid.es> Message-ID: Hi All, I have uploaded the latest version of slides at this link: https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v3.pptx BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:31 A: fiware-i2nd at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review FYI BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:30 A: 'Juanjo Hierro' Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review Dear Juanjo, please find attached the draft presentation for I2ND chapter. Best Regards 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: domenica 13 novembre 2011 23:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Draft agenda for the review Hi all, Please find enclosed the draft agenda of the first official review meeting that will take place on November 22nd in Brussels. As you see, we have booked a 30 mins presentation for each of the WPs linked to FI-WARE chapters. I would recommend that you prepare a maximum of 10-12 slides. I already provide some hints about how to structure these presentations last Friday. Don't hesitate to make any question or share any doubt you may have. A first complete draft of the presentation for your chapter is expected by EOB this Wednesday. Again, following is the index you should develop in your presentations (please follow the titles): * " Vision (/)" (follow the convention 1/3, 2/3, 3/3 on the title to distinguish among the several slides). These should be 3 slides to elaborate on the vision and the description of the most important GEs. * "Focus for the first release". This is one, maximum two slides elaborating on what you expect FI-WARE to deliver for the first major release (planned to be delivered by end of April 2012 and available on the FI-WARE testbed by end of July 2012. * "Response to comments by reviewers". These should be slides addressing reviewers' comments to their revision of the first release of the FI-WARE Product Vision deliverable (check my email also sent last Friday) Thomas: I would ask you to prepare a presentation about FI-WARE in the context of the FI-PPP (part of introduction timeslot at the beginning of the review). There, you have to elaborate on the relationship between UC projects in FI-WARE, how we are approaching the interaction with them, etc. Nuria: You have to prepare a few slides (3-4) on collaboration activities. They should align with contents of the report on Collaboration activities that Miguel has already asked you to complete on the Wiki (note there was a report on Collaboration activities deliverable that was due end of October) Matteo/Stephano: the presentation on developers tools will not contain a "response to comments by reviewers", therefore you may not need the 30 mins. Miguel: the slides reporting on resources consumption and whatever else may be relevant about the management report will go in the last timeslot. Best regards, -- Juanjo -------- Original Message -------- Subject: Draft agenda for the review Date: Thu, 10 Nov 2011 12:09:46 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Jose Jimenez , Miguel Carrillo , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find a proposed agenda for the review meeting on November 22nd Comments/feedback is welcome. Don't hesitate to ask any question you may have. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 jeanpierre.lerouzic at orange.com Thu Nov 17 09:38:13 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 17 Nov 2011 09:38:13 +0100 Subject: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review In-Reply-To: References: <4EBBB0FA.3020007@tid.es> <4EC046E6.6020408@tid.es> Message-ID: Hi Pier, Hans and all, The modification I proposed yesterday doesn't appear in this presentation. Do you have any opinion about it? 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? : mercredi 16 novembre 2011 23:34 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi All, I have uploaded the latest version of slides at this link: https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v3.pptx BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:31 A: fiware-i2nd at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review FYI BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:30 A: 'Juanjo Hierro' Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review Dear Juanjo, please find attached the draft presentation for I2ND chapter. Best Regards 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: domenica 13 novembre 2011 23:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Draft agenda for the review Hi all, Please find enclosed the draft agenda of the first official review meeting that will take place on November 22nd in Brussels. As you see, we have booked a 30 mins presentation for each of the WPs linked to FI-WARE chapters. I would recommend that you prepare a maximum of 10-12 slides. I already provide some hints about how to structure these presentations last Friday. Don't hesitate to make any question or share any doubt you may have. A first complete draft of the presentation for your chapter is expected by EOB this Wednesday. Again, following is the index you should develop in your presentations (please follow the titles): * " Vision (/)" (follow the convention 1/3, 2/3, 3/3 on the title to distinguish among the several slides). These should be 3 slides to elaborate on the vision and the description of the most important GEs. * "Focus for the first release". This is one, maximum two slides elaborating on what you expect FI-WARE to deliver for the first major release (planned to be delivered by end of April 2012 and available on the FI-WARE testbed by end of July 2012. * "Response to comments by reviewers". These should be slides addressing reviewers' comments to their revision of the first release of the FI-WARE Product Vision deliverable (check my email also sent last Friday) Thomas: I would ask you to prepare a presentation about FI-WARE in the context of the FI-PPP (part of introduction timeslot at the beginning of the review). There, you have to elaborate on the relationship between UC projects in FI-WARE, how we are approaching the interaction with them, etc. Nuria: You have to prepare a few slides (3-4) on collaboration activities. They should align with contents of the report on Collaboration activities that Miguel has already asked you to complete on the Wiki (note there was a report on Collaboration activities deliverable that was due end of October) Matteo/Stephano: the presentation on developers tools will not contain a "response to comments by reviewers", therefore you may not need the 30 mins. Miguel: the slides reporting on resources consumption and whatever else may be relevant about the management report will go in the last timeslot. Best regards, -- Juanjo -------- Original Message -------- Subject: Draft agenda for the review Date: Thu, 10 Nov 2011 12:09:46 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Jose Jimenez , Miguel Carrillo , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find a proposed agenda for the review meeting on November 22nd Comments/feedback is welcome. Don't hesitate to ask any question you may have. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Nov 17 09:59:02 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Nov 2011 09:59:02 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Fwd: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) In-Reply-To: <4EC46CA9.8010207@tid.es> References: <4EC466D2.5080102@tid.es> <4EC46CA9.8010207@tid.es> Message-ID: Hi All, here is the link to D2.2b, I'm going to send you also those pointing to other deliverables just submitted to EC. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 03:09 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) FYI. Feel free to share with your teams. Cheers, -- Juanjo -------- Original Message -------- Subject: Submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) Date: Thu, 17 Nov 2011 02:43:46 +0100 From: JUAN JOSE HIERRO SUREDA To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , rdifrancesco at ymail.com , bel.piet1 at gmail.com CC: FI-WARE project EC mailbox , JOSE JIMENEZ DELGADO , MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA Dear PO and FI-WARE project reviewers, This is the official submission of deliverable D.2.2.b FI-WARE High-level Description (Product Vision) deliverable of the FI-WARE project. You can download a .pdf version of this deliverable at: https://forge.fi-ware.eu/docman/view.php/7/624/FI-WARE+High-level+Description+Product+Vision+11-11-16.pdf The FI-WARE High-level Description (Product Vision) is a living document, constantly updated on the public Wiki of the FI-WARE project (http://wiki.fi-ware.eu). You can always get access it on line at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision The submitted D.2.2.b deliverable indeed correspond to a snapshot of the contents of the FI-WARE High-level Description (Product Vision) available on the Wiki. This snapshot has been produced using standard extensions of MediaWiki enabling to generate .pdf books from MediaWiki-based Wiki contents. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 pierangelo.garino at telecomitalia.it Thu Nov 17 09:59:18 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Nov 2011 09:59:18 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.12.2.a Report on Communication and Dissemination activities In-Reply-To: <4EC46CBD.7090908@tid.es> References: <4EC46A1A.8060100@tid.es> <4EC46CBD.7090908@tid.es> Message-ID: As said... Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 03:09 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.12.2.a Report on Communication and Dissemination activities FYI. Feel free to share with your teams. Cheers, -- Juanjo -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.12.2.a Report on Communication and Dissemination activities Date: Thu, 17 Nov 2011 02:57:46 +0100 From: JUAN JOSE HIERRO SUREDA To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , rdifrancesco at ymail.com , bel.piet1 at gmail.com CC: FI-WARE project EC mailbox , JOSE JIMENEZ DELGADO , MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA Dear PO and FI-WARE project reviewers, This is the official submission of FI-WARE deliverable D.12.2.a Report on Communication and Dissemination activities. You can download a .pdf version of this deliverable at: * https://forge.fi-ware.eu/docman/view.php/7/625/D.12.2.a+Communication_Dissemination_Report.pdf This deliverable is a living document, constantly updated on the public Wiki of the FI-WARE project (http://wiki.fi-ware.eu). You can always get access it on line at: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Communication_activities * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Dissemination_activities The submitted D.12.2.a deliverable indeed correspond to a snapshot of the contents of the contents available on the Wiki. This snapshot has been produced using standard extensions of MediaWiki enabling to generate .pdf books from MediaWiki-based Wiki contents. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 pierangelo.garino at telecomitalia.it Thu Nov 17 09:59:33 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Nov 2011 09:59:33 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.12.3.a Report on Collaboration activities In-Reply-To: <4EC46CE0.8070702@tid.es> References: <4EC46BE7.30002@tid.es> <4EC46CE0.8070702@tid.es> Message-ID: As said n. 3... Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 03:10 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.12.3.a Report on Collaboration activities FYI. Feel free to share with your teams. Cheers, -- Juanjo -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.12.3.a Report on Collaboration activities Date: Thu, 17 Nov 2011 03:05:27 +0100 From: JUAN JOSE HIERRO SUREDA To: Arian.ZWEGERS at ec.europa.eu , dgr at whitestein.com , msli at icfocus.co.uk , rdifrancesco at ymail.com , bel.piet1 at gmail.com CC: FI-WARE project EC mailbox , JOSE JIMENEZ DELGADO , MIGUEL CARRILLO PACHECO , JUAN JOSE HIERRO SUREDA Dear PO and FI-WARE project reviewers, This is the official submission of FI-WARE deliverable D.12.3.a Report on Collaboration activities. You can download a .pdf version of this deliverable at: * https://forge.fi-ware.eu/docman/view.php/7/626/D.12.3.a+Collaboration+Report.pdf This deliverable is a living document, constantly updated on the public Wiki of the FI-WARE project (http://wiki.fi-ware.eu). You can always get access it on line at: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities The submitted D.12.3.a deliverable indeed corresponds to a snapshot of the contents available on the Wiki. This snapshot has been produced using standard extensions of MediaWiki enabling to generate .pdf books from MediaWiki-based Wiki contents. Best regards, Juanjo Hierro Chief Architect & Technical Manager FI-WARE project www.fi-ware.eu ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 pierangelo.garino at telecomitalia.it Thu Nov 17 15:40:28 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Nov 2011 15:40:28 +0100 Subject: [Fiware-i2nd] R: R: [Fiware-wpl] Fwd: Draft agenda for the review In-Reply-To: References: <4EBBB0FA.3020007@tid.es> <4EC046E6.6020408@tid.es> Message-ID: Hi Jean-Pierre, yes we didn't insert it just because we didn't catch your mail (too many unread mails yesterday during the meeting to have time to look at all of them :( We'll keep your modification into account for the updates. I'm aware that yesterday, during the T7.4 session, there were some unclear point about the API_mediation asset: it would be better if you can discuss this with Hans, Marius and the other people of the task before proceeding with the modification. BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: gioved? 17 novembre 2011 09:38 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi Pier, Hans and all, The modification I proposed yesterday doesn't appear in this presentation. Do you have any opinion about it? 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? : mercredi 16 novembre 2011 23:34 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi All, I have uploaded the latest version of slides at this link: https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v3.pptx BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:31 A: fiware-i2nd at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review FYI BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:30 A: 'Juanjo Hierro' Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review Dear Juanjo, please find attached the draft presentation for I2ND chapter. Best Regards 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: domenica 13 novembre 2011 23:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Draft agenda for the review Hi all, Please find enclosed the draft agenda of the first official review meeting that will take place on November 22nd in Brussels. As you see, we have booked a 30 mins presentation for each of the WPs linked to FI-WARE chapters. I would recommend that you prepare a maximum of 10-12 slides. I already provide some hints about how to structure these presentations last Friday. Don't hesitate to make any question or share any doubt you may have. A first complete draft of the presentation for your chapter is expected by EOB this Wednesday. Again, following is the index you should develop in your presentations (please follow the titles): * " Vision (/)" (follow the convention 1/3, 2/3, 3/3 on the title to distinguish among the several slides). These should be 3 slides to elaborate on the vision and the description of the most important GEs. * "Focus for the first release". This is one, maximum two slides elaborating on what you expect FI-WARE to deliver for the first major release (planned to be delivered by end of April 2012 and available on the FI-WARE testbed by end of July 2012. * "Response to comments by reviewers". These should be slides addressing reviewers' comments to their revision of the first release of the FI-WARE Product Vision deliverable (check my email also sent last Friday) Thomas: I would ask you to prepare a presentation about FI-WARE in the context of the FI-PPP (part of introduction timeslot at the beginning of the review). There, you have to elaborate on the relationship between UC projects in FI-WARE, how we are approaching the interaction with them, etc. Nuria: You have to prepare a few slides (3-4) on collaboration activities. They should align with contents of the report on Collaboration activities that Miguel has already asked you to complete on the Wiki (note there was a report on Collaboration activities deliverable that was due end of October) Matteo/Stephano: the presentation on developers tools will not contain a "response to comments by reviewers", therefore you may not need the 30 mins. Miguel: the slides reporting on resources consumption and whatever else may be relevant about the management report will go in the last timeslot. Best regards, -- Juanjo -------- Original Message -------- Subject: Draft agenda for the review Date: Thu, 10 Nov 2011 12:09:46 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Jose Jimenez , Miguel Carrillo , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find a proposed agenda for the review meeting on November 22nd Comments/feedback is welcome. Don't hesitate to ask any question you may have. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 01CCA53F.3B7DE1D0]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 Thu Nov 17 15:46:28 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 17 Nov 2011 15:46:28 +0100 Subject: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review In-Reply-To: References: <4EBBB0FA.3020007@tid.es> <4EC046E6.6020408@tid.es> Message-ID: Hi Pier and all, I understand. You can call me anytime today at +33 2 99 12 48 93 except after 17h or tomorrow except between 14 and 15h. Or if you prefer you can send me a couple of questions by email to give me some time to think about it and we book a phone conference at a convenient time. Best regards, Jean-Pierre De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoy? : jeudi 17 novembre 2011 15:40 ? : LE ROUZIC Jean-Pierre RD-MAPS-REN Cc : Hans.Einsiedler at telekom.de; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Henrik Abramowicz (henrik.abramowicz at ericsson.com); fiware-i2nd at lists.fi-ware.eu Objet : R: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi Jean-Pierre, yes we didn't insert it just because we didn't catch your mail (too many unread mails yesterday during the meeting to have time to look at all of them L We'll keep your modification into account for the updates. I'm aware that yesterday, during the T7.4 session, there were some unclear point about the API_mediation asset: it would be better if you can discuss this with Hans, Marius and the other people of the task before proceeding with the modification. BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: gioved? 17 novembre 2011 09:38 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi Pier, Hans and all, The modification I proposed yesterday doesn't appear in this presentation. Do you have any opinion about it? 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? : mercredi 16 novembre 2011 23:34 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: [Fiware-wpl] Fwd: Draft agenda for the review Hi All, I have uploaded the latest version of slides at this link: https://forge.fi-ware.eu/docman/view.php/10/615/FI-WARE_review_WP7-v3.pptx BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:31 A: fiware-i2nd at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review FYI BR Pier Da: Garino Pierangelo Inviato: mercoled? 16 novembre 2011 23:30 A: 'Juanjo Hierro' Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: R: [Fiware-wpl] Fwd: Draft agenda for the review Dear Juanjo, please find attached the draft presentation for I2ND chapter. Best Regards 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: domenica 13 novembre 2011 23:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Fwd: Draft agenda for the review Hi all, Please find enclosed the draft agenda of the first official review meeting that will take place on November 22nd in Brussels. As you see, we have booked a 30 mins presentation for each of the WPs linked to FI-WARE chapters. I would recommend that you prepare a maximum of 10-12 slides. I already provide some hints about how to structure these presentations last Friday. Don't hesitate to make any question or share any doubt you may have. A first complete draft of the presentation for your chapter is expected by EOB this Wednesday. Again, following is the index you should develop in your presentations (please follow the titles): * " Vision (/)" (follow the convention 1/3, 2/3, 3/3 on the title to distinguish among the several slides). These should be 3 slides to elaborate on the vision and the description of the most important GEs. * "Focus for the first release". This is one, maximum two slides elaborating on what you expect FI-WARE to deliver for the first major release (planned to be delivered by end of April 2012 and available on the FI-WARE testbed by end of July 2012. * "Response to comments by reviewers". These should be slides addressing reviewers' comments to their revision of the first release of the FI-WARE Product Vision deliverable (check my email also sent last Friday) Thomas: I would ask you to prepare a presentation about FI-WARE in the context of the FI-PPP (part of introduction timeslot at the beginning of the review). There, you have to elaborate on the relationship between UC projects in FI-WARE, how we are approaching the interaction with them, etc. Nuria: You have to prepare a few slides (3-4) on collaboration activities. They should align with contents of the report on Collaboration activities that Miguel has already asked you to complete on the Wiki (note there was a report on Collaboration activities deliverable that was due end of October) Matteo/Stephano: the presentation on developers tools will not contain a "response to comments by reviewers", therefore you may not need the 30 mins. Miguel: the slides reporting on resources consumption and whatever else may be relevant about the management report will go in the last timeslot. Best regards, -- Juanjo -------- Original Message -------- Subject: Draft agenda for the review Date: Thu, 10 Nov 2011 12:09:46 +0100 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu CC: Jose Jimenez , Miguel Carrillo , CARLOS RALLI UCENDO , "jhierro >> \"Juan J. Hierro\"" Hi Arian, Please find a proposed agenda for the review meeting on November 22nd Comments/feedback is welcome. Don't hesitate to ask any question you may have. Best regards, -- Juanjo Hierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 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 Nov 17 18:01:43 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Nov 2011 18:01:43 +0100 Subject: [Fiware-i2nd] Berlin Meeting- My notes Message-ID: Dear All, Today it was nearly impossible for me surviving to the mail flooding of the last couple of days. I couldn't draft an effective minute of the meeting we had (I thank you all again for attending, I always find them very productive!). So I decided to just clean up a little bit my notes, and to send them to you just to report a list of actions we agreed (no dates defined, but we should try and be very rapid in tackling them). Hope you can understand what I wrote, on the other hand if you have more details and want to add them, or correct mistakes, please do it and recirculate, thanks. 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: I2ND_Berlin_Meeting_Notes_2011_11_15-16.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 22588 bytes Desc: I2ND_Berlin_Meeting_Notes_2011_11_15-16.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 pierangelo.garino at telecomitalia.it Fri Nov 18 10:19:33 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 18 Nov 2011 10:19:33 +0100 Subject: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Message-ID: Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) - Slides 2 to 5: check that I didn't make any error with my small modifications - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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 -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review I2ND 11-11-18.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 595411 bytes Desc: FI-WARE M6 Review I2ND 11-11-18.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review chapter-template 11-11-17.ppt Type: application/vnd.ms-powerpoint Size: 708096 bytes Desc: FI-WARE M6 Review chapter-template 11-11-17.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 Klaus.Wuenstel at alcatel-lucent.com Fri Nov 18 13:10:46 2011 From: Klaus.Wuenstel at alcatel-lucent.com (WUENSTEL, Klaus) Date: Fri, 18 Nov 2011 13:10:46 +0100 Subject: [Fiware-i2nd] Proposed modifications: URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: A References: A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0693ABDC@SLFSNX.rcs.alcatel-research.de> Dear Pier, attached please find some modifications in the slides (marked in red) which Thomas and I consider as important for transfering our messages. Best regards Klaus ________________________________ 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, 18. November 2011 10:20 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) - Slides 2 to 5: check that I didn't make any error with my small modifications - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks J BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE_M6_Review_I2ND_11-11-18_ALUD.pptx Type: application/octet-stream Size: 577411 bytes Desc: FI-WARE_M6_Review_I2ND_11-11-18_ALUD.pptx URL: From pierangelo.garino at telecomitalia.it Fri Nov 18 15:13:50 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 18 Nov 2011 15:13:50 +0100 Subject: [Fiware-i2nd] R: Proposed modifications: URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0693ABDC@SLFSNX.rcs.alcatel-research.de> References: A <133D9897FB9C5E4E9DF2779DC91E947C0693ABDC@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi Klaus and Thomas, thanks, I included your modifications, just two minor changes in: - slide 1: I2ND addresses intelligent connectivity (I2ND added) - you also commented on slide 13: I rephrased in this way 'FI-WARE services are usually provided through...' BR Pier P.S.: Please other Partners to provide their update, I have been already asked to contribute the slides.... Da: WUENSTEL, Klaus [mailto:Klaus.Wuenstel at alcatel-lucent.com] Inviato: venerd? 18 novembre 2011 13:11 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; BANNIZA, Thomas-Rolf Oggetto: Proposed modifications: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear Pier, attached please find some modifications in the slides (marked in red) which Thomas and I consider as important for transfering our messages. Best regards Klaus ________________________________ 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, 18. November 2011 10:20 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) - Slides 2 to 5: check that I didn't make any error with my small modifications - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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 01CCA604.AD0ECC90]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 serge.defrance at technicolor.com Fri Nov 18 15:30:35 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Fri, 18 Nov 2011 15:30:35 +0100 Subject: [Fiware-i2nd] R: Proposed modifications: URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: References: A <133D9897FB9C5E4E9DF2779DC91E947C0693ABDC@SLFSNX.rcs.alcatel-research.de> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01235ADCBC@MOPESMBX01.eu.thmulti.com> Pier, No comment from our side. Good luck for Tuesday. Cheers, 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: vendredi 18 novembre 2011 15:14 To: WUENSTEL, Klaus Cc: BANNIZA, Thomas-Rolf; fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Proposed modifications: URGENT (DEALINE TODAY!): UPDATE to Slides for the review Hi Klaus and Thomas, thanks, I included your modifications, just two minor changes in: - slide 1: I2ND addresses intelligent connectivity (I2ND added) - you also commented on slide 13: I rephrased in this way 'FI-WARE services are usually provided through...' BR Pier P.S.: Please other Partners to provide their update, I have been already asked to contribute the slides.... Da: WUENSTEL, Klaus [mailto:Klaus.Wuenstel at alcatel-lucent.com] Inviato: venerd? 18 novembre 2011 13:11 A: Garino Pierangelo Cc: fiware-i2nd at lists.fi-ware.eu; BANNIZA, Thomas-Rolf Oggetto: Proposed modifications: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear Pier, attached please find some modifications in the slides (marked in red) which Thomas and I consider as important for transfering our messages. Best regards Klaus ________________________________ 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, 18. November 2011 10:20 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) - Slides 2 to 5: check that I didn't make any error with my small modifications - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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 01CCA607.045DCDA0]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 01CCA607.045DCDA0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Fri Nov 18 16:18:02 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 18 Nov 2011 16:18:02 +0100 Subject: [Fiware-i2nd] R: URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: References: Message-ID: Hi All, Many thanks to those who sent revisions, I just sent the latest updated version of slides to Juanjo (attached). Please notice that I mentioned we'll provide some entry about Open calls by early Monday, when we are at the rehearsal meeting in Brussels, so please continue to evaluate this aspects and send me your contribution by then. Have a nice week-end! Pier P.S.: I forgot the assets slide, now it's in! Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di Garino Pierangelo Inviato: venerd? 18 novembre 2011 10:20 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) - Slides 2 to 5: check that I didn't make any error with my small modifications - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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 01CCA60D.A57C3C70]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 M6 Review I2ND 11-11-18.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 601227 bytes Desc: FI-WARE M6 Review I2ND 11-11-18.pptx 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 Nov 18 17:07:03 2011 From: chris.woods at intel.com (Woods, Chris) Date: Fri, 18 Nov 2011 16:07:03 +0000 Subject: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: References: Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B344ADE@irsmsx503.ger.corp.intel.com> Hi Pier, Some updates included in the slide deck. See below and attached for details. 6 minutes late! - sorry, 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: Friday, November 18, 2011 9:20 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) Suggestion: Enabling new FI-WARE end user experiences and supporting future internet development, by providing application specific intelligent connectivity via openly specified interfaces. - Slides 2 to 5: check that I didn't make any error with my small modifications Slide 2 [cid:image002.png at 01CCA60B.2FEF8860] - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. [cid:image003.png at 01CCA60C.1CA53830] - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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 01CCA60A.C71E5780]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: image002.png Type: image/png Size: 32506 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 26855 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE M6 Review I2ND 11-11-18(woods).pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 595649 bytes Desc: FI-WARE M6 Review I2ND 11-11-18(woods).pptx 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 Fri Nov 18 21:52:12 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 18 Nov 2011 21:52:12 +0100 Subject: [Fiware-i2nd] R: URGENT (DEALINE TODAY!): UPDATE to Slides for the review In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B344ADE@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B344ADE@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris, Thanks, every refinement is worth until Monday ;-) I have included most of your suggestions, I just considered the following to be kept for next period: - Slide 1: changed the sentence in the blue box (But I'll 'weight' it against the other... what is the opinion of other partners?) - Slide 2: rearrangement ok - Slide 9: Webinos interaction removed (we aren't yet formally 'linked') and 'Additional assets required to meet core functionality' removed, unless we are able to specify the gaps to be proposed in Open calls (otherwise it would be a little bit contradictory). Have a nice week-end! BR Pier Da: Woods, Chris [mailto:chris.woods at intel.com] Inviato: venerd? 18 novembre 2011 17:07 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Hi Pier, Some updates included in the slide deck. See below and attached for details. 6 minutes late! - sorry, 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: Friday, November 18, 2011 9:20 AM To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] URGENT (DEALINE TODAY!): UPDATE to Slides for the review Dear All, the creation process for the review meeting slides is progressing, and we are asked to make further refinements to our slides. Please find attached an update which comply with the latest template received (also the template is attached, in case you want to check it; please read the Notes associated to slides). You'll see that most of our work was already well in line with that template, except some important modifications. There are in particular a few points which absolutely need your contribution, along with revision of other contents; here are the main issues: - Slide 1: please review the light blue box text, and possibly improve it (it should be a motto) Suggestion: Enabling new FI-WARE end user experiences and supporting future internet development, by providing application specific intelligent connectivity via openly specified interfaces. - Slides 2 to 5: check that I didn't make any error with my small modifications Slide 2 [cid:image002.png at 01CCA63B.430F01C0] - Slide 6: not changed so far (revise it anyway) - Slide 7: just changed the graphical format - Slide 8: we discussed open calls issue, and we know it's really difficult for us to provide an input now. Maybe this slide will not be used, but try anyway to provide some input, just in case it is absolutely necessary. - Slide 9: Most important one to be revised: I attempted to get some 'highs' and 'lows' + challenges and lessons learned by the achievmenet slides we produced (which are now left as backup only): please add new, and/or revise old, contributions. [cid:image003.png at 01CCA63B.430F01C0] - Slide 10: not sure it must be customized for I2ND (there was another one more general in the template I got), however just in case it is necessary, I have provided some inputs (taken from our previous 'Conclusions' slide) Please revise carefully the whole slide set, + make the necessary updates as required above, and send to me NO LATER THAN 17:00 CET, thanks :) BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 17 novembre 2011 19:19 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] URGENT: Slides for the review (status and more detailed template) Hi all, Only 3 of you (as far as I know) have sent to me their slides for the review. This scares me a bit and I would kindly ask you to take the necessary actions. A concern, once I have reviewed the presentations you sent is that you didn't follow that much my guidelines. We should try to look coordinated, and nothing better than showing slides that look like such coordination indeed took place. Probably I didn't give too much details in a first shot, so therefore I have prepared a revised version of the template slides with more detailed guidelines (including notes for each slide) you MUST follow. I have added a few bits of what some of the WPLs who sent to me a first draft added to the script I provided. I believe now we will have something rather complete. Please follow the template and, if there is something that you feel would be hard to develop for your particular chapter, please let me know and we will discuss it. I expect to see a rather elaborated draft version of your slides by EOB tomorrow. Please send your presentation: * Using a file name for your .ppt with the form: "FI-WARE M6 Review 11-11-.ppt" * In Re: to this email Best 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:image004.gif at 01CCA63B.430F01C0]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: image002.png Type: image/png Size: 32506 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 26855 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.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 Mon Nov 21 16:57:41 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 21 Nov 2011 16:57:41 +0100 Subject: [Fiware-i2nd] Review: Slides for I2ND chapter after rehearsal Message-ID: Dear All, here are the I2ND slides revised during the rehearsal, including the slide about Open Calls (to be checked/agreed). 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: FI-WARE M6 Review I2ND 11-11-21.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 592485 bytes Desc: FI-WARE M6 Review I2ND 11-11-21.pptx 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 Nov 23 10:08:58 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 23 Nov 2011 10:08:58 +0100 Subject: [Fiware-i2nd] I2ND confcall today cancelled + First Review Meeting early results Message-ID: Dear All, due to the fact we had the I2ND meeting last week, Hans is not available and I'm just back from the review meeting, you may have noticed that the I2ND periodic call has not been proposed today. I assume the actions defined there are being addressed and I expect they are completed asap. I take also the opportunity to let you know that the review meeting yesterday has been successful: the work we are doing has been appreciated by the reviewing panel, although they expect that, due to the nature, amount of efforts and funds in the project, we do not simply make it a good FP7 project but rather an outstanding project, and all participants have to commit to this. Later I'll provide you more info on the outcomes. 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 Nov 23 10:53:20 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 23 Nov 2011 09:53:20 +0000 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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: wp4wp7overlap-study.mm Type: application/octet-stream Size: 47615 bytes Desc: wp4wp7overlap-study.mm URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP4 and WP7 Overlaps.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 29592 bytes Desc: WP4 and WP7 Overlaps.docx URL: From jeanpierre.lerouzic at orange.com Wed Nov 23 11:20:59 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Wed, 23 Nov 2011 11:20:59 +0100 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Message-ID: Hi Chris and all, Thanks for the effort, it's not a small work. Here are three comments. (1) I think there is also some overlap between WP7 and WP8: * Epic Device Connectivity "As a FI-Ware application developer I need to ensure a great user experience by having access to information about and control of device connectivity" * User Profile "As connected device application user I want to access to my applications through secure and easy to use identification and authentication procedures, and with consistent privacy policies supported. * Subscriber Privacy Protection" "As a FI-Ware provider I have to ensure that users of my platform can trust the FI-Ware platform and the applications which run on and within that platform" (2) IMO there is certainly an overlap between technologies such as Openstack/Quantum or OpenSwitch in one hand and WP7.3 (NetIc) in the other hand, but not with WP7.4 (S3C). (3) OpenStack Keystone IMO is related to WP8, not WP7 as it's an identity service similar to the WP8 Identity enabler. Furthermore I think WP4 misunderstood some security or even basic management aspects when it wrote sentences like "In order to manage access and role-based rights of cloud resources (e.g. SSO, RBAC), I as the end user require an API to manipulate these aspects in a automated fashion." It's only my opinion. 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 23 novembre 2011 10:53 ? : fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 chris.woods at intel.com Wed Nov 23 15:27:40 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 23 Nov 2011 14:27:40 +0000 Subject: [Fiware-i2nd] Available for meeting in Stuttgart 7-8th Feb 2012 Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B3456F5@irsmsx503.ger.corp.intel.com> Hi Pier, Just a note to confirm that, yes, I am available to meet in Stuttgart on the 7th -8th of Feb. I hope this works for everyone else too? 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.defrance at technicolor.com Thu Nov 24 10:27:43 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 24 Nov 2011 10:27:43 +0100 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Hi Chris, Regarding the section of your document < WP4 and WP7 overlaps > devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 chris.woods at intel.com Thu Nov 24 16:49:21 2011 From: chris.woods at intel.com (Woods, Chris) Date: Thu, 24 Nov 2011 15:49:21 +0000 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: <187F4CC97FD0B6488FAE608A8038FF143B39585F@irsmsx503.ger.corp.intel.com> Hi Serge, + Adding Wolfgang Great feedback! - Could you update the document on the Forge site(Wp4 and wp7 overlaps.docx), to remove any erroneous overlaps wrt cloud edge? I would appreciate your insights on the following questions - I'm not sure I completely understand your thinking especially on the security issues. Question: What security mechanism will the cloud proxy apply to ensure that 3rd party code running on the proxy doesn't access resources for which it does not have permission? e.g. how does the developer of a proxy application signal that the proxy application needs access to users shared hard drives? How does the user (consumer) accept this request? OR user's remote control device? What happens if the app turns out to be bad? How does the user (consumer or a network operator) black list the app or limit it's capabilities? Question: Is there an overlap with RBAC? Or Security.Network? Question: Will the developer of the could proxy need to learn a new security framework for the proxy? Question: Can the developer of the could proxy use the same API and security structure used in the cloud? I see large overlaps across Cloud Proxy, CDI, WP4, and WP8 on these topics? Having a unified vision for security would be compelling from a security POV (presenting a unified security interface), from a developer adoption and convince POV, and from a resources POV, having a streamlined set of security requirements will aid development time. Chris From: Defrance Serge [mailto:serge.defrance at technicolor.com] Sent: Thursday, November 24, 2011 9:28 AM To: Woods, Chris; fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: RE: WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document < WP4 and WP7 overlaps > devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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. ------------------------------------------------------------- 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 jeanpierre.lerouzic at orange.com Fri Nov 25 10:34:39 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Fri, 25 Nov 2011 10:34:39 +0100 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: Hi all, Serge, If I understand correctly the cloud proxy concept, it means that: ? From the point of view of the home devices, all services are accessed through the cloud proxy which unifies the services interfaces (hence the name cloud proxy). ? From the point of view of services the cloud proxy, doesn't unify the home devices. At a technical level, I understood during the WP7 session in Turin that the Cloud proxy, is a kind of bare metal OS that executes applications in the form of light VMs. Cloud applications would download those light VMs on the bare metal OS which would run them. The rationale being that broadband connection may be sometimes slow and it's better to execute applications locally. I think that in WP4 EPICS you use the word "network" more with the meaning of a computer network interface (Ethernet and so on), than a Telecom network. This is IMO well described in one of WP4 EPIC: FIWARE.Epic.Cloud.ResourceManager.Network , especially the mention of L2/L3. But if we decide than computers are not permanently connected through their network interfaces (which is suggested by the whole concept of a "cloud proxy"), the difference between a computer network and a telecom network is quite blurred IMO as you will have to introduce connection protocols (like PPP over xyz). It seems to me that there is in WP4 a collision course between two network notions. My own understanding of OpenStack Quantum is that it deals with virtual NIC which in my opinion doesn't align well with the "cloud proxy" concept which is more about application running on devices (but not as native applications). If the WP4 "cloud proxy" is it about virtualized local applications then what Chris suggested as overlap seems to me correct, or the WP4 "cloud proxy" is about virtualized NICs (L2/L3) which is a different topic where I agree there is not much overlap with WP7 network API EPICS. If my understanding happens to be correct I think it would be nice to: ? Have a project agreement on vocabulary and concepts (what is a network?) ? Have a project policy to reduce the usage of overloaded concepts (for ex: "user", when there are many kind of users as you rightly suggested). ? Try to clarify what the "cloud proxy" is about (is it about virtualized local applications or is it about virtualized NIC?) 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 Defrance Serge Envoy? : jeudi 24 novembre 2011 10:28 ? : Woods, Chris; fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : Re: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document ? WP4 and WP7 overlaps ? devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 serge.defrance at technicolor.com Fri Nov 25 14:00:55 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Fri, 25 Nov 2011 14:00:55 +0100 Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics In-Reply-To: References: <187F4CC97FD0B6488FAE608A8038FF143B345560@irsmsx503.ger.corp.intel.com> <453EEB4CD4162742B6EF3D3F84E88A6E012375A925@MOPESMBX01.eu.thmulti.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E012833D63A@MOPESMBX01.eu.thmulti.com> Hi Jean Pierre, The cloud proxy is a device located at the boundary between the private home network and the cloud (public network). It may offer assistance to home devices to access cloud services (not mandatory, home devices can still directly access to cloud services), like data caching when uploading a big amount of data. The cloud proxy is unique, WP7 "cloud proxy" and WP4 "cloud proxy" is the same device. The reason of the split between WP4 and WP7 is that some functions of the cloud proxy may more relate to - one hand to cloud functions like the API (and associated functional in the cloud proxy) used by a cloud application to authenticate to the cloud proxy and download code to be executed on the cloud proxy (WP4), - and on the other hand to network and devices interfaces like a kind of a SDK that the downloaded code may use to access home network resources (resources located in the home as storage or simple devices). Presently, we (Technicolor) do not consider the cloud proxy as part of the cloud, but more as a particular device (a super gateway) which is almost always present (cloud application may rely on) and which offer standardized APIs. Virtualisation on the cloud proxy is mainly for the sake of isolation between processes which are executed on it, as far as some code may be downloaded from the cloud from more or less trustworthy sources. I hope this help to a better understanding. However, I may have missed some of your points. Cheers, Serge. From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: vendredi 25 novembre 2011 10:35 To: Defrance Serge; chris.woods at intel.com Cc: fiware-cloud at lists.fi-ware.eu; fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi all, Serge, If I understand correctly the cloud proxy concept, it means that: ? From the point of view of the home devices, all services are accessed through the cloud proxy which unifies the services interfaces (hence the name cloud proxy). ? From the point of view of services the cloud proxy, doesn't unify the home devices. At a technical level, I understood during the WP7 session in Turin that the Cloud proxy, is a kind of bare metal OS that executes applications in the form of light VMs. Cloud applications would download those light VMs on the bare metal OS which would run them. The rationale being that broadband connection may be sometimes slow and it's better to execute applications locally. I think that in WP4 EPICS you use the word "network" more with the meaning of a computer network interface (Ethernet and so on), than a Telecom network. This is IMO well described in one of WP4 EPIC: FIWARE.Epic.Cloud.ResourceManager.Network, especially the mention of L2/L3. But if we decide than computers are not permanently connected through their network interfaces (which is suggested by the whole concept of a "cloud proxy"), the difference between a computer network and a telecom network is quite blurred IMO as you will have to introduce connection protocols (like PPP over xyz). It seems to me that there is in WP4 a collision course between two network notions. My own understanding of OpenStack Quantum is that it deals with virtual NIC which in my opinion doesn't align well with the "cloud proxy" concept which is more about application running on devices (but not as native applications). If the WP4 "cloud proxy" is it about virtualized local applications then what Chris suggested as overlap seems to me correct, or the WP4 "cloud proxy" is about virtualized NICs (L2/L3) which is a different topic where I agree there is not much overlap with WP7 network API EPICS. If my understanding happens to be correct I think it would be nice to: ? Have a project agreement on vocabulary and concepts (what is a network?) ? Have a project policy to reduce the usage of overloaded concepts (for ex: "user", when there are many kind of users as you rightly suggested). ? Try to clarify what the "cloud proxy" is about (is it about virtualized local applications or is it about virtualized NIC?) 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 Defrance Serge Envoy? : jeudi 24 novembre 2011 10:28 ? : Woods, Chris; fiware-i2nd Cc : fiware-cloud at lists.fi-ware.eu Objet : Re: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hi Chris, Regarding the section of your document ? WP4 and WP7 overlaps ? devoted to cloud edge, I think there is a misunderstanding. You first mention the epic "Home system modeling" for WP7 and in front many WP4 epics related to the cloud resource management. The WP7 epic relates to resources which are located inside the home system. They are made of a collection of some devices for which the cloud proxy will behave as a kind of aggregator. It is a tentative to unify the access to home system resources through the cloud proxy. But the home system is not considered (or managed) by the cloud proxy as a cloud : the cloud proxy considers each device as unique, offering specific resources. In addition, the word "user" may have two different significations, either meaning cloud user (I understand application provider) or, in the context of the cloud proxy, end user (I understand application consumer). Consequently, to my opinion, there is no overlapping between the WP7 epic "home system modeling" and the WP4 epic you mention. Concerning the WP7 epic "Other drivers", this concerns the potential access to devices inside the home system. The cloud proxy may need a specific driver for accessing a specific resource (hard disk, wireless keyboard, remote controller,... ). The three first epics you mention from WP4 are also part of the cloud proxy : "Service Platform Provider" is the interface with cloud application so that they can authenticate and execute a code on the cloud proxy, "Virtual system environment" realizes on the cloud proxy the necessary execution environment isolation for different codes downloaded on the cloud proxy by different cloud applications. "Local Resource Monitoring" is an interface with cloud application to report on cloud proxy status and capabilities. To my opinion, there is no overlap with the WP7 epic. You also mention some epics related to security in the cloud. I do not see overlap neither with our WP7 epic, although I agree that, some security functions may also concern the "Service Platform Provider" epic (WP4 internal overlapping in this case). Hoping my comments help, Cheers, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 23 novembre 2011 10:53 To: fiware-i2nd Cc: fiware-cloud at lists.fi-ware.eu Subject: [Fiware-i2nd] WP4 WP7 - Overlapping Epics Hello Folks, Please find attached, and on the Forge site two key documents which describe epics which may overlap between WP4 and WP7. The "WP4 and WP7 Overlaps.docx" is the key document to review. My self (WP7) and Andrew Edmonds (WP4) conducted the overlap study and prepared the initial documents attached. As a courtesy I wanted to share these findings with the WP4 team as well. This work was done initially as an internal WP7 task. It aims to aid all WP7 participants in identifying similar or overlapping functionality / requirements within WP4, and helping to pro-actively provoke discussion between the related team members. These documents aim to highlight possible overlaps - they do not mandate that overlaps must occur. Their main purpose is simply to provoke discussion and requirement sharing between WP4 and WP7, so that any cross dependencies / requirements / functionality could be discussed and highlighted at an early stage. I hope you'll find these documents useful. Attached & Forge Link Wp4 and wp7 overlaps.docx This document outlines the Epics in WP4 and WP7 which may be related. The document aims to provide all members of WP7 with an initial assessment of potential overlaps. It is the responsibility of each of the tasks to follow up with their colleagues in WP4 Wp4wp7overlap-study.mm Working document (Mind-Map) showing related Epics between WP4 and WP7 Chris Woods ------------------------------------------------------------- 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 andi at dis.uniroma1.it Tue Nov 29 14:34:58 2011 From: andi at dis.uniroma1.it (Andi) Date: Tue, 29 Nov 2011 14:34:58 +0100 Subject: [Fiware-i2nd] FiWare T7.3: Work on NetIC API In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0693AE47@SLFSNX.rcs.alcatel-research.de> References: <133D9897FB9C5E4E9DF2779DC91E947C0693AE47@SLFSNX.rcs.alcatel-research.de> Message-ID: <4ED4DF82.6010401@dis.uniroma1.it> Dear Thomas and Klaus, I have just uploaded a document that describes the information that can be obtained using the OpenFlow protocol. Please find the document in this link: https://forge.fi-ware.eu/docman/view.php/10/662/FI-WARE_NetIC_OpenFlow+statistics_v0.2.docx Best regards, Andi On 11/23/2011 04:39 PM, BANNIZA, Thomas-Rolf wrote: > Dear partners, > > in our meeting in Berlin last week we concluded that next step in our task work is the NetIC API specification. > > As a first step, we agreed to set up a list of resources (might be e.g. nodes, links, ports, but could be also something different) and associated parameters which are of interest to be exchanged via the interface. > We should separate the list entries into 2 sections: > a) information from network (e.g. topology, link load), and > b) influence on network (e.g. set up/change virtual networks, resource reservation). > We should first focus on a). > > To come to this list we have to tackle some points (among others, this list is not exhaustive!): > - As we aim for a technology independent IF, we should have (at least) the core of the API technology independent, therefore we have to come to a technology independent answer to the question: what is a resource, and what are potential associated parameters. > - If we assume a resource on the level of network elements, we need a function which maps path-related requests (i.e. from one endpoint in the network to another) to the affected resources. > > As we have discussed this item intensively in Berlin, we would assume that work on it is already on the way by the partners. We kindly ask you to send us your first contributions in the next days, by this we should be able to have a first version of the list until Friday, 2.12. Early feedback is highly wellcome, this would help also to come to a common 'style' of description. > > If there is anything unclear or if you have further ideas or suggestions to bring forward this issue, please don't hesitate to contact us. > > Best regards, > Thomas& Klaus > > > > > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Thomas R. Banniza > Alcatel-Lucent Deutschland AG > Bell Labs Germany > Dept. ZFZ/N > > Lorenzstrasse 10 > 70435 Stuttgart, Germany > > Phone: +49 711 821-32232 > Fax: +49 711 821-32185 > > email: Thomas-Rolf.Banniza at alcatel-lucent.com > Web: www.alcatel-lucent.com > > Alcatel-Lucent Deutschland AG > Sitz der Gesellschaft: Stuttgart ? Amtsgericht Stuttgart HRB 4026 > Vorsitzender des Aufsichtsrates: Michael Oppenhoff > Vorstand: Alf Henryk Wulf (Vorsitzender) ? Hans-J?rg Daub ? > Dr. Rainer Fechner ? Peter Kury > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Alcatel-Lucent : At the Speed of Ideas > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Diese E-Mail-Nachricht und ihre etwaigen Anlagen k?nnen vertrauliche Informationen > enthalten. Wenn Sie diese E-Mail-Nachricht irrt?mlich erhalten haben, bitten wir Sie, > uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon > gefertigte Kopien umgehend zu vernichten. Die irrt?mlich erhaltene E-Mail und > ihre etwaigen Anlagen d?rfen weder weitergeleitet noch anderweitig verwendet werden. > > This e-mail and its attachments, if any, may contain confidential information. > If you have received this e-mail in error, please notify us and delete or destroy > the e-mail and its attachments, if any, immediately. If you have received this e-mail > in error, you must not forward or make use of the e-mail and its attachments, if any. > > > > > > > > > > From Thomas-Rolf.Banniza at alcatel-lucent.com Tue Nov 29 17:29:03 2011 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Tue, 29 Nov 2011 17:29:03 +0100 Subject: [Fiware-i2nd] FiWare T7.3: Work on NetIC API In-Reply-To: <4ED4DF82.6010401@dis.uniroma1.it> References: <133D9897FB9C5E4E9DF2779DC91E947C0693AE47@SLFSNX.rcs.alcatel-research.de> <4ED4DF82.6010401@dis.uniroma1.it> Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C0693B0B5@SLFSNX.rcs.alcatel-research.de> Dear Andi, many thanks for your input. Reading the file, OpenFlow appears potentially being able to report in a quite detailed way on the resources in the network under control. But this level of detail might bear also a problem: we have to find a way to 'abstract' the information to make it manageable for a potential user/application. Presumably, 1) the network provider might not be willing to disclose all the details of his network and 2) the potential user might get easily buried with the details. So our next steps of work should comprise selecting a subset of information which 1) is really anticipated by an interface user and 2) is (ideally) as much as possible technology independent (if the user really needs deeper information, which is technology specific, we might have another query type for this). @ other task 3 members: are there any further ideas/suggestions/comments on this topic? @ other tasks, in particular task 4: are there already some ideas, what they expect from NetIC? Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Andi [mailto:andi at dis.uniroma1.it] Gesendet: Dienstag, 29. November 2011 14:35 An: BANNIZA, Thomas-Rolf Cc: marco.castrucci at dis.uniroma1.it; vincenzo.suraci at dis.uniroma1.it; pietrabissa at dis.uniroma1.it; lorant.nemeth at nsn.com; jozsef.varga at nsn.com; Hans.Einsiedler at telekom.de; CIMMINO, Antonio; DONADIO, Pasquale; PARLADORI, Giorgio; WUENSTEL, Klaus; fiware-i2nd at lists.fi-ware.eu Betreff: Re: FiWare T7.3: Work on NetIC API Dear Thomas and Klaus, I have just uploaded a document that describes the information that can be obtained using the OpenFlow protocol. Please find the document in this link: https://forge.fi-ware.eu/docman/view.php/10/662/FI-WARE_NetIC_OpenFlow+statistics_v0.2.docx Best regards, Andi On 11/23/2011 04:39 PM, BANNIZA, Thomas-Rolf wrote: > Dear partners, > > in our meeting in Berlin last week we concluded that next step in our task work is the NetIC API specification. > > As a first step, we agreed to set up a list of resources (might be e.g. nodes, links, ports, but could be also something different) and associated parameters which are of interest to be exchanged via the interface. > We should separate the list entries into 2 sections: > a) information from network (e.g. topology, link load), and > b) influence on network (e.g. set up/change virtual networks, resource reservation). > We should first focus on a). > > To come to this list we have to tackle some points (among others, this list is not exhaustive!): > - As we aim for a technology independent IF, we should have (at least) the core of the API technology independent, therefore we have to come to a technology independent answer to the question: what is a resource, and what are potential associated parameters. > - If we assume a resource on the level of network elements, we need a function which maps path-related requests (i.e. from one endpoint in the network to another) to the affected resources. > > As we have discussed this item intensively in Berlin, we would assume that work on it is already on the way by the partners. We kindly ask you to send us your first contributions in the next days, by this we should be able to have a first version of the list until Friday, 2.12. Early feedback is highly wellcome, this would help also to come to a common 'style' of description. > > If there is anything unclear or if you have further ideas or suggestions to bring forward this issue, please don't hesitate to contact us. > > Best regards, > Thomas& Klaus > > > > > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Thomas R. Banniza > Alcatel-Lucent Deutschland AG > Bell Labs Germany > Dept. ZFZ/N > > Lorenzstrasse 10 > 70435 Stuttgart, Germany > > Phone: +49 711 821-32232 > Fax: +49 711 821-32185 > > email: Thomas-Rolf.Banniza at alcatel-lucent.com > Web: www.alcatel-lucent.com > > Alcatel-Lucent Deutschland AG > Sitz der Gesellschaft: Stuttgart ? Amtsgericht Stuttgart HRB 4026 > Vorsitzender des Aufsichtsrates: Michael Oppenhoff > Vorstand: Alf Henryk Wulf (Vorsitzender) ? Hans-J?rg Daub ? > Dr. Rainer Fechner ? Peter Kury > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Alcatel-Lucent : At the Speed of Ideas > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Diese E-Mail-Nachricht und ihre etwaigen Anlagen k?nnen vertrauliche Informationen > enthalten. Wenn Sie diese E-Mail-Nachricht irrt?mlich erhalten haben, bitten wir Sie, > uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon > gefertigte Kopien umgehend zu vernichten. Die irrt?mlich erhaltene E-Mail und > ihre etwaigen Anlagen d?rfen weder weitergeleitet noch anderweitig verwendet werden. > > This e-mail and its attachments, if any, may contain confidential information. > If you have received this e-mail in error, please notify us and delete or destroy > the e-mail and its attachments, if any, immediately. If you have received this e-mail > in error, you must not forward or make use of the e-mail and its attachments, if any. > > > > > > > > > > From andi at dis.uniroma1.it Wed Nov 30 10:37:01 2011 From: andi at dis.uniroma1.it (Andi) Date: Wed, 30 Nov 2011 10:37:01 +0100 Subject: [Fiware-i2nd] FiWare T7.3: Work on NetIC API In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0693B0B5@SLFSNX.rcs.alcatel-research.de> References: <133D9897FB9C5E4E9DF2779DC91E947C0693AE47@SLFSNX.rcs.alcatel-research.de> <4ED4DF82.6010401@dis.uniroma1.it> <133D9897FB9C5E4E9DF2779DC91E947C0693B0B5@SLFSNX.rcs.alcatel-research.de> Message-ID: <4ED5F93D.3030009@dis.uniroma1.it> Dear Thomas, yes the document goes very deep in the details, but in this first version of the document we wanted to report the "potentiality" of the OpenFlow Protocol. I thought that this might be useful if we make an intersection between the information available from different protocols, so we don't loose any possible important data in this operation. We agree with you that in order to provide a technology-independent interface we should select a subset of the information provided by the OpenFlow Switchs and maybe further extrapolated data from the controller. Best regards, Andi On 29/11/2011 17:29, BANNIZA, Thomas-Rolf wrote: > Dear Andi, > > many thanks for your input. > > Reading the file, OpenFlow appears potentially being able to report in a quite detailed way on the resources in the network under control. But this level of detail might bear also a problem: we have to find a way to 'abstract' the information to make it manageable for a potential user/application. Presumably, 1) the network provider might not be willing to disclose all the details of his network and 2) the potential user might get easily buried with the details. > > So our next steps of work should comprise selecting a subset of information which 1) is really anticipated by an interface user and 2) is (ideally) as much as possible technology independent (if the user really needs deeper information, which is technology specific, we might have another query type for this). > > @ other task 3 members: are there any further ideas/suggestions/comments on this topic? > > @ other tasks, in particular task 4: are there already some ideas, what they expect from NetIC? > > Best regards, > Thomas > > > > -----Urspr?ngliche Nachricht----- > Von: Andi [mailto:andi at dis.uniroma1.it] > Gesendet: Dienstag, 29. November 2011 14:35 > An: BANNIZA, Thomas-Rolf > Cc: marco.castrucci at dis.uniroma1.it; vincenzo.suraci at dis.uniroma1.it; pietrabissa at dis.uniroma1.it; lorant.nemeth at nsn.com; jozsef.varga at nsn.com; Hans.Einsiedler at telekom.de; CIMMINO, Antonio; DONADIO, Pasquale; PARLADORI, Giorgio; WUENSTEL, Klaus; fiware-i2nd at lists.fi-ware.eu > Betreff: Re: FiWare T7.3: Work on NetIC API > > Dear Thomas and Klaus, > > I have just uploaded a document that describes the information that can > be obtained using the OpenFlow protocol. Please find the document in > this link: > https://forge.fi-ware.eu/docman/view.php/10/662/FI-WARE_NetIC_OpenFlow+statistics_v0.2.docx > > Best regards, > Andi > > > > On 11/23/2011 04:39 PM, BANNIZA, Thomas-Rolf wrote: >> Dear partners, >> >> in our meeting in Berlin last week we concluded that next step in our task work is the NetIC API specification. >> >> As a first step, we agreed to set up a list of resources (might be e.g. nodes, links, ports, but could be also something different) and associated parameters which are of interest to be exchanged via the interface. >> We should separate the list entries into 2 sections: >> a) information from network (e.g. topology, link load), and >> b) influence on network (e.g. set up/change virtual networks, resource reservation). >> We should first focus on a). >> >> To come to this list we have to tackle some points (among others, this list is not exhaustive!): >> - As we aim for a technology independent IF, we should have (at least) the core of the API technology independent, therefore we have to come to a technology independent answer to the question: what is a resource, and what are potential associated parameters. >> - If we assume a resource on the level of network elements, we need a function which maps path-related requests (i.e. from one endpoint in the network to another) to the affected resources. >> >> As we have discussed this item intensively in Berlin, we would assume that work on it is already on the way by the partners. We kindly ask you to send us your first contributions in the next days, by this we should be able to have a first version of the list until Friday, 2.12. Early feedback is highly wellcome, this would help also to come to a common 'style' of description. >> >> If there is anything unclear or if you have further ideas or suggestions to bring forward this issue, please don't hesitate to contact us. >> >> Best regards, >> Thomas& Klaus >> >> >> >> >> >> >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> Thomas R. Banniza >> Alcatel-Lucent Deutschland AG >> Bell Labs Germany >> Dept. ZFZ/N >> >> Lorenzstrasse 10 >> 70435 Stuttgart, Germany >> >> Phone: +49 711 821-32232 >> Fax: +49 711 821-32185 >> >> email: Thomas-Rolf.Banniza at alcatel-lucent.com >> Web: www.alcatel-lucent.com >> >> Alcatel-Lucent Deutschland AG >> Sitz der Gesellschaft: Stuttgart ? Amtsgericht Stuttgart HRB 4026 >> Vorsitzender des Aufsichtsrates: Michael Oppenhoff >> Vorstand: Alf Henryk Wulf (Vorsitzender) ? Hans-J?rg Daub ? >> Dr. Rainer Fechner ? Peter Kury >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Alcatel-Lucent : At the Speed of Ideas >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> Diese E-Mail-Nachricht und ihre etwaigen Anlagen k?nnen vertrauliche Informationen >> enthalten. Wenn Sie diese E-Mail-Nachricht irrt?mlich erhalten haben, bitten wir Sie, >> uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon >> gefertigte Kopien umgehend zu vernichten. Die irrt?mlich erhaltene E-Mail und >> ihre etwaigen Anlagen d?rfen weder weitergeleitet noch anderweitig verwendet werden. >> >> This e-mail and its attachments, if any, may contain confidential information. >> If you have received this e-mail in error, please notify us and delete or destroy >> the e-mail and its attachments, if any, immediately. If you have received this e-mail >> in error, you must not forward or make use of the e-mail and its attachments, if any. >> >> >> >> >> >> >> >> >> >> From mcp at tid.es Wed Nov 30 13:34:15 2011 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 30 Nov 2011 13:34:15 +0100 Subject: [Fiware-i2nd] Need your help: vote for a submission from FI-WARE Message-ID: <4ED622C7.4030905@tid.es> Dear all, Acting on behalf of FI-WARE, Thierry Nagellen has just submitted a topic for workshop in the Future Internet Assembly to be celebrated in Aalborg. This topic could have the FI PPP as sponsor and we should have technical presentations (from FI-Ware partners but also from other contributors as Smart Santander or IoT-A projects) and some new Use Cases to improve the requirements picture We need your support to get there and there is very little time left. We would appreciate it if you could go to this link, login with a gmail user and vote if you like it: http://www.future-internet.eu/home/shape-fia.html?modSeries=111dab&modTopic=40&modSubmission=5c4fe7 Thanks for your cooperation Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx From serge.defrance at technicolor.com Wed Nov 30 16:15:49 2011 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 30 Nov 2011 16:15:49 +0100 Subject: [Fiware-i2nd] Mind Map of All Epics in WP7 In-Reply-To: <187F4CC97FD0B6488FAE608A8038FF143B2FD06D@irsmsx503.ger.corp.intel.com> References: <187F4CC97FD0B6488FAE608A8038FF143B2FD06D@irsmsx503.ger.corp.intel.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E013B122C20@MOPESMBX01.eu.thmulti.com> Dear all, I checked the useful mind map which Chris has circulated to us, looking for potential functional overlaps. Regarding tasks 7.3 and 7.4, I do not identify (presently) any overlap with the functions located in the cloud proxy. Regarding task 7.1, some functions implemented in devices may also be implemented in the cloud proxy, in particular functions which could be realized on the cloud proxy on behalf of an end user. Main of these are in my view listed in the following epics: - Personal data services : this information may be duplicated on the cloud proxy so that it is always accessible (to a fiware application), even when the end-user is not connected. It may encompass shared data (like personal pictures or files). - User profile : the cloud proxy may connect to a cloud service on behalf of an end-user (for a back ground task like a data backup for instance). - Subscriber privacy protection : the cloud proxy, which potentially may host code downloaded from cloud application, has also to authenticate the code source. In this list of three topics, however, the two first are not related directly to the cloud proxy itself, but related to applications which may run on the cloud proxy. For these two cases, the overlap is mainly due to the fact that we can consider the cloud proxy as an end device. In that sense, device sensors may be added in this list. The last topic (subscriber privacy protection) is related to the cloud proxy specific functions : when requiring the possibility to download code in a virtual container on the cloud proxy, the application has to authenticate and provide a requirement list in term of access to the home network resource. The mechanism has not yet been defined but it could be nice to have equivalent authentication mechanism if possible. Note also that this authentication function of the cloud proxy has been identified as being relevant for WP4 as far as it concern the cloud proxy management (epics : service platform manager). Best regards, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Woods, Chris Sent: mercredi 16 novembre 2011 14:31 To: 'Garino Pierangelo (pierangelo.garino at telecomitalia.it)' Cc: fiware-i2nd Subject: [Fiware-i2nd] Mind Map of All Epics in WP7 Folks, Please find attached a mind-map of all WP7 epics. Best viewed with FreeMind. Attached PDF for those without the application. 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: