From pierangelo.garino at telecomitalia.it Wed Mar 6 10:26:43 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 6 Mar 2013 10:26:43 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Guidelines for the creation of the Architecture In-Reply-To: <5135C793.6040605@tid.es> References: <5135C793.6040605@tid.es> Message-ID: Dear GE Coords, As you know the process for generating the new Architecture deliverable (D2.3.2b) is on going. While in the mail below you can find the details, and deadlines, for the entire process to complete, I summarise here what is required as first steps concerning our chapter contributions: - The update of the architecture page can be done, as it has been so far, in the original public wiki page at Interface to Networks and Devices (I2ND) and the corresponding GE pages: o FIWARE.ArchitectureDescription.I2ND.CDI o FIWARE.ArchitectureDescription.I2ND.CE o FIWARE.ArchitectureDescription.I2ND.NetIC o FIWARE.ArchitectureDescription.I2ND.S3C - Please each GE coord to check that all the expected updates are done in those pages. Deadline for completing updates is Friday 8th march at 12:00 CET, which allows me to have a draft .doc ready by the same day EOB, as already announced in previous mails (and PhCs) - The guidelines to update properly the architecture description are at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions - I'll take care of all the other steps involving the 'deliverable cockpit' to have the document ready according to the further instructions below. It is at the moment sufficient for you to know that the automatic generation of a draft deliverable (.doc file) can be made available approx. twice a day, assuming that I make the modifications in the cockpit: to do this I kindly ask you to report to me when you have completed the update of one of your pages, so that I can trigger the re-generation of the .doc. - Once this first version of the deliverable is ready, the peer review will be performed. The modification steps which originate from the review will be done on the .doc file directly. Please complete those actions according to the schedule, in case you have any doubt about the process let me know. Thanks and BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Miguel Carrillo Inviato: marted? 5 marzo 2013 11:23 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: [Fiware-wpl] Guidelines for the creation of the Architecture Dear all, Let us condensate the procedure for the Architecture review in one message. The calendar is the one agreed yesterday in the WPL/WPA call: 1. First draft of contributions by chapter ready for peer review: end of February 2. .docx first version of chapter ready by March 8 3. Comments on first draft (.docx with traced changes) due by March 13th 4. .docx second version of chapters ready for peer review: March 22nd 5. Comments on second draft due by April 2nd 6. Final version: April 10th As you surely recall, the guidelines for the Architecture doc are under: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions The process will be like reflected on the FI-WARE Architecture peer-review cockpit: * We can use any wiki in each chapter but we need to have all the pages of each chapter on the same wiki for the docx generation. It sounds painful but believe me, it is not thanks to the tools provided by Thorsten and his team. Do not change this until you receive a separate message that I will send with more details later today. * Each WPL will generate a docx document per chapter (SAP will provide support to the doc generation if needed). o Upload the generated doc to "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review" o Add the link to the doc to the cockpit o Further instructions here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Deliverables.GeneratingDeliverables * The document from a given chapter will be taken by the reviewers in charge of reviewing it using the link in the cockpit * The WPL of the chapter that reviews it will make sure that it is reviewed before the deadline. Up to him how to organize it internally. * All the reviewers of a WP receive the same document but each one suggests changes for the GE (or GEs) they review. There is a line per GE, up to each WP to merge them or use them separately. Once finished, they will upload their reviews to the right folder: o "FI-WARE private" project -> Docs -> folder ""Peer reviews" -> subfolder "Architecture Review" o The link (or links if more than one) to the doc (or docs) will be added to the cockpit * Each WPL will analyse with his team the comments provided and will generate a new version of the chapter docx to be further reviewed. The new version should be available on the deliverable cockpit. Note that from this point on, chapter should drive further updates on the Word document, instead of any temporary wiki * The reviewers will have a second round of comments. * The final version will be generated for delivery. At this point, we will merge the contributions from all chapters (it is a single monolithic deliverable) and send it to the EC. * Chapter leaders will then coordinate updates of the public wiki to align with the Word document that was submitted to the EC This is the assignment: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net 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:00000000000000000000000000000003 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_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Thu Mar 7 09:17:31 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 7 Mar 2013 09:17:31 +0100 Subject: [Fiware-i2nd] wiki pages where preparing the chapter specific deliverables (D7.3.2, D7.4.2, D7.5.2) Message-ID: Dear All, Planning the preparation of the deliverables concerning WP7 in the period April/June, I have structured the private I2ND wiki page to contain a section for drafting such pages. As you know, the deliverable production will be automated, inside a deliverable cockpit of the fiware-private wiki. Nonetheless, we have the freedom to use chapter-private wiki pages to draft the documents which , thanks to the procedures set by the wiki admins, will be easily ported to the other wiki later. Here is the link to our page where the documents can be drafted: 2.3 Deliverables to be ready for FI-WARE R2 (April-June 2013) You'll also find few notes on the contents expected for each (although I didn't create any template in the pages yet...) by looking at the pages produced for the first FI-WARE Release last year. Please let me know if you have any question and/or doubt about this, thanks. Please also take into account that, along with those deliverables, we are currently fully involved also in: a) Completion of the Updated Architecture deliverable (D2.3.2) --> First draft ready by tomorrow! b) Preparation of Updated Open Specifications (D7.1.2) --> First draft ready by end of April And both are being prepared in other places (i.e. the fiware public wiki and the deliverable cockpit). 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 pierangelo.garino at telecomitalia.it Wed Mar 13 17:37:07 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 13 Mar 2013 17:37:07 +0100 Subject: [Fiware-i2nd] Periodic I2ND call Message-ID: Hi All, here is the reminder for tomorrow?s PhC, with a provisional agenda: * Backlog management * Workplan/outcomes from WPL/WPA PhC * Architecture deliverable * Open Specs deliverable * GE Releases * Implementation * Accompanying deliverables * Cross-chapter topics * (Status of I2ND internal white paper) * AOB BR Pier (new) Reminder for periodic I2ND audioconference. Below are listed the 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 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 BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid: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: not available Type: text/calendar Size: 5825 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_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Thu Mar 14 10:18:56 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 14 Mar 2013 10:18:56 +0100 Subject: [Fiware-i2nd] I Joined PhC now Message-ID: Please join the call... 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 Hans.Einsiedler at telekom.de Tue Mar 26 17:34:41 2013 From: Hans.Einsiedler at telekom.de (Hans.Einsiedler at telekom.de) Date: Tue, 26 Mar 2013 17:34:41 +0100 Subject: [Fiware-i2nd] Urgent request for help Message-ID: Dear all, As you know, next week is the use case week in Madrid and I have the pleasure do present our Chapter. Therefore I want to ask you for help. Please send me until tomorrow - Wednesday - evening some input in form of slides: - The new architectural figure of the your GE (1 slide) - List of GEs which can be used by the third party developers and application developers (1 slide) - Two sub-GEs which are ready by end of March (1 slide) - Optional a use case description, how to use the two sub-GEs (1 slide) Please contact me directly, if you have questions. Many thanks and cheers, Hans Message Classification: [ ] Public [ ] Private [X] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary ================================================================ Hans Joachim Einsiedler Deutsche Telekom AG T-Labs (Research & Innovation) Winterfeldtstrasse 21 D-10781 Berlin Phone: +49 30 8353-58423 Fax: +49 391 580220712 Mobile: +49 170 22 74 682 mailto: hans.einsiedler at telekom.de www.telekom.com ================================================================ Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick 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 pierangelo.garino at telecomitalia.it Wed Mar 27 11:38:50 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 27 Mar 2013 11:38:50 +0100 Subject: [Fiware-i2nd] Periodic I2ND call Message-ID: Dear All, As usual here is the proposed agenda: * Release of deliverables for period April - July 2013 * (shared desktop session with join.me planned, be prepared to use it) * Review of workplan * Updates and additional details on procedures * Backlog Management * Check on GEi * For Minor Release 2.2 * For FI-WARE R2 * Testbed ?Integration? * Further outcomes from WPL/WPA PhC * Live demo * Cross-chapter topics * AOB There are rather important topics to discuss, so I invite all of you to join the call tomorrow. BR Pier (new) Reminder for periodic I2ND audioconference. Below are listed the 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 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 BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid: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: not available Type: text/calendar Size: 6188 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_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Thu Mar 28 09:56:53 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 28 Mar 2013 09:56:53 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B551FAF46@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B551FAF46@EX10-MB2-MAD.hi.inet> Message-ID: Dear GE Coords (and All), FYI (it will be discussed this morning in the call). BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di MANUEL ESCRICHE VICENTE Inviato: mercoled? 27 marzo 2013 16:33 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened Dear Partners, As you know we are about to finish Sprint 2.2.3 corresponding to M23. This sprint closes Release 2.2 Next 1.April (M24) Sprint 2.3.1 (1st sprint of Release 2.3) is opened. Please, update your backlog items accordingly. 1. Close the tickets you finished along M23 (if not already done) 2. Update tickets under execution not finished to belong to Sprint 2.3.1 3. Open those new tickets you have scheduled/planned for Release 2.3 Sprint 2.3.1 - be aware Release 2.3 is the last release available for the current reporting period. Let me stress agile is obsessed with delivery, so there's need to commit to the backlog content allocated for a sprint (step 3), then few tickets are moved to next sprint (step 2). During this month we have updated the wiki templates for the public backlog items, please, check your content is consistent. Now there're fewer fields than before but still some content is missing or not correct. The templates have categories, please, check your team is using them properly. If anything, please, let me know. Thanks for cooperation! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 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_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Thu Mar 28 10:26:45 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 28 Mar 2013 10:26:45 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" In-Reply-To: <2981E9D6242FCF47ADC9B5DBA5DFD66460FD31DF@DEWDFEMB11A.global.corp.sap> References: <2981E9D6242FCF47ADC9B5DBA5DFD66460FB3B57@DEWDFEMB11A.global.corp.sap> <15438_1363678684_514815DC_15438_13773_1_976A65C5A08ADF49B9A8523F7F81925C0BC08C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2981E9D6242FCF47ADC9B5DBA5DFD66460FC3D0F@DEWDFEMB11A.global.corp.sap> <514AB78C.4030102@tid.es> <2981E9D6242FCF47ADC9B5DBA5DFD66460FD31DF@DEWDFEMB11A.global.corp.sap> Message-ID: Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Sandfuchs, Thorsten Inviato: mercoled? 27 marzo 2013 18:25 A: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear colleagues, I updated the new "FI-WARE citymap" as good as I could with relevant GEs, that I could gather from all over the places (quite a hassle to get them together). Please find the yEd files attached and a screenshot down below. Please update your content if I made some mistakes by yourself. I as well integrated the I2ND chapter, hopefully as envisioned. Any more comments? Now it should be ready to be uploaded to the fi-ware architecture page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture I think we should try to improve this page respectively - my proposal is: - Take some of the role descriptions (basically covering the roles on the diagram) out of the 3rd party innovation guide and copy & paste them to the architecture page https://forge.fi-ware.eu/docman/view.php/7/1257/Third+Party+Innovation+Enablement+in+FI-WARE+12-08-30.pdf - Have at least one decent paragraph covering every chapter and this together with "short"-version on how it _really_ interrelates to other chapters (referencing the boxes on this city map) I know this information is partially "there" in the product vision, but there it is quite old and does not cover the things that we currently "see" evolving - so I think it is our "duty" to open the eyes of others :)) What do you think? Best, /Thorsten [cid:image002.png at 01CE2B18.30049820] From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Donnerstag, 21. M?rz 2013 08:58 To: Juanjo Hierro; Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: R: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear All, I share the opinion by Juanjo concerning the inclusion of I2ND GEs in the diagram: although I was not very active so far on this topic due to absolute lack of time, I started investigating how the GEs of this chapter could be inserted in the overall picture, which is not always easy if the result needs to be 'clear and compact'. The distinction between backend and local GEs, as well as the access devices, would be also an important 'message' to be conveyed through the diagram. I'll try as well to make some proposal with an I2ND update on the diagram, hopefully by today EOB, but most probably tomorrow morning. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: gioved? 21 marzo 2013 08:32 A: Sandfuchs, Thorsten Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Oggetto: Re: [Fiware-wpl] [Fiware-wpa] FW: FIWARE Cross-chapter "Diagram" Dear Thorsten, We didn't address this during our WPL/WPA confcall because we run out of time and this is an issue that can be handle off-line through active discussion in the mailing list. I'm happy to incorporate this kind of picture in the introduction of the Architecture document but I believe there are still some improvements we have to make in the picture if we don't want it to be a mere collection of boxes clustered in chapters ... inmho that would be a source of criticism. There are at least two enhancements I would like to implement in the picture and would go on this direction: * It would be nice to distinguish between backend and Local (cloud edge or however we want to call it). This distinction applies to infrastructure and the FI-WARE software running on top of that infrastructure. Besides, this will allow to position also the network and therefore the places where I2ND GEs will fit (otherwise completely missed in the proposed picture). It would even be nice to incorporate access devices (the devices -PC, laptops, tablets, mobiles- from which enduser access to applications) * It is nice to incorporate existing backend systems with which integration of FI-WARE GEs will typically be performed (to be implemented by each FI-WARE Instance Provider). However, I wouldn't position them in the picture "below" FI-WARE GEs and at the same level as the infrastructure. Besides this, I miss some of the FI-WARE GEs in the Data Chapter (e.g., Semantic Application support) and the ones listed for the IoT chapter are wrong. I can make a proposal but only later this evening. If Thorsten may come with an alternative based on the above comments, it would be nice. I don't believe "we have literally no time". I believe we have already agreed that the Architecture deliverable will be submitted April 10th so there is still some time ... 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) Coordinator and 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 On 21/03/13 07:56, Sandfuchs, Thorsten wrote: Hi Thierry, Alex, It seems that this was not discussed in the WPL/WPA meeting (at least judging by the minutes), therefore I will fwup offline: - yes chapters _should_ anyway use FMC - but the "new" citymap is not enfocing this more than before - currently I would foresee the citymap just on the subsuming pages - Thierry: the dark grey boxes were supposed to depict 2nd level, like you proposed - when we compiled this diagram, we only knew of the apps-specific ones - please add yours to the diagram directly - Alex: coming up with reasonable connections between the chapters might still work, but a real complete picture probably is not "consumable" any more. I would opt for depicting "Autobahn" like connections between the chapters, but no footpath (if I stay in the citymap context :)). Please add the required "autobahn" lanes, where you think they are needed. If I got Juanjo right he opted to not have any connections depicted on this particular diagram as it as well blurs the picture and might lead to more questions than answers... So how should we go forward: - I will start to edit the fiware-wiki and add the current picture and some words around (but most probably this would be more apps specific) o I would go for the fiware wiki directly as we really have literally no time to finalized this - send objections if you think this is not - I could additionally upload the yed-files to the private wiki or a forge - or do you think it is better to "share" them via one of the source control systems? - I basically count on your contributions to the yed diagrams & the wiki text Anything else? Best, /Thorsten From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 19. M?rz 2013 08:38 To: Alex Glikson; Sandfuchs, Thorsten Cc: fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" I am completely aligned with the need of this big picture but do we have to introduce the FMC diagram for each technical chapter? But not all chapters have the FMC diagram... And if we try to show the interactions between GEs from one chapter, the reader should also expect the interactions between chapters and I think we miss information for that Regarding GE in release 1 and release 2 we should use colors or dotted lines for the shapes to show what is already running and what we would deliver in release 2. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : lundi 18 mars 2013 20:16 ? : Sandfuchs, Thorsten Cc : fiware-wpl-bounces at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Good idea. Maybe we can also add the main relationships between GEs typically reflected on architecture diagrams of the individual chapters (maybe omitting some of the details). Regarding #2 -- new Cloud GEs are certainly missing. Alex ==================================================================================================== Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: "Sandfuchs, Thorsten" > To: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, Date: 18/03/2013 03:27 PM Subject: [Fiware-wpl] FW: FIWARE Cross-chapter "Diagram" Sent by: fiware-wpl-bounces at lists.fi-ware.eu ________________________________ Dear colleagues, Given our current assumptions to deliver the next FI-WARE architecture by beginning of April, we would like to propose to enhance the description on the main Cross-chapter wiki page with the picture "citymap" below. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture What do you think on how to proceed: 1. Should we do it at all? (upload this picture and enhance the page with a small description in relation to the picture) 2. What is missing in terms of your chapter (most v2-GEs are most probably missing from other chapters than "apps") 3. Should we prepare this move in the fiware-private wiki? Or can we do the changes directly? If I got it correctly the changes would be needed to be implemented by the 22. March. So this week. Right? Thanks for any feedback & best regards, /Thorsten From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten Sent: Donnerstag, 7. Februar 2013 13:48 To: fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] FIWARE Cross-chapter "Diagram" Dear colleagues, we at SAP had the idea to at least try to come up with some new diagrams which potentially helps us and our stakeholders to better understand and talk about the capabilities provided. The attached file uses yEd format and all the grey boxes point to v2-GEs that were "known" while introducing the diagram. It might very well be that for your chapter there are missing components. It would be nice if you could validate the picture taking "your" chapter as the view point and/or contribute to the diagram directly. It would even be good if we could have visual connections between the given chapters and GEs - currently this is more like a "city map" than like an architecture. Any feedback appreciated. There is a second yed-file attached, where the involved components for the live-demonstrator are depicted. This is currently only an example on how to exploit the given diagram. Best, /Thorsten -- Thorsten Sandfuchs Enterprise Platform Fabric SAP Next Business and Technology SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung oder Weitergabe der E-Mail ausdr?cklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! [attachment "fiware-cross-chapter_v3_demo_app.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "fiware-cross-chapter_v3.graphml" deleted by Alex Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex Glikson/Haifa/IBM] _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image004.gif at 01CE2B18.30049820]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: 119048 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 677 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-cross-chapter_v4.graphml Type: application/octet-stream Size: 83961 bytes Desc: fiware-cross-chapter_v4.graphml URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pierangelo.garino at telecomitalia.it Thu Mar 28 16:40:00 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 28 Mar 2013 16:40:00 +0100 Subject: [Fiware-i2nd] Perr review of Apps chapter architecture Message-ID: Dear All, here I replicate the information I have put in the PhC minutes right now, with the proposed list of people to involve in the peer review of Apps chapter architecture. I have attempted to involve a larger set of reviewers, to share the workload of such activity among most of us, if not all. Reviewers have to download the Apps document (see below where it is), go to the specific section they have to review and do the review according to the items explained below (and in the minutes): 1. 2. Perform peer review on second draft by April 4th a. We review Apps chapter: you have to download the document at link http://www.google.com/url?q=https://forge.fi-ware.eu/docman/view.php/27/2007/D232_WP3_v3_generated.docx&usd=2&usg=ALhdy2-MEuhIJcdsPkmhZS8BqbyTtokoJA * Review must be done in the .docx (track changes and comments) * NOTE: DO NOT REVIEW the sub-sections on 'Open Specifications' and corresponding API, if present in your section: they are not part of Architecture deliverable!! * Guidelines at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions * List of Reviewers for GEs (document sections): . Sect 1-2. Introduction/Architecture : All reviewers (useful to understand global architecture of chapter) i. 4. Repository: Andi (see NOTE above) ii. 5. Marketplace: Mohamed (see NOTE above) iii. 6. Registry: Marius iv. 7. RSS: Lorenzo v. 8. Mediator: Roman vi. 9. Apps Store: Henk vii. 11. Service Mashup: Joszef (see NOTE above) viii. 12. Application Mashup: Pier ix. 13. Lightweighted Semantic-Enabled Composition: Gianmario (see NOTE above) Please let me know *asap* if there are troubles in performing the review assigned to you, and put in cc the GE Coord who can support me in finding a solution, thanks. Please consider also that nearly all of us might be unfamiliar with most of the topics we have to review, so denying to perform the review could put in a critical situation as well other members of the team... Thanks a lot for your support, and very best Easter wishes :) Best Regards Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid: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: