From jeanpierre.lerouzic at orange.com Thu Dec 1 10:44:18 2011 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 1 Dec 2011 10:44:18 +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: Hi all, >> @ other tasks, in particular task 4: are there already some ideas, what they expect from NetIC? Here is some random thoughts: Usage oriented classes, several classes for OPEX, environmental information (routes that don't use much power), combined/variable classes and virtual networks? With more details: * Quality classes: Not really QoS in classical way, but usage oriented classes, for example if I want to do Instant messaging, I don't need a high QoS as anyway it's easy to implement redundancy at the client level, but I need some real time QoS, let say delay should be lower than a first threshold but I don't need delay better than another threshold. * Several classes for OPEX minded operators: Whatever the user needs, I as a OPEX minded operator I want a low cost network where cost is guaranteed to be lower some threshold.. * Environmental information (routes that don't use much power): Please route my packets only on energy saving routers. * Combined/variable classes: I as an operator I want to be able to change my mind about my network requirements several time per day. * virtual networks? I want to share a physical network with other stakeholders Best regards, Jean-Pierre -----Message d'origine----- De?: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de BANNIZA, Thomas-Rolf Envoy??: mardi 29 novembre 2011 17:29 ??: Andi Cc?: marco.castrucci at dis.uniroma1.it; fiware-i2nd at lists.fi-ware.eu Objet?: Re: [Fiware-i2nd] FiWare T7.3: Work on NetIC API 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. > > > > > > > > > > _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd From pierangelo.garino at telecomitalia.it Mon Dec 5 15:32:08 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 5 Dec 2011 15:32:08 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, here is the proposed agenda for our periodic confcall: 1) Review meeting preliminary results 2) Status of activity in WP and Tasks & Workplan 2a) Shorter Term . Sprint1 outcomes (retrospective meeting) . Planning of Sprint2 (end 31 Dec) 2b) Longer Term . Info on proposed document format . Architecture specs (End Jan) . GE Specs (End Apr) 3) Further items 3a) Management of tickets from UCPs 3b) Open Calls Please circulate any further topic you?d like to discuss in the call, thanks. 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: 3722 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 chris.woods at intel.com Tue Dec 6 22:51:38 2011 From: chris.woods at intel.com (Woods, Chris) Date: Tue, 6 Dec 2011 21:51:38 +0000 Subject: [Fiware-i2nd] =?windows-1252?q?CDI_Sprint_Entry_Statement=3A_Spri?= =?windows-1252?q?nt_2_=96_=28Dec_1st_to_Dec_31st_2011=29?= Message-ID: <6561D414F94B1346BD04F33925F8BFE19AC893@IRSMSX101.ger.corp.intel.com> CDI Sprint Entry Statement: Sprint 2 ? (Dec 1st to Dec 31st 2011) Purpose of this communication This communication provides a quick overview of the tasks each partner within CDI (WP7.1) will attempt during the next sprint. Sprint Goals Items each partner intends to achieve during the sprint. Intel ? Provide client architecture document ? Secure Intel legal permission to access Webinos Code base ? Work with Pier to secure FI-WARE / Webinos collaboration University of Rome ? Gain entry into Webinos Project for University of Rome Telecom Italia ? Fully understand and provide access to TI's Web Runtime ? Address legal issues with Nick Allot (Webinos) for Fi-WARE & Webinos collaboration ? Define a consistent set of features for the 1st minor release of FI-WARE Non Goals Non Goals are items which are deliberately stated by a partner to be out of scope for a sprint. Note: No Non-Goals where identified at this time. Stretch Goals Items each partner would like to achieve if they have additional time during the sprint. Intel ? Provide working development environment University of Rome ? Assess Webinos Code - enabling introduction of QoE API specification Blocking items Anything halting or preventing a partner from executing, consider these items a call for assistance by a partner. Intel ? Awaiting access to TI?s Web Run Time environment University of Rome ? Awaiting access to Webinos Telecom Italia ? Awaiting approval from internal TI team to make Web Run Time available to FI WARE Goals achieved last sprint (Sprint 1) Intel ? Overlap analysis between WP7 and other FI-WARE WPs ? Mind Map of Epics ? Progressing legal adoption of Webinos for Intel ? Overview of current Web Run Time technology, Tizen, Webinos, WAC, PhoneGap University of Rome ? Defined GE Studied state of the art in Web Run Times and identified lack of APIs on QoE measurement and management on device. ? Studied how to adapt Android Platform to support custom Web Run Time Telecom Italia ? Managed inclusion of assets from IT ? Primary analysis of device APIs including Webinos and WAC ? Identifying features for Sprint and 1st Release of FI WARE Wiki entries, backlog tracker etc. ------------------------------------------------------------- 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: CDI Sprint Entry Statement.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 21889 bytes Desc: CDI Sprint Entry Statement.docx URL: From pierangelo.garino at telecomitalia.it Wed Dec 7 08:26:34 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 7 Dec 2011 08:26:34 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable In-Reply-To: <4ED63FF2.6020400@tid.es> References: <4ED63FF2.6020400@tid.es> Message-ID: FYI. We'll talk about this item in the call today. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 30 novembre 2011 15:39 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] IMPORTANT: Approach for Architecture Specification Deliverable Hi all, As you know, we have to start working on the Architecture Specifications, which is one of the deliverables that is due in month 9, that is, end of January. My intention is to adopt a pragmatic approach, trying to generate something that can be integrated as part of the GE Open Specifications that we have to produce by month 12. My vision is that all GE Open Specifications should start with a chapter where an overview of the envisioned Architecture for the GE is described. While style would be narrative, the description should be enough concrete, i.e., formulated over actual data type, interface and operation names and elaborating on the base interaction scenarios involving the different entities exporting the defined interfaces. Then, after that chapter, the detailed specification of all data types and interfaces with their operations, are provided (this including signature of operations and accurate description of expected behaviour linked to operations) Then, the Architecture Specification deliverable would be just the result of developing this overview chapter. But nothing better than an example, so let me use one taken from OMG's set of CORBA Services Specifications. Along my many years involved in different standardization efforts, I have found that OMG CORBA Service specs are rather comprehensive and close to what programmers (our ultimate customers!) love to see. Please find enclosed the CORBA Event Service Specifications. What I would then select as the Architecture description are the contents of the following sections: * The whole chapter 1 * Section 2.2 and 2.4 (which some people may have argued should have been included in chapter 1 :-) Note that anyone who reads the mentioned sections would get a CLEAR picture of what is the Architecture of the service and what are going to be the entities and interfaces/operations that will be supported in a compliant implementation. The conceptual and programming model would be also rather clear from a programmer's perspective. Therefore, rather valuable information for an application developer perspective which is what really should matter to us. A side benefit is that what will remain as pending regarding GE Open Specifications will be less, that is, the detailed specification of data types and interfaces/operations. One thing that we will have to define is the set of conventions that we should all follow whenever we need to draw any figure, like figures 1-x or 2-x. For this, Thomas and me will come soon to you with a proposal in short time. Please take your time to analyze this carefully and formulate any question you may have. From now on, I assume that you will start planning activities in Sprint 2 and 3 dealing with development of these specifications within each of your chapters. This may well take the form of Work Items in the tracker. 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: Event Service Specification 04-10-02.pdf Type: application/pdf Size: 515254 bytes Desc: Event Service Specification 04-10-02.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 pierangelo.garino at telecomitalia.it Wed Dec 7 10:08:18 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 7 Dec 2011 10:08:18 +0100 Subject: [Fiware-i2nd] Web conferencing PIN Message-ID: Hi All, this is a new PIN to attempt using web conferencing tool (powwownow at the moment): 217938 Please don't use it for the confcall today, but maybe during the call we can try this new one for the web only! In that case, you should open the URL powwownow.yuuguu.com 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 Dec 7 10:53:00 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 7 Dec 2011 10:53:00 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] GUIDELINE: FI-WARE Architecture Specifications: proposed solution for some of the pending questions In-Reply-To: <4EDF1BED.7060805@tid.es> References: <4EDF1BED.7060805@tid.es> Message-ID: FYI. Please send a feedback on FMC notation use. Thanks Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: mercoled? 7 dicembre 2011 08:55 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] GUIDELINE: FI-WARE Architecture Specifications: proposed solution for some of the pending questions Hi all, On Nov 30th, I sent a detailed email describing how I think we should approach development of the next major deliverable, i.e., the deliverable on FI-WARE Architecture Specifications. I hope that all of you had already read carefully its contents so that we all are on the same page. There were two questions that were pending to solve before starting the actual writing of the deliverable on the Wiki. I elaborate on the proposed approach for both of them here. 1. Conventions for figures to include in Architecture Specifications In order to get an harmonized set of specifications a convention for figures describing aspects of the Functional Architecture linked to a GE has to be adopted. After some analysis, Thomas and me have decided to propose following FMC conventions for "Block Diagrams - Compositional Structures" defined in [1]. Note that the adoption of FMC conventions is limited to these Block Diagrams. Rest is not mandatory at all (nor indeed needed for this deliverable). Unless we hear about any objection, this will be the adopted recommendation you should forward to your teams. The gallery of basic elements used in FMC Block Diagrams is pretty simple, so I'm sure you could use any of your favorite editing tools for creating Architecture Description Diagrams, even powerpoint. For those who may not want to use powerpoint but a drawing tool that is better tailored to draw Diagrams, we may recommend yED (see [2]) 2. Uploading contents on the Wiki As already explained in one of my previous mails in response to a question made by Torsten, we will definitively go for developing contents of this deliverable on the Wiki. Therefore, one of the questions we should answer first is where on the Wiki. Here you are a list of points that describe the approach I suggest we should follow: * A new entry on the main home page of the FI-WARE Wiki will be created titled "FI-WARE Architecture". This will lead to a Wiki page were we will provide: * a short introduction of the goal of the Architecture Specifications * links to specific Wiki pages, one per chapter of FI-WARE. Each of these Wiki pages will be structured so that it includes an Introduction section (we will decide what comes here later) and a section per GE who should follow the structure we described in the email I sent on Nov 30 (note that the CORBA Event Service example I provided would map to the concept of a single GE in FI-WARE like the Pub/Sub Broker GE) * a link to a Wiki page to be titled "Bringing all pieces together", were we will elaborate on the description of how the different chapters will connect together from an architectural point of view, serving example (but generic) use case scenarios. * We should include a section titled "Open Specifications" at each of the GE sections we have under the "Materializing the FI-WARE Vision" part of the Wiki. This section will contain a bullet list of two items, each one linking to a Wiki page. The first one will be titled "Architecture Specification" and the second one will be titled "Detailed Interface Specifications". The first one will be a direct link to the section dedicated to the GE under the "FI-WARE Architecture" part of the Wiki described in the point above (note this will allow to navigate to concrete GE Architecture Specifications from the "Materializing the FI-WARE Vision" part of the Wiki, but that is precisely something we want to achieve). The second one will be where the detailed description of what remains regarding the complete set of Open Specifications linked to a GE, that is, the detailed description (signature and behaviour description of provided APIs, definition of protocols, non-functional mandatory features, etc) of interfaces introduced in the Architecture Specification. A draft of the guidelines, based on the above descriptive text, will be made soon available on the FI-WARE Project Handbook available on the Wiki. Please don't hesitate to make any question or formulate any doubt so that answers can help to enrich the guidelines. Please share this email with members of your team. Cheers, -- Juanjo References: [1] - http://www.fmc-modeling.org/notation_reference [2] - http://www.yworks.com/en/products_yed_about.html ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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 Wed Dec 7 15:46:44 2011 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 7 Dec 2011 14:46:44 +0000 Subject: [Fiware-i2nd] =?windows-1252?q?CDI_Sprint_Entry_Statement=3A_Spri?= =?windows-1252?q?nt_2_=96_=28Dec_1st_to_Dec_31st_2011=29?= In-Reply-To: <6561D414F94B1346BD04F33925F8BFE19AC893@IRSMSX101.ger.corp.intel.com> References: <6561D414F94B1346BD04F33925F8BFE19AC893@IRSMSX101.ger.corp.intel.com> Message-ID: <6561D414F94B1346BD04F33925F8BFE19ACBE1@IRSMSX101.ger.corp.intel.com> Hi Pier, Vincenzo, As promised during our call this morning, I?ve created tracker items for each of us. The original email below has been updated with the necessary links. You can find this document on the forge here. Thanks, Chris From: Woods, Chris Sent: Tuesday, December 06, 2011 9:52 PM To: fiware-i2nd Subject: CDI Sprint Entry Statement: Sprint 2 ? (Dec 1st to Dec 31st 2011) CDI Sprint Entry Statement: Sprint 2 ? (Dec 1st to Dec 31st 2011) Purpose of this communication This communication provides a quick overview of the tasks each partner within CDI (WP7.1) will attempt during the next sprint. Sprint Goals Items each partner intends to achieve during the sprint. Sprint Goals Items each partner intends to achieve during the sprint. Intel ? Provide client architecture document ? Secure Intel legal permission to access Webinos Code base ? Work with Pier to secure FI-WARE / Webinos collaboration University of Rome ? Gain entry into Webinos Project for University of Rome Telecom Italia ? Fully understand and provide access to TI's Web Runtime ? Address legal issues with Nick Allot (Webinos) for Fi-WARE & Webinos collaboration ? Define a consistent set of features for the 1st minor release of FI-WARE Non Goals Non Goals are items which are deliberately stated by a partner to be out of scope for a sprint. Note: No Non-Goals where identified at this time. Stretch Goals Items each partner would like to achieve if they have additional time during the sprint. Intel ? Provide working development environment University of Rome ? Assess Webinos Code - enabling introduction of QoE API specification Blocking items Anything halting or preventing a partner from executing, consider these items a call for assistance by a partner. Intel ? Awaiting access to TI?s Web Run Time environment University of Rome ? Awaiting access to Webinos Telecom Italia ? Awaiting approval from internal TI team to make Web Run Time available to FI WARE Goals achieved last sprint (Sprint 1) Intel ? Overlap analysis between WP7 and other FI-WARE WPs ? Mind Map of Epics ? Progressing legal adoption of Webinos for Intel ? Overview of current Web Run Time technology, Tizen, Webinos, WAC, PhoneGap University of Rome ? Defined GE Studied state of the art in Web Run Times and identified lack of APIs on QoE measurement and management on device. ? Studied how to adapt Android Platform to support custom Web Run Time Telecom Italia ? Managed inclusion of assets from IT ? Primary analysis of device APIs including Webinos and WAC ? Identifying features for Sprint and 1st Release of FI WARE Wiki entries, backlog tracker etc. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Dec 7 16:59:45 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 7 Dec 2011 16:59:45 +0100 Subject: [Fiware-i2nd] Periodic I2ND confcall - Minutes Message-ID: Dear All, The minutes of the confcall we had this morning are now available at the link: https://forge.fi-ware.eu/docman/view.php/10/676/I2ND_Confcall_20111207_minutes.doc Moreover, the action points list file (excel) has been updated here: https://forge.fi-ware.eu/docman/view.php/10/484/Action+List_20111207.xlsx Please take note also of the following link: http://www.doodle.com/dmaqsn5yg4mppug7 There, you can indicate the days you are present in the weeks around the end of the Year, please insert your inputs asap, thanks. Finally, I inform you again that tomorrow and Friday I won't be at work (Holiday & Company's closure). 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 Dec 19 17:12:32 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 19 Dec 2011 17:12:32 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] We are on Facebook now! In-Reply-To: <4EEF616A.9000307@tid.es> References: <4EEF616A.9000307@tid.es> Message-ID: Hi All, a message for fans of Facebook ;-) 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 Miguel Carrillo Inviato: luned? 19 dicembre 2011 17:08 A: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] We are on Facebook now! Dear all, We have our Facebook page now. You can reach it on: WPL, can you please disseminate this within your respective WPs? http://www.facebook.com/pages/FI-WARE/251366491587242 Please tick on the "I like it" button to help us grow a reasonable number of votes on Facebook. Thanks Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito C _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 5 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ Madrid 28050 (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-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 Tue Dec 20 15:23:14 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 20 Dec 2011 15:23:14 +0100 Subject: [Fiware-i2nd] Periodic I2ND Confcall Message-ID: Dear All, Tomorrow it?s time for our periodic confcall. Altough I?m aware that some of us are already on holiday, I?d like in any case to have a very short call to check the activity status, and gather any issue which might impact the planned activities. 1) Status of activity in Tasks (5? per Task Coord if they are available) 2) Ticket handling 3) Next steps 4) AOB (including Season?s Greetings ;-) Please circulate any further topic you?d like to discuss in the call, thanks. 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: 3677 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 thomas.michael.bohnert at sap.com Wed Dec 21 23:19:24 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Wed, 21 Dec 2011 23:19:24 +0100 Subject: [Fiware-i2nd] DCPerf 2012 Message-ID: <771C9B001456D64783596DDC3801C6EA2837781D69@DEWDFECCR09.wdf.sap.corp> http://www.zurich.ibm.com/dcperf12/ The 2nd international workshop on Data Center Performance Data centers have become an integral part of the backbone infrastructure for information technology. In particular, they provide a cost-efficient solution for provisioning a wide range of computing resources in diverse environments such as for business, scientific, or mobile purposes. Owing to the rapid growth of user-defined and user-generated programs, applications and content, the complexity of deploying and operating data centers is expected to increase. Considering the high volume of mixed workloads, the diversity of services offered, and the increasing mobility of users across geographically distributed areas, the performance optimization of data centers has become ever more necessary and challenging, especially concerning criteria such as scalability, reliability, manageability, power efficiency, area density, and operating costs. As a result, adaptive and autonomic optimization strategies are essential for managing the multi-dimensional complexity of data center performance. The goal of this workshop is to promote a community-wide discussion to find and identify suitable strategies to enable effective and scalable data center performance optimizations. We are looking for papers that present new techniques, introduce new methodologies, propose new research directions, or discuss strategies for resolving open performance problems at all layers of a data center. Topics of interest include (but are not limited to) Data center communication ? Intra/inter DC communication ? Network protocols ? Security Data center virtualization ? Hardware support ? Hypervisors ? Virtualized storage Data center performance ? Power / Reliability ? Performance evaluation/modeling Data center applications ? Cloud computing ? Content distribution ? Hadoop applications Data center systems ? DC architectures ? Resource allocation ? Content distribution ? Empirical studies Chair: Thomas Michael Bohnert SAP/ZHAW TPC chairs: Lydia Chen, IBM Research - Zurich Laboratory, Switzerland Florin Ciucu, T-Labs / TU Berlin, Germany Publicity and publication chair: Robert Birke, IBM Research - Zurich Laboratory, Switzerland Steering committee Peter M?ller, IBM Research - Zurich Laboratory, Switzerland Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Alok Choudhary, Northwerstern University, USA Martin Schmatz, IBM Research - Zurich Laboratory, Switzerland Anand Sivasubramaniam, Penn State University, USA Larry Xue, Arizona State University, USA From thomas.michael.bohnert at sap.com Wed Dec 21 23:09:24 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Wed, 21 Dec 2011 23:09:24 +0100 Subject: [Fiware-i2nd] DCPerf 2012 Message-ID: <771C9B001456D64783596DDC3801C6EA2837781D59@DEWDFECCR09.wdf.sap.corp> http://www.zurich.ibm.com/dcperf12/ The 2nd international workshop on Data Center Performance Data centers have become an integral part of the backbone infrastructure for information technology. In particular, they provide a cost-efficient solution for provisioning a wide range of computing resources in diverse environments such as for business, scientific, or mobile purposes. Owing to the rapid growth of user-defined and user-generated programs, applications and content, the complexity of deploying and operating data centers is expected to increase. Considering the high volume of mixed workloads, the diversity of services offered, and the increasing mobility of users across geographically distributed areas, the performance optimization of data centers has become ever more necessary and challenging, especially concerning criteria such as scalability, reliability, manageability, power efficiency, area density, and operating costs. As a result, adaptive and autonomic optimization strategies are essential for managing the multi-dimensional complexity of data center performance. The goal of this workshop is to promote a community-wide discussion to find and identify suitable strategies to enable effective and scalable data center performance optimizations. We are looking for papers that present new techniques, introduce new methodologies, propose new research directions, or discuss strategies for resolving open performance problems at all layers of a data center. Topics of interest include (but are not limited to) Data center communication ? Intra/inter DC communication ? Network protocols ? Security Data center virtualization ? Hardware support ? Hypervisors ? Virtualized storage Data center performance ? Power / Reliability ? Performance evaluation/modeling Data center applications ? Cloud computing ? Content distribution ? Hadoop applications Data center systems ? DC architectures ? Resource allocation ? Content distribution ? Empirical studies Chair: Thomas Michael Bohnert SAP/ZHAW TPC chairs: Lydia Chen, IBM Research - Zurich Laboratory, Switzerland Florin Ciucu, T-Labs / TU Berlin, Germany Publicity and publication chair: Robert Birke, IBM Research - Zurich Laboratory, Switzerland Steering committee Peter M?ller, IBM Research - Zurich Laboratory, Switzerland Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Alok Choudhary, Northwerstern University, USA Martin Schmatz, IBM Research - Zurich Laboratory, Switzerland Anand Sivasubramaniam, Penn State University, USA Larry Xue, Arizona State University, USA From pierangelo.garino at telecomitalia.it Wed Dec 28 10:27:56 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 28 Dec 2011 10:27:56 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall 21/12/2011- Minutes Message-ID: Dear All, you can find the minutes of the I2ND periodic confcall of last week at link: https://forge.fi-ware.eu/docman/view.php/10/714/I2ND_Confcall_20111221_minutes.doc The excel spreadsheet with the list of action points at the same location on the Forge site has been updated as well. You'll notice the template used for the minutes is now the standard one provided for FI-WARE. Please use this template for any new minutes you should create in the future. Wishing you a Happy New Year! 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 Dec 28 11:43:59 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 28 Dec 2011 11:43:59 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call In-Reply-To: <4EF42CEA.6030009@tid.es> References: <4EF42CEA.6030009@tid.es> Message-ID: Dear All, I forward you a mail describing the expected topics that will be addressed by the first FI-WARE Open Call. Please read it in detail, as there are a number of items which involve I2ND, especially topics for the second Open Call (Q1 2012) and with relationship with the Task Forces we mentioned in our last periodic confcall. This means we need to promptly activate ourselves to contribute to such activities. 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? 23 dicembre 2011 08:26 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] IMPORTANT TO SYNC: FI-WARE First Open Call Hi all, This is to report to you about the decisions taken regarding topics for the first Open Call in FI-WARE. Please share this info with your respective teams. Going through a sequence of three intensive dedicated confcalls, the FI-PPP AB has came to an agreement on how to handle the higher priority topics raised by the UC projects as well as what will be the topics to be addressed in the first Open Call (a number of topics proposed by FI-WARE have been incorporated in the analysis in respect to this last point). You can get a wrap-up of this exercise summarizing the agreements reached looking at the sheet titled "Wrapup" in the following shared Google docs spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE&hl=en_US#gid=1 As you will see, only two topics will be addressed in the first Open Call. Following the advice of our PO, Arian Zwegers, we have decided to split the original first Open Call into two Open Calls, therefore having a total of three Open Calls overall. We have also decided to go for a very short list of topics in this first Open Call. This is because: * Again, following our PO advice, we have to take the opportunity of this Open Call to learn about how to manage the Open Call process so it's better to make it a "small trial" * We had to face the challenge of describing in detail and in collaboration with the UC projects what we will ask for in the description of this first Open Call, which has to be issued by end of January 2012. We have little time/resources to do this for too many topics, overall taking into account that we need to face a number of deliverables by end of January. In addition, many of the high-priority topics that both UC projects and ourselves have in our list (some of them shared) are still described in a too high-level so clearly there is a need to work on further refining them as to distill the actual features we want to support in FI-WARE. This is something that makes sense to afford during Q1 of 2012. Regarding the two particular topics selected for the first Open Call, let me elaborate a bit on them: * Middleware for efficient and QoS/Security-aware invocation of services as well as exchange of messages. There were several UC projects that were asking for this, not just for implementing communication between different parts of the application but for invoking services exposed to applications by the FI-WARE GEs. Therefore, we will have to go for it definitively. However, I see here the opportunity to drive what has to be developed in a way it can become useful in FI-WARE to help a) solving some of the issues we had identified during our Security workshop on November that have to do with managing access control through credentials when handling requests to services, b) dealing with several accountability and traceability issues and c) enabling a technology-neutral definition of GE interfaces. I will elaborate more on what I believe we may push into the definition of requirements for such middleware in the "Glue Middleware" Task Force we agreed to launch in our last joint WPLs/WPAs follow-up confcall. * Business Models and Business Elements (BM & BE) Definition and Simulation This is leveraged in a request made by UC projects to have means for simulating how costs of deploying a given application on top of FI-WARE (not only hosting service costs but costs derived from using other FI-WARE GE services or even third-party application services) could be simulated. Here, I found the opportunity to map this to our critical need to address the development of a BM & BE definition support component in the context of the first Open Call since this will be a base component of the Business Framework Reference Architecture for which an asset hadn't been identified. On the other hand, from my point of view, merging the two things together makes a lot of sense because any party that is able to contribute a product that implements this sort of simulation (which is the ultimate need expressed by the UC projects) may have probably implemented its own tools for defining the basic BM & BE on which simulation is based. Therefore, it makes sense to me to go and adapt our basic BM & BE Model to the one such potential new partner may bring. Regarding the rest of topics some of you had proposed, they where discussed and we agreed that they may go for the second call after their functional description is further defined, which is something that should happen during Q1 2012. Regarding the rest of topics raised by the UC projects, I would like to highlight the following: * Augmented Reality and 3D User Interfaces were brought to the table. Fair enough, these topics are clearly something we were not covering but have to do a lot with the kind of User Experiences someone would expect to see supported in Future Internet Applications. Therefore, I find it rather suitable to cover them through Open Calls which may attract rather specialized partners on the topics. In my view, this may probably lead to definition of a Working Package on User Interface support where, BTW, we may explore whether multi-device and multi-channel access to applications (currently in WP3 and somehow lacking of support) may be collocated. * Many UC projects are looking for means in the platform that will enable them to assure certain QoS at infrastructure level not just at centralized Data Centers but end-to-end. This had been mapped into a number of requests assigned to the I2ND chapter. UC projects do not expect to manage QoS at communication level from the application themselves (other than through the basic middleware targeted in the 1st Open Call). What they expect is to be able to select, configure and contract the SLA linked to an application at configuration&deployment time. SLAs that I see would be expressed in terms of a number of SLOs (Service Level Objectives). In words of one UC project: What would be very nice to have is a service which I can ask: "I need connectivity from A to B", and the service will answer "OK, you have 10 possible paths, price is such, characteristics of connection are such". If this is done properly, my application can then choose the "most reliable", "least expensive", or "most secure" path (and this will be seutp automatically). Next thing would be monitoring to see if the promised characteristics were really delivered (otherwise I don't pay...) I agree this has to be a functionality that has to be provided by FI-WARE but will require a close coordination between the Cloud, I2ND and Apps (Business Framework) chapter, so let's really assign this a high priority in our discussions. BTW, this clearly matches one of the cross-chapter Task Forces we identified during our last joint WPLs/WPAs confcall (Network-aware Cloud Task Force) * Many UC projects also have requirements for distributing their applications partly in the centralized Data Centers and partly in cloud proxies at the network-edge. Many of them wish to see the concept of cloud-proxy generalized as to cover smartphones and other smart but small devices. This comes along the need to be able to describe this distributed taxonomy at the time applications are configured and deployed on FI-WARE as well as the need to define means for handling failures in communication between the Data Center clouds and cloud proxies (periodic synchronizations and the like). This doesn't come as something new to us, but confirms the need to afford the definition of the necessary components at the Cloud chapter that can deal with this and prepare this as a subject for the second Open Call. * Another common requirements have to do with a) being able to assign a level of certainty/trust to data being managed by the application and b) being able to manage access and views to data depending on credentials of the user on behalf of whom an application is trying to get access to data. Both requirements are clearly generic and probably useful for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Several UC projects also expressed the need for several kind of "data-stream-oriented" GEs. For instance, the notion of Publish/Subscribe but linked to streams rather than to atomic data units. Again, this seems to be something generic and useful enough for many applications but we agreed we have to explore to what extend this lead to definition and development (through an Open Call) of enablers that can really qualify as generic and go beyond those defined in the Data/Context Management chapter. * Rest of requirements were about topics I believe most probably are already in our roadmap or should not be a big issue to include in our roadmap. We agreed to follow them during Q1 2012 as to confirm this or not. Hope this long summary gives you a clear picture. Next steps will mean working on the detailed development of Epics that will be published as part of the first Open Call and will provide an enough detailed description of what we are looking for there. In addition, setting up a number of Task Forces on the topics above, involving UC projects, where we will address identification of Features. Such features will either enrich our current FI-WARE backlog (because we find they would fit within the roadmap of already identified GEs) or will be used for describing what will be requested in the second Open Call. More details will follow in the first weeks of January. I take advantage of this email to wish you all a very nice Christmas and a Happy New Year. Cheers, ------------- Juanjo Hierro Product Development and Innovation (PDI) - Telefonica Digital email: jhierro at tid.es twitter: twitter.com/JuanjoHierro ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its 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: