From maarten.los at atosresearch.eu Wed Oct 10 10:08:34 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Wed, 10 Oct 2012 10:08:34 +0200 Subject: [Fiware-iot] IoT-Minutes-Telco-26092012.docx(fiware-iot@lists.fi-ware.eu) In-Reply-To: <047d7b676446da616704ca95f554@google.com> References: <047d7b676446da616704ca95f554@google.com> Message-ID: <461EDDC0FEB25648B2FE8B0145848AA5015AC2B3@INTMAIL02.es.int.atosorigin.com> Dear partners, Will there be an IoT Weekly meeting this week? Thanks, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Thierry Nagellen (Google Drive) Sent: mi?rcoles, 26 de septiembre de 2012 9:42 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT-Minutes-Telco-26092012.docx(fiware-iot at lists.fi-ware.eu) Document I've shared IoT-Minutes-Telco-26092012.docx Click to open: ? IoT-Minutes-Telco-26092012.docx Google Drive: create, share, and keep all your stuff in one place. Logo for Google Drive ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Mon Oct 15 09:55:29 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Mon, 15 Oct 2012 09:55:29 +0200 Subject: [Fiware-iot] I: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications References: <50770372.4030804@tid.es> <507795E8.60806@tid.es> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5A135088B@GRFMBX702BA020.griffon.local> Hi all, Regarding the email Juanjo sent about the internal peer-review, we recently made a review of wp I2ND (see the attachment). Does anybody else had the chance to have a look at I2ND documentation? In this case we can merge your comments and have a review including different points of view. Best regards, Sabrina Da: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 12 ottobre 2012 06:01 A: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi, You may have received an email from your WPL or WPA regarding instructions about how we are going to tackle the third and final peer review of the FI-WARE GE Open Specifications that we have to resubmit by November 2nd at the latest (see attachment) IMPORTANT NOTE: We rather NEED that you to carry out a peer-review that focuses on how suitable the contents are. We are afraid that some of the peer-reviews carry out so far were mostly "editorial", i.e., polishing the English, highlighting issues regarding the structure, etc. We need that people review the document from the perspective of a developer or a potential implementer of the spec and point out what you don't understand, what you miss, etc. The intend of this message is twofold. First, make sure it arrives without further delays in your inbox. Second, add a number of enhancements to the process described in the original email that hopefully will allow to make it faster and more efficient. The enhancements have to do with trying to carry out the peer-review using docx files rather than reading the wiki and providing a list of change requests in a separate form. This would allow to drop out the part of the revision form that I sent earlier which had to do with providing detailed editorial comments. Please find attached the revised form. The following is a description of the whole process with the suggested enhancements. If you hadn't read the original email, you just need to read this. For every FI-WARE GE Open Specification (as listed in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications), we will have to carry out the following steps. 1. Generate docx-version of each of the FI-WARE GE Open Specifications to ease the review. There are multiple ways for doing so and it is up to each Chapter to select its preferred one, but here you are a simple set of steps you can follow to generate a docx version (I have used this personally and have found it rather straightforward): * Create a document in Google docs (I hope you have an account, otherwise agree with your WPL on how to get access to one or come back to us :-) * Go to the wiki page of the deliverable. Don't forget to access it in "read" mode (i.e., not logged in FusionForge) because that would avoid copying the "edits" * Copy and Paste directly from the Wiki page into the Google Docs. Notes: * You have to split this in several steps, because Google docs gets blocked if you try to copy&paste too many pages with too many figures. * Don't forget to add the API specs. Typically, you have to first copy&paste what is in the first-level FI-WARE GE Open Specification wiki page, then navigate to each API specification wiki page and copy and paste the contents. * Once the document is generated, you can save it as a Word docx in your local PC. * Run a quick check through the docx file fixing some easy-to-solve questions such as adjusting size of figures, doing some pagination which could easy reading, etc. Please, don't try to make it perfect, we just need a version on which you may apply changes and track those changes with the standard MS Word change control tools. 1. Upload the generated file in either SVN or the docman of the "FI-WARE Private" project in FusionForge (whatever tool you prefer) 2. Add the link to the docx file in SVN or docman to the column "Doc to review" corresponding to the FI-WARE GE in the following shared spreadsheet in Google that we will use as cockpit for the following-up the whole process: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc 3. Sent an email to the WPL of the reviewing chapter so that they know that the docx associated to the FI-WARE GE Open Specification is available for review. Please, don't wait until the rest of docs associated to other FI-WARE Open Specifications in your same chapter are uploaded. Leaders of reviewing chapters are also asked to check when there are new documents to review from time to time. 4. Carry out the review you have been assigned. Reviewers would be required to generate two files, that they should upload again to SVN or docman (whatever you prefer) and link from the Google cockpit. If you are a reviewer, please don't wait until you have both. Please upload each as soon as it is available and inform the leader of the chapter being reviewed that you have done so: * A commented docx for the deliverable which would include all comments under change control. A link to this file should be provided in the "Commented doc" column of the cockpit. * the simple FI-WARE Peer-review form attached. A link to this file should be provided in the "Simple peer-review form" column of the cockpit. 1. Process comments. This would be carried out typically by the owner of the FI-WARE GE Open Specifications. This would imply: * generate a temporary draft by means of accepting/rejecting changes from the commented docx of your specifications * consider general comments in the FI-WARE Peer-review form linked to your FI-WARE GE Open Specifications and introduce changes that you would consider may address them 1. You will generate a new docx by means of implementing step 6 you should upload to the SVN or docman of "FI-WARE Private" and will provide a link to it in column "Revised doc" of the cockpit 2. You will have to update the contents of the public wiki with the contents of the document associated to the revised version It's up to each Chapter Leader to decide how to organize: * Steps 1-4. Some of the Chapter Leaders may prefer to perform these steps by themselves but others may decide to distribute the task associated to each FI-WARE GE Open Specification in his chapter * Step 5. Chapter Leaders will organize the assigned peer-review involving members of his chapter. How he does this is up to him and members of the chapter. They are asked to fill the column title "Assigned reviewer" to communicate who has been assigned the task to review a given doc. Note that you can start the review of an Open Specification as soon as the file is available (i.e., there is a link available in column "Doc to review" of the Peer-Review cockpit. * Steps 6-8. I can imagine that the owner of a FI-WARE GE Open Specification will carry out these steps. However, the Chapter Leader may decide to carry out the update of the wiki, or distribute the task and assign it also to owners of each FI-WARE GE Open Specification VERY IMPORTANT: * PLEASE try to make steps 1-4 as soon as possible. Our experience is that this could be performed in maximum one hour per GE specification, probably much less. The sooner you make docx for review available on the cockpit, the sooner someone will review it. * Step 8 is quite important because we plan to submit the final deliverables based on docx documents that will be generated once again from the wiki. Therefore, if you don't update the wiki, the resubmitted deliverable will go without your changes. SAP is working in a number of tools and processes that will help to produce the docx documents that will be finally submitted and I would like to thank them for the work they are doing in this respect. Milestones for the peer-review are the following: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Assignment of peer-reviewers is as follows: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Hope it works. Please try to make this final push. We face a critical milestone in the project that has to do with delivering a complete and rich set of FI-WARE Open Specifications. How they will be judged by reviewers will play a relevant role in our next, critical, review. Don't hesitate to ask any question or doubt. Last but not least, I would like to thank SAP for the support in defining this process and the work they are doing developing the tools that will try to automate the final generation of deliverables as much as possible. 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 -------- Original Message -------- Subject: [Fiware-wpa] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Date: Thu, 11 Oct 2012 08:59:09 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ 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 ________________________________ 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 -------------- A non-text attachment was scrubbed... Name: Comments I2ND Architecture.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 24994 bytes Desc: Comments I2ND Architecture.docx 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 Tobias.Jacobs at neclab.eu Mon Oct 15 10:26:25 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 15 Oct 2012 08:26:25 +0000 Subject: [Fiware-iot] .docx linked to the FI-WARE IoT Backend Things Management GE uploaded and ready for revision In-Reply-To: <50785C85.3030109@tid.es> References: <50785C85.3030109@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D38EC2135@DAPHNIS.office.hd> Hi Thierry and Juanjo, Thanks for creating the doc, Juanjo! I have to admit that I do not understand what my role in the review process is - as far as I understood it is the WPLs who organize the review process (and then possibly delegate some of the work). Best Tobias -----Original Message----- From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Freitag, 12. Oktober 2012 20:08 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; thierry.nagellen at orange.com Subject: .docx linked to the FI-WARE IoT Backend Things Management GE uploaded and ready for revision Hi Tobias and Thierry, I have created the .docx of the FI-WARE IoT Backend Things Management GE and uploaded it to the docman system in FusionForge. I have updated the Peer-review cockpit to mark that it is ready for the last peer-review. I will try in the remaining of today to upload the other GEs in the IoT chapter. Hope it helps. I will be announcing their availability as soon as they have been uploaded. Cheers, -- 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 From Tobias.Jacobs at neclab.eu Mon Oct 15 11:40:48 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 15 Oct 2012 09:40:48 +0000 Subject: [Fiware-iot] WP5 status Message-ID: <8755F290097BD941865DC4245B335D2D38EC21F2@DAPHNIS.office.hd> Dear WP5 Members, We have not really heard from each others for a couple of weeks. Maybe it would be good to have a phone call this week. Could Orange organize it? Suggested items for the Agenda would be: - Status of the deliverables that need to be done for the next review - GE status, WP5 integration plan - Scenario and plan for the demo to be conducted for the review (?) Thanks and best regards Salvatore and Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 12 20:08:05 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 12 Oct 2012 20:08:05 +0200 Subject: [Fiware-iot] .docx linked to the FI-WARE IoT Backend Things Management GE uploaded and ready for revision Message-ID: <50785C85.3030109@tid.es> Hi Tobias and Thierry, I have created the .docx of the FI-WARE IoT Backend Things Management GE and uploaded it to the docman system in FusionForge. I have updated the Peer-review cockpit to mark that it is ready for the last peer-review. I will try in the remaining of today to upload the other GEs in the IoT chapter. Hope it helps. I will be announcing their availability as soon as they have been uploaded. Cheers, -- 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 From jhierro at tid.es Fri Oct 12 07:23:17 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 12 Oct 2012 07:23:17 +0200 Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY In-Reply-To: <5073BF60.4020201@tid.es> References: <5073BF60.4020201@tid.es> Message-ID: <5077A945.9020908@tid.es> Hi all, You may have probably received an email with the detailed instructions we will follow to carry out the third peer-review of FI-WARE GE Open Specifications. Previous to that, there was a step that each of the chapters had to carry out that implied a deep re-structuring of the wiki. This was decided several weeks ago and October 9-10 were days that were booked to perform the necessary steps in this re-structuring. Find below the email I sent to the WPLs/WPAs on the matter. Unfortunately, Thierry was sick and couldn't forward all this to you. Besides, I didn't realize myself because otherwise I may have forwarded the emails also to the IoT list. Nevertheless, don't worry, I'll take the action of re-structuring the contents of the wiki regarding the IoT chapter and get it ready along this morning (you owe me a beer ;-). The only info that I really need is who should be listed as owner of the specifications of each GE. My educated guess is the following: * Backend Things Management GE: NEC, Telefonica I+D * Backend Device Management GE: Orange, Telef?nica I+D, NSN (we will need to consult Lorant or Denes) * Gateway Device Management GE: Ericsson * Gateway Data Handling GE: Orange * Gateway Protocol Adapter GE: Orange, Ericsson, Telecom Italia PLEASE, CONFIRM the above assumptions are correct. This is needed because we will include a copyright section on the Architecture Description and Open Specification documents linked to each of the FI-WARE GEs. A Legal Notice will also be added (the same we added to the API specs) which makes reference to the "copyright owners". Note that copyright only applies to specifications (and architecture descriptions). Cheers, -- 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 -------- Original Message -------- Subject: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Date: Tue, 09 Oct 2012 08:08:32 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu , Sandfuchs, Thorsten Hi all, This is a reminder that you have until EOB TODAY to re-structure the contents of the wiki that relate to GEs in your chapter. The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: 1. You should include a Copyright section which lists the copyright holders 2. You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications 3. You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. 4. Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. 5. Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) 6. On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. Indeed, it may not be a bad idea that each chapter leader takes care of the whole chapter revision himself or with the help of a few people. It's up to you. I have already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. That will save you some time. It took me a while (not more than half an hour) but I volunteered to speed up the overall process. If you have any doubt, don't hesitate to ask Thorsten (in copy of this email) or me 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 12 08:12:41 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 12 Oct 2012 08:12:41 +0200 Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY In-Reply-To: <5077A945.9020908@tid.es> References: <5073BF60.4020201@tid.es> <5077A945.9020908@tid.es> Message-ID: <5077B4D9.5010709@tid.es> Hi, I finished the exercise and now you can get the list of FI-WARE GE Open Specifications linked to the IoT Chapter at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Internet_of_Things_.28IoT.29_Services_Enablement_Chapter Please, don't forget to confirm me what are the names of the companies we should list in the copyright sections of each specification. Last but not least, there is something that has called my attention ... I haven't seen any API specified regarding the IoT Gateway Protocol Adapter GE ... Is this correct ? It is the only FI-WARE GE that I know which doesn't export any API ... Cheers, -- 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 On 12/10/12 07:23, Juanjo Hierro wrote: Hi all, You may have probably received an email with the detailed instructions we will follow to carry out the third peer-review of FI-WARE GE Open Specifications. Previous to that, there was a step that each of the chapters had to carry out that implied a deep re-structuring of the wiki. This was decided several weeks ago and October 9-10 were days that were booked to perform the necessary steps in this re-structuring. Find below the email I sent to the WPLs/WPAs on the matter. Unfortunately, Thierry was sick and couldn't forward all this to you. Besides, I didn't realize myself because otherwise I may have forwarded the emails also to the IoT list. Nevertheless, don't worry, I'll take the action of re-structuring the contents of the wiki regarding the IoT chapter and get it ready along this morning (you owe me a beer ;-). The only info that I really need is who should be listed as owner of the specifications of each GE. My educated guess is the following: * Backend Things Management GE: NEC, Telefonica I+D * Backend Device Management GE: Orange, Telef?nica I+D, NSN (we will need to consult Lorant or Denes) * Gateway Device Management GE: Ericsson * Gateway Data Handling GE: Orange * Gateway Protocol Adapter GE: Orange, Ericsson, Telecom Italia PLEASE, CONFIRM the above assumptions are correct. This is needed because we will include a copyright section on the Architecture Description and Open Specification documents linked to each of the FI-WARE GEs. A Legal Notice will also be added (the same we added to the API specs) which makes reference to the "copyright owners". Note that copyright only applies to specifications (and architecture descriptions). Cheers, -- 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 -------- Original Message -------- Subject: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Date: Tue, 09 Oct 2012 08:08:32 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu , Sandfuchs, Thorsten Hi all, This is a reminder that you have until EOB TODAY to re-structure the contents of the wiki that relate to GEs in your chapter. The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: 1. You should include a Copyright section which lists the copyright holders 2. You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications 3. You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. 4. Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. 5. Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) 6. On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. Indeed, it may not be a bad idea that each chapter leader takes care of the whole chapter revision himself or with the help of a few people. It's up to you. I have already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. That will save you some time. It took me a while (not more than half an hour) but I volunteered to speed up the overall process. If you have any doubt, don't hesitate to ask Thorsten (in copy of this email) or me 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri Oct 12 16:20:27 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 12 Oct 2012 16:20:27 +0200 Subject: [Fiware-iot] Test - Please discard Message-ID: <5078272B.3040901@tid.es> -- 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 From Tobias.Jacobs at neclab.eu Tue Oct 16 09:17:22 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 16 Oct 2012 07:17:22 +0000 Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY In-Reply-To: <5077A945.9020908@tid.es> References: <5073BF60.4020201@tid.es> <5077A945.9020908@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D38EC2358@DAPHNIS.office.hd> Hi Juanjo, Thanks a lot for your efforts! Yes, I can confirm NEC's partial ownership of the Things Management GE. Best Tobias PS: _.._..,_,_ ( ) ]~,"-.-~~[ .=])' (; ([ | ]:: ' [ '=]): .) ([ |:: ' | ~~----~~ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: Freitag, 12. Oktober 2012 07:23 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Hi all, You may have probably received an email with the detailed instructions we will follow to carry out the third peer-review of FI-WARE GE Open Specifications. Previous to that, there was a step that each of the chapters had to carry out that implied a deep re-structuring of the wiki. This was decided several weeks ago and October 9-10 were days that were booked to perform the necessary steps in this re-structuring. Find below the email I sent to the WPLs/WPAs on the matter. Unfortunately, Thierry was sick and couldn't forward all this to you. Besides, I didn't realize myself because otherwise I may have forwarded the emails also to the IoT list. Nevertheless, don't worry, I'll take the action of re-structuring the contents of the wiki regarding the IoT chapter and get it ready along this morning (you owe me a beer ;-). The only info that I really need is who should be listed as owner of the specifications of each GE. My educated guess is the following: * Backend Things Management GE: NEC, Telefonica I+D * Backend Device Management GE: Orange, Telef?nica I+D, NSN (we will need to consult Lorant or Denes) * Gateway Device Management GE: Ericsson * Gateway Data Handling GE: Orange * Gateway Protocol Adapter GE: Orange, Ericsson, Telecom Italia PLEASE, CONFIRM the above assumptions are correct. This is needed because we will include a copyright section on the Architecture Description and Open Specification documents linked to each of the FI-WARE GEs. A Legal Notice will also be added (the same we added to the API specs) which makes reference to the "copyright owners". Note that copyright only applies to specifications (and architecture descriptions). Cheers, -- 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 -------- Original Message -------- Subject: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Date: Tue, 09 Oct 2012 08:08:32 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu , Sandfuchs, Thorsten Hi all, This is a reminder that you have until EOB TODAY to re-structure the contents of the wiki that relate to GEs in your chapter. The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: 1. You should include a Copyright section which lists the copyright holders 2. You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications 3. You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. 4. Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. 5. Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) 6. On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. Indeed, it may not be a bad idea that each chapter leader takes care of the whole chapter revision himself or with the help of a few people. It's up to you. I have already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. That will save you some time. It took me a while (not more than half an hour) but I volunteered to speed up the overall process. If you have any doubt, don't hesitate to ask Thorsten (in copy of this email) or me 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maarten.los at atosresearch.eu Tue Oct 16 10:50:33 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Tue, 16 Oct 2012 10:50:33 +0200 Subject: [Fiware-iot] I: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5A135088B@GRFMBX702BA020.griffon.local> References: <50770372.4030804@tid.es> <507795E8.60806@tid.es> <36A93B31228D3B49B691AD31652BCAE9A5A135088B@GRFMBX702BA020.griffon.local> Message-ID: <461EDDC0FEB25648B2FE8B0145848AA50165919E@INTMAIL02.es.int.atosorigin.com> Hi Sabrina, From our side, we haven?t looked at the I2ND doc, I think this was for the second review round. If I understand correctly, in the third round IoT is tasked with reviewing the Data chapter. Not sure how this is coordinated in the end, but hopefully things will become clearer in tomorrow?s telco. Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Guerra Sabrina Sent: lunes, 15 de octubre de 2012 9:55 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] I: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi all, Regarding the email Juanjo sent about the internal peer-review, we recently made a review of wp I2ND (see the attachment). Does anybody else had the chance to have a look at I2ND documentation? In this case we can merge your comments and have a review including different points of view. Best regards, Sabrina Da: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerd? 12 ottobre 2012 06:01 A: fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi, You may have received an email from your WPL or WPA regarding instructions about how we are going to tackle the third and final peer review of the FI-WARE GE Open Specifications that we have to resubmit by November 2nd at the latest (see attachment) IMPORTANT NOTE: We rather NEED that you to carry out a peer-review that focuses on how suitable the contents are. We are afraid that some of the peer-reviews carry out so far were mostly "editorial", i.e., polishing the English, highlighting issues regarding the structure, etc. We need that people review the document from the perspective of a developer or a potential implementer of the spec and point out what you don't understand, what you miss, etc. The intend of this message is twofold. First, make sure it arrives without further delays in your inbox. Second, add a number of enhancements to the process described in the original email that hopefully will allow to make it faster and more efficient. The enhancements have to do with trying to carry out the peer-review using docx files rather than reading the wiki and providing a list of change requests in a separate form. This would allow to drop out the part of the revision form that I sent earlier which had to do with providing detailed editorial comments. Please find attached the revised form. The following is a description of the whole process with the suggested enhancements. If you hadn't read the original email, you just need to read this. For every FI-WARE GE Open Specification (as listed in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications), we will have to carry out the following steps. 1. Generate docx-version of each of the FI-WARE GE Open Specifications to ease the review. There are multiple ways for doing so and it is up to each Chapter to select its preferred one, but here you are a simple set of steps you can follow to generate a docx version (I have used this personally and have found it rather straightforward): 1. Create a document in Google docs (I hope you have an account, otherwise agree with your WPL on how to get access to one or come back to us :-) 2. Go to the wiki page of the deliverable. Don't forget to access it in "read" mode (i.e., not logged in FusionForge) because that would avoid copying the "edits" 3. Copy and Paste directly from the Wiki page into the Google Docs. Notes: * You have to split this in several steps, because Google docs gets blocked if you try to copy&paste too many pages with too many figures. * Don't forget to add the API specs. Typically, you have to first copy&paste what is in the first-level FI-WARE GE Open Specification wiki page, then navigate to each API specification wiki page and copy and paste the contents. 4. Once the document is generated, you can save it as a Word docx in your local PC. 5. Run a quick check through the docx file fixing some easy-to-solve questions such as adjusting size of figures, doing some pagination which could easy reading, etc. Please, don't try to make it perfect, we just need a version on which you may apply changes and track those changes with the standard MS Word change control tools. 2. Upload the generated file in either SVN or the docman of the "FI-WARE Private" project in FusionForge (whatever tool you prefer) 3. Add the link to the docx file in SVN or docman to the column "Doc to review" corresponding to the FI-WARE GE in the following shared spreadsheet in Google that we will use as cockpit for the following-up the whole process: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc 4. Sent an email to the WPL of the reviewing chapter so that they know that the docx associated to the FI-WARE GE Open Specification is available for review. Please, don't wait until the rest of docs associated to other FI-WARE Open Specifications in your same chapter are uploaded. Leaders of reviewing chapters are also asked to check when there are new documents to review from time to time. 5. Carry out the review you have been assigned. Reviewers would be required to generate two files, that they should upload again to SVN or docman (whatever you prefer) and link from the Google cockpit. If you are a reviewer, please don't wait until you have both. Please upload each as soon as it is available and inform the leader of the chapter being reviewed that you have done so: 1. A commented docx for the deliverable which would include all comments under change control. A link to this file should be provided in the "Commented doc" column of the cockpit. 2. the simple FI-WARE Peer-review form attached. A link to this file should be provided in the "Simple peer-review form" column of the cockpit. 1. Process comments. This would be carried out typically by the owner of the FI-WARE GE Open Specifications. This would imply: 1. generate a temporary draft by means of accepting/rejecting changes from the commented docx of your specifications 2. consider general comments in the FI-WARE Peer-review form linked to your FI-WARE GE Open Specifications and introduce changes that you would consider may address them 1. You will generate a new docx by means of implementing step 6 you should upload to the SVN or docman of "FI-WARE Private" and will provide a link to it in column "Revised doc" of the cockpit 2. You will have to update the contents of the public wiki with the contents of the document associated to the revised version It's up to each Chapter Leader to decide how to organize: * Steps 1-4. Some of the Chapter Leaders may prefer to perform these steps by themselves but others may decide to distribute the task associated to each FI-WARE GE Open Specification in his chapter * Step 5. Chapter Leaders will organize the assigned peer-review involving members of his chapter. How he does this is up to him and members of the chapter. They are asked to fill the column title "Assigned reviewer" to communicate who has been assigned the task to review a given doc. Note that you can start the review of an Open Specification as soon as the file is available (i.e., there is a link available in column "Doc to review" of the Peer-Review cockpit. * Steps 6-8. I can imagine that the owner of a FI-WARE GE Open Specification will carry out these steps. However, the Chapter Leader may decide to carry out the update of the wiki, or distribute the task and assign it also to owners of each FI-WARE GE Open Specification VERY IMPORTANT: * PLEASE try to make steps 1-4 as soon as possible. Our experience is that this could be performed in maximum one hour per GE specification, probably much less. The sooner you make docx for review available on the cockpit, the sooner someone will review it. * Step 8 is quite important because we plan to submit the final deliverables based on docx documents that will be generated once again from the wiki. Therefore, if you don't update the wiki, the resubmitted deliverable will go without your changes. SAP is working in a number of tools and processes that will help to produce the docx documents that will be finally submitted and I would like to thank them for the work they are doing in this respect. Milestones for the peer-review are the following: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Assignment of peer-reviewers is as follows: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Hope it works. Please try to make this final push. We face a critical milestone in the project that has to do with delivering a complete and rich set of FI-WARE Open Specifications. How they will be judged by reviewers will play a relevant role in our next, critical, review. Don't hesitate to ask any question or doubt. Last but not least, I would like to thank SAP for the support in defining this process and the work they are doing developing the tools that will try to automate the final generation of deliverables as much as possible. 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 -------- Original Message -------- Subject: [Fiware-wpa] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Date: Thu, 11 Oct 2012 08:59:09 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From t.elsaleh at surrey.ac.uk Tue Oct 16 12:19:45 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Tue, 16 Oct 2012 11:19:45 +0100 Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY In-Reply-To: <5077A945.9020908@tid.es> References: <5073BF60.4020201@tid.es> <5077A945.9020908@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA5960B6BF5@EXMB05CMS.surrey.ac.uk> Hello Juanjo, I'm not sure about ownership, but this is just to reaffirm USurrey's contribution (i.e. Discovery engine) towards the Things Mgmt GE for the Second release. Best regards, Tarek ------------------------------------------------------------- Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 ------------------------------------------------------------- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro Sent: 12 October 2012 06:23 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Fwd: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Hi all, You may have probably received an email with the detailed instructions we will follow to carry out the third peer-review of FI-WARE GE Open Specifications. Previous to that, there was a step that each of the chapters had to carry out that implied a deep re-structuring of the wiki. This was decided several weeks ago and October 9-10 were days that were booked to perform the necessary steps in this re-structuring. Find below the email I sent to the WPLs/WPAs on the matter. Unfortunately, Thierry was sick and couldn't forward all this to you. Besides, I didn't realize myself because otherwise I may have forwarded the emails also to the IoT list. Nevertheless, don't worry, I'll take the action of re-structuring the contents of the wiki regarding the IoT chapter and get it ready along this morning (you owe me a beer ;-). The only info that I really need is who should be listed as owner of the specifications of each GE. My educated guess is the following: * Backend Things Management GE: NEC, Telefonica I+D * Backend Device Management GE: Orange, Telef?nica I+D, NSN (we will need to consult Lorant or Denes) * Gateway Device Management GE: Ericsson * Gateway Data Handling GE: Orange * Gateway Protocol Adapter GE: Orange, Ericsson, Telecom Italia PLEASE, CONFIRM the above assumptions are correct. This is needed because we will include a copyright section on the Architecture Description and Open Specification documents linked to each of the FI-WARE GEs. A Legal Notice will also be added (the same we added to the API specs) which makes reference to the "copyright owners". Note that copyright only applies to specifications (and architecture descriptions). Cheers, -- 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 -------- Original Message -------- Subject: IMPORTANT REMINDER: Re-structuring of the public wiki contents to be finished by EOB TODAY Date: Tue, 09 Oct 2012 08:08:32 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu , Sandfuchs, Thorsten Hi all, This is a reminder that you have until EOB TODAY to re-structure the contents of the wiki that relate to GEs in your chapter. The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: 1. You should include a Copyright section which lists the copyright holders 2. You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications 3. You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. 4. Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. 5. Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) 6. On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. Indeed, it may not be a bad idea that each chapter leader takes care of the whole chapter revision himself or with the help of a few people. It's up to you. I have already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. That will save you some time. It took me a while (not more than half an hour) but I volunteered to speed up the overall process. If you have any doubt, don't hesitate to ask Thorsten (in copy of this email) or me 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Oct 17 09:12:58 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 17 Oct 2012 07:12:58 +0000 Subject: [Fiware-iot] WP5 status In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC21F2@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38EC21F2@DAPHNIS.office.hd> Message-ID: <18227_1350457979_507E5A7B_18227_16549_1_976A65C5A08ADF49B9A8523F7F81925C067149@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I apologize for the delay but because of some serious health concerns I was not available. For who are available we will have the IoT weekly meeting today (Thanks Tobias for your email) with powwownow facilities: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf pin code : 028919 We have a meeting tomorrow between WPL/WPA to discuss the scenario plan for the review so all ideas are welcome. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : lundi 15 octobre 2012 11:41 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] WP5 status Dear WP5 Members, We have not really heard from each others for a couple of weeks. Maybe it would be good to have a phone call this week. Could Orange organize it? Suggested items for the Agenda would be: - Status of the deliverables that need to be done for the next review - GE status, WP5 integration plan - Scenario and plan for the demo to be conducted for the review (?) Thanks and best regards Salvatore and Tobias _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabioluigi.bellifemine at telecomitalia.it Tue Oct 16 14:15:01 2012 From: fabioluigi.bellifemine at telecomitalia.it (Bellifemine Fabio Luigi) Date: Tue, 16 Oct 2012 14:15:01 +0200 Subject: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware References: Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C203@GRFMBX707BA020.griffon.local> Dear Fi-ware partners, I am pleased to inform you that the ZigBee Gateway Device software module was released in Open source under the Apache 2 license. The web page of the project ZigBee4OSGi http://zb4o.aaloa.org/ includes now the logo of FiWare and a reference to the project as one of the contributors. You are welcome to disseminate this result of Telecom Italia in FiWare. Best regards, Fabio Bellifemine From: Bellifemine Fabio Luigi Sent: luned? 24 settembre 2012 12:54 To: 'thierry.nagellen at orange.com'; 'fiware-iot at lists.fi-ware.eu' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; Borean Claudio; Ranalli Andrea Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry and Fi-ware WP5 partners, As anticipated in February, we are pleased to inform you that we are now ready to release in open source our ZigBee Gateway Device implementation. It is the software that Sabrina already provided as contribution of Telecom Italia to WP5. The software will be released by Telecom Italia under the Apache 2 license. In order to properly acknowledge the Fi-ware activities, we would like to add the following sentence to the Notice file and to the released manual: This work of Telecom Italia s.p.a. has been partly supported by the European Commission under the EU's Seventh Framework Programme (FP7) within the context of the WP5 of the FP7-285248 FI-WARE project (http://www.fi-ware.eu/) We welcome any suggestion and recommendation. Best regards, Fabio Bellifemine. From: Bellifemine Fabio Luigi Sent: 14 February 2012 14:59 To: 'thierry.nagellen at orange.com' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com; Elia Gabriele Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry, we analyzed your proposal. We do also think that Fi-Ware has the unique opportunity to launch a new ecosystem and that it should absolutely be based upon worldwide well-defined standards. We believe that our ETSI M2M-like implementation is not appropriate for Fi-Ware as there are still many differences with ETSI M2M and as it is a vertical implementation strictly based upon the requirements of the Energy at home project. On the other hand we feel that we could help Fi-Ware to fill a gap in communicating with Things. We believe that the project is very concentrated on the platform (and that is a strength) with less emphasis and attention on how such a platform will communicate with the Things and with which Things it should communicate (and that might be a possible weakness of the project). We want then to propose you to integrate our implementation of the ZigBee Network Device specifications (see http://www.zigbee.org/). Such a standard specifies how the ZigBee world of Things should interact with the IP world and, in particular, with a platform through a gateway. It is a RESTful interface that every standard ZigBee Gateway Device is required to expose. One of the work items of ETSI M2M is exactly the harmonization with ZigBee Gateway Device specifications. By using such an interface the Fi-Ware platform will be able to communicate with any ZigBee device independently on the specific application profile (be it home automation, smart energy, building automation, health care, or others). That is - in our view - a big benefit and value to Fi-Ware. If you look at the ZigBee site (sections on products), there are today a few hundreds of ZigBee compliant products offered by several companies. Our implementation is based upon two sw modules: - GAL. This module shall be hosted on the gateway device. It implements the ZigBee specifications and it is the layer responsible for inter-working between wireless ZigBee devices and IP world. It exposes a RESTful interface to the cloud platform. It also implement all the state machines required by the standard in order to implement network discovery, device discovery, device and network configuration, communication with devices, ... This module is provided to Fi-Ware as background of Telecom Italia free for the usages of the project and under a FRAND license later (fair, reasonable and non discriminatory). - jGAL. This module shall be hosted on the platform or, eventually, also on OSGi gateway devices. It communicates via REST with the ZigBee gateways according to the ZigBee specifications. On the other side it shall provide a simple Java in-process interface. We are pleased to work on this module as foreground of Telecom Italia in Fi-Ware. We believe that this module can also become the basis for an open source project of Fi-Ware that we are pleased to contribute to launch. The GAL and a basic implementation of jGAL can surely be provided by Telecom Italia by April 2012 as planned by you. I am available for a phone call to discuss in more detail this proposal. Thank you, Fabio Bellifemine. From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: 31 January 2012 15:07 To: Bellifemine Fabio Luigi; Elia Gabriele Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com Subject: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear M Bellifemine, Dear M Elia, We had last week in Madrid the General Meeting of FI-Ware, the Core Platform project from the Public-Private-Partnership Future Internet, a FP7 program initiative where 21 major European ICT partners collaborate. Some of the strategic objectives of this program, and especially FI-Ware as the major technical project, are to push some standards and to launch a new ecosystem, typically based on a developers' community, to adopt quickly these standards and develop new applications on the top of them. I am the Work Package leader of the "Internet of Things" technical area in FI-Ware where we managed in October 2011 between several standards in our area to identify which could be useful regarding our architecture. We reached a consensus to use two of them: ? OMA-NGSI 9&10, which are following meta-data approach and would support a common way to exchange some data between several components ? ETSI-M2M where a stable version is now available and is obviously related to Internet of Things For this second standard, main actors as Ericsson, Nokia Siemens Networks, Orange and of course Telecom Italia agreed to provide an ETSI M2M interface on their assets they expect to improve through the FI-Ware project. As you can understand, it would be very fruitful for the ICT community to have such main actors providing a common interface and demonstrate how interoperability would be easier in the Future. Based on the exchanges we had last week with Ms Sabrina Guerra and M Gian Piero Fici, and as they explained us before, Telecom Italia achieved a first ETSI M2M implementation for an internal research project in the Energy area. We would invite you to study the following proposals to improve this ETSI M2M implementation: 1. Full Restful binding: as your implementation is the first one, we understood that it is not fully Restful compliant. The FI-Ware partners involved in this subject propose to work on a full RESTful binding (REST in the relevant interface for FI-Ware). We could contribute altogether to build this RESTful interface which is one of our objectives for end of April 2012 and share it to demonstrate interoperability. In this case, our proposal is that, based on the consortium agreement all partners signed, we could launch an internal FI-Ware internal open-source community between Telecom Italia, Orange, NSN and Ericsson, community which could be open to other FI-Ware Internet of Things partners if they want to implement this interface. We could increase in this case the development effort you manage for the time being by 2 or 3. In this case we would be able to demonstrate concretely a first interoperability in April and emphasize a lot standard adoption to the European ICT community, which should be a great result for Europe and ETSI. 2. If we are successful, our second proposal would be to transform this first implementation into a Reference Implementation. We would suggest maintaining alive this Reference Implementation, to extend the Open Source community and to launch an official one, open to all developers. This community should be supported by FI-Ware and prepare by FI-Ware. This community would provide a professional Reference Implementation, following ETSI M2M improvement, keeping Telecom Operators and their suppliers involved in, and provide at the end low-cost solutions. As you can understand, we think that it is "time to market" now for ETSI M2M and we expect to share among the partners developments and launch ETSI M2M as soon as possible for the best of our markets. Thank you for your feedback. 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: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 sabrina.guerra at telecomitalia.it Wed Oct 17 09:29:46 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 17 Oct 2012 09:29:46 +0200 Subject: [Fiware-iot] R: WP5 status In-Reply-To: <18227_1350457979_507E5A7B_18227_16549_1_976A65C5A08ADF49B9A8523F7F81925C067149@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D38EC21F2@DAPHNIS.office.hd> <18227_1350457979_507E5A7B_18227_16549_1_976A65C5A08ADF49B9A8523F7F81925C067149@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5A15AC4E9@GRFMBX702BA020.griffon.local> Hi all, At what time is the conference call? Best regards Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 17 ottobre 2012 09:13 A: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Oggetto: Re: [Fiware-iot] WP5 status Dear all, I apologize for the delay but because of some serious health concerns I was not available. For who are available we will have the IoT weekly meeting today (Thanks Tobias for your email) with powwownow facilities: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf pin code : 028919 We have a meeting tomorrow between WPL/WPA to discuss the scenario plan for the review so all ideas are welcome. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : lundi 15 octobre 2012 11:41 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] WP5 status Dear WP5 Members, We have not really heard from each others for a couple of weeks. Maybe it would be good to have a phone call this week. Could Orange organize it? Suggested items for the Agenda would be: - Status of the deliverables that need to be done for the next review - GE status, WP5 integration plan - Scenario and plan for the demo to be conducted for the review (?) Thanks and best regards Salvatore and Tobias _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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 thierry.nagellen at orange.com Wed Oct 17 09:30:45 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 17 Oct 2012 07:30:45 +0000 Subject: [Fiware-iot] WP5 status In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5A15AC4E9@GRFMBX702BA020.griffon.local> References: <8755F290097BD941865DC4245B335D2D38EC21F2@DAPHNIS.office.hd> <18227_1350457979_507E5A7B_18227_16549_1_976A65C5A08ADF49B9A8523F7F81925C067149@PEXCVZYM13.corporate.adroot.infra.ftgroup> <36A93B31228D3B49B691AD31652BCAE9A5A15AC4E9@GRFMBX702BA020.griffon.local> Message-ID: <25272_1350459046_507E5EA6_25272_1704_1_976A65C5A08ADF49B9A8523F7F81925C067190@PEXCVZYM13.corporate.adroot.infra.ftgroup> I propose the same timeslot as usual : 10h00 BR Thierry De : Guerra Sabrina [mailto:sabrina.guerra at telecomitalia.it] Envoy? : mercredi 17 octobre 2012 09:30 ? : NAGELLEN Thierry OLNC/OLPS; Tobias Jacobs; fiware-iot at lists.fi-ware.eu Objet : R: [Fiware-iot] WP5 status Hi all, At what time is the conference call? Best regards Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 17 ottobre 2012 09:13 A: Tobias Jacobs; fiware-iot at lists.fi-ware.eu Oggetto: Re: [Fiware-iot] WP5 status Dear all, I apologize for the delay but because of some serious health concerns I was not available. For who are available we will have the IoT weekly meeting today (Thanks Tobias for your email) with powwownow facilities: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf pin code : 028919 We have a meeting tomorrow between WPL/WPA to discuss the scenario plan for the review so all ideas are welcome. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : lundi 15 octobre 2012 11:41 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] WP5 status Dear WP5 Members, We have not really heard from each others for a couple of weeks. Maybe it would be good to have a phone call this week. Could Orange organize it? Suggested items for the Agenda would be: - Status of the deliverables that need to be done for the next review - GE status, WP5 integration plan - Scenario and plan for the demo to be conducted for the review (?) Thanks and best regards Salvatore and Tobias _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. -------------- 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 fano.ramparany at orange.com Wed Oct 17 12:36:13 2012 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Wed, 17 Oct 2012 10:36:13 +0000 Subject: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware In-Reply-To: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C203@GRFMBX707BA020.griffon.local> References: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C203@GRFMBX707BA020.griffon.local> Message-ID: <10830_1350470175_507E8A1F_10830_2197_1_c0f3a263-3cb0-4d19-bb1e-5c80cc0f9b42@PEXCVZYH02.corporate.adroot.infra.ftgroup> Dear Fabio, Thank you for your announcement. We would like to test and use your module in the context of the OUTSMART FI PPP UC project, and would appreciate if you could tell us how to proceed. Thank you very much in advance, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Bellifemine Fabio Luigi Envoy? : mardi 16 octobre 2012 14:15 ? : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc : Borean Claudio; Ranalli Andrea Objet : Re: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fi-ware partners, I am pleased to inform you that the ZigBee Gateway Device software module was released in Open source under the Apache 2 license. The web page of the project ZigBee4OSGi http://zb4o.aaloa.org/ includes now the logo of FiWare and a reference to the project as one of the contributors. You are welcome to disseminate this result of Telecom Italia in FiWare. Best regards, Fabio Bellifemine From: Bellifemine Fabio Luigi Sent: luned? 24 settembre 2012 12:54 To: 'thierry.nagellen at orange.com'; 'fiware-iot at lists.fi-ware.eu' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; Borean Claudio; Ranalli Andrea Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry and Fi-ware WP5 partners, As anticipated in February, we are pleased to inform you that we are now ready to release in open source our ZigBee Gateway Device implementation. It is the software that Sabrina already provided as contribution of Telecom Italia to WP5. The software will be released by Telecom Italia under the Apache 2 license. In order to properly acknowledge the Fi-ware activities, we would like to add the following sentence to the Notice file and to the released manual: This work of Telecom Italia s.p.a. has been partly supported by the European Commission under the EU's Seventh Framework Programme (FP7) within the context of the WP5 of the FP7-285248 FI-WARE project (http://www.fi-ware.eu/) We welcome any suggestion and recommendation. Best regards, Fabio Bellifemine. From: Bellifemine Fabio Luigi Sent: 14 February 2012 14:59 To: 'thierry.nagellen at orange.com' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com; Elia Gabriele Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry, we analyzed your proposal. We do also think that Fi-Ware has the unique opportunity to launch a new ecosystem and that it should absolutely be based upon worldwide well-defined standards. We believe that our ETSI M2M-like implementation is not appropriate for Fi-Ware as there are still many differences with ETSI M2M and as it is a vertical implementation strictly based upon the requirements of the Energy at home project. On the other hand we feel that we could help Fi-Ware to fill a gap in communicating with Things. We believe that the project is very concentrated on the platform (and that is a strength) with less emphasis and attention on how such a platform will communicate with the Things and with which Things it should communicate (and that might be a possible weakness of the project). We want then to propose you to integrate our implementation of the ZigBee Network Device specifications (see http://www.zigbee.org/). Such a standard specifies how the ZigBee world of Things should interact with the IP world and, in particular, with a platform through a gateway. It is a RESTful interface that every standard ZigBee Gateway Device is required to expose. One of the work items of ETSI M2M is exactly the harmonization with ZigBee Gateway Device specifications. By using such an interface the Fi-Ware platform will be able to communicate with any ZigBee device independently on the specific application profile (be it home automation, smart energy, building automation, health care, or others). That is - in our view - a big benefit and value to Fi-Ware. If you look at the ZigBee site (sections on products), there are today a few hundreds of ZigBee compliant products offered by several companies. Our implementation is based upon two sw modules: - GAL. This module shall be hosted on the gateway device. It implements the ZigBee specifications and it is the layer responsible for inter-working between wireless ZigBee devices and IP world. It exposes a RESTful interface to the cloud platform. It also implement all the state machines required by the standard in order to implement network discovery, device discovery, device and network configuration, communication with devices, ... This module is provided to Fi-Ware as background of Telecom Italia free for the usages of the project and under a FRAND license later (fair, reasonable and non discriminatory). - jGAL. This module shall be hosted on the platform or, eventually, also on OSGi gateway devices. It communicates via REST with the ZigBee gateways according to the ZigBee specifications. On the other side it shall provide a simple Java in-process interface. We are pleased to work on this module as foreground of Telecom Italia in Fi-Ware. We believe that this module can also become the basis for an open source project of Fi-Ware that we are pleased to contribute to launch. The GAL and a basic implementation of jGAL can surely be provided by Telecom Italia by April 2012 as planned by you. I am available for a phone call to discuss in more detail this proposal. Thank you, Fabio Bellifemine. From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: 31 January 2012 15:07 To: Bellifemine Fabio Luigi; Elia Gabriele Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com Subject: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear M Bellifemine, Dear M Elia, We had last week in Madrid the General Meeting of FI-Ware, the Core Platform project from the Public-Private-Partnership Future Internet, a FP7 program initiative where 21 major European ICT partners collaborate. Some of the strategic objectives of this program, and especially FI-Ware as the major technical project, are to push some standards and to launch a new ecosystem, typically based on a developers' community, to adopt quickly these standards and develop new applications on the top of them. I am the Work Package leader of the "Internet of Things" technical area in FI-Ware where we managed in October 2011 between several standards in our area to identify which could be useful regarding our architecture. We reached a consensus to use two of them: ? OMA-NGSI 9&10, which are following meta-data approach and would support a common way to exchange some data between several components ? ETSI-M2M where a stable version is now available and is obviously related to Internet of Things For this second standard, main actors as Ericsson, Nokia Siemens Networks, Orange and of course Telecom Italia agreed to provide an ETSI M2M interface on their assets they expect to improve through the FI-Ware project. As you can understand, it would be very fruitful for the ICT community to have such main actors providing a common interface and demonstrate how interoperability would be easier in the Future. Based on the exchanges we had last week with Ms Sabrina Guerra and M Gian Piero Fici, and as they explained us before, Telecom Italia achieved a first ETSI M2M implementation for an internal research project in the Energy area. We would invite you to study the following proposals to improve this ETSI M2M implementation: 1. Full Restful binding: as your implementation is the first one, we understood that it is not fully Restful compliant. The FI-Ware partners involved in this subject propose to work on a full RESTful binding (REST in the relevant interface for FI-Ware). We could contribute altogether to build this RESTful interface which is one of our objectives for end of April 2012 and share it to demonstrate interoperability. In this case, our proposal is that, based on the consortium agreement all partners signed, we could launch an internal FI-Ware internal open-source community between Telecom Italia, Orange, NSN and Ericsson, community which could be open to other FI-Ware Internet of Things partners if they want to implement this interface. We could increase in this case the development effort you manage for the time being by 2 or 3. In this case we would be able to demonstrate concretely a first interoperability in April and emphasize a lot standard adoption to the European ICT community, which should be a great result for Europe and ETSI. 2. If we are successful, our second proposal would be to transform this first implementation into a Reference Implementation. We would suggest maintaining alive this Reference Implementation, to extend the Open Source community and to launch an official one, open to all developers. This community should be supported by FI-Ware and prepare by FI-Ware. This community would provide a professional Reference Implementation, following ETSI M2M improvement, keeping Telecom Operators and their suppliers involved in, and provide at the end low-cost solutions. As you can understand, we think that it is "time to market" now for ETSI M2M and we expect to share among the partners developments and launch ETSI M2M as soon as possible for the best of our markets. Thank you for your feedback. 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. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. -------------- 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 fano.ramparany at orange.com Wed Oct 17 16:57:08 2012 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Wed, 17 Oct 2012 14:57:08 +0000 Subject: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware In-Reply-To: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C61D@GRFMBX707BA020.griffon.local> References: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C203@GRFMBX707BA020.griffon.local> <10830_1350470175_507E8A1F_10830_2197_1_c0f3a263-3cb0-4d19-bb1e-5c80cc0f9b42@PEXCVZYH02.corporate.adroot.infra.ftgroup> <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C61D@GRFMBX707BA020.griffon.local> Message-ID: <21249_1350485832_507EC748_21249_3721_1_9b3321c4-d50a-4e5e-8bf6-dff18cb2fd34@PEXCVZYH02.corporate.adroot.infra.ftgroup> Hi Fabio, Thank you for your reply. We'll look forward to it. Best regards, Fano De : Bellifemine Fabio Luigi [mailto:fabioluigi.bellifemine at telecomitalia.it] Envoy? : mercredi 17 octobre 2012 13:02 ? : RAMPARANY Fano OLNC/OLPS; NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc : Borean Claudio; Ranalli Andrea; GRATTARD Gilles OLNC/OLPS; Guerra Sabrina Objet : RE: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fano, thanks for your interest. In a few days the software will be downloadable directly by the ZigBee4OSGi web site. From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: mercoled? 17 ottobre 2012 12:36 To: Bellifemine Fabio Luigi; NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc: Borean Claudio; Ranalli Andrea; GRATTARD Gilles OLNC/OLPS Subject: RE: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fabio, Thank you for your announcement. We would like to test and use your module in the context of the OUTSMART FI PPP UC project, and would appreciate if you could tell us how to proceed. Thank you very much in advance, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Bellifemine Fabio Luigi Envoy? : mardi 16 octobre 2012 14:15 ? : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc : Borean Claudio; Ranalli Andrea Objet : Re: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fi-ware partners, I am pleased to inform you that the ZigBee Gateway Device software module was released in Open source under the Apache 2 license. The web page of the project ZigBee4OSGi http://zb4o.aaloa.org/ includes now the logo of FiWare and a reference to the project as one of the contributors. You are welcome to disseminate this result of Telecom Italia in FiWare. Best regards, Fabio Bellifemine From: Bellifemine Fabio Luigi Sent: luned? 24 settembre 2012 12:54 To: 'thierry.nagellen at orange.com'; 'fiware-iot at lists.fi-ware.eu' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; Borean Claudio; Ranalli Andrea Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry and Fi-ware WP5 partners, As anticipated in February, we are pleased to inform you that we are now ready to release in open source our ZigBee Gateway Device implementation. It is the software that Sabrina already provided as contribution of Telecom Italia to WP5. The software will be released by Telecom Italia under the Apache 2 license. In order to properly acknowledge the Fi-ware activities, we would like to add the following sentence to the Notice file and to the released manual: This work of Telecom Italia s.p.a. has been partly supported by the European Commission under the EU's Seventh Framework Programme (FP7) within the context of the WP5 of the FP7-285248 FI-WARE project (http://www.fi-ware.eu/) We welcome any suggestion and recommendation. Best regards, Fabio Bellifemine. From: Bellifemine Fabio Luigi Sent: 14 February 2012 14:59 To: 'thierry.nagellen at orange.com' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com; Elia Gabriele Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry, we analyzed your proposal. We do also think that Fi-Ware has the unique opportunity to launch a new ecosystem and that it should absolutely be based upon worldwide well-defined standards. We believe that our ETSI M2M-like implementation is not appropriate for Fi-Ware as there are still many differences with ETSI M2M and as it is a vertical implementation strictly based upon the requirements of the Energy at home project. On the other hand we feel that we could help Fi-Ware to fill a gap in communicating with Things. We believe that the project is very concentrated on the platform (and that is a strength) with less emphasis and attention on how such a platform will communicate with the Things and with which Things it should communicate (and that might be a possible weakness of the project). We want then to propose you to integrate our implementation of the ZigBee Network Device specifications (see http://www.zigbee.org/). Such a standard specifies how the ZigBee world of Things should interact with the IP world and, in particular, with a platform through a gateway. It is a RESTful interface that every standard ZigBee Gateway Device is required to expose. One of the work items of ETSI M2M is exactly the harmonization with ZigBee Gateway Device specifications. By using such an interface the Fi-Ware platform will be able to communicate with any ZigBee device independently on the specific application profile (be it home automation, smart energy, building automation, health care, or others). That is - in our view - a big benefit and value to Fi-Ware. If you look at the ZigBee site (sections on products), there are today a few hundreds of ZigBee compliant products offered by several companies. Our implementation is based upon two sw modules: - GAL. This module shall be hosted on the gateway device. It implements the ZigBee specifications and it is the layer responsible for inter-working between wireless ZigBee devices and IP world. It exposes a RESTful interface to the cloud platform. It also implement all the state machines required by the standard in order to implement network discovery, device discovery, device and network configuration, communication with devices, ... This module is provided to Fi-Ware as background of Telecom Italia free for the usages of the project and under a FRAND license later (fair, reasonable and non discriminatory). - jGAL. This module shall be hosted on the platform or, eventually, also on OSGi gateway devices. It communicates via REST with the ZigBee gateways according to the ZigBee specifications. On the other side it shall provide a simple Java in-process interface. We are pleased to work on this module as foreground of Telecom Italia in Fi-Ware. We believe that this module can also become the basis for an open source project of Fi-Ware that we are pleased to contribute to launch. The GAL and a basic implementation of jGAL can surely be provided by Telecom Italia by April 2012 as planned by you. I am available for a phone call to discuss in more detail this proposal. Thank you, Fabio Bellifemine. From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: 31 January 2012 15:07 To: Bellifemine Fabio Luigi; Elia Gabriele Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com Subject: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear M Bellifemine, Dear M Elia, We had last week in Madrid the General Meeting of FI-Ware, the Core Platform project from the Public-Private-Partnership Future Internet, a FP7 program initiative where 21 major European ICT partners collaborate. Some of the strategic objectives of this program, and especially FI-Ware as the major technical project, are to push some standards and to launch a new ecosystem, typically based on a developers' community, to adopt quickly these standards and develop new applications on the top of them. I am the Work Package leader of the "Internet of Things" technical area in FI-Ware where we managed in October 2011 between several standards in our area to identify which could be useful regarding our architecture. We reached a consensus to use two of them: ? OMA-NGSI 9&10, which are following meta-data approach and would support a common way to exchange some data between several components ? ETSI-M2M where a stable version is now available and is obviously related to Internet of Things For this second standard, main actors as Ericsson, Nokia Siemens Networks, Orange and of course Telecom Italia agreed to provide an ETSI M2M interface on their assets they expect to improve through the FI-Ware project. As you can understand, it would be very fruitful for the ICT community to have such main actors providing a common interface and demonstrate how interoperability would be easier in the Future. Based on the exchanges we had last week with Ms Sabrina Guerra and M Gian Piero Fici, and as they explained us before, Telecom Italia achieved a first ETSI M2M implementation for an internal research project in the Energy area. We would invite you to study the following proposals to improve this ETSI M2M implementation: 1. Full Restful binding: as your implementation is the first one, we understood that it is not fully Restful compliant. The FI-Ware partners involved in this subject propose to work on a full RESTful binding (REST in the relevant interface for FI-Ware). We could contribute altogether to build this RESTful interface which is one of our objectives for end of April 2012 and share it to demonstrate interoperability. In this case, our proposal is that, based on the consortium agreement all partners signed, we could launch an internal FI-Ware internal open-source community between Telecom Italia, Orange, NSN and Ericsson, community which could be open to other FI-Ware Internet of Things partners if they want to implement this interface. We could increase in this case the development effort you manage for the time being by 2 or 3. In this case we would be able to demonstrate concretely a first interoperability in April and emphasize a lot standard adoption to the European ICT community, which should be a great result for Europe and ETSI. 2. If we are successful, our second proposal would be to transform this first implementation into a Reference Implementation. We would suggest maintaining alive this Reference Implementation, to extend the Open Source community and to launch an official one, open to all developers. This community should be supported by FI-Ware and prepare by FI-Ware. This community would provide a professional Reference Implementation, following ETSI M2M improvement, keeping Telecom Operators and their suppliers involved in, and provide at the end low-cost solutions. As you can understand, we think that it is "time to market" now for ETSI M2M and we expect to share among the partners developments and launch ETSI M2M as soon as possible for the best of our markets. Thank you for your feedback. 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. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. -------------- 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 jhierro at tid.es Wed Oct 17 20:25:33 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 17 Oct 2012 20:25:33 +0200 Subject: [Fiware-iot] [Suspected Spam] Fwd: 3rd Peer review of FI-WARE Open Specifications - Data/Context Chapter files available In-Reply-To: <1971FF81B8E01C45991F6F92B9E3B25039148CA7@EX10-MB2-MAD.hi.inet> References: <1971FF81B8E01C45991F6F92B9E3B25039148CA7@EX10-MB2-MAD.hi.inet> Message-ID: <507EF81D.30507@tid.es> Just to make sure it arrives asap ... -------- Original Message -------- Subject: 3rd Peer review of FI-WARE Open Specifications - Data/Context Chapter files available Date: Wed, 17 Oct 2012 17:23:32 +0200 From: CARLOS RALLI UCENDO To: thierry.nagellen at orange.com CC: JUAN JOSE HIERRO SUREDA Dear Thierry, We have just completed the generation of .docx files with Data/Context GEs Open Specifications. The files are linked in the 3rd Peer review cockpit page available at: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 As long as there is one week for your colleagues within IoT to perform the reviews, I would appreciate if you can distribute it to them. Should you have any comment or suggestion, please drop me an e-mail. Thanks, Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Inicio del mensaje reenviado: De: Juanjo Hierro > Asunto: [Fiware-wpa] Fwd: LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Fecha: 12 de octubre de 2012 06:00:40 GMT+02:00 Para: "fiware at lists.fi-ware.eu" >, "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" > Hi, You may have received an email from your WPL or WPA regarding instructions about how we are going to tackle the third and final peer review of the FI-WARE GE Open Specifications that we have to resubmit by November 2nd at the latest (see attachment) IMPORTANT NOTE: We rather NEED that you to carry out a peer-review that focuses on how suitable the contents are. We are afraid that some of the peer-reviews carry out so far were mostly "editorial", i.e., polishing the English, highlighting issues regarding the structure, etc. We need that people review the document from the perspective of a developer or a potential implementer of the spec and point out what you don't understand, what you miss, etc. The intend of this message is twofold. First, make sure it arrives without further delays in your inbox. Second, add a number of enhancements to the process described in the original email that hopefully will allow to make it faster and more efficient. The enhancements have to do with trying to carry out the peer-review using docx files rather than reading the wiki and providing a list of change requests in a separate form. This would allow to drop out the part of the revision form that I sent earlier which had to do with providing detailed editorial comments. Please find attached the revised form. The following is a description of the whole process with the suggested enhancements. If you hadn't read the original email, you just need to read this. For every FI-WARE GE Open Specification (as listed in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications), we will have to carry out the following steps. 1. Generate docx-version of each of the FI-WARE GE Open Specifications to ease the review. There are multiple ways for doing so and it is up to each Chapter to select its preferred one, but here you are a simple set of steps you can follow to generate a docx version (I have used this personally and have found it rather straightforward): * Create a document in Google docs (I hope you have an account, otherwise agree with your WPL on how to get access to one or come back to us :-) * Go to the wiki page of the deliverable. Don't forget to access it in "read" mode (i.e., not logged in FusionForge) because that would avoid copying the "edits" * Copy and Paste directly from the Wiki page into the Google Docs. Notes: * You have to split this in several steps, because Google docs gets blocked if you try to copy&paste too many pages with too many figures. * Don't forget to add the API specs. Typically, you have to first copy&paste what is in the first-level FI-WARE GE Open Specification wiki page, then navigate to each API specification wiki page and copy and paste the contents. * Once the document is generated, you can save it as a Word docx in your local PC. * Run a quick check through the docx file fixing some easy-to-solve questions such as adjusting size of figures, doing some pagination which could easy reading, etc. Please, don't try to make it perfect, we just need a version on which you may apply changes and track those changes with the standard MS Word change control tools. 2. Upload the generated file in either SVN or the docman of the "FI-WARE Private" project in FusionForge (whatever tool you prefer) 3. Add the link to the docx file in SVN or docman to the column "Doc to review" corresponding to the FI-WARE GE in the following shared spreadsheet in Google that we will use as cockpit for the following-up the whole process: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc 4. Sent an email to the WPL of the reviewing chapter so that they know that the docx associated to the FI-WARE GE Open Specification is available for review. Please, don't wait until the rest of docs associated to other FI-WARE Open Specifications in your same chapter are uploaded. Leaders of reviewing chapters are also asked to check when there are new documents to review from time to time. 5. Carry out the review you have been assigned. Reviewers would be required to generate two files, that they should upload again to SVN or docman (whatever you prefer) and link from the Google cockpit. If you are a reviewer, please don't wait until you have both. Please upload each as soon as it is available and inform the leader of the chapter being reviewed that you have done so: * A commented docx for the deliverable which would include all comments under change control. A link to this file should be provided in the "Commented doc" column of the cockpit. * the simple FI-WARE Peer-review form attached. A link to this file should be provided in the "Simple peer-review form" column of the cockpit. 6. Process comments. This would be carried out typically by the owner of the FI-WARE GE Open Specifications. This would imply: * generate a temporary draft by means of accepting/rejecting changes from the commented docx of your specifications * consider general comments in the FI-WARE Peer-review form linked to your FI-WARE GE Open Specifications and introduce changes that you would consider may address them 7. You will generate a new docx by means of implementing step 6 you should upload to the SVN or docman of "FI-WARE Private" and will provide a link to it in column "Revised doc" of the cockpit 8. You will have to update the contents of the public wiki with the contents of the document associated to the revised version It's up to each Chapter Leader to decide how to organize: * Steps 1-4. Some of the Chapter Leaders may prefer to perform these steps by themselves but others may decide to distribute the task associated to each FI-WARE GE Open Specification in his chapter * Step 5. Chapter Leaders will organize the assigned peer-review involving members of his chapter. How he does this is up to him and members of the chapter. They are asked to fill the column title "Assigned reviewer" to communicate who has been assigned the task to review a given doc. Note that you can start the review of an Open Specification as soon as the file is available (i.e., there is a link available in column "Doc to review" of the Peer-Review cockpit. * Steps 6-8. I can imagine that the owner of a FI-WARE GE Open Specification will carry out these steps. However, the Chapter Leader may decide to carry out the update of the wiki, or distribute the task and assign it also to owners of each FI-WARE GE Open Specification VERY IMPORTANT: * PLEASE try to make steps 1-4 as soon as possible. Our experience is that this could be performed in maximum one hour per GE specification, probably much less. The sooner you make docx for review available on the cockpit, the sooner someone will review it. * Step 8 is quite important because we plan to submit the final deliverables based on docx documents that will be generated once again from the wiki. Therefore, if you don't update the wiki, the resubmitted deliverable will go without your changes. SAP is working in a number of tools and processes that will help to produce the docx documents that will be finally submitted and I would like to thank them for the work they are doing in this respect. Milestones for the peer-review are the following: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Assignment of peer-reviewers is as follows: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data Hope it works. Please try to make this final push. We face a critical milestone in the project that has to do with delivering a complete and rich set of FI-WARE Open Specifications. How they will be judged by reviewers will play a relevant role in our next, critical, review. Don't hesitate to ask any question or doubt. Last but not least, I would like to thank SAP for the support in defining this process and the work they are doing developing the tools that will try to automate the final generation of deliverables as much as possible. 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 -------- Original Message -------- Subject: [Fiware-wpa] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Date: Thu, 11 Oct 2012 08:59:09 +0200 From: Juanjo Hierro To: fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu http://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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabioluigi.bellifemine at telecomitalia.it Wed Oct 17 13:02:26 2012 From: fabioluigi.bellifemine at telecomitalia.it (Bellifemine Fabio Luigi) Date: Wed, 17 Oct 2012 13:02:26 +0200 Subject: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware In-Reply-To: <10830_1350470175_507E8A1F_10830_2197_1_c0f3a263-3cb0-4d19-bb1e-5c80cc0f9b42@PEXCVZYH02.corporate.adroot.infra.ftgroup> References: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C203@GRFMBX707BA020.griffon.local> <10830_1350470175_507E8A1F_10830_2197_1_c0f3a263-3cb0-4d19-bb1e-5c80cc0f9b42@PEXCVZYH02.corporate.adroot.infra.ftgroup> Message-ID: <51508CA9C4AE774DAC3FC6B8F0E5A5384691C1C61D@GRFMBX707BA020.griffon.local> Dear Fano, thanks for your interest. In a few days the software will be downloadable directly by the ZigBee4OSGi web site. From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: mercoled? 17 ottobre 2012 12:36 To: Bellifemine Fabio Luigi; NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc: Borean Claudio; Ranalli Andrea; GRATTARD Gilles OLNC/OLPS Subject: RE: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fabio, Thank you for your announcement. We would like to test and use your module in the context of the OUTSMART FI PPP UC project, and would appreciate if you could tell us how to proceed. Thank you very much in advance, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Bellifemine Fabio Luigi Envoy? : mardi 16 octobre 2012 14:15 ? : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; jhierro at tid.es Cc : Borean Claudio; Ranalli Andrea Objet : Re: [Fiware-iot] ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Fi-ware partners, I am pleased to inform you that the ZigBee Gateway Device software module was released in Open source under the Apache 2 license. The web page of the project ZigBee4OSGi http://zb4o.aaloa.org/ includes now the logo of FiWare and a reference to the project as one of the contributors. You are welcome to disseminate this result of Telecom Italia in FiWare. Best regards, Fabio Bellifemine From: Bellifemine Fabio Luigi Sent: luned? 24 settembre 2012 12:54 To: 'thierry.nagellen at orange.com'; 'fiware-iot at lists.fi-ware.eu' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; Borean Claudio; Ranalli Andrea Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry and Fi-ware WP5 partners, As anticipated in February, we are pleased to inform you that we are now ready to release in open source our ZigBee Gateway Device implementation. It is the software that Sabrina already provided as contribution of Telecom Italia to WP5. The software will be released by Telecom Italia under the Apache 2 license. In order to properly acknowledge the Fi-ware activities, we would like to add the following sentence to the Notice file and to the released manual: This work of Telecom Italia s.p.a. has been partly supported by the European Commission under the EU's Seventh Framework Programme (FP7) within the context of the WP5 of the FP7-285248 FI-WARE project (http://www.fi-ware.eu/) We welcome any suggestion and recommendation. Best regards, Fabio Bellifemine. From: Bellifemine Fabio Luigi Sent: 14 February 2012 14:59 To: 'thierry.nagellen at orange.com' Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com; Elia Gabriele Subject: RE: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear Thierry, we analyzed your proposal. We do also think that Fi-Ware has the unique opportunity to launch a new ecosystem and that it should absolutely be based upon worldwide well-defined standards. We believe that our ETSI M2M-like implementation is not appropriate for Fi-Ware as there are still many differences with ETSI M2M and as it is a vertical implementation strictly based upon the requirements of the Energy at home project. On the other hand we feel that we could help Fi-Ware to fill a gap in communicating with Things. We believe that the project is very concentrated on the platform (and that is a strength) with less emphasis and attention on how such a platform will communicate with the Things and with which Things it should communicate (and that might be a possible weakness of the project). We want then to propose you to integrate our implementation of the ZigBee Network Device specifications (see http://www.zigbee.org/). Such a standard specifies how the ZigBee world of Things should interact with the IP world and, in particular, with a platform through a gateway. It is a RESTful interface that every standard ZigBee Gateway Device is required to expose. One of the work items of ETSI M2M is exactly the harmonization with ZigBee Gateway Device specifications. By using such an interface the Fi-Ware platform will be able to communicate with any ZigBee device independently on the specific application profile (be it home automation, smart energy, building automation, health care, or others). That is - in our view - a big benefit and value to Fi-Ware. If you look at the ZigBee site (sections on products), there are today a few hundreds of ZigBee compliant products offered by several companies. Our implementation is based upon two sw modules: - GAL. This module shall be hosted on the gateway device. It implements the ZigBee specifications and it is the layer responsible for inter-working between wireless ZigBee devices and IP world. It exposes a RESTful interface to the cloud platform. It also implement all the state machines required by the standard in order to implement network discovery, device discovery, device and network configuration, communication with devices, ... This module is provided to Fi-Ware as background of Telecom Italia free for the usages of the project and under a FRAND license later (fair, reasonable and non discriminatory). - jGAL. This module shall be hosted on the platform or, eventually, also on OSGi gateway devices. It communicates via REST with the ZigBee gateways according to the ZigBee specifications. On the other side it shall provide a simple Java in-process interface. We are pleased to work on this module as foreground of Telecom Italia in Fi-Ware. We believe that this module can also become the basis for an open source project of Fi-Ware that we are pleased to contribute to launch. The GAL and a basic implementation of jGAL can surely be provided by Telecom Italia by April 2012 as planned by you. I am available for a phone call to discuss in more detail this proposal. Thank you, Fabio Bellifemine. From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: 31 January 2012 15:07 To: Bellifemine Fabio Luigi; Elia Gabriele Cc: Garino Pierangelo; Fici Gian Piero; Guerra Sabrina; lorant.farkas at nsn.com; denes.bisztray at nsn.com Subject: ETSI M2M reference implementation: proposal to share your reults in FI-Ware Dear M Bellifemine, Dear M Elia, We had last week in Madrid the General Meeting of FI-Ware, the Core Platform project from the Public-Private-Partnership Future Internet, a FP7 program initiative where 21 major European ICT partners collaborate. Some of the strategic objectives of this program, and especially FI-Ware as the major technical project, are to push some standards and to launch a new ecosystem, typically based on a developers' community, to adopt quickly these standards and develop new applications on the top of them. I am the Work Package leader of the "Internet of Things" technical area in FI-Ware where we managed in October 2011 between several standards in our area to identify which could be useful regarding our architecture. We reached a consensus to use two of them: ? OMA-NGSI 9&10, which are following meta-data approach and would support a common way to exchange some data between several components ? ETSI-M2M where a stable version is now available and is obviously related to Internet of Things For this second standard, main actors as Ericsson, Nokia Siemens Networks, Orange and of course Telecom Italia agreed to provide an ETSI M2M interface on their assets they expect to improve through the FI-Ware project. As you can understand, it would be very fruitful for the ICT community to have such main actors providing a common interface and demonstrate how interoperability would be easier in the Future. Based on the exchanges we had last week with Ms Sabrina Guerra and M Gian Piero Fici, and as they explained us before, Telecom Italia achieved a first ETSI M2M implementation for an internal research project in the Energy area. We would invite you to study the following proposals to improve this ETSI M2M implementation: 1. Full Restful binding: as your implementation is the first one, we understood that it is not fully Restful compliant. The FI-Ware partners involved in this subject propose to work on a full RESTful binding (REST in the relevant interface for FI-Ware). We could contribute altogether to build this RESTful interface which is one of our objectives for end of April 2012 and share it to demonstrate interoperability. In this case, our proposal is that, based on the consortium agreement all partners signed, we could launch an internal FI-Ware internal open-source community between Telecom Italia, Orange, NSN and Ericsson, community which could be open to other FI-Ware Internet of Things partners if they want to implement this interface. We could increase in this case the development effort you manage for the time being by 2 or 3. In this case we would be able to demonstrate concretely a first interoperability in April and emphasize a lot standard adoption to the European ICT community, which should be a great result for Europe and ETSI. 2. If we are successful, our second proposal would be to transform this first implementation into a Reference Implementation. We would suggest maintaining alive this Reference Implementation, to extend the Open Source community and to launch an official one, open to all developers. This community should be supported by FI-Ware and prepare by FI-Ware. This community would provide a professional Reference Implementation, following ETSI M2M improvement, keeping Telecom Operators and their suppliers involved in, and provide at the end low-cost solutions. As you can understand, we think that it is "time to market" now for ETSI M2M and we expect to share among the partners developments and launch ETSI M2M as soon as possible for the best of our markets. Thank you for your feedback. 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:image001.gif at 01CDAC66.494B84A0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. -------------- 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 thierry.nagellen at orange.com Thu Oct 18 09:26:02 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 18 Oct 2012 07:26:02 +0000 Subject: [Fiware-iot] 3rd Peer Review: deadline 23rd of October Message-ID: <17256_1350545163_507FAF0B_17256_330_1_976A65C5A08ADF49B9A8523F7F81925C067648@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, As discussed yesterday during our weekly meeting, we have to achieve for the 23rd of October the 3rd peer review of some GEs from our colleagues to improve the quality of doc we will provide to the Commission for the next review. You can find in the spreadsheet the link to the document you have to revise. If you have any question, feel free to share your concerns. BR Thierry _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3rdPeer Review-GEs.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12829 bytes Desc: 3rdPeer Review-GEs.xlsx URL: From thierry.nagellen at orange.com Thu Oct 18 09:38:31 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 18 Oct 2012 07:38:31 +0000 Subject: [Fiware-iot] Fi-Ware Catalogue: how to fulfil the GEs description Message-ID: <17256_1350545913_507FB1F9_17256_1265_1_976A65C5A08ADF49B9A8523F7F81925C0676A8@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, Please refer to this page on the Fi-Ware wiki to improve GEs description on the Fi-Ware catalogue (http://catalogue.fi-ware.eu) because there are some inconsistencies not on the first folder (overview) but on the other (instance, download and documentation). The catalogue ould be the main entry point to download and use Fi-Ware Generic Enablers so their description should be clear and similar. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tools.Catalogue#Guidelines_on_what_to_write Thanks for your support 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Thu Oct 18 11:12:56 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 18 Oct 2012 09:12:56 +0000 Subject: [Fiware-iot] Splitting the Things Management GE Message-ID: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Oct 18 11:51:30 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 18 Oct 2012 11:51:30 +0200 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> Message-ID: <507FD122.7020908@tid.es> We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Oct 18 11:58:48 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 18 Oct 2012 11:58:48 +0200 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <507FD122.7020908@tid.es> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> Message-ID: <507FD2D8.4010704@tid.es> Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Oct 19 13:59:11 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 19 Oct 2012 11:59:11 +0000 Subject: [Fiware-iot] Evaluation of status GE Message-ID: <15589_1350647952_50814090_15589_4206_1_976A65C5A08ADF49B9A8523F7F81925C067C46@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Please be aware that Miguel is checking the status of GEs documentation for release 1 and that we could receive many recommendations to improve the different manuals (User guide, administration guide, etc...) and we will have only next week to improve them. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Mon Oct 22 13:38:24 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 22 Oct 2012 11:38:24 +0000 Subject: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Message-ID: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don't miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:part1.02000800.03040801 at tid.es] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gefebija.png Type: image/png Size: 81628 bytes Desc: gefebija.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From gianpiero.fici at telecomitalia.it Mon Oct 22 20:12:32 2012 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Mon, 22 Oct 2012 20:12:32 +0200 Subject: [Fiware-iot] I: TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! In-Reply-To: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: Hi Thierry, I just uploaded the docx with the comments for the BigData Open Specification in the docman (https://forge.fi-ware.eu/docman/index.php?group_id=27). I also added the link to the uploaded document in the cockpit (https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0). The only thing I am not able to locate is the simple FI-WARE Peer-review form Juanjo is asking to add along with the document containing the comments. Could you help me to find this final piece of information? Thank you very much. Bye, Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: luned? 22 ottobre 2012 13:38 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don't miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:part1.02000800.03040801 at tid.es] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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: gefebija.png Type: image/png Size: 81628 bytes Desc: gefebija.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt 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 p.barnaghi at surrey.ac.uk Mon Oct 22 20:18:31 2012 From: p.barnaghi at surrey.ac.uk (p.barnaghi at surrey.ac.uk) Date: Mon, 22 Oct 2012 19:18:31 +0100 Subject: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! In-Reply-To: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: Dear Thierry, The peer reviews for Semantic Annotation and Semantic Support GEs are now uploaded on Forge: https://forge.fi-ware.eu/docman/view.php/27/1437/Semantic_annotation_FI-WARE+Peer-Review+Form+12-10-11.docx https://forge.fi-ware.eu/docman/view.php/27/1436/Semantic_support_FI-WARE+Peer-Review+Form+12-10-11.docx Best, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com [thierry.nagellen at orange.com] Sent: 22 October 2012 12:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don?t miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:part1.02000800.03040801 at tid.es] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gefebija.png Type: image/png Size: 81628 bytes Desc: gefebija.png URL: From thierry.nagellen at orange.com Tue Oct 23 08:16:52 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 23 Oct 2012 06:16:52 +0000 Subject: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! In-Reply-To: References: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <24681_1350973013_50863655_24681_61_1_976A65C5A08ADF49B9A8523F7F81925C0683B6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Thanks a lot Payam De : p.barnaghi at surrey.ac.uk [mailto:p.barnaghi at surrey.ac.uk] Envoy? : lundi 22 octobre 2012 20:19 ? : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu Objet : RE: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear Thierry, The peer reviews for Semantic Annotation and Semantic Support GEs are now uploaded on Forge: https://forge.fi-ware.eu/docman/view.php/27/1437/Semantic_annotation_FI-WARE+Peer-Review+Form+12-10-11.docx https://forge.fi-ware.eu/docman/view.php/27/1436/Semantic_support_FI-WARE+Peer-Review+Form+12-10-11.docx Best, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com [thierry.nagellen at orange.com] Sent: 22 October 2012 12:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don't miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:image001.png at 01CDB0F6.C1559FF0] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 81628 bytes Desc: image001.png URL: From thierry.nagellen at orange.com Tue Oct 23 08:48:22 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 23 Oct 2012 06:48:22 +0000 Subject: [Fiware-iot] I: TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! In-Reply-To: References: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <24825_1350974903_50863DB7_24825_1984_1_976A65C5A08ADF49B9A8523F7F81925C0683E8@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Gian-Piero The Fi-Ware peer review for mis available on the docman in Fi-Ware templates folder. Here is the link. https://forge.fi-ware.eu/docman/view.php/7/1262/FI-WARE+Peer-Review+Form+12-09-05.docx BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Fici Gian Piero Envoy? : lundi 22 octobre 2012 20:13 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] I: TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi Thierry, I just uploaded the docx with the comments for the BigData Open Specification in the docman (https://forge.fi-ware.eu/docman/index.php?group_id=27). I also added the link to the uploaded document in the cockpit (https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0). The only thing I am not able to locate is the simple FI-WARE Peer-review form Juanjo is asking to add along with the document containing the comments. Could you help me to find this final piece of information? Thank you very much. Bye, Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: luned? 22 ottobre 2012 13:38 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don't miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:image001.png at 01CDB0FB.28002370] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 81628 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From Ernoe.Kovacs at neclab.eu Tue Oct 23 10:31:47 2012 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Tue, 23 Oct 2012 08:31:47 +0000 Subject: [Fiware-iot] FI-Ware: Decision on offer to become Work Package Architect for WP5 Message-ID: <8152E2132B13FB488CFD1947E2DEF19C5558272F@DAPHNIS.office.hd> Dear members of the IoT Chapter of FI-WARE, dear Juanjo, Thank you very much for your offer to NEC to take over the role of Work Package Architect of FI-WARE IoT. Unfortunately, after intensive internal discussion we came to the conclusion that we cannot take over that role due to a lack of available resources. We need our people currently working in FI-WARE to fully concentrate on the GE development and we also have no additional person available for the tasks of a Work Package Architect. Please be aware that NEC already coordinating the FI-Ware standardization activities and for that have shifted some substantial resources to that task. We sincerely hope that the position of WPA will be filled soon again by a suitable partner. With kind regards Ern? Kovacs & the NEC FI-Ware team ========================================================== Dr. Ern? Kovacs Senior Manager Internet Services NEC Europe Ltd. NEC Laboratories Europe Kurf?rsten-Anlage 36 D-69115 Heidelberg, Germany Phone: +49 (6221) 4342 - 131 Fax: +49 (6221) 4342 - 155 Mobile: +49 (163) 2086046 EMail: ernoe.kovacs at nw.neclab.eu http://www.netlab.nec.de ========================================================== Registered Office: NEC House, 1 Victoria Road, London W3 6BL, UK Registered in England, No. 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Tue Oct 23 11:56:42 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 23 Oct 2012 11:56:42 +0200 Subject: [Fiware-iot] R: I: TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! In-Reply-To: References: <18419_1350905905_50853031_18419_256_6_976A65C5A08ADF49B9A8523F7F81925C0681B0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5A45F4F5D@GRFMBX702BA020.griffon.local> Hi Thierry, we also uploaded the simple FI-WARE Peer-review form in the doc man for the peer reviews in the Data folder(https://forge.fi-ware.eu/docman/index.php?group_id=27). There is also the link to the uploaded document in the cockpit (https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0). Please let us know if everything is ok. Best regards, Sabrina and Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Fici Gian Piero Inviato: luned? 22 ottobre 2012 20:13 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] I: TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi Thierry, I just uploaded the docx with the comments for the BigData Open Specification in the docman (https://forge.fi-ware.eu/docman/index.php?group_id=27). I also added the link to the uploaded document in the cockpit (https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0). The only thing I am not able to locate is the simple FI-WARE Peer-review form Juanjo is asking to add along with the document containing the comments. Could you help me to find this final piece of information? Thank you very much. Bye, Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: luned? 22 ottobre 2012 13:38 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] TR: [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Dear partners, Just to remind you that we have to achieve the peer review of Data and Context Management. Here is the place to put the documents after your review. The deadline is tomorrow EOB. Till now I just have the feedback from Marteen. Please don't miss the deadline. We will have to work after that on the review that the I2ND chapter is managing on our Open Specs and GEs. BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 22 octobre 2012 12:52 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Reminder: Peer review of Architecture and Open Specifications to be ready by EOB tomorrow !! Hi all, We have created the placeholders in the docman system of the "FI-WARE Private" project that you may use for uploading the .docx files with results of your peer-review. They are located at the path: /Peer reviews/Open Specifications resubmission M18/ where we have created a folder per chapter. The folder "Apps" should be used to upload the documents with comments/changes linked to Open Specifications of the FI-WARE Apps Chapter. You can check the structure we have created at: https://forge.fi-ware.eu/docman/index.php?group_id=27 [cid:image001.png at 01CDB115.77F24C90] Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image002.gif at 01CDB115.77F24C90]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 81628 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From Tobias.Jacobs at neclab.eu Tue Oct 23 14:30:05 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 23 Oct 2012 12:30:05 +0000 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <507FD2D8.4010704@tid.es> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> Message-ID: <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Oct 23 21:07:30 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 23 Oct 2012 21:07:30 +0200 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> Message-ID: <5086EAF2.4020003@tid.es> Hi, I believe that I already mentioned in a previous email that we would implement this change for the Second Release. We won't implement it for this release. Making the split now would have a hughe impact on the FI-WARE software release update we committed to deliver by end of this month. Miguel Carrillo, in copy, can elaborate on the impact of splitting this now. Cheers, -- 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 On 23/10/12 14:30, Tobias Jacobs wrote: Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Oct 23 21:56:32 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 23 Oct 2012 19:56:32 +0000 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <5086EAF2.4020003@tid.es> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> <5086EAF2.4020003@tid.es> Message-ID: <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I fully agree with Juanjo that we will manage this issue in November. This implies impact on architecture, interfaces as typically the Configuration GE does not have a concrete public interface today. BR Thierry De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mardi 23 octobre 2012 21:08 ? : Tobias Jacobs Cc : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo; jhierro >> "Juan J. Hierro" Objet : Re: Splitting the Things Management GE Hi, I believe that I already mentioned in a previous email that we would implement this change for the Second Release. We won't implement it for this release. Making the split now would have a hughe impact on the FI-WARE software release update we committed to deliver by end of this month. Miguel Carrillo, in copy, can elaborate on the impact of splitting this now. Cheers, -- 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 On 23/10/12 14:30, Tobias Jacobs wrote: Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ 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 ________________________________ 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed Oct 24 09:07:32 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 24 Oct 2012 07:07:32 +0000 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> <5086EAF2.4020003@tid.es> <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D38EC3E7F@DAPHNIS.office.hd> Dear all, I totally agree with you to do the split for the 2nd release, but we could start preparing it now in the private wiki, so I just like to have an overview of the places where changes need to be implemented. The ConfigManager GE does have public interfaces: Context Providers register to it via NGSI 9, and it exposes an NGSI-9 discovery interface. This interface is also used by the IoT Broker anyway, so I think there is nothing that needs to be added to the open spec - just some restructuring. Best Tobias From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 23. Oktober 2012 21:57 To: Juanjo Hierro; Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo Subject: RE: Splitting the Things Management GE Dear all, I fully agree with Juanjo that we will manage this issue in November. This implies impact on architecture, interfaces as typically the Configuration GE does not have a concrete public interface today. BR Thierry De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mardi 23 octobre 2012 21:08 ? : Tobias Jacobs Cc : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo; jhierro >> "Juan J. Hierro" Objet : Re: Splitting the Things Management GE Hi, I believe that I already mentioned in a previous email that we would implement this change for the Second Release. We won't implement it for this release. Making the split now would have a hughe impact on the FI-WARE software release update we committed to deliver by end of this month. Miguel Carrillo, in copy, can elaborate on the impact of splitting this now. Cheers, -- 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 On 23/10/12 14:30, Tobias Jacobs wrote: Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ 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 ________________________________ 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Oct 24 09:08:32 2012 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 24 Oct 2012 09:08:32 +0200 Subject: [Fiware-iot] [Suspected Spam] Re: Splitting the Things Management GE In-Reply-To: <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> <5086EAF2.4020003@tid.es> <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <508793F0.70302@tid.es> Dear all, Then it is not necessary to elaborate on the impact on this. It would actually be painful. Best regards, Miguel El 23/10/2012 21:56, thierry.nagellen at orange.com escribi?: Dear all, I fully agree with Juanjo that we will manage this issue in November. This implies impact on architecture, interfaces as typically the Configuration GE does not have a concrete public interface today. BR Thierry De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mardi 23 octobre 2012 21:08 ? : Tobias Jacobs Cc : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo; jhierro >> "Juan J. Hierro" Objet : Re: Splitting the Things Management GE Hi, I believe that I already mentioned in a previous email that we would implement this change for the Second Release. We won't implement it for this release. Making the split now would have a hughe impact on the FI-WARE software release update we committed to deliver by end of this month. Miguel Carrillo, in copy, can elaborate on the impact of splitting this now. Cheers, -- 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 On 23/10/12 14:30, Tobias Jacobs wrote: Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project - including the testbed, all deliverables, etc. - is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts - and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ 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 ________________________________ 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 _________________________________________________________________________________________________________________________ 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. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed Oct 24 09:10:45 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 24 Oct 2012 07:10:45 +0000 Subject: [Fiware-iot] Phone Conference Message-ID: <8755F290097BD941865DC4245B335D2D38EC3EA0@DAPHNIS.office.hd> Hi WP5, Is there a phone conference today? Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Oct 24 09:34:19 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 07:34:19 +0000 Subject: [Fiware-iot] Phone Conference In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC3EA0@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38EC3EA0@DAPHNIS.office.hd> Message-ID: <604_1351064061_508799FD_604_1096_1_976A65C5A08ADF49B9A8523F7F81925C06896D@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all I would propose to have the weekly meeting on Friday morning because we have some work to achieve and some of you did not manage the peer review of Data&Context management chapter that we had to achieve for yesterday EOB! At least I cannot find any link in the spreadsheet (but maybe you cannot access it) https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 So I have checked the folder also on the Fi-Ware private wiki https://forge.fi-ware.eu/docman/index.php?group_id=27# And some docs are missing! (sometimes we have the Open Specs doc with comments but not the Peer review form, and sometimes just the peer review forms I have also to check the catalogue because they are some inconsistencies regarding GE descriptions, name of the GEs and content we can find in Instance, Documentation and Download folders. I'm sending another email this morning on this subject. We have to improve the status of all this points quickly because the next review will evaluate FI-Ware on these points. Take time this morning to fulfill these requirements. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : mercredi 24 octobre 2012 09:11 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Phone Conference Hi WP5, Is there a phone conference today? Best Tobias _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3rdPeer Review-GEs 10-24-2012.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 13007 bytes Desc: 3rdPeer Review-GEs 10-24-2012.xlsx URL: From thierry.nagellen at orange.com Wed Oct 24 09:42:16 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 07:42:16 +0000 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <4635_1351064537_50879BD9_4635_212_1_976A65C5A08ADF49B9A8523F7F81925C068996@PEXCVZYM13.corporate.adroot.infra.ftgroup> Quand : vendredi 26 octobre 2012 10:30-12:00 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Emplacement : Powownow facilities Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* powwownow PIN dedicated to the FI-WARE IoT chapter: 028919 http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1881 bytes Desc: not available URL: From thierry.nagellen at orange.com Wed Oct 24 14:53:10 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 12:53:10 +0000 Subject: [Fiware-iot] Update on catalogue Message-ID: <4230_1351083191_5087E4B7_4230_467_6_976A65C5A08ADF49B9A8523F7F81925C068BBA@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Please find here under the email from Juanjo to manage some changes on the catalogue. It seems that when we have several instantiations of some GEs it is a bit confusing so we have to re-organize the catalogue introducing the name of the asset in association with the name of the GE. If there is no name for the asset, you can create one or just put the name of the company. We should find: Gateway Data Handling GE - CEP Manager (Orange with different instances mobile/java/OSGi) Gateway Data Handling GE - SOL/CEP (Atos) Things Management GE - TID/NEC (this one will evolve as soon as we will have delivered the release, we will split it into the IoT broker and the Configuration Management GE to dissociate TID and NEC assets) Protocol Adpater GE - Telecom Italia (or name of the Zigbee Gateway you pushed in Open Source) Please note that all folders have to be reviewed: overview (we do not have to justify several instantiations as in Gateway Data Handling GE), instances where we have to put the IP address to test it on the testbed, download (if a fully integrated package is available to test the GE "at home"), documentation( with links to the manuals and user test plans as well as the licence model you will apply "at the end": typically you can say it will be in Open Source but consider that the current version is not stable enough to provide it immediately. Thanks a lot to do that quickly because as explained by Juanjo they will manage some actions tomorrow morning at 10:00 AM to be aligned. BR TThierry De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 24 octobre 2012 00:16 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT but EASY Action Point on FI-WARE GE owners Hi, If you are the owner of the reference implementation of any FI-WARE GE, this is an email you should pay special attention to. We need that you implement a couple of APs that are quite easy to implement but relatively urgent (we would need them being implemented by Thursday 10:00am). They were already identified in the joint WPLs/WPAs confcall that took place on October 15th and we asked chapters to implement them by mid last week but little progress has been made. As mentioned, the changes are pretty simple. We need you to: * Change the name of the entry linked to your product (GE implementation) in the FI-WARE Catalogue so that it takes the form: * - (e.g., "Big Data Analysis - SAMSON" or "Complex Event Processing (CEP) - PROTON" * You provide information about the name of your product (GE implementation), accompanied by the name of your organization, in column C of the following shared public spreadsheet: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 Besides, you should update documentation that is specific to your product (Unit Testing Plan and the different guides) so that they use the name of the product when you are referring to your product. If you were using the name of the GE it implemented Some of you may argue that your product has currently no name ... if that is the case, this is a good opportunity to give it a name :-) On Thursday 10:00am we will adopt the following decisions regarding GE implementations for which the requested changes above have not been implemented: * We will change the name of the entry linked to your product (GE implementation) in the FI-WARE Catalogue so that it will take the form: * - 's Implementation (e.g., "Cloud Proxy - Technicolor's Implementation) * We will change the information about the name of your product (GE implementation) in column C of the shared public spreadsheet mentioned above so that it reads: * 's implementation With these change we pretend to provide consistent messages to users of FI-WARE, making the distinction between FI-WARE GE Open Specifications and FI-WARE GE Implementations more clear: 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From thierry.nagellen at orange.com Wed Oct 24 15:06:44 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 13:06:44 +0000 Subject: [Fiware-iot] Demo scenario for review Message-ID: <8795_1351084004_5087E7E4_8795_516_1_976A65C5A08ADF49B9A8523F7F81925C068BF2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, We discussed this point during our last weekly meeting and have a WPL/WPA meeting last week. I do not have currently a draft version of what could be achieve from the Fi-Ware point of view but it is expected that we could show a scenario which will simulate some events from IoT coming through the Pub/Sub broker and using some other Data&Context management GEs. So the small scenario we described between Gateway Data Handling GE and Things Management GE (Query context and update context) to show that NGSI is available between the 2 GEs. The input for Pub/Sub broker will be "static" as the interface is not compliant today. We need here a task force with (TID/NEC and Orange, Atos as follower) to list all tasks. Tobias/Salvatore could you take the lead on that with Laurent and Ken? The other part of the scenario has been described by Sabrina (Thanks Sabrina) to show that we can switch off/switch on a zigbee lamp in Turin using the Gateway device management GE on the testbed in Sevilla (really using Internet and REST interface to do that). The task force is essentially TI and Ericsson. Sabrina, could you take the lead and organize a first meeting with Ericsson on this point. At least from IoT chapter, we will be able to demonstrate that software is running and deliver some services. As soon as I have something on the whole demo, I am going to inform you. BR Thierry [cid:image002.jpg at 01CDB1F9.2DDFB0E0] 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 37544 bytes Desc: image002.jpg URL: From jhierro at tid.es Wed Oct 24 15:24:55 2012 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 24 Oct 2012 13:24:55 +0000 Subject: [Fiware-iot] Splitting the Things Management GE In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC3E7F@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38EC38FC@DAPHNIS.office.hd> <507FD122.7020908@tid.es> <507FD2D8.4010704@tid.es> <8755F290097BD941865DC4245B335D2D38EC3DAA@DAPHNIS.office.hd> <5086EAF2.4020003@tid.es> <1172_1351022193_5086F671_1172_13239_1_976A65C5A08ADF49B9A8523F7F81925C068875@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D38EC3E7F@DAPHNIS.office.hd> Message-ID: Fine to start working on it in the private wiki Enviado desde mi iPad El 24/10/2012, a las 09:08, "Tobias Jacobs" > escribi?: Dear all, I totally agree with you to do the split for the 2nd release, but we could start preparing it now in the private wiki, so I just like to have an overview of the places where changes need to be implemented. The ConfigManager GE does have public interfaces: Context Providers register to it via NGSI 9, and it exposes an NGSI-9 discovery interface. This interface is also used by the IoT Broker anyway, so I think there is nothing that needs to be added to the open spec ? just some restructuring. Best Tobias From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Dienstag, 23. Oktober 2012 21:57 To: Juanjo Hierro; Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo Subject: RE: Splitting the Things Management GE Dear all, I fully agree with Juanjo that we will manage this issue in November. This implies impact on architecture, interfaces as typically the Configuration GE does not have a concrete public interface today. BR Thierry De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mardi 23 octobre 2012 21:08 ? : Tobias Jacobs Cc : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es); Miguel Carrillo; jhierro >> "Juan J. Hierro" Objet : Re: Splitting the Things Management GE Hi, I believe that I already mentioned in a previous email that we would implement this change for the Second Release. We won't implement it for this release. Making the split now would have a hughe impact on the FI-WARE software release update we committed to deliver by end of this month. Miguel Carrillo, in copy, can elaborate on the impact of splitting this now. Cheers, -- 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 On 23/10/12 14:30, Tobias Jacobs wrote: Hi Juanjo, all, In the next weeks we would like to implement the split of the Things Management GE between Configuration Management and IoT Broker. In order not to introduce inconsistencies, we try to get an overview of which wiki pages and what else needs to be changed accordingly. In my opinion, this is - the architecture description - the open spec - the backlog (with features, epics, etc.) In addition - the tracker system - the catalogue (should this be now done already or at a later time?) Anything else we forgot? Best regards Tobias From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Donnerstag, 18. Oktober 2012 11:59 To: Juanjo Hierro Cc: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu; KEN GUNNAR ZANGELIN (kzangeli at tid.es) Subject: Re: Splitting the Things Management GE Of course, by no means this change would fit in in the first Release. This is something to be planned as part of the Second Release activities. I guess it was somehow implicit, but just wanted to make it explicit :-) Cheers, -- 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 On 18/10/12 11:51, Juanjo Hierro wrote: We are in principle Ok. The only point I would make (and here now with the hat of Chief Architect / TM) is that we shouldn't do this until we have the Architecture Description and Open Specification pages of those two potential new GEs ready. A suggestion is to create a space in the private wiki (either the private wiki of the IoT Chapter or the FI-WARE Private wiki) where to work in the development of the new contents that would correspond to the IoT Broker and the Configuration Management GE. Cheers, -- 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 On 18/10/12 11:12, Tobias Jacobs wrote: Dear Thierry, dear Juanjo, After some months of experience with having a joint GE together with another project partner, we came to the conclusion that it would have many advantages to split the Things Management GE among Configuration Management and IoT Broker. The main problem is that the whole project ? including the testbed, all deliverables, etc. ? is built on the assumption that each GE is provided by one responsible partner. This has a lot of implications, e.g. - Compatibility issues regarding the GE licence - In all deliverables, the granularity is per GE, and it is considerable effort to work around that - At the moment the GE is shared between two partners, but in future releases it is planned that even more partners (SAP, USurrey) are going to develop further parts ? and then it is really going to be messy. Technically it would be absolutely no problem to do the split, as the two GE parts have a well-defined interface between them. I do not know when exactly and how to perform such a split, but I would prefer to do it as soon as possible. Please tell me what you think about this, and of course I would also like to hear the opinion of Telefonica, our partner developing the other part of the Things Management GE. Best regards Tobias ________________________________ 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 ________________________________ 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 _________________________________________________________________________________________________________________________ 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Oct 24 15:59:11 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 13:59:11 +0000 Subject: [Fiware-iot] Release evaluation: many actions to manage quickly Message-ID: <12554_1351087152_5087F430_12554_1003_4_976A65C5A08ADF49B9A8523F7F81925C068CAE@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Miguel managed a review of what we have to deliver for the release and beyond the catalogue that we have to update, they are many other points (check the spreadsheet) which are not at the right level: update on the cockpit, update on manuals (I do not see so many new versions on the private wiki, did you update the versions on the public wiki?) If you have the sanity check (Unit Test plan is successful) please update the cockpit. Thanks 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoR Release 1.2 Review.xlsx.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 17786 bytes Desc: IoR Release 1.2 Review.xlsx.xlsx URL: From thierry.nagellen at orange.com Wed Oct 24 16:19:17 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 24 Oct 2012 14:19:17 +0000 Subject: [Fiware-iot] IoT Webinars Message-ID: <12554_1351088358_5087F8E6_12554_2645_1_976A65C5A08ADF49B9A8523F7F81925C068CF3@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners, To pursue some efforts on communication and dissemination, we have to organize some webinars (45mn or 1 hour) per GE. We are going to discuss this issue Friday morning during the weekly meeting. Regarding the GE which are available today should have a webinar for: Things Management GE (TID+NEC), Gateway Data Handling GE (Orange+Atos), Gateway Device Management GE (Ericsson) and Protocol Adpater GE (Telecom Italia). Webinars are providing flexibility when the Architect Weeks required lots of resources and time. The first one should be the more difficult to put in place and need also some preparation. Be careful to plan timeslots to prepare the webinar before to organize it. We should not provide a webinar per assets but we can explain the scope of the GE and then provide some examples based on the assets. Facilities: who is not able to organize a webinar (technical constraint, no experience)? Who is used to manage a webinar? Just a way to share experience and tools. Each of us could use different tools but we can also decide to use the same tools. AP: if you have some concerns to organize a webinar, do not wait for Friday, send me an email so we will try to identify some actions to solve the problem Regarding the deadlines: first webinar before the 20th of November (before the review) and 2 other slots, typically we could expect 1 in December and 1 in January AP: for Friday, identify which are the dates when you can do the webinars Do not fulfill the spreadsheet; I will do it when I will have all dates especially we have also to identify common date for 2 of them. BR Thierry De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mercredi 24 octobre 2012 01:28 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware] AP on FI-WARE GE implementation owners regarding fixing dates for webinars about their FI-WARE GE implementation products Dear all, One of the APs that owners of FI-WARE GE implementations should take care of has to do with defining a calendar for webinars regarding their products. A webinar should be structured as a slot of 45 min - 1 hour maximum. Following the suggestion of some people that have setup webinars in another projects, the recommendation is that the webinars will be organized by two persons (a moderator and a presenter). Some tool should be used by the organizer that will enable to share the screen with attendees. Besides, we will use a special FI-WARE related twitter channel so that the moderator can twit while the presentation evolves and attendees can formulate questions. Questions will be collected by the moderator so every ten minutes these questions will be asked by the moderator to the presenter. In this way the presentation will proceed in a more easy way without the risk of interruptions and network overload. More detailed instructions will be provided in a couple of days. You have to plan at least one webinar for your GE implementation (a "developers' primer") and define at least two dates where the webinar will be made. You have to setup the date&time for those webinars at the following shared spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDRKeUpILUxzTjNNUFZBQUhfM0U4aFE#gid=0 You will find a row per GE implementation covering the mandatory webinar you should organize (developers' primer). You may add rows with dates regarding complementary webinars. You should program the first date of your first webinar sometime before the November 1th-20th period and the second before December 7th (may also fit within the November 1th-20th period) It's ok that you use your favorite tools for setting up the bridge, sharing the screen and chatting but you should indicate this using notes in column F "tools, bridge and dial-in details". WE NEED that you complete your input to the spreadsheet above no later than END OF THIS WEEK. This is because we will forward the spreadsheet to the UC projects so that they can record their intend to attend what webinar. Don't hesitate to ask any question you may have. Cheers, -- 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00003.txt URL: From Tobias.Jacobs at neclab.eu Wed Oct 24 16:36:27 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 24 Oct 2012 14:36:27 +0000 Subject: [Fiware-iot] Demo scenario for review In-Reply-To: <8795_1351084004_5087E7E4_8795_516_1_976A65C5A08ADF49B9A8523F7F81925C068BF2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8795_1351084004_5087E7E4_8795_516_1_976A65C5A08ADF49B9A8523F7F81925C068BF2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D38EC407E@DAPHNIS.office.hd> Hi Thierry, all, Do I understand that we are talking about a demo scenario for interaction between Gateway Data Handling and Backend Things Management? Does the pub/sub broker also play a role in it? The first question is which NGSI operation is used for the shown interactions. Possibilities are - Data Handling sends update to Things Management. But in this case the Things Management GE just forwards it to the pub/sub broker, which is not too exciting. - The ThingsManagement GE queries the Data Handling GE for data. Maybe there could be two (or more) instances of the Data Handling GE, each providing a distinct attribute of the same context element, and the Things Management GE does the aggregation. Of course this depends on which operations the Data Handling GE supports - is there new information on that? Can sensors or other event producers be connected to the Data Handling GE, so that the scenario looks more realistic? Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: Mittwoch, 24. Oktober 2012 15:07 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Demo scenario for review Importance: High Dear all, We discussed this point during our last weekly meeting and have a WPL/WPA meeting last week. I do not have currently a draft version of what could be achieve from the Fi-Ware point of view but it is expected that we could show a scenario which will simulate some events from IoT coming through the Pub/Sub broker and using some other Data&Context management GEs. So the small scenario we described between Gateway Data Handling GE and Things Management GE (Query context and update context) to show that NGSI is available between the 2 GEs. The input for Pub/Sub broker will be "static" as the interface is not compliant today. We need here a task force with (TID/NEC and Orange, Atos as follower) to list all tasks. Tobias/Salvatore could you take the lead on that with Laurent and Ken? The other part of the scenario has been described by Sabrina (Thanks Sabrina) to show that we can switch off/switch on a zigbee lamp in Turin using the Gateway device management GE on the testbed in Sevilla (really using Internet and REST interface to do that). The task force is essentially TI and Ericsson. Sabrina, could you take the lead and organize a first meeting with Ericsson on this point. At least from IoT chapter, we will be able to demonstrate that software is running and deliver some services. As soon as I have something on the whole demo, I am going to inform you. BR Thierry [cid:image001.jpg at 01CDB205.B636D5C0] 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 37544 bytes Desc: image001.jpg URL: From thierry.nagellen at orange.com Thu Oct 25 08:42:55 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 25 Oct 2012 06:42:55 +0000 Subject: [Fiware-iot] Demo scenario for review In-Reply-To: <8755F290097BD941865DC4245B335D2D38EC407E@DAPHNIS.office.hd> References: <8795_1351084004_5087E7E4_8795_516_1_976A65C5A08ADF49B9A8523F7F81925C068BF2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D38EC407E@DAPHNIS.office.hd> Message-ID: <11742_1351147377_5088DF70_11742_2042_1_976A65C5A08ADF49B9A8523F7F81925C068EDB@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tobias, Currently we will have a static link with pub/sub broker in the way that the pub/sub should use a file with some things events descriptions and they will manage a aprt of the demo between DCM GEs. To our side, we do not achieve the link between Gateway Device Management GE so we do not have concrete sensors to provide some inputs. We will have to simulate that at the Gateway Data Handling level. For the link between Gateway Data Handling and Things Management, we should be able to manage query context as well as update context. I think it is a good idea to have 2 instances but we have to discuss how it could be put in place. Of course, based on the other part of the demo (Zigbee lamp) maybe we can also use the data from this demo to define a static view of zigbee lamp context. I would not push everything to be integrated for the next 4 weeks if it is too complex... But maybe Ericsson will be able also to improve this interface between Device Management and Data Handling? BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 24 octobre 2012 16:36 ? : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu Objet : RE: Demo scenario for review Hi Thierry, all, Do I understand that we are talking about a demo scenario for interaction between Gateway Data Handling and Backend Things Management? Does the pub/sub broker also play a role in it? The first question is which NGSI operation is used for the shown interactions. Possibilities are - Data Handling sends update to Things Management. But in this case the Things Management GE just forwards it to the pub/sub broker, which is not too exciting. - The ThingsManagement GE queries the Data Handling GE for data. Maybe there could be two (or more) instances of the Data Handling GE, each providing a distinct attribute of the same context element, and the Things Management GE does the aggregation. Of course this depends on which operations the Data Handling GE supports - is there new information on that? Can sensors or other event producers be connected to the Data Handling GE, so that the scenario looks more realistic? Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: Mittwoch, 24. Oktober 2012 15:07 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Demo scenario for review Importance: High Dear all, We discussed this point during our last weekly meeting and have a WPL/WPA meeting last week. I do not have currently a draft version of what could be achieve from the Fi-Ware point of view but it is expected that we could show a scenario which will simulate some events from IoT coming through the Pub/Sub broker and using some other Data&Context management GEs. So the small scenario we described between Gateway Data Handling GE and Things Management GE (Query context and update context) to show that NGSI is available between the 2 GEs. The input for Pub/Sub broker will be "static" as the interface is not compliant today. We need here a task force with (TID/NEC and Orange, Atos as follower) to list all tasks. Tobias/Salvatore could you take the lead on that with Laurent and Ken? The other part of the scenario has been described by Sabrina (Thanks Sabrina) to show that we can switch off/switch on a zigbee lamp in Turin using the Gateway device management GE on the testbed in Sevilla (really using Internet and REST interface to do that). The task force is essentially TI and Ericsson. Sabrina, could you take the lead and organize a first meeting with Ericsson on this point. At least from IoT chapter, we will be able to demonstrate that software is running and deliver some services. As soon as I have something on the whole demo, I am going to inform you. BR Thierry [cid:image001.jpg at 01CDB28C.54961560] 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 _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 37544 bytes Desc: image001.jpg URL: From thierry.nagellen at orange.com Fri Oct 26 14:24:23 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 26 Oct 2012 12:24:23 +0000 Subject: [Fiware-iot] Doodle for IoT Webinar Message-ID: <7334_1351254265_508A80F9_7334_2035_1_976A65C5A08ADF49B9A8523F7F81925C069470@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As discussed this morning, here is the doodle to identify when could happen the 1st IoT webinar the week before the review. We will use a half day to explain GEs and show how to use them. Scenarios we rae defining for the review should be a guideline. http://www.doodle.com/qtukdwsbhrhqxfqc Please provide your vote before Wednesday 31st October EOB. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Oct 26 14:27:59 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 26 Oct 2012 12:27:59 +0000 Subject: [Fiware-iot] Doodle Demo Scenario 1 Message-ID: <28535_1351254480_508A81D0_28535_12273_1_976A65C5A08ADF49B9A8523F7F81925C06948C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As discussed this morning, here is the Doodle for the 1st confcall on scenario 1 for the demo (review meeting) dedicated to Protocol Adpater GE and Gateway Device Management GE. Telecom Italia and Ericsson hate to attend this meeting. Please provide your vote before Monday 29th October 4:00 PM. http://www.doodle.com/uh6pnwimyrtxusvz 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Oct 26 14:31:28 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 26 Oct 2012 12:31:28 +0000 Subject: [Fiware-iot] Doodle demo scenario 2 Message-ID: <28535_1351254689_508A82A1_28535_12576_1_976A65C5A08ADF49B9A8523F7F81925C0694A0@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As discussed this morning here is the doodle for the first confcall on IoT demo scenario 2 which involves Gateway Data Handling GE, Things Management GE with its 2 components IoT Broker and Configuration Management. Partners NEC, Orange, Telefonica and Atos are required. Please provide your votes before Monday 29th October 4:00 PM http://www.doodle.com/vvc89mfwu8hn74fp 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Mon Oct 29 14:09:59 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 29 Oct 2012 13:09:59 +0000 Subject: [Fiware-iot] Reminder: Doodle Demo Scenario 1 Message-ID: <19491_1351516200_508E8028_19491_814_1_976A65C5A08ADF49B9A8523F7F81925C069AC4@PEXCVZYM13.corporate.adroot.infra.ftgroup> Just a reminder because nobody answer to this doodle for scenario 1. Telecom Italia and Ericsson: please fulfill it before 4:00 PM today! BR Thierry De : NAGELLEN Thierry OLNC/OLPS Envoy? : vendredi 26 octobre 2012 14:28 ? : fiware-iot at lists.fi-ware.eu Objet : Doodle Demo Scenario 1 Importance : Haute Dear all, As discussed this morning, here is the Doodle for the 1st confcall on scenario 1 for the demo (review meeting) dedicated to Protocol Adpater GE and Gateway Device Management GE. Telecom Italia and Ericsson hate to attend this meeting. Please provide your vote before Monday 29th October 4:00 PM. http://www.doodle.com/uh6pnwimyrtxusvz 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Mon Oct 29 14:11:49 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 29 Oct 2012 13:11:49 +0000 Subject: [Fiware-iot] TR: Doodle demo scenario 2 Message-ID: <17383_1351516310_508E8096_17383_482_1_976A65C5A08ADF49B9A8523F7F81925C069AD7@PEXCVZYM13.corporate.adroot.infra.ftgroup> Just a reminder because some contributors are missing (TID) Please fulfill the doodle before 4:00PM today! BR Thierry De : NAGELLEN Thierry OLNC/OLPS Envoy? : vendredi 26 octobre 2012 14:31 ? : fiware-iot at lists.fi-ware.eu Objet : Doodle demo scenario 2 Importance : Haute Dear all, As discussed this morning here is the doodle for the first confcall on IoT demo scenario 2 which involves Gateway Data Handling GE, Things Management GE with its 2 components IoT Broker and Configuration Management. Partners NEC, Orange, Telefonica and Atos are required. Please provide your votes before Monday 29th October 4:00 PM http://www.doodle.com/vvc89mfwu8hn74fp 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Mon Oct 29 14:24:01 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 29 Oct 2012 13:24:01 +0000 Subject: [Fiware-iot] REMINDER: Doodle for IoT Webinar Message-ID: <17385_1351517042_508E8372_17385_1944_1_976A65C5A08ADF49B9A8523F7F81925C069B00@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, This is a reminder because only one person fulfilled some dates in this Doodle. This is also an issue for every GE owner to manage these webinars so give us our availability on this week. BR Thierry De : NAGELLEN Thierry OLNC/OLPS Envoy? : vendredi 26 octobre 2012 14:24 ? : fiware-iot at lists.fi-ware.eu Objet : Doodle for IoT Webinar Dear all, As discussed this morning, here is the doodle to identify when could happen the 1st IoT webinar the week before the review. We will use a half day to explain GEs and show how to use them. Scenarios we rae defining for the review should be a guideline. http://www.doodle.com/qtukdwsbhrhqxfqc Please provide your vote before Wednesday 31st October EOB. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Tue Oct 30 13:18:22 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 30 Oct 2012 12:18:22 +0000 Subject: [Fiware-iot] demo scenario Message-ID: <8755F290097BD941865DC4245B335D2D38EC4698@DAPHNIS.office.hd> Dear all, About the scenario for the demo with IoT Broker + Data Handling GE: Can the owners of the Data Handling GE implementations come up with the main demo scenario? For us it is hard to tell which scenario could be used to demonstrate the capabilities of the Data Handling GE. >From the Things Management GE perspective, the main request is that we have two (or more) instances of the Data Handling GE in the demo scenario, so that the ability to combine information from different sources can be demonstrated. This information is nothing new if you were in last Friday's phone conference, I just wanted to point it out again in preparation of tomorrow's phone call. Best regards Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Oct 30 16:41:42 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 30 Oct 2012 15:41:42 +0000 Subject: [Fiware-iot] AP after peer reviews Message-ID: <25889_1351611702_508FF536_25889_3219_1_976A65C5A08ADF49B9A8523F7F81925C069F8E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I sent separately some emails to some of you who have more concrete actions to do regarding the peer reviews we received from I2ND colleagues. We have currently a WPL/WPA meeting and the deadline for improvement is next Monday morning (5th of November). https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 If it seems we have lots of to do, I think that some inconsistencies are really pointed out and many external links especially for standards are missing (as we are using them every day they seem explicit but not really for external people) Be careful also on relationships with external GEs from the other chapters (typically PubSub broker) we need sometimes to be more explicit on the potential link/interface but maintain also consistency with their names/description. This is an additional work we have to do because the other do not explain how they expect to interact with other GEs but it is also part of the added value we (IoT chapter) provide to Fi-Ware being fully include in the whole architecture. Thanks for your support. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Oct 31 09:35:16 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 31 Oct 2012 08:35:16 +0000 Subject: [Fiware-iot] AP for today Message-ID: <4539_1351672517_5090E2C5_4539_683_3_976A65C5A08ADF49B9A8523F7F81925C06A15F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, We will not have the meeting today as we have two meetings in the afternoon for the demo (scenarios 1 + 2). We have a deadline today for the catalogue. Only the IoT entries which are correctly described will be provided to the EC and Use Case projects; The main points we have to solve are: Protocol Adapter -ZPA (Telecom Italia): Did you receive the sanity check email so we can publish it? Gateway Data Handling GE: we have to split it into 2 entries: Orange and Atos before EOB Feedback from TID: download tab in the GE description on the catalogue => we have just to put links to content we have to provide on the SVN. We do not have to replicate storage. This approach would also provide some management of who will download some software packages because you have to register to access the SVN. I recommend till we have a common policy at project level that, if you provide software packages, you put a date mechanism to avoid that this package will work after end of April 2013 (2nd Fi-Ware release and end of first phase). It is a simple way to manage IPR and know who will continue to use your GE inside and outside the PPP. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Wed Oct 31 09:52:00 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 31 Oct 2012 09:52:00 +0100 Subject: [Fiware-iot] R: AP for today In-Reply-To: <4539_1351672517_5090E2C5_4539_683_3_976A65C5A08ADF49B9A8523F7F81925C06A15F@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <4539_1351672517_5090E2C5_4539_683_3_976A65C5A08ADF49B9A8523F7F81925C06A15F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5A6D8666A@GRFMBX702BA020.griffon.local> Hi Thierry, about the Protocol Adapter - ZPA we have passed the sanity check and we have published our GE this morning. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 31 ottobre 2012 09:35 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] AP for today Dear all, We will not have the meeting today as we have two meetings in the afternoon for the demo (scenarios 1 + 2). We have a deadline today for the catalogue. Only the IoT entries which are correctly described will be provided to the EC and Use Case projects; The main points we have to solve are: Protocol Adapter -ZPA (Telecom Italia): Did you receive the sanity check email so we can publish it? Gateway Data Handling GE: we have to split it into 2 entries: Orange and Atos before EOB Feedback from TID: download tab in the GE description on the catalogue => we have just to put links to content we have to provide on the SVN. We do not have to replicate storage. This approach would also provide some management of who will download some software packages because you have to register to access the SVN. I recommend till we have a common policy at project level that, if you provide software packages, you put a date mechanism to avoid that this package will work after end of April 2013 (2nd Fi-Ware release and end of first phase). It is a simple way to manage IPR and know who will continue to use your GE inside and outside the PPP. 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 _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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 thierry.nagellen at orange.com Wed Oct 31 09:52:49 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 31 Oct 2012 08:52:49 +0000 Subject: [Fiware-iot] AP for today In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5A6D8666A@GRFMBX702BA020.griffon.local> References: <4539_1351672517_5090E2C5_4539_683_3_976A65C5A08ADF49B9A8523F7F81925C06A15F@PEXCVZYM13.corporate.adroot.infra.ftgroup> <36A93B31228D3B49B691AD31652BCAE9A5A6D8666A@GRFMBX702BA020.griffon.local> Message-ID: <18637_1351673571_5090E6E3_18637_6744_1_976A65C5A08ADF49B9A8523F7F81925C06A19E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Sabrina Good news. Thank you very much. BR Theirry De : Guerra Sabrina [mailto:sabrina.guerra at telecomitalia.it] Envoy? : mercredi 31 octobre 2012 09:52 ? : NAGELLEN Thierry OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu Objet : R: AP for today Hi Thierry, about the Protocol Adapter - ZPA we have passed the sanity check and we have published our GE this morning. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 31 ottobre 2012 09:35 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] AP for today Dear all, We will not have the meeting today as we have two meetings in the afternoon for the demo (scenarios 1 + 2). We have a deadline today for the catalogue. Only the IoT entries which are correctly described will be provided to the EC and Use Case projects; The main points we have to solve are: Protocol Adapter -ZPA (Telecom Italia): Did you receive the sanity check email so we can publish it? Gateway Data Handling GE: we have to split it into 2 entries: Orange and Atos before EOB Feedback from TID: download tab in the GE description on the catalogue => we have just to put links to content we have to provide on the SVN. We do not have to replicate storage. This approach would also provide some management of who will download some software packages because you have to register to access the SVN. I recommend till we have a common policy at project level that, if you provide software packages, you put a date mechanism to avoid that this package will work after end of April 2013 (2nd Fi-Ware release and end of first phase). It is a simple way to manage IPR and know who will continue to use your GE inside and outside the PPP. 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 _________________________________________________________________________________________________________________________ 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. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is 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]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ 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. -------------- 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 t.elsaleh at surrey.ac.uk Wed Oct 31 17:09:12 2012 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 31 Oct 2012 16:09:12 +0000 Subject: [Fiware-iot] AP after peer reviews In-Reply-To: <25889_1351611702_508FF536_25889_3219_1_976A65C5A08ADF49B9A8523F7F81925C069F8E@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <25889_1351611702_508FF536_25889_3219_1_976A65C5A08ADF49B9A8523F7F81925C069F8E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59625BF26@EXMB05CMS.surrey.ac.uk> Hello Tobias, Juanjo, RE: FI-WARE IoT Backend Things Management GE Open Specification (FI-WARE-2012-10-01) I have gone through the comments by the reviewer with regards to the USurrey's section on the Discovery Engine. As editors for the Document, I would like to ask how to go about putting the corrections for the document. Shall I just email it to you or is there somehow to upload the corrections? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: 30 October 2012 15:42 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] AP after peer reviews Dear all, I sent separately some emails to some of you who have more concrete actions to do regarding the peer reviews we received from I2ND colleagues. We have currently a WPL/WPA meeting and the deadline for improvement is next Monday morning (5th of November). https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 If it seems we have lots of to do, I think that some inconsistencies are really pointed out and many external links especially for standards are missing (as we are using them every day they seem explicit but not really for external people) Be careful also on relationships with external GEs from the other chapters (typically PubSub broker) we need sometimes to be more explicit on the potential link/interface but maintain also consistency with their names/description. This is an additional work we have to do because the other do not explain how they expect to interact with other GEs but it is also part of the added value we (IoT chapter) provide to Fi-Ware being fully include in the whole architecture. Thanks for your support. 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 _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: