From pierangelo.garino at telecomitalia.it Wed Feb 1 09:53:07 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 1 Feb 2012 09:53:07 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] First FI-WARE Open Call announced In-Reply-To: <4F28EE96.7060404@tid.es> References: <4F28EE96.7060404@tid.es> Message-ID: FYI. 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? 1 febbraio 2012 08:50 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] First FI-WARE Open Call announced Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid: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 Wed Feb 1 11:58:07 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 1 Feb 2012 11:58:07 +0100 Subject: [Fiware-i2nd] I: Standardization In-Reply-To: References: Message-ID: Hi All, Later I'll send a provisional agenda for tomorrow's call, I anticipate however that one of topics will be the standardization deliverable: please check the slide attached which lists the inputs expected at WP level. I remind also that each Partner has to contribute directly to the deliverable for the part concerning the Partner itself - word Doc attached - but this will not be discussed in our call. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 1 febbraio 2012 08:18 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc: Ernoe.Kovacs at neclab.eu Oggetto: [Fiware-wpl] Standardization Dear all, On behalf of NEC, do not forget standardization deliverable: one action per partner and one action per WPL (a whole introduction to describe how your WPs expect to deal with standardization) We missed the deadline which was yesterday so we have to improve it ASAP. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84+33 679 85 08 44 New email address: thierry.nagellen at orange.com 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: 2012-01-25 FI-WARE Standardization_Request.pptx Type: application/octet-stream Size: 761098 bytes Desc: 2012-01-25 FI-WARE Standardization_Request.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_Input_for_Standardisation_Plan_5AnswersFrom26_20120125.docx Type: application/octet-stream Size: 284478 bytes Desc: FI-Ware_Input_for_Standardisation_Plan_5AnswersFrom26_20120125.docx 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 Feb 1 17:13:59 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 1 Feb 2012 17:13:59 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, Here are the proposed topics for tomorrow?s confcall: * Architecture description * Plannning * Features for First major release * Sprints 4 to 6 * Deliverables * Standardisation per WP * Implementation supports * Interaction with other chapters * 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 The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Talk to you tomorrow! Pier Dear All, following the proposal made in these days about moving the day/time of the periodic confcall, please find here the new proposed ?placeholder?, that?s is Thursday at 11:00 every 2 weeks. Thu 2nd is the first call we?ll have. Best Regards Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5249 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 jeanpierre.lerouzic at orange.com Thu Feb 2 12:05:44 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 2 Feb 2012 12:05:44 +0100 Subject: [Fiware-i2nd] [Fi-Ware S3C] Orange Plan for next months Message-ID: Hi all, Here is what we are working on at Orange: The plan is to provide for the end of February A Mediation API and a telecom AS. I can't provide more precise milestones for next month's but for this year this is the Orange plan in 7.4 * A Telecom AS is being assembled for FIware for the end of February: o It will be made accessible from the Internet. o If everything goes on schedule, we should have an Telecom AS operating above a base free software (Mobicents / JBoss). * We would then have later (June?) a Telecom AS API based on SOAP accessible from the Internet and the telephone network via SIP. * Then (October?) we will look at the API OneAPI to add a layer on top of REST Telecom AS, which would be easier to use. This development would be delivered to FIware under a free license. Finally the study OneAPI will add the REST API on top of Telecom AS. * We will provide a Mediation API platform by the end of February. o It will be enriched and integrated with other results from Fi-Ware all along the year. * We will provide as an asset a Voice messaging platform probably by June. Probably I will be able to make refinements to this plan as the work will progress. Best regards, Jean-Pierre -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas-Rolf.Banniza at alcatel-lucent.com Thu Feb 2 14:42:29 2012 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Thu, 2 Feb 2012 14:42:29 +0100 Subject: [Fiware-i2nd] holiday table Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06C8068F@SLFSNX.rcs.alcatel-research.de> Dear partners! As discussed in the WP7 telco this morning, please find at https://forge.fi-ware.eu/plugins/mediawiki/wiki/i2nd/index.php/WP7_holiday_table (please log in to forge prior to clicking) a holiday list where you can enter your not-availability due to holidays or other reasons. The table can also be accessed from the private I2ND Wiki homepage. Best regards, Thomas ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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 Hans.Einsiedler at telekom.de Thu Feb 2 17:49:50 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 2 Feb 2012 17:49:50 +0100 Subject: [Fiware-i2nd] Block diagram S3C Message-ID: Dear all, As mentioned, please find attached the diagram. Comments are highly welcome. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary Please note, my fax number has changed! ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423??????? Fax: +49 391 580220712 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: Assets-Enabler-Blocks-v3.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 83029 bytes Desc: Assets-Enabler-Blocks-v3.pptx URL: From pierangelo.garino at telecomitalia.it Fri Feb 3 11:12:08 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 3 Feb 2012 11:12:08 +0100 Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Message-ID: Dear All, you can find the minutes of the confcall held yesterday at the following link: https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc Please correct possible mistakes, thanks. Moreover, there are important updates concerning two of the topics discussed there: - Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions. - Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions PLEASE TAKE NOTE that the first part of guideline "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE , while the second part "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib page. About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way): (...) Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced (...) Hope this helps in making more uniform and formally consistent the descriptions. 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 Hans.Einsiedler at telekom.de Tue Feb 7 12:25:37 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Tue, 7 Feb 2012 12:25:37 +0100 Subject: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with my laptop Message-ID: Dear all, I have to apologise. On Friday I had problems with my laptop. The data is currently under restoration. I had to change the computer, so I do not have all information and only restricted access. Therefore I have generated some text and the new version of the pictures from Madrid. I will be available on Wednesday. Comments are highly welcome. Cheers, Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Assets-Enabler-Blocks-v4.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 82945 bytes Desc: Assets-Enabler-Blocks-v4.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Wiki-Text-I2ND-general-S3C.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 481368 bytes Desc: Wiki-Text-I2ND-general-S3C.docx URL: From serge.defrance at technicolor.com Wed Feb 8 09:06:50 2012 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 8 Feb 2012 09:06:50 +0100 Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates In-Reply-To: References: Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01623944D2@MOPESMBX01.eu.thmulti.com> Pier and all, I updated the contribution regarding cloud edge for the D2.3 on our I2ND private wiki. However I don't know how to add figure. Maybe Pier you can help me ? 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 3 f?vrier 2012 11:12 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear All, you can find the minutes of the confcall held yesterday at the following link: https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc Please correct possible mistakes, thanks. Moreover, there are important updates concerning two of the topics discussed there: - Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions. - Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions PLEASE TAKE NOTE that the first part of guideline "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE , while the second part "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib page. About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way): (...) Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced (...) Hope this helps in making more uniform and formally consistent the descriptions. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCE640.FDEB3F50]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 serge.defrance at technicolor.com Wed Feb 8 09:58:40 2012 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 8 Feb 2012 09:58:40 +0100 Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E01623944D2@MOPESMBX01.eu.thmulti.com> References: <453EEB4CD4162742B6EF3D3F84E88A6E01623944D2@MOPESMBX01.eu.thmulti.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E0162394606@MOPESMBX01.eu.thmulti.com> Dear all, I found the way to upload figures to the wiki. Contribution is now up to date. Pier, let me know if any problem. Note also that I shall be out of office from 10/02 to 20/02 (included, back to my office 21st of February). Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Defrance Serge Sent: mercredi 8 f?vrier 2012 09:07 To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Pier and all, I updated the contribution regarding cloud edge for the D2.3 on our I2ND private wiki. However I don't know how to add figure. Maybe Pier you can help me ? 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 3 f?vrier 2012 11:12 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear All, you can find the minutes of the confcall held yesterday at the following link: https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc Please correct possible mistakes, thanks. Moreover, there are important updates concerning two of the topics discussed there: - Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions. - Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions PLEASE TAKE NOTE that the first part of guideline "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE , while the second part "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib page. About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way): (...) Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced (...) Hope this helps in making more uniform and formally consistent the descriptions. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCE648.3C2E1AB0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Wed Feb 8 11:29:12 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 8 Feb 2012 11:29:12 +0100 Subject: [Fiware-i2nd] R: Confcall minutes - 02/02/2012 + Important Updates In-Reply-To: <453EEB4CD4162742B6EF3D3F84E88A6E0162394606@MOPESMBX01.eu.thmulti.com> References: <453EEB4CD4162742B6EF3D3F84E88A6E01623944D2@MOPESMBX01.eu.thmulti.com> <453EEB4CD4162742B6EF3D3F84E88A6E0162394606@MOPESMBX01.eu.thmulti.com> Message-ID: Hi Serge, Thanks a lot for your effort. I reviewed the CE page you have provided, and I believe you have done already a rather extended description. By trying to evaluate it against the guidelines however, I identified some aspects which probably need to be updated (mostly moving portions of what described already), here I report them using as reference the sections in the page: - Overview: Ok, but see next point - Basic Concepts: o Maybe the picture can be anticipated already in the 'Overview' along with some of the text there, i.e. everything up to 'The cloud proxy is acting as an organizing agent of the home network, in particular unifying the access to the data contained in the home network.' included. o Remaining text should stay in the 'basic concepts' section, however I consider a part of it as introductory (or complementary) to the 'general description and architecture' which is currently in the following section - Main Interactions o The actual contents of the 'main interactions' sections should be a description (a number of items) about how the CE is going to interact with the 'rest of the world' (or better the reverse: how the rest of world will interact with CE...): this has to be in narrative description (no need at the moment for having a list of parameters and expected data format), but this should be more or less a list of 'interfacing functions' to interact with the GE (unless the CE is self-contained, i.e. it doesn't have interactions with the outside world, e.g. other GEs or application developers or applications, but I think this is not the case, otherwise nobody would be able to use it ;-) o As reference, you can (re)check the guidelines page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions and the first example in line with those guidelines (but not completely yet, so pay attention!) which is the usual QueryBroker description at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker o I therefore believe that the 'general description and architecture' should be moved in previous section, almost entirely in my view, or at least up to the entire 'home system management' description. o Sub-section 'Home System Modelling, Basic Design Principles' is more in line with the expected contents of this section, but probably it should be made clearer who does it and how the interaction is expected to happen (e.g. who and how is going to create/model the files explained). o Not completely sure, but probably also the registration mechanism described ion the description of the entire 'home system management' could be one of the interactions described here. I wonder if a reference e.g. to how applications can be managed could be put here. Hope this is clear, otherwise we can have a short call e.g. today afternoon (I should be free from 15 to 17). BR Pier Da: Defrance Serge [mailto:serge.defrance at technicolor.com] Inviato: mercoled? 8 febbraio 2012 09:59 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear all, I found the way to upload figures to the wiki. Contribution is now up to date. Pier, let me know if any problem. Note also that I shall be out of office from 10/02 to 20/02 (included, back to my office 21st of February). Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Defrance Serge Sent: mercredi 8 f?vrier 2012 09:07 To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Pier and all, I updated the contribution regarding cloud edge for the D2.3 on our I2ND private wiki. However I don't know how to add figure. Maybe Pier you can help me ? 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 3 f?vrier 2012 11:12 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear All, you can find the minutes of the confcall held yesterday at the following link: https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc Please correct possible mistakes, thanks. Moreover, there are important updates concerning two of the topics discussed there: - Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions. - Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions PLEASE TAKE NOTE that the first part of guideline "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE , while the second part "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib page. About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way): (...) Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced (...) Hope this helps in making more uniform and formally consistent the descriptions. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCE652.918D11F0]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 Wed Feb 8 14:58:37 2012 From: serge.defrance at technicolor.com (Defrance Serge) Date: Wed, 8 Feb 2012 14:58:37 +0100 Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates In-Reply-To: References: <453EEB4CD4162742B6EF3D3F84E88A6E01623944D2@MOPESMBX01.eu.thmulti.com> <453EEB4CD4162742B6EF3D3F84E88A6E0162394606@MOPESMBX01.eu.thmulti.com> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01628CC789@MOPESMBX01.eu.thmulti.com> Dear Pier, I updated my contribution according to your comments. In particular, I have added to figures to better describe the interaction between the local devices in the home network and the cloud proxy (home system management). Do not hesitate to tell me if additional comments. Best Regards, Serge. From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: mercredi 8 f?vrier 2012 11:29 To: Defrance Serge Cc: fiware-i2nd at lists.fi-ware.eu Subject: R: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Hi Serge, Thanks a lot for your effort. I reviewed the CE page you have provided, and I believe you have done already a rather extended description. By trying to evaluate it against the guidelines however, I identified some aspects which probably need to be updated (mostly moving portions of what described already), here I report them using as reference the sections in the page: - Overview: Ok, but see next point - Basic Concepts: o Maybe the picture can be anticipated already in the 'Overview' along with some of the text there, i.e. everything up to 'The cloud proxy is acting as an organizing agent of the home network, in particular unifying the access to the data contained in the home network.' included. o Remaining text should stay in the 'basic concepts' section, however I consider a part of it as introductory (or complementary) to the 'general description and architecture' which is currently in the following section - Main Interactions o The actual contents of the 'main interactions' sections should be a description (a number of items) about how the CE is going to interact with the 'rest of the world' (or better the reverse: how the rest of world will interact with CE...): this has to be in narrative description (no need at the moment for having a list of parameters and expected data format), but this should be more or less a list of 'interfacing functions' to interact with the GE (unless the CE is self-contained, i.e. it doesn't have interactions with the outside world, e.g. other GEs or application developers or applications, but I think this is not the case, otherwise nobody would be able to use it ;-) o As reference, you can (re)check the guidelines page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions and the first example in line with those guidelines (but not completely yet, so pay attention!) which is the usual QueryBroker description at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker o I therefore believe that the 'general description and architecture' should be moved in previous section, almost entirely in my view, or at least up to the entire 'home system management' description. o Sub-section 'Home System Modelling, Basic Design Principles' is more in line with the expected contents of this section, but probably it should be made clearer who does it and how the interaction is expected to happen (e.g. who and how is going to create/model the files explained). o Not completely sure, but probably also the registration mechanism described ion the description of the entire 'home system management' could be one of the interactions described here. I wonder if a reference e.g. to how applications can be managed could be put here. Hope this is clear, otherwise we can have a short call e.g. today afternoon (I should be free from 15 to 17). BR Pier Da: Defrance Serge [mailto:serge.defrance at technicolor.com] Inviato: mercoled? 8 febbraio 2012 09:59 A: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear all, I found the way to upload figures to the wiki. Contribution is now up to date. Pier, let me know if any problem. Note also that I shall be out of office from 10/02 to 20/02 (included, back to my office 21st of February). Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Defrance Serge Sent: mercredi 8 f?vrier 2012 09:07 To: Garino Pierangelo; fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Pier and all, I updated the contribution regarding cloud edge for the D2.3 on our I2ND private wiki. However I don't know how to add figure. Maybe Pier you can help me ? 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 3 f?vrier 2012 11:12 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Confcall minutes - 02/02/2012 + Important Updates Dear All, you can find the minutes of the confcall held yesterday at the following link: https://forge.fi-ware.eu/docman/view.php/10/779/I2ND_Confcall_20120202_minutes.doc Please correct possible mistakes, thanks. Moreover, there are important updates concerning two of the topics discussed there: - Standardisation per WP: we have now a .doc template for WP contribution (which implies also an excel one...), although it seems rather more extended that what it was planned earlier. I'll send a separate mail to Task cords about this, to coordinate the actions. - Architecture description: there are guidelines available at the link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions PLEASE TAKE NOTE that the first part of guideline "FI-WARE GE Architecture Descriptions" concerns the description of a single GE architecture (what we call Open Specifications, e.g. the page FIWARE.OpenSpecification.I2ND.CE , while the second part "FI-WARE Chapter Architecture Description" describes the overall architecture contribution, i.e. the entire Deliverable "D2.3 FIWARE Architecture" - I2ND Contrib page. About the latter item, there's also an interesting discussion going on in the WPL/WPA list, about the use of uniform terms; below is an excerpt of a mail by Juanjo, we're all assumed to adopt the description style and terms suggested when referring to 'GE (open) specifications' and 'GE implementations' (including the non-verbose way): (...) Strictly speaking, we should never use the term "Generic Enabler" or "GE" alone in many of our sentences. It doesn't mean anything tangible. What do really exist (i.e., refers to something "tangible") are things like: * "GE specifications" (or "GE Open Specifications") * "a GE implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". Then, whenever we say, as part of a given Architecture Description (which I believe we should not try to call "Specification") something like: "The IaaS Service Manager GE invokes the xxx operation exported by an IaaS Resource Manager GE to instruct them to provision the VApp" (A) we should indeed say: "The IaaS Service Manager GE implementation invokes the xxx operation exported by an IaaS Resource Manager GE implementation to instruct them to provision the VApp" (B) However, I believe that this would lead us to documents that would be rather "verbose". On the other hand, using (A) instead of (B) in standard specifications is rather common and many people would understand that you should make the distinction but you don't make it to for the sake of non-verbosity. I would go for putting a note somewhere at the beginning of the Architecture Description deliverable, where we may say something as: In order to avoid a too verbose text, we typically use the term " GE" or simply "" (e.g., "QueryBroker GE" or "QueryBroker") to refer to "an implementation of the GE Open Specifications" (e.g., "an implementation of the QueryBroker GE Open Specifications"). Note that the notion of GE is abstract and what actually refers to tangible things are: * "GE Open Specifications" which contain all information required in order to build components which can work as implementations of GEs. * "a GE Implementation" which refers to components in a given product that implement a given GE Open Specification and therefore may claim that they are "compliant with the GE Open Specifications". You may refer to the set of terms and definitions provided at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision#Summary_of_key_concepts_introduced (...) Hope this helps in making more uniform and formally consistent the descriptions. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCE672.23277370]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 01CCE672.23277370]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 Klaus.Wuenstel at alcatel-lucent.com Wed Feb 8 15:47:16 2012 From: Klaus.Wuenstel at alcatel-lucent.com (WUENSTEL, Klaus) Date: Wed, 8 Feb 2012 15:47:16 +0100 Subject: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> Dear colleagues of FI-WARE WP7, as confirmed in last week's phone conference we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in Stuttgart. For timely planning we provide you here with information on closely located hotels and some information how to get to our meeting centre at Alcatel-Lucent in Stuttgart, Lorenzstra?e 10, see information below. For our internal planning we need the names and affiliation of participants still within the next week. Therefore I ask you to send me this information latest until Thursday, 15 February. ----------------------------------------------------- Hotels close-by: Golden Leaf Hotel, Stuttgart Zuffenhausen (1 km distance to Alcatel-Lucent) Sch?tzenb?hlstrasse 16, D-70435 Stuttgart * http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html ACHAT Comfort Hotel, Stuttgart (1 km distance to Alcatel-Lucent) Wollinstra?e 6, 70439 Stuttgart * http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 Holiday Inn, Stuttgart Weilimdorf (6 km distance to Alcatel-Lucent) Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf * http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail ----------------------------------------------------- Travel information: s. attachment. ----------------------------------------------------- Hope to see you soon and best regards Klaus & Thomas DR. KLAUS WUENSTEL ALCATEL-LUCENT DEUTSCHLAND AG BELL LABS, GERMANY Lorenzstra?e 10, 70435 Stuttgart, Germany Phone: +49 711 821 32248 Klaus.Wuenstel at alcatel-lucent.com Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, Chairman of the Board of Directors: Michael Oppenhoff, Board of Management: Alf Henryk Wulf (Chairman) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: alu_stuttgart_Travel-Info_.pdf Type: application/pdf Size: 163746 bytes Desc: alu_stuttgart_Travel-Info_.pdf URL: From pierangelo.garino at telecomitalia.it Wed Feb 8 22:45:57 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 8 Feb 2012 22:45:57 +0100 Subject: [Fiware-i2nd] R: WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> References: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> Message-ID: Dear Klaus, I wish to thank you very much for your confirmation to host the I2ND meeting at Alcatel-Lucent premises. According to what we proposed, the meeting will start at around 13:00/14:00 the first day, and it will end approx. at 16:00 the second day. I kindly ask all the I2ND-ists to propose specific important items for the meeting agenda, in any case a first draft will be circulated beginning of next week. Please provide also to Klaus the required information about meeting attendants. Best Regards Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di WUENSTEL, Klaus Inviato: mercoled? 8 febbraio 2012 15:47 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear colleagues of FI-WARE WP7, as confirmed in last week's phone conference we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in Stuttgart. For timely planning we provide you here with information on closely located hotels and some information how to get to our meeting centre at Alcatel-Lucent in Stuttgart, Lorenzstra?e 10, see information below. For our internal planning we need the names and affiliation of participants still within the next week. Therefore I ask you to send me this information latest until Thursday, 15 February. ----------------------------------------------------- Hotels close-by: Golden Leaf Hotel, Stuttgart Zuffenhausen (1 km distance to Alcatel-Lucent) Sch?tzenb?hlstrasse 16, D-70435 Stuttgart * http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html ACHAT Comfort Hotel, Stuttgart (1 km distance to Alcatel-Lucent) Wollinstra?e 6, 70439 Stuttgart * http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 Holiday Inn, Stuttgart Weilimdorf (6 km distance to Alcatel-Lucent) Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf * http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail ----------------------------------------------------- Travel information: s. attachment. ----------------------------------------------------- Hope to see you soon and best regards Klaus & Thomas DR. KLAUS WUENSTEL ALCATEL-LUCENT DEUTSCHLAND AG BELL LABS, GERMANY Lorenzstra?e 10, 70435 Stuttgart, Germany Phone: +49 711 821 32248 Klaus.Wuenstel at alcatel-lucent.com Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, Chairman of the Board of Directors: Michael Oppenhoff, Board of Management: Alf Henryk Wulf (Chairman) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe 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 Feb 9 14:12:53 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 9 Feb 2012 14:12:53 +0100 Subject: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with mylaptop In-Reply-To: References: Message-ID: Hi Hans and all, I still have no answer from IEEE IPR team, I think we can safely assume that we can use the IEEE 802.21 template. Otherwise I have no comment about the included text. 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 Hans.Einsiedler at telekom.de Envoy? : mardi 7 f?vrier 2012 12:26 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with mylaptop Dear all, I have to apologise. On Friday I had problems with my laptop. The data is currently under restoration. I had to change the computer, so I do not have all information and only restricted access. Therefore I have generated some text and the new version of the pictures from Madrid. I will be available on Wednesday. Comments are highly welcome. Cheers,< mal>Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.defrance at technicolor.com Thu Feb 9 14:43:52 2012 From: serge.defrance at technicolor.com (Defrance Serge) Date: Thu, 9 Feb 2012 14:43:52 +0100 Subject: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart In-Reply-To: References: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> Message-ID: <453EEB4CD4162742B6EF3D3F84E88A6E01629CDAC4@MOPESMBX01.eu.thmulti.com> Klaus, Pier, and all, I confirm my attendance to the next WP7 meeting in Stuttgart. Regarding the meeting time, if possible, I would prefer to start early (13h00 instead of 14h00) and finish early because my plane leaves at 17h25. Anyway I shall have to leave at 16h00 (maybe a little bit before depending on the time for reaching the airport from Alcatel facilities). Lastly, I will not able to join the next conf call (next Thursday), being on holidays until the 21st of February. For Technicolor, Henk intends to join this conf call. Best Regards, Serge. From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: mercredi 8 f?vrier 2012 22:46 To: WUENSTEL, Klaus Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear Klaus, I wish to thank you very much for your confirmation to host the I2ND meeting at Alcatel-Lucent premises. According to what we proposed, the meeting will start at around 13:00/14:00 the first day, and it will end approx. at 16:00 the second day. I kindly ask all the I2ND-ists to propose specific important items for the meeting agenda, in any case a first draft will be circulated beginning of next week. Please provide also to Klaus the required information about meeting attendants. Best Regards Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di WUENSTEL, Klaus Inviato: mercoled? 8 febbraio 2012 15:47 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear colleagues of FI-WARE WP7, as confirmed in last week's phone conference we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in Stuttgart. For timely planning we provide you here with information on closely located hotels and some information how to get to our meeting centre at Alcatel-Lucent in Stuttgart, Lorenzstra?e 10, see information below. For our internal planning we need the names and affiliation of participants still within the next week. Therefore I ask you to send me this information latest until Thursday, 15 February. ----------------------------------------------------- Hotels close-by: Golden Leaf Hotel, Stuttgart Zuffenhausen (1 km distance to Alcatel-Lucent) Sch?tzenb?hlstrasse 16, D-70435 Stuttgart * http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html ACHAT Comfort Hotel, Stuttgart (1 km distance to Alcatel-Lucent) Wollinstra?e 6, 70439 Stuttgart * http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 Holiday Inn, Stuttgart Weilimdorf (6 km distance to Alcatel-Lucent) Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf * http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail ----------------------------------------------------- Travel information: s. attachment. ----------------------------------------------------- Hope to see you soon and best regards Klaus & Thomas DR. KLAUS WUENSTEL ALCATEL-LUCENT DEUTSCHLAND AG BELL LABS, GERMANY Lorenzstra?e 10, 70435 Stuttgart, Germany Phone: +49 711 821 32248 Klaus.Wuenstel at alcatel-lucent.com Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, Chairman of the Board of Directors: Michael Oppenhoff, Board of Management: Alf Henryk Wulf (Chairman) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe 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 01CCE739.20139C50]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 marius-iulian.corici at fokus.fraunhofer.de Thu Feb 9 16:06:06 2012 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Thu, 9 Feb 2012 16:06:06 +0100 Subject: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems withmylaptop In-Reply-To: References: Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA104D13EA9@EXCHSRV.fokus.fraunhofer.de> Hello all, The template of the 802.21 is the same for all IEEE standards in the wireless domain. A very good example can be found in 802.11 (standard free for download): http://standards.ieee.org/getieee802/download/802.11-2007.pdf in section 10 (as general description) and as specific for a primitive for example in section 10.3 or 10.4. I asked other projects from FOKUS working closely with IEEE standards and it seems that they use the same template based on the 802.11 for describing the APIs. Greetings, Marius Corici From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of jeanpierre.lerouzic at orange.com Sent: Thursday, February 09, 2012 2:13 PM To: Hans.Einsiedler at telekom.de; fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems withmylaptop Hi Hans and all, I still have no answer from IEEE IPR team, I think we can safely assume that we can use the IEEE 802.21 template. Otherwise I have no comment about the included text. 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 Hans.Einsiedler at telekom.de Envoy? : mardi 7 f?vrier 2012 12:26 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with mylaptop Dear all, I have to apologise. On Friday I had problems with my laptop. The data is currently under restoration. I had to change the computer, so I do not have all information and only restricted access. Therefore I have generated some text and the new version of the pictures from Madrid. I will be available on Wednesday. Comments are highly welcome. Cheers,< mal>Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: From marius-iulian.corici at fokus.fraunhofer.de Fri Feb 10 12:39:08 2012 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Fri, 10 Feb 2012 12:39:08 +0100 Subject: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with my laptop In-Reply-To: References: Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA104D13EE6@EXCHSRV.fokus.fraunhofer.de> Hello, Please find attached a new version of the document, following the TID requirements for formatting. Major changes: reference to 802.x management not to 802.21 for the design interface. Removed the contributor names from the picture, added some "overview" description. Greetings, Marius Corici From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Thursday, February 09, 2012 12:34 PM To: Hans.Einsiedler at telekom.de Cc: Corici, Marius-Iulian; Henrik Abramowicz (henrik.abramowicz at ericsson.com); jeanpierre.lerouzic at orange.com; Woods, Chris; Bollano Gianmario; Schulze, Frank Subject: R: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with my laptop Hi Hans, I have a couple of questions concerning the interaction between S3C and CDI: - You envisage to adopt 802.21 I assume to manage the handovers, is this right? But what's the impact on the CDI (or the device itself) i.e. what do we need to support on it (specific developments, ect)? - What about remote device management, is there some asset or functionality inside S3C doing that? For instance, we were considering an OMA DM client (with an eye to its evolution) on the CDI to provide this functionality, what about server side, are there functionalities planned in S3C? 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 Hans.Einsiedler at telekom.de Inviato: marted? 7 febbraio 2012 12:26 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] [I2ND-fi-ware] Text for the Wiki - problems with my laptop Dear all, I have to apologise. On Friday I had problems with my laptop. The data is currently under restoration. I had to change the computer, so I do not have all information and only restricted access. Therefore I have generated some text and the new version of the pictures from Madrid. I will be available on Wednesday. Comments are highly welcome. Cheers,< mal>Hans Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Wiki-Text-I2ND-general-S3C-v2.0.docx Type: application/octet-stream Size: 672054 bytes Desc: Wiki-Text-I2ND-general-S3C-v2.0.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Assets-Enabler-Blocks-v5.pptx Type: application/octet-stream Size: 100727 bytes Desc: Assets-Enabler-Blocks-v5.pptx URL: From pierangelo.garino at telecomitalia.it Mon Feb 13 10:46:31 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 13 Feb 2012 10:46:31 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs Message-ID: Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... 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: I2D_Architecture.jpg Type: image/jpeg Size: 37564 bytes Desc: I2D_Architecture.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I2D_Architecture.svg Type: application/octet-stream Size: 25715 bytes Desc: I2D_Architecture.svg 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 Mon Feb 13 11:15:40 2012 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Mon, 13 Feb 2012 11:15:40 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: A References: A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.nemeth at nsn.com Mon Feb 13 11:18:08 2012 From: lorant.nemeth at nsn.com (Lorant Nemeth) Date: Mon, 13 Feb 2012 11:18:08 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> Message-ID: <4F38E360.7080808@nsn.com> Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: > Dear Pier, > after a first look on the figure I'm not sure whether the > differentiation between on one hand applications and cloud services > only talking with CDI and CE (I assume this should reflect > intercations with end devices?) and on the other hand FIWARE GEs only > talking with NetIC and S3C is correct. Do you think that NetIC and S3C > are only used by FiWare internal? In my eyes, > there might exist applications outside FiWare which might request from > S3C or NEtIC some specific connectivity or at least wants to gather > information about e.g. the traffic situation in the network. > 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:* Montag, 13. Februar 2012 10:47 > *An:* fiware-i2nd at lists.fi-ware.eu > *Betreff:* [Fiware-i2nd] Overall architecture for I2ND GEs > > Dear All, > > I tried to represent through FMC notation, as planned for the entire > Architecture deliverable, the high-level architecture of the I2ND > GEs. You can find the current drawing in the attached image. Do you > believe it could well represent/substitute the current picture we used > so far? > > Please let me know what would you modify in it. > > One comment: as I don't have Visio, I downloaded the yEd (free) tool, > and I generated this diagram with it. I'm also able to export it as > SVG, but I'm not sure it will be possible to import e.g. in Visio (the > reverse doesn't work, I already tried it!), can some of you attempt to > do this with the attached .svg file? The use of different file formats > is becoming an issue when trying to cooperatively work on the same > diagram... > > BR > > Pier > > ------------------------------------------------------------------ > *Telecom Italia > *Pierangelo Garino > Innovation & Industry Relations -- Research & Prototyping > > Via G. Reiss Romoli 274, I-10148 TORINO > > Tel: +39 011 228 7142 > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra azione > derivante dalla conoscenza di queste informazioni sono rigorosamente > vietate. Qualora abbiate ricevuto questo documento per errore siete > cortesemente pregati di darne immediata comunicazione al mittente e di > provvedere alla sua distruzione, Grazie. > > /This e-mail and any attachments//is //confidential and may contain > privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is > unauthorised. If you are not the intended recipient, please delete > this message and any attachments and advise the sender by return > e-mail, Thanks./ > > *Rispetta l'ambiente. Non stampare questa mail se non ? necessario.* > > > > _______________________________________________ > Fiware-i2nd mailing list > Fiware-i2nd at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hans.Einsiedler at telekom.de Mon Feb 13 11:50:28 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Mon, 13 Feb 2012 11:50:28 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: <4F38E360.7080808@nsn.com> References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> Message-ID: Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I2ND-architecture.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 89652 bytes Desc: I2ND-architecture.pptx URL: From jeanpierre.lerouzic at orange.com Mon Feb 13 11:57:32 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Mon, 13 Feb 2012 11:57:32 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> Message-ID: Hi all, We could simplify a bit the presentation by stating the Fi-Ware and external GEs can both access NetIC and S3C. But it might be difficult to understand why: * external GEs have the right to access NetIC * Fi-Ware Applications and services can't access NetIC BR, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Hans.Einsiedler at telekom.de Envoy? : lundi 13 f?vrier 2012 11:50 ? : lorant.nemeth at nsn.com; Thomas-Rolf.Banniza at alcatel-lucent.com Cc : fiware-i2nd at lists.fi-ware.eu Objet : Re: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas-Rolf.Banniza at alcatel-lucent.com Mon Feb 13 12:48:48 2012 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Mon, 13 Feb 2012 12:48:48 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Feb 13 14:32:30 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 13 Feb 2012 14:32:30 +0100 Subject: [Fiware-i2nd] R: Overall architecture for I2ND GEs In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> Message-ID: Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: luned? 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: 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: I2D_Architecture-2.jpg Type: image/jpeg Size: 42638 bytes Desc: I2D_Architecture-2.jpg 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 jozsef.varga at nsn.com Mon Feb 13 14:49:37 2012 From: jozsef.varga at nsn.com (Varga, Jozsef (NSN - HU/Budapest)) Date: Mon, 13 Feb 2012 15:49:37 +0200 Subject: [Fiware-i2nd] R: Overall architecture for I2ND GEs In-Reply-To: A References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> A Message-ID: Hi, I agree that the "circled lines" are just connections, so several of them may represent the same interface. For the NetIC connections I assume that a text will clarify when an entity can access the NetIC directly and when through the S3C (depending on whether it is trusted or not, i,e, features like security needed or not). My related comment that I would assume that it is possible that a network operator may access the NetIC directly, so I would add one more circled line there. Br, Jozsef This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of ext Garino Pierangelo Sent: Monday, February 13, 2012 2:33 PM To: BANNIZA, Thomas-Rolf; Hans.Einsiedler at telekom.de; jeanpierre.lerouzic at orange.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: Overall architecture for I2ND GEs Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: luned? 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: 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 jeanpierre.lerouzic at orange.com Mon Feb 13 14:50:35 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Mon, 13 Feb 2012 14:50:35 +0100 Subject: [Fiware-i2nd] Overall architecture for I2ND GEs In-Reply-To: References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi, Sorry, I understand it's a lot of work but I also wonder why every actors *except* the network operators have access to NetIC? I would have said the reverse thing (*only* the network operators have access to NetIC) BR, Jean-Pierre De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoy? : lundi 13 f?vrier 2012 14:33 ? : BANNIZA, Thomas-Rolf; Hans.Einsiedler at telekom.de; LE ROUZIC Jean-Pierre RD-MAPS-REN Cc : fiware-i2nd at lists.fi-ware.eu Objet : R: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: luned? 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: 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 Mon Feb 13 16:58:11 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 13 Feb 2012 16:58:11 +0100 Subject: [Fiware-i2nd] R: Overall architecture for I2ND GEs In-Reply-To: References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> Message-ID: Hi Jean-Pierre, Basically you're right; Hans told me he will provide a more detailed answer to this point, so let's wait this for further analysis. On the other hand, we should mainly discuss with NetIC people whether to keep the link between App developers/GEs to NetIC or not (in Jozsef's comment, it is implicitly said that there is such connection). BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: luned? 13 febbraio 2012 14:51 A: Garino Pierangelo; Thomas-Rolf.Banniza at alcatel-lucent.com; Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, Sorry, I understand it's a lot of work but I also wonder why every actors *except* the network operators have access to NetIC? I would have said the reverse thing (*only* the network operators have access to NetIC) BR, Jean-Pierre De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoy? : lundi 13 f?vrier 2012 14:33 ? : BANNIZA, Thomas-Rolf; Hans.Einsiedler at telekom.de; LE ROUZIC Jean-Pierre RD-MAPS-REN Cc : fiware-i2nd at lists.fi-ware.eu Objet : R: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: luned? 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: 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 01CCEA70.AB1CA640]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 Thomas-Rolf.Banniza at alcatel-lucent.com Mon Feb 13 17:10:17 2012 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Mon, 13 Feb 2012 17:10:17 +0100 Subject: [Fiware-i2nd] R: Overall architecture for I2ND GEs In-Reply-To: A References: A <133D9897FB9C5E4E9DF2779DC91E947C06C80B17@SLFSNX.rcs.alcatel-research.de> <4F38E360.7080808@nsn.com> <133D9897FB9C5E4E9DF2779DC91E947C06C80B29@SLFSNX.rcs.alcatel-research.de> A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06C80B85@SLFSNX.rcs.alcatel-research.de> Hi Pier, as already stated (by me and Jozsef), there will be network operators among the clients of NetIC. There will be e.g. a use case in which an operator will control network actions via NetIC. As far as no operator boundaries are affected it is not needed that S3C interfaces between the potetinal operator and NetIC (this is probably in Jozsef's mind). Furthermore, information services provided by NetIC might be of interest for any client, be it an operator, a FiWare internal or external application. And they need not to be filtered by S3C. 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: Montag, 13. Februar 2012 16:58 An: jeanpierre.lerouzic at orange.com; BANNIZA, Thomas-Rolf; Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] R: Overall architecture for I2ND GEs Hi Jean-Pierre, Basically you're right; Hans told me he will provide a more detailed answer to this point, so let's wait this for further analysis. On the other hand, we should mainly discuss with NetIC people whether to keep the link between App developers/GEs to NetIC or not (in Jozsef's comment, it is implicitly said that there is such connection). BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: luned? 13 febbraio 2012 14:51 A: Garino Pierangelo; Thomas-Rolf.Banniza at alcatel-lucent.com; Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, Sorry, I understand it's a lot of work but I also wonder why every actors *except* the network operators have access to NetIC? I would have said the reverse thing (*only* the network operators have access to NetIC) BR, Jean-Pierre De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoy? : lundi 13 f?vrier 2012 14:33 ? : BANNIZA, Thomas-Rolf; Hans.Einsiedler at telekom.de; LE ROUZIC Jean-Pierre RD-MAPS-REN Cc : fiware-i2nd at lists.fi-ware.eu Objet : R: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: luned? 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. 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: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-i2nd -- L?r?nt N?meth R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From Hans.Einsiedler at telekom.de Mon Feb 13 23:58:21 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Mon, 13 Feb 2012 23:58:21 +0100 Subject: [Fiware-i2nd] [I2ND-fi-ware] Task 7.4 Message-ID: Dear all, For Task 7.4 people: Please check the S3C chapter in the Wiki - if it is up. I have done some minor changes and it seems in the middle of editing the server disappeared or it is a mistake of handling on my side. I do not know. However, I have no access anymore. I have done some changes in the figures. So there a currently missing. I will add them by tomorrow - Tuesday. Comments are highly welcome. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: Einsiedler, Hans Sent: Dienstag, 7. Februar 2012 12:26 To: fiware-i2nd at lists.fi-ware.eu Subject: [I2ND-fi-ware] Text for the Wiki - problems with my laptop Dear all, I have to apologise. On Friday I had problems with my laptop. The data is currently under restoration. I had to change the computer, so I do not have all information and only restricted access. Therefore I have generated some text and the new version of the pictures from Madrid. I will be available on Wednesday. Comments are highly welcome. Cheers, Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Feb 15 15:31:57 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 15 Feb 2012 15:31:57 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, Here are the proposed topics for tomorrow?s confcall: * Architecture and Open Specifications description * Contribution to Technical Roadmap deliverable * Preparation of I2ND meeting in Stuttgart * 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 The following shared doc will be used again to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Talk to you tomorrow! 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: 3583 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USA_en_pwn-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: USA_en_pwn-dial-in-numbers.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Thu Feb 16 10:15:48 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 16 Feb 2012 10:15:48 +0100 Subject: [Fiware-i2nd] New architecture Message-ID: ------------------------------------------------------------------ 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: I2D_Architecture-3.jpg Type: image/jpeg Size: 45679 bytes Desc: I2D_Architecture-3.jpg 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 Feb 16 11:29:43 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 16 Feb 2012 11:29:43 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Hi All, the minutes of today's confcall are on the Forge site at link: https://forge.fi-ware.eu/docman/view.php/10/808/I2ND_Confcall_20120216_minutes.doc 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 Thu Feb 16 12:30:32 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 16 Feb 2012 12:30:32 +0100 Subject: [Fiware-i2nd] Architecture in ppt Message-ID: Hi Hans, here is the high level architecture picture created with PowerPoint, for use in the introductory part of the wiki page. 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: CDI_architecture-3.ppt Type: application/vnd.ms-powerpoint Size: 152576 bytes Desc: CDI_architecture-3.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 jeanpierre.lerouzic at orange.com Thu Feb 16 14:51:45 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Thu, 16 Feb 2012 14:51:45 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall In-Reply-To: References: Message-ID: Hi Hans and all, I have an action point to provide Orange's workplan in WP7.4 by this afternoon. Below you can find when, for which Fi-Ware event, what is provided and who is responsible at Orange and what is provided as a server in our premise (asset) and what is provided as open source. This is subject to further refinements. February 2012: - First release of API mediation platform (Philippe) - First version of WSC as open source (Jean-Pierre) May 2012: 1st release of the FI-WARE Testbed - API mediation platform with management GUI, this is released to Fi-Ware as Open source (possibly delayed) (Philippe) - Telecom server behind Orange's Nursery (as Orange's Fiware asset) (Benoit) - Voicemail and messaging platform (as Orange's Fiware asset) (Michel) - October 2012: 1st UC conceptual prototypes finished UC Projects - API mediation platform with management GUI, this is released to Fi-Ware as Open source (Philippe) - Telecom server running on Open source WAS (Orange's Fiware asset) (possibly delivered earlier) (Benoit) o Accessible in SOAP and SIP - OneAPI SMS/MMS (Philippe) - second version of WSC (Jean-Pierre) April 2013: 2nd UC conceptual prototypes finished - OneAPI ( REST) over the Telecom server, this is released to Fi-Ware as Open source (possibly delivered earlier) (Benoit) - API mediation platform monitoring SIP requests, this is released to Fi-Ware as Open source (Philippe) - Third version of WSC as open source (Jean-Pierre) July 2013: 2nd release of the FI-WARE Testbed - OneAPI ( REST) over the Telecom server, this is released to Fi-Ware as Open source (possibly delivered earlier) (Benoit) - API mediation platform *possibly*monitoring WebRTC requests, PUSH APIs, this is released to Fi-Ware as Open source (Philippe) April 2014: FI-WARE v3 to be transferred to UC for instantiation and trials - Final integrated product (integrated internally Orange components, and externally with I2ND other components) 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? : jeudi 16 f?vrier 2012 11:30 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] I2ND Periodic Confcall Hi All, the minutes of today's confcall are on the Forge site at link: https://forge.fi-ware.eu/docman/view.php/10/808/I2ND_Confcall_20120216_minutes.doc BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- 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 marius-iulian.corici at fokus.fraunhofer.de Thu Feb 16 15:33:49 2012 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Thu, 16 Feb 2012 15:33:49 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall In-Reply-To: References: Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA104D140B6@EXCHSRV.fokus.fraunhofer.de> Hello Hans, Fraunhofer contribution to S3C roadmap attached. Greetings, Marius Corici From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Thursday, February 16, 2012 2:52 PM To: Hans.Einsiedler at telekom.de; Corici, Marius-Iulian; pierangelo.garino at telecomitalia.it Cc: fiware-i2nd at lists.fi-ware.eu; philippe.deschaseaux at orange.com; benoit.sibaud at orange.com; jerome.bidet at orange.com; michel.gaillard at orange.com Subject: RE: [Fiware-i2nd] I2ND Periodic Confcall Hi Hans and all, I have an action point to provide Orange's workplan in WP7.4 by this afternoon. Below you can find when, for which Fi-Ware event, what is provided and who is responsible at Orange and what is provided as a server in our premise (asset) and what is provided as open source. This is subject to further refinements. February 2012: - First release of API mediation platform (Philippe) - First version of WSC as open source (Jean-Pierre) May 2012: 1st release of the FI-WARE Testbed - API mediation platform with management GUI, this is released to Fi-Ware as Open source (possibly delayed) (Philippe) - Telecom server behind Orange's Nursery (as Orange's Fiware asset) (Benoit) - Voicemail and messaging platform (as Orange's Fiware asset) (Michel) - October 2012: 1st UC conceptual prototypes finished UC Projects - API mediation platform with management GUI, this is released to Fi-Ware as Open source (Philippe) - Telecom server running on Open source WAS (Orange's Fiware asset) (possibly delivered earlier) (Benoit) o Accessible in SOAP and SIP - OneAPI SMS/MMS (Philippe) - second version of WSC (Jean-Pierre) April 2013: 2nd UC conceptual prototypes finished - OneAPI ( REST) over the Telecom server, this is released to Fi-Ware as Open source (possibly delivered earlier) (Benoit) - API mediation platform monitoring SIP requests, this is released to Fi-Ware as Open source (Philippe) - Third version of WSC as open source (Jean-Pierre) July 2013: 2nd release of the FI-WARE Testbed - OneAPI ( REST) over the Telecom server, this is released to Fi-Ware as Open source (possibly delivered earlier) (Benoit) - API mediation platform *possibly*monitoring WebRTC requests, PUSH APIs, this is released to Fi-Ware as Open source (Philippe) April 2014: FI-WARE v3 to be transferred to UC for instantiation and trials - Final integrated product (integrated internally Orange components, and externally with I2ND other components) 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? : jeudi 16 f?vrier 2012 11:30 ? : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] I2ND Periodic Confcall Hi All, the minutes of today's confcall are on the Forge site at link: https://forge.fi-ware.eu/docman/view.php/10/808/I2ND_Confcall_20120216_minutes.doc BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- 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: Contributions to Technical Roadmap Deliverable.docx Type: application/octet-stream Size: 17175 bytes Desc: Contributions to Technical Roadmap Deliverable.docx URL: From pierangelo.garino at telecomitalia.it Thu Feb 16 16:49:03 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 16 Feb 2012 16:49:03 +0100 Subject: [Fiware-i2nd] Interaction Matrix with other GEs Message-ID: Hi All, here is the table where we can collect all the information about interfacing our GEs both internally and externally to I2ND. Please contribute to complete the tables (each per GE) and circulate among the group asap, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Interaction_I2ND_GEs_Other_Chapters.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 21492 bytes Desc: Interaction_I2ND_GEs_Other_Chapters.xlsx 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 Hans.Einsiedler at telekom.de Thu Feb 16 18:36:42 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 16 Feb 2012 18:36:42 +0100 Subject: [Fiware-i2nd] High level archtecture description is available Message-ID: Dear all, I have finished with the description: https://forge.fi-ware.eu/plugins/mediawiki/wiki/i2nd/index.php/Deliverable_%22D2.3_FIWARE_Architecture%22_-_I2ND_Contrib Please have a look. Feel free to do changes. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [X] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary Please note, my fax number has changed! ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423 Fax: +49 391 580220712 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 -------------- An HTML attachment was scrubbed... URL: From Hans.Einsiedler at telekom.de Thu Feb 16 21:26:41 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 16 Feb 2012 21:26:41 +0100 Subject: [Fiware-i2nd] Interaction Matrix with other GEs In-Reply-To: References: Message-ID: Dear all, Please find attached the table for S3C. For the Task 7.4 people: Please check, what I have added. Many thanks and cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Donnerstag, 16. Februar 2012 16:49 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Interaction Matrix with other GEs Hi All, here is the table where we can collect all the information about interfacing our GEs both internally and externally to I2ND. Please contribute to complete the tables (each per GE) and circulate among the group asap, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCECF1.AC98F2C0]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: Copy of Interaction_I2ND_GEs_Other_Chapters-S3C.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 21660 bytes Desc: Copy of Interaction_I2ND_GEs_Other_Chapters-S3C.xlsx URL: From Hans.Einsiedler at telekom.de Thu Feb 16 21:28:11 2012 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Thu, 16 Feb 2012 21:28:11 +0100 Subject: [Fiware-i2nd] Interaction Matrix with other GEs In-Reply-To: References: Message-ID: Dear all, Please find attached the table for S3C. For the Task 7.4 people: Please check, what I have added. Many thanks and cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Garino Pierangelo Sent: Donnerstag, 16. Februar 2012 16:49 To: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] Interaction Matrix with other GEs Hi All, here is the table where we can collect all the information about interfacing our GEs both internally and externally to I2ND. Please contribute to complete the tables (each per GE) and circulate among the group asap, thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CCECF1.AC98F2C0]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: Copy of Interaction_I2ND_GEs_Other_Chapters-S3C.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 21660 bytes Desc: Copy of Interaction_I2ND_GEs_Other_Chapters-S3C.xlsx URL: From pierangelo.garino at telecomitalia.it Fri Feb 17 09:59:38 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 17 Feb 2012 09:59:38 +0100 Subject: [Fiware-i2nd] IMPORTANT: Deliv pages copied @ 11 CET!! Message-ID: Hi All, today at 11:00am CET I'll start copying the pages of I2ND contribution to D2.3, from our own i2d wiki to the fi-ware-private wiki. Please make sure that you do not make any further changes to those pages after that time. As soon as the operation is complete, I'll send you a confirmation mail. Thanks and 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 Fri Feb 17 12:46:52 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 17 Feb 2012 12:46:52 +0100 Subject: [Fiware-i2nd] Deliv pages ported!! Message-ID: Dear All, the porting of wiki pages is now complete, along with the pictures. Please check that everything is fine and nothing has been lost in the porting. The official I2ND contribution to D2.3 is now available at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND VERY IMPORTANT: Please make any further modifications to these pages only (and I see there is the need for modifications...), don't use any longer the i2nd wiki previously used!! Later we'll decide how to manage the two sets of pages, especially in view of the D7.1 preparation. Thanks and BR Pier Da: Garino Pierangelo Inviato: venerd? 17 febbraio 2012 10:00 A: fiware-i2nd at lists.fi-ware.eu Oggetto: IMPORTANT: Deliv pages copied @ 11 CET!! Priorit?: Alta Hi All, today at 11:00am CET I'll start copying the pages of I2ND contribution to D2.3, from our own i2d wiki to the fi-ware-private wiki. Please make sure that you do not make any further changes to those pages after that time. As soon as the operation is complete, I'll send you a confirmation mail. Thanks and 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 Fri Feb 17 14:48:36 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 17 Feb 2012 14:48:36 +0100 Subject: [Fiware-i2nd] Input to std plan -> please verify! Message-ID: Hi All, here is the text I have prepared for contribution to WP11 considering all the inputs I got and also the remarks which were raised, please check if everything is ok for you, then I'll send it to the task coord. ------------------------------------------------------------------ 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_Standardisation_Plan_20120207-WP7.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 556511 bytes Desc: FI-WARE_Standardisation_Plan_20120207-WP7.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 pasquale.donadio at alcatel-lucent.com Mon Feb 20 13:06:05 2012 From: pasquale.donadio at alcatel-lucent.com (DONADIO, PASQUALE (PASQUALE)) Date: Mon, 20 Feb 2012 13:06:05 +0100 Subject: [Fiware-i2nd] R: WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> References: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> Message-ID: Dear Klaus, I confirm my attendance to the next WP7 meeting in Stuttgart. Best Regards, Pasquale ________________________________ Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di WUENSTEL, Klaus Inviato: mercoled? 8 febbraio 2012 15.47 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear colleagues of FI-WARE WP7, as confirmed in last week's phone conference we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in Stuttgart. For timely planning we provide you here with information on closely located hotels and some information how to get to our meeting centre at Alcatel-Lucent in Stuttgart, Lorenzstra?e 10, see information below. For our internal planning we need the names and affiliation of participants still within the next week. Therefore I ask you to send me this information latest until Thursday, 15 February. ----------------------------------------------------- Hotels close-by: Golden Leaf Hotel, Stuttgart Zuffenhausen (1 km distance to Alcatel-Lucent) Sch?tzenb?hlstrasse 16, D-70435 Stuttgart * http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html ACHAT Comfort Hotel, Stuttgart (1 km distance to Alcatel-Lucent) Wollinstra?e 6, 70439 Stuttgart * http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 Holiday Inn, Stuttgart Weilimdorf (6 km distance to Alcatel-Lucent) Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf * http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail ----------------------------------------------------- Travel information: s. attachment. ----------------------------------------------------- Hope to see you soon and best regards Klaus & Thomas DR. KLAUS WUENSTEL ALCATEL-LUCENT DEUTSCHLAND AG BELL LABS, GERMANY Lorenzstra?e 10, 70435 Stuttgart, Germany Phone: +49 711 821 32248 Klaus.Wuenstel at alcatel-lucent.com Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, Chairman of the Board of Directors: Michael Oppenhoff, Board of Management: Alf Henryk Wulf (Chairman) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe -------------- next part -------------- An HTML attachment was scrubbed... URL: From castrucci at dis.uniroma1.it Thu Feb 23 19:22:31 2012 From: castrucci at dis.uniroma1.it (Marco Castrucci) Date: Thu, 23 Feb 2012 19:22:31 +0100 Subject: [Fiware-i2nd] Greetings Message-ID: <008901ccf258$1c502500$ddc7c002@cratr70> Dear all, as some of you already know, I'm going to leave University of Rome for a new job in a management consulting firm in Rome. As you have seen, Andi Palo is taking care of all the activities I was in charge of in Task 7.3, anyway I will continue to support him for some time to assure continuity. I have enjoyed working with all of you and I thank you for the joint efforts we have done. In particular, I would like to thank Pier for his effort in coordinating all the activities within this WP, and Thomas and Klaus for the job done in T7.3. I wish you all the best for the future and for a successful FI-WARE project, and I really hope to find new opportunities to work again with you in the future. Ciao Marco (castrucci82 at yahoo.it) -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Mon Feb 27 10:02:19 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 27 Feb 2012 10:02:19 +0100 Subject: [Fiware-i2nd] R: Greetings In-Reply-To: <008901ccf258$1c502500$ddc7c002@cratr70> References: <008901ccf258$1c502500$ddc7c002@cratr70> Message-ID: Dear Marco, I wish to thank you for all the contributions you brought to FI-WARE, it has been a great pleasure working with you, particularly during those initial steps which involved all of us in a very fruitful cooperation to set up properly the project activities. I sincerely wish you all the best for your new job, being sure it will let you to achieve outstanding results, and maybe we'll work together again in the future. With my Best Regards Pier Da: Marco Castrucci [mailto:castrucci at dis.uniroma1.it] Inviato: gioved? 23 febbraio 2012 19:23 A: fiware-i2nd Cc: Garino Pierangelo; Klaus Wuenstel; BANNIZA, Thomas-Rolf Oggetto: Greetings Dear all, as some of you already know, I'm going to leave University of Rome for a new job in a management consulting firm in Rome. As you have seen, Andi Palo is taking care of all the activities I was in charge of in Task 7.3, anyway I will continue to support him for some time to assure continuity. I have enjoyed working with all of you and I thank you for the joint efforts we have done. In particular, I would like to thank Pier for his effort in coordinating all the activities within this WP, and Thomas and Klaus for the job done in T7.3. I wish you all the best for the future and for a successful FI-WARE project, and I really hope to find new opportunities to work again with you in the future. Ciao Marco (castrucci82 at yahoo.it) Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From chris.woods at intel.com Mon Feb 27 10:23:48 2012 From: chris.woods at intel.com (Woods, Chris) Date: Mon, 27 Feb 2012 09:23:48 +0000 Subject: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart In-Reply-To: References: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> Message-ID: <6561D414F94B1346BD04F33925F8BFE19E329B@IRSMSX101.ger.corp.intel.com> Dear Klaus, Sorry for the delay - I would also like to confirm my attendance. Many thanks, Chris From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of DONADIO, PASQUALE (PASQUALE) Sent: Monday, February 20, 2012 12:06 PM To: Wuenstel, Klaus (Klaus) Cc: fiware-i2nd at lists.fi-ware.eu Subject: [Fiware-i2nd] R: WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear Klaus, I confirm my attendance to the next WP7 meeting in Stuttgart. Best Regards, Pasquale ________________________________ Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di WUENSTEL, Klaus Inviato: mercoled? 8 febbraio 2012 15.47 A: fiware-i2nd at lists.fi-ware.eu Oggetto: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart Dear colleagues of FI-WARE WP7, as confirmed in last week's phone conference we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in Stuttgart. For timely planning we provide you here with information on closely located hotels and some information how to get to our meeting centre at Alcatel-Lucent in Stuttgart, Lorenzstra?e 10, see information below. For our internal planning we need the names and affiliation of participants still within the next week. Therefore I ask you to send me this information latest until Thursday, 15 February. ----------------------------------------------------- Hotels close-by: Golden Leaf Hotel, Stuttgart Zuffenhausen (1 km distance to Alcatel-Lucent) Sch?tzenb?hlstrasse 16, D-70435 Stuttgart * http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html ACHAT Comfort Hotel, Stuttgart (1 km distance to Alcatel-Lucent) Wollinstra?e 6, 70439 Stuttgart * http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 Holiday Inn, Stuttgart Weilimdorf (6 km distance to Alcatel-Lucent) Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf * http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail ----------------------------------------------------- Travel information: s. attachment. ----------------------------------------------------- Hope to see you soon and best regards Klaus & Thomas DR. KLAUS WUENSTEL ALCATEL-LUCENT DEUTSCHLAND AG BELL LABS, GERMANY Lorenzstra?e 10, 70435 Stuttgart, Germany Phone: +49 711 821 32248 Klaus.Wuenstel at alcatel-lucent.com Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, Chairman of the Board of Directors: Michael Oppenhoff, Board of Management: Alf Henryk Wulf (Chairman) ? Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe ------------------------------------------------------------- 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 Tue Feb 28 16:56:45 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 28 Feb 2012 16:56:45 +0100 Subject: [Fiware-i2nd] Wiki Architecture pages Message-ID: Dear All, Here is a short summary of the analysis on the I2ND pages for Architecture deliverable https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND Each Item below corresponds to one section of the document; for each, some suggestion is given about what needs to be done in my opinion, to better comply with templates and guidelines. - Introduction ok - Overview ok - Open specifications of each GE (Task Coords to organize work on them) o Note: Common structure of each GE page should be: ? Overview ? It might Include the architecture of GE (see below) ? Basic Concepts ? It might Include the architecture of GE (architecture must be present either here or in the Overview) ? Main Interactions ? Sub-sections for each interface/functionality exposed ? Basic Design Principles o CDI page ? Modifications are under evaluation between Chris and myself o CE page ? The 'basic design principles' portion should be pulled out from each subsection of 'Main Interactions' and should go to the final 'Basic Design Principles' section (not present now) o NetIC page ? General Note should go into Overview (subsection in it?) ? Basic Design Principles: should these items go into Basic Concepts or should they be moved to end of page, as actual 'Basic Design Principles' section? I would vote for option 1... ? Main Interactions should be moved up one layer of structure ? NetIC Architecture should be moved down one layer of structure o S3C page ? Hans is taking care of it, he'll provide more details on the possible updates - Interfaces to other GEs -> Pier/Hans agreed to populate the section according to the GE interfacing tables circulated in past days Can you have a look at these details and provide possible updates to the pages if you agree on what proposed, thanks a lot. 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:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jeanpierre.lerouzic at orange.com Tue Feb 28 17:24:26 2012 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Tue, 28 Feb 2012 17:24:26 +0100 Subject: [Fiware-i2nd] Wiki Architecture pages In-Reply-To: References: Message-ID: Hi all, A few comments, sorry if I am out of discussion's context. ? When I look at the picture in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND I have the impression ( from this picture) that the added value of S3C is only that it gives access to CDI and Cloud proxy to network operators. In effect apps developers and cloud services (in upper layer) have access to everything while network operators have also access to NetIC. As in the subsequent text in the Wiki, my understanding of the role of S3C was different, I supposed it was to expose Network APIs to the upper layer of effect apps developers and cloud services. Plus if network operators have a direct access to NetIC why would they bother to go to S3C first to give them access to NetIC? I would have expected something like that : ? Another thing is that I don't feel at ease with the EPC "OTT API" for two reasons: o First, OTTs often use HTTP and Orange provides a HTTP API exposure layer. So if the "EPC OTT API is also in HTTP, probably it must go through the API mediation layer. o Second, even if the "EPC OTT API" is not about HTTP, IMO it must be a bit clearer defined both in terms of protocol and in terms of usage. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mardi 28 f?vrier 2012 16:57 ? : Hans Einsiedler (Hans.Einsiedler at telekom.de); WUENSTEL, Klaus; BANNIZA, Thomas-Rolf; Woods, Chris; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Defrance Serge Cc : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] Wiki Architecture pages Dear All, Here is a short summary of the analysis on the I2ND pages for Architecture deliverable https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND Each Item below corresponds to one section of the document; for each, some suggestion is given about what needs to be done in my opinion, to better comply with templates and guidelines. - Introduction ok - Overview ok - Open specifications of each GE (Task Coords to organize work on them) o Note: Common structure of each GE page should be: ? Overview ? It might Include the architecture of GE (see below) ? Basic Concepts ? It might Include the architecture of GE (architecture must be present either here or in the Overview) ? Main Interactions ? Sub-sections for each interface/functionality exposed ? Basic Design Principles o CDI page ? Modifications are under evaluation between Chris and myself o CE page ? The 'basic design principles' portion should be pulled out from each subsection of 'Main Interactions' and should go to the final 'Basic Design Principles' section (not present now) o NetIC page ? General Note should go into Overview (subsection in it?) ? Basic Design Principles: should these items go into Basic Concepts or should they be moved to end of page, as actual 'Basic Design Principles' section? I would vote for option 1... ? Main Interactions should be moved up one layer of structure ? NetIC Architecture should be moved down one layer of structure o S3C page ? Hans is taking care of it, he'll provide more details on the possible updates - Interfaces to other GEs -> Pier/Hans agreed to populate the section according to the GE interfacing tables circulated in past days Can you have a look at these details and provide possible updates to the pages if you agree on what proposed, thanks a lot. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- 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: 83410 bytes Desc: image002.png URL: From marius-iulian.corici at fokus.fraunhofer.de Tue Feb 28 17:53:11 2012 From: marius-iulian.corici at fokus.fraunhofer.de (Corici, Marius-Iulian) Date: Tue, 28 Feb 2012 17:53:11 +0100 Subject: [Fiware-i2nd] Wiki Architecture pages In-Reply-To: References: Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA104D14344@EXCHSRV.fokus.fraunhofer.de> Hello Jean-Pierre, The OTT API is not dependent on a specific communication protocol of the platform. It exposes a plain IP connection on top of which can run anything and a set of DIAMETER control interfaces enabling the transmission of QoS requirements, charging information and to fetch HSS subscription profile and notifications on data path events. This is the lowest and the most open OTT interface (with specific security risks and so on...) This gives a high degree of liberty, and with extended liberty also an extender responsibility of the OTT platform creator is required. The main target of the API are the OTT platforms that are currently developed by the operators themselves and not integration of third party OTTs. For example the API is also used by the IMS Core as part of S3C. Modified the wiki accordingly. Greetings, Marius Corici From: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Sent: Tuesday, February 28, 2012 5:24 PM To: pierangelo.garino at telecomitalia.it; Hans.Einsiedler at telekom.de; Klaus.Wuenstel at alcatel-lucent.com; Thomas-Rolf.Banniza at alcatel-lucent.com; chris.woods at intel.com; Corici, Marius-Iulian; serge.defrance at technicolor.com Cc: fiware-i2nd at lists.fi-ware.eu Subject: RE: [Fiware-i2nd] Wiki Architecture pages Hi all, A few comments, sorry if I am out of discussion's context. ? When I look at the picture in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND I have the impression ( from this picture) that the added value of S3C is only that it gives access to CDI and Cloud proxy to network operators. In effect apps developers and cloud services (in upper layer) have access to everything while network operators have also access to NetIC. As in the subsequent text in the Wiki, my understanding of the role of S3C was different, I supposed it was to expose Network APIs to the upper layer of effect apps developers and cloud services. Plus if network operators have a direct access to NetIC why would they bother to go to S3C first to give them access to NetIC? I would have expected something like that : ? Another thing is that I don't feel at ease with the EPC "OTT API" for two reasons: o First, OTTs often use HTTP and Orange provides a HTTP API exposure layer. So if the "EPC OTT API is also in HTTP, probably it must go through the API mediation layer. o Second, even if the "EPC OTT API" is not about HTTP, IMO it must be a bit clearer defined both in terms of protocol and in terms of usage. Best regards, Jean-Pierre De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoy? : mardi 28 f?vrier 2012 16:57 ? : Hans Einsiedler (Hans.Einsiedler at telekom.de); WUENSTEL, Klaus; BANNIZA, Thomas-Rolf; Woods, Chris; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Defrance Serge Cc : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] Wiki Architecture pages Dear All, Here is a short summary of the analysis on the I2ND pages for Architecture deliverable https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND Each Item below corresponds to one section of the document; for each, some suggestion is given about what needs to be done in my opinion, to better comply with templates and guidelines. - Introduction ok - Overview ok - Open specifications of each GE (Task Coords to organize work on them) o Note: Common structure of each GE page should be: ? Overview ? It might Include the architecture of GE (see below) ? Basic Concepts ? It might Include the architecture of GE (architecture must be present either here or in the Overview) ? Main Interactions ? Sub-sections for each interface/functionality exposed ? Basic Design Principles o CDI page ? Modifications are under evaluation between Chris and myself o CE page ? The 'basic design principles' portion should be pulled out from each subsection of 'Main Interactions' and should go to the final 'Basic Design Principles' section (not present now) o NetIC page ? General Note should go into Overview (subsection in it?) ? Basic Design Principles: should these items go into Basic Concepts or should they be moved to end of page, as actual 'Basic Design Principles' section? I would vote for option 1... ? Main Interactions should be moved up one layer of structure ? NetIC Architecture should be moved down one layer of structure o S3C page ? Hans is taking care of it, he'll provide more details on the possible updates - Interfaces to other GEs -> Pier/Hans agreed to populate the section according to the GE interfacing tables circulated in past days Can you have a look at these details and provide possible updates to the pages if you agree on what proposed, thanks a lot. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 83410 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: From Thomas-Rolf.Banniza at alcatel-lucent.com Tue Feb 28 18:03:17 2012 From: Thomas-Rolf.Banniza at alcatel-lucent.com (BANNIZA, Thomas-Rolf) Date: Tue, 28 Feb 2012 18:03:17 +0100 Subject: [Fiware-i2nd] Wiki Architecture pages In-Reply-To: A References: A Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C06E03411@SLFSNX.rcs.alcatel-research.de> Dear Pier and Hans, please find on https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.I2ND.NetIC the edited version of NetIC description. 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: Dienstag, 28. Februar 2012 16:57 An: Hans Einsiedler (Hans.Einsiedler at telekom.de); WUENSTEL, Klaus; BANNIZA, Thomas-Rolf; Woods, Chris; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); Defrance Serge Cc: fiware-i2nd at lists.fi-ware.eu Betreff: [Fiware-i2nd] Wiki Architecture pages Dear All, Here is a short summary of the analysis on the I2ND pages for Architecture deliverable https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3I2ND Each Item below corresponds to one section of the document; for each, some suggestion is given about what needs to be done in my opinion, to better comply with templates and guidelines. - Introduction ok - Overview ok - Open specifications of each GE (Task Coords to organize work on them) o Note: Common structure of each GE page should be: ? Overview ? It might Include the architecture of GE (see below) ? Basic Concepts ? It might Include the architecture of GE (architecture must be present either here or in the Overview) ? Main Interactions ? Sub-sections for each interface/functionality exposed ? Basic Design Principles o CDI page ? Modifications are under evaluation between Chris and myself o CE page ? The 'basic design principles' portion should be pulled out from each subsection of 'Main Interactions' and should go to the final 'Basic Design Principles' section (not present now) o NetIC page ? General Note should go into Overview (subsection in it?) ? Basic Design Principles: should these items go into Basic Concepts or should they be moved to end of page, as actual 'Basic Design Principles' section? I would vote for option 1... ? Main Interactions should be moved up one layer of structure ? NetIC Architecture should be moved down one layer of structure o S3C page ? Hans is taking care of it, he'll provide more details on the possible updates - Interfaces to other GEs -> Pier/Hans agreed to populate the section according to the GE interfacing tables circulated in past days Can you have a look at these details and provide possible updates to the pages if you agree on what proposed, thanks a lot. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreasimeoni84 at gmail.com Wed Feb 29 10:25:29 2012 From: andreasimeoni84 at gmail.com (andrea simeoni) Date: Wed, 29 Feb 2012 10:25:29 +0100 Subject: [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, Stuttgart In-Reply-To: <6561D414F94B1346BD04F33925F8BFE19E329B@IRSMSX101.ger.corp.intel.com> References: <133D9897FB9C5E4E9DF2779DC91E947C06C8098B@SLFSNX.rcs.alcatel-research.de> <6561D414F94B1346BD04F33925F8BFE19E329B@IRSMSX101.ger.corp.intel.com> Message-ID: Dear Klaus, I also confirm my attendance to the next WP7 meeting in Stuttgard, with the UNIROMA1 partner. Best regards, Andrea 2012/2/27 Woods, Chris > Dear Klaus,**** > > ** ** > > Sorry for the delay ? I would also like to confirm my attendance.**** > > ** ** > > Many thanks,**** > > Chris**** > > ** ** > > *From:* fiware-i2nd-bounces at lists.fi-ware.eu [mailto: > fiware-i2nd-bounces at lists.fi-ware.eu] *On Behalf Of *DONADIO, PASQUALE > (PASQUALE) > *Sent:* Monday, February 20, 2012 12:06 PM > *To:* Wuenstel, Klaus (Klaus) > *Cc:* fiware-i2nd at lists.fi-ware.eu > *Subject:* [Fiware-i2nd] R: WP7 meeting, 6-7 March at Alcatel-Lucent, > Stuttgart**** > > ** ** > > Dear Klaus,**** > > ** ** > > I confirm my attendance to the next WP7 meeting in Stuttgart.**** > > ** ** > > Best Regards,**** > > ** ** > > Pasquale**** > ------------------------------ > > *Da:* fiware-i2nd-bounces at lists.fi-ware.eu > [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] *Per conto di *WUENSTEL, > Klaus > *Inviato:* mercoled? 8 febbraio 2012 15.47 > *A:* fiware-i2nd at lists.fi-ware.eu > *Oggetto:* [Fiware-i2nd] WP7 meeting, 6-7 March at Alcatel-Lucent, > Stuttgart**** > > ** ** > > Dear colleagues of FI-WARE WP7,**** > > ** ** > > as confirmed in last week?s phone conference > we will have a WP7 meeting on 6-7 March, hosted by Alcatel-Lucent in > Stuttgart.**** > > ** ** > > For timely planning we provide you here with information on closely > located hotels**** > > and some information how to get to our meeting centre at Alcatel-Lucent > in Stuttgart,**** > > Lorenzstra?e 10, see information below.**** > > ** ** > > For our internal planning we need the *names and affiliation of > participants** > *still within the next week. **** > > Therefore I ask you to send me this information latest until *Thursday, > 15 February*.**** > > ** ** > > *-----------------------------------------------------* > > *Hotels close-by:** *** > > *Golden Leaf Hotel, Stuttgart Zuffenhausen *(1 km distance to > Alcatel-Lucent) > Sch?tzenb?hlstrasse 16, D-70435 Stuttgart**** > > - > http://www.golden-leaf-hotel.de/en/stuttgart/hotel-hsz/uebersicht.html > **** > > ** ** > > *ACHAT Comfort Hotel, Stuttgart *(1 km distance to Alcatel-Lucent)**** > > Wollinstra?e 6, 70439 Stuttgart**** > > ** ** > > - > http://www.hotel.de/booking.aspx?gclid=CIqYqOW3jq4CFU2GDgodHzLReQ&h_hmid=52285&cpn=42&cpnll=371 > **** > > ** ** > > *Holiday Inn, Stuttgart Weilimdorf *(6 km distance to Alcatel-Lucent)** > ** > > Mittlerer Pfad 25-27, 70499 Stuttgart-Weilimdorf**** > > ** ** > > - http://www.holidayinn.com/hotels/gb/en/stuttgart/strgc/hoteldetail > **** > > *-----------------------------------------------------* > > ** ** > > *Travel information:* s. attachment.**** > > * * > > *-----------------------------------------------------* > > * * > > * * > > Hope to see you soon and best regards**** > > Klaus & Thomas**** > > ** ** > > ** ** > > ** ** > > *DR. KLAUS WUENSTEL > ALCATEL-LUCENT DEUTSCHLAND AG > BELL LABS, GERMANY > **Lorenzstra?e 10, 70435 Stuttgart, Germany** > Phone: +49 711 821 32248 > **Klaus.Wuenstel at alcatel-lucent.com > **Domicile of the Company: Stuttgart ? Local Court Stuttgart HRB 4026, ** > Chairman of the Board of Directors: Michael Oppenhoff, > Board of Management: Alf Henryk Wulf (Chairman) ? > Hans-J?rg Daub ? Dr. Rainer Fechner ? Andeas Gehe*** > > ** ** > ------------------------------------------------------------- > 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. > > _______________________________________________ > Fiware-i2nd mailing list > Fiware-i2nd at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-i2nd > > -- Andrea Simeoni -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Wed Feb 29 11:03:08 2012 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 29 Feb 2012 11:03:08 +0100 Subject: [Fiware-i2nd] I2ND Periodic Confcall Message-ID: Dear All, Here are the proposed topics for tomorrow?s confcall: - Finalisation of Architecture description - Technical Roadmap contributions - Agenda for I2ND meeting in Stuttgart - 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. The following shared doc will be used again to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit 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 Talk to you tomorrow! Pier -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2607 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: