From raihan.ul-islam at neclab.eu Wed Jan 8 09:53:34 2014 From: raihan.ul-islam at neclab.eu (Raihan Ul-Islam) Date: Wed, 8 Jan 2014 08:53:34 +0000 Subject: [Fiware-iot] Conference call today ? Message-ID: Hi all, Will we have a conference call today? Best Raihan ========================================================== Raihan Ul Islam Software Engineer NEC Europe Ltd. NEC Laboratories Europe Kurf?rsten-Anlage 36 D-69115 Heidelberg, Germany Phone: +49 (6221) 4342 - 256 Fax: +49 (6221) 4342 - 155 Mobile: +49 (0) 17679030334 EMail: raihan.ul-islam at neclab.eu http://www.netlab.nec.de ========================================================== | NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, GB | Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From raihan.ul-islam at neclab.eu Wed Jan 8 10:03:14 2014 From: raihan.ul-islam at neclab.eu (Raihan Ul-Islam) Date: Wed, 8 Jan 2014 09:03:14 +0000 Subject: [Fiware-iot] Conference call today ? Message-ID: Hi all, Will we have a conference call today? Best Raihan ========================================================== Raihan Ul Islam Software Engineer NEC Europe Ltd. NEC Laboratories Europe Kurf?rsten-Anlage 36 D-69115 Heidelberg, Germany Phone: +49 (6221) 4342 - 256 Fax: +49 (6221) 4342 - 155 Mobile: +49 (0) 17679030334 EMail: raihan.ul-islam at neclab.eu http://www.netlab.nec.de ========================================================== | NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, GB | Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Jan 14 22:05:51 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 14 Jan 2014 21:05:51 +0000 Subject: [Fiware-iot] Actions to manage quickly Message-ID: <25880_1389733552_52D5A6B0_25880_14783_1_976A65C5A08ADF49B9A8523F7F81925C17857A@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, I will be in Brussels tomorrow for FI-Ware, pushing GEs to EC EIP team, the team who manages the SCC calls for Smart Cities. We would have the opportunities to explain in infodays that Cities can use FI-Ware GEs for future projects and services. So I'm not able to manage the IoT weekly meeting but we have some urgent issues. The most critical is the status of R3.2 delivery planned for End of January. We have to provide all elements for internal review: software packages available, and the 3 guides also available * Unit Testing Plan with new tests for the new features implemented in R3.1 and R3.2 * Installation and Administration Guide: reading this document a newcomer is able to install everything to have a running instance of your GEi * User and Programmer Guide: both should understand how to use your GEi after reading your document You can find in the attached file the status for IoT: we are far to reach the right level of quality. For some GEi this is the first round so it is normal that some improvements have to be done (typically for SAP) but some documents are missing (Fraunhofer, Atos). So please check in detail everything, I've tried to provide some quick comments focusing on what are the main points to improve. Send me an email if you have any question and we can have P2P telco on Thursday to go through the docs. It was difficult to identify some features and I need validation that everything for Protocol Adapter ZPA will be done for R3.3 so maybe never achieved because after GEis discussion during the last review... And typically the backlog is not always aligned with the features and the expected release described in the IoT Technical Roadmap. So next point will be again the improvement of the backlog. About what we have to stop and what could continue, we are waiting for a general email from Juanjo to all GEi owners after some clarifications from our PO. In the same time, we have to revise the Technical Roadmap for R3.3. We agree for a common sentence for the features we will not be able to develop because the Commission asked us to stop the development but in a first step, check that the existing features are correctly dispatched between the different R3.X releases and if needed update R3.3 and the backlog accordingly. BR Thierry 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, 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, 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: Status IoT Delivery 2014-01-15.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 28718 bytes Desc: Status IoT Delivery 2014-01-15.xlsx URL: From Tobias.Jacobs at neclab.eu Fri Jan 17 15:07:57 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 17 Jan 2014 14:07:57 +0000 Subject: [Fiware-iot] Actions to manage quickly In-Reply-To: <25880_1389733552_52D5A6B0_25880_14783_1_976A65C5A08ADF49B9A8523F7F81925C17857A@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <25880_1389733552_52D5A6B0_25880_14783_1_976A65C5A08ADF49B9A8523F7F81925C17857A@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D474118FB@DAPHNIS.office.hd> Hi Thierry, I have two questions 1) (FI-WARE general) has there been a change in the release schedule? Because when I look at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates I am reading that release 3.2 has been at the end of December. We actually released version 3.2 of the NEC IoT Broker there, and we are not planning another release at the end of January, because the R3.3 require more substantial work. 2) (IoT Broker specific) Is there an explanation why in the spreadsheet the lines regarding the R3.2 features are marked yellow? The Unit test plan covers these features. Best regards 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: Dienstag, 14. Januar 2014 22:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Actions to manage quickly Importance: High Hi All, I will be in Brussels tomorrow for FI-Ware, pushing GEs to EC EIP team, the team who manages the SCC calls for Smart Cities. We would have the opportunities to explain in infodays that Cities can use FI-Ware GEs for future projects and services. So I'm not able to manage the IoT weekly meeting but we have some urgent issues. The most critical is the status of R3.2 delivery planned for End of January. We have to provide all elements for internal review: software packages available, and the 3 guides also available * Unit Testing Plan with new tests for the new features implemented in R3.1 and R3.2 * Installation and Administration Guide: reading this document a newcomer is able to install everything to have a running instance of your GEi * User and Programmer Guide: both should understand how to use your GEi after reading your document You can find in the attached file the status for IoT: we are far to reach the right level of quality. For some GEi this is the first round so it is normal that some improvements have to be done (typically for SAP) but some documents are missing (Fraunhofer, Atos). So please check in detail everything, I've tried to provide some quick comments focusing on what are the main points to improve. Send me an email if you have any question and we can have P2P telco on Thursday to go through the docs. It was difficult to identify some features and I need validation that everything for Protocol Adapter ZPA will be done for R3.3 so maybe never achieved because after GEis discussion during the last review... And typically the backlog is not always aligned with the features and the expected release described in the IoT Technical Roadmap. So next point will be again the improvement of the backlog. About what we have to stop and what could continue, we are waiting for a general email from Juanjo to all GEi owners after some clarifications from our PO. In the same time, we have to revise the Technical Roadmap for R3.3. We agree for a common sentence for the features we will not be able to develop because the Commission asked us to stop the development but in a first step, check that the existing features are correctly dispatched between the different R3.X releases and if needed update R3.3 and the backlog accordingly. BR Thierry 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, 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, 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 Jan 17 15:45:03 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 17 Jan 2014 14:45:03 +0000 Subject: [Fiware-iot] Actions to manage quickly In-Reply-To: <8755F290097BD941865DC4245B335D2D474118FB@DAPHNIS.office.hd> References: <25880_1389733552_52D5A6B0_25880_14783_1_976A65C5A08ADF49B9A8523F7F81925C17857A@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D474118FB@DAPHNIS.office.hd> Message-ID: <24857_1389969905_52D941F0_24857_91_1_976A65C5A08ADF49B9A8523F7F81925C17B02D@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tobias, To answer your questions: 1. No change regarding the planning of release. R3.2 is closed since end of December 2013 with software delivery but we have to manage now the peer-review of the associated documentation (official deliverables planned for 31-01-2014). We are now in sprint R3.3.1 but no delivery is expected at the end of January. 2. Green, Yellow and Red colors are just for me to manage the different releases and to point out that we will have less time to modify or validate anything because the end of the project is closer for the different minor releases. (bug correction or integration between GEs will be more difficult for features in R3.3) BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : vendredi 17 janvier 2014 15:08 ? : NAGELLEN Thierry IMT/OLPS; fiware-iot at lists.fi-ware.eu Cc : Salvatore Longo; Raihan Ul-Islam Objet : RE: Actions to manage quickly Hi Thierry, I have two questions 1) (FI-WARE general) has there been a change in the release schedule? Because when I look at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates I am reading that release 3.2 has been at the end of December. We actually released version 3.2 of the NEC IoT Broker there, and we are not planning another release at the end of January, because the R3.3 require more substantial work. 2) (IoT Broker specific) Is there an explanation why in the spreadsheet the lines regarding the R3.2 features are marked yellow? The Unit test plan covers these features. Best regards 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: Dienstag, 14. Januar 2014 22:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Actions to manage quickly Importance: High Hi All, I will be in Brussels tomorrow for FI-Ware, pushing GEs to EC EIP team, the team who manages the SCC calls for Smart Cities. We would have the opportunities to explain in infodays that Cities can use FI-Ware GEs for future projects and services. So I'm not able to manage the IoT weekly meeting but we have some urgent issues. The most critical is the status of R3.2 delivery planned for End of January. We have to provide all elements for internal review: software packages available, and the 3 guides also available ? Unit Testing Plan with new tests for the new features implemented in R3.1 and R3.2 ? Installation and Administration Guide: reading this document a newcomer is able to install everything to have a running instance of your GEi ? User and Programmer Guide: both should understand how to use your GEi after reading your document You can find in the attached file the status for IoT: we are far to reach the right level of quality. For some GEi this is the first round so it is normal that some improvements have to be done (typically for SAP) but some documents are missing (Fraunhofer, Atos). So please check in detail everything, I've tried to provide some quick comments focusing on what are the main points to improve. Send me an email if you have any question and we can have P2P telco on Thursday to go through the docs. It was difficult to identify some features and I need validation that everything for Protocol Adapter ZPA will be done for R3.3 so maybe never achieved because after GEis discussion during the last review... And typically the backlog is not always aligned with the features and the expected release described in the IoT Technical Roadmap. So next point will be again the improvement of the backlog. About what we have to stop and what could continue, we are waiting for a general email from Juanjo to all GEi owners after some clarifications from our PO. In the same time, we have to revise the Technical Roadmap for R3.3. We agree for a common sentence for the features we will not be able to develop because the Commission asked us to stop the development but in a first step, check that the existing features are correctly dispatched between the different R3.X releases and if needed update R3.3 and the backlog accordingly. BR Thierry 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, 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, 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, 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, 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 Jan 20 08:49:43 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 20 Jan 2014 07:49:43 +0000 Subject: [Fiware-iot] First botnet of IoT Message-ID: <13859_1390204183_52DCD517_13859_8808_1_976A65C5A08ADF49B9A8523F7F81925C17B15A@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Maybe some of you ahve heard or read something about this "first botnet" of IoT. Of course this is an issue that we have never found time to target in FI-Ware despite many requirement from Pascal as Security WPL but I have at least one comment and one question regarding this article: 1. This article arrived just 2 days after Google published the announcement of Nest Cast financial operation, so to close from my point of view to be really true, especially while Proofpoint claim to have the solution to avoid this 2. Have you heard before any other concrete example of this kind of attack based on IoT devices, not only botnet but also hack of data? http://www.proofpoint.com./products/targeted-attack-protection/internet-of-things.php 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon Jan 20 13:01:48 2014 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 20 Jan 2014 13:01:48 +0100 Subject: [Fiware-iot] New Orion Context Broker release (0.9.1 FI-WARE 3.3.1) Message-ID: <52DD102C.902@tid.es> Hi, A new Orion Context Broker release (0.9.1 FI-WARE 3.3.1) has just been released, corresponding to January sprint. You will find the RPM package at https://forge.fi-ware.eu/frs/?group_id=7 This is mainly a maintenance version of 0.9.0. New functionality has not been added. Changelog for this new version: - Added: tracelevels for input/output for notifications and registrations forwarding - Added: creDate attribute now also for attributes in mongodb - Fixed: race-condition in HTTP client code, affecting mainly the sending of notifications (closes issue #13) - Fixed: modDate is now set for entities and attributes at creation time - Fixed: added the missing comma for the ContextRegistration vector at rendering registerContextRequest - Fixed: registrationId is now mandatory for registerContextResponse - Fixed: correct rendering of ContextRegistrationAttribute (its metadata XML tag was incorrect) - Fixed: duration no longer returned in response payloads if the incoming duration was invalid - Fixed: better RegisterProviderRequest validity check. This fix improves the error responses for ngsi9 convenience operations - Fixed: bug regarding the 'default' value of 'subscriptionId'. Before this PR, in the case of an undefined subscriptionId, the string 'No SubscriptionId' was used. - Fixed: orionError responses now correctly rendered (the top-level '{' and '}' were missing) Any feedback or bug report on this new release is welcome! Best regards, ------ Ferm?n ________________________________ 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 Tue Jan 21 10:22:46 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 21 Jan 2014 09:22:46 +0000 Subject: [Fiware-iot] confcall tomorrow Message-ID: <8755F290097BD941865DC4245B335D2D47413DEA@DAPHNIS.office.hd> Hi Thierry, all, Will we have a confcall tomorrow morning? Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Jan 21 10:26:11 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 21 Jan 2014 09:26:11 +0000 Subject: [Fiware-iot] confcall tomorrow In-Reply-To: <8755F290097BD941865DC4245B335D2D47413DEA@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D47413DEA@DAPHNIS.office.hd> Message-ID: <13840_1390296372_52DE3D34_13840_18317_1_976A65C5A08ADF49B9A8523F7F81925C17B5BF@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tobias Yes we will have the conf call tomorrow. Subjects are deliverables for the end of the month (documentation + textbed) and revised Architecture and Open Specs, as well as Tracker status. I will also provide a quick feedback from last review, Xifi and new platforms and on-going call 3. GoogleDocs will come this afternoon. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mardi 21 janvier 2014 10:23 ? : fiware-iot at lists.fi-ware.eu; NAGELLEN Thierry IMT/OLPS Objet : confcall tomorrow Hi Thierry, all, Will we have a confcall tomorrow morning? 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Tue Jan 21 11:34:05 2014 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 21 Jan 2014 10:34:05 +0000 Subject: [Fiware-iot] confcall tomorrow In-Reply-To: <13840_1390296372_52DE3D34_13840_18317_1_976A65C5A08ADF49B9A8523F7F81925C17B5BF@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D47413DEA@DAPHNIS.office.hd> <13840_1390296372_52DE3D34_13840_18317_1_976A65C5A08ADF49B9A8523F7F81925C17B5BF@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <867496D3-BF4C-4313-AFBB-07A77502C68A@tid.es> Hi all, I'll get back to work on Thursday after my paternity leave since as most of you know my second child, Martin, was born on Jan 5th. Therefore I'll not connect but I'll send an e-mail to Thierry to get up to date. See you! Best regards. El 21/01/2014, a las 10:30, "thierry.nagellen at orange.com" > escribi?: Hi Tobias Yes we will have the conf call tomorrow. Subjects are deliverables for the end of the month (documentation + textbed) and revised Architecture and Open Specs, as well as Tracker status. I will also provide a quick feedback from last review, Xifi and new platforms and on-going call 3. GoogleDocs will come this afternoon. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mardi 21 janvier 2014 10:23 ? : fiware-iot at lists.fi-ware.eu; NAGELLEN Thierry IMT/OLPS Objet : confcall tomorrow Hi Thierry, all, Will we have a confcall tomorrow morning? 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ 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 Jan 21 15:36:14 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 21 Jan 2014 14:36:14 +0000 Subject: [Fiware-iot] Tomorrow IoT weekly meeting Message-ID: <13284_1390314976_52DE85E0_13284_9869_1_976A65C5A08ADF49B9A8523F7F81925C17B804@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, Here is the link for tomorrow meeting, lots of points to address so please join the meeting on time. https://docs.google.com/document/d/1usc02qsahXGJW9YrKyUsuGR9QGZ-5jGdilxAKaU8xeM/edit 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, 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, 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 Thu Jan 23 10:57:59 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 23 Jan 2014 09:57:59 +0000 Subject: [Fiware-iot] IoT Architecture: actions to manage quickly Message-ID: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Thu Jan 23 11:45:18 2014 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 23 Jan 2014 10:45:18 +0000 Subject: [Fiware-iot] IoT Architecture: actions to manage quickly In-Reply-To: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9859FDD9A@EXMB05CMS.surrey.ac.uk> Hello Thierry, All the information that is specific to the IoT Discovery has been added in the "optional features". If I understand correctly, is that an introduction should be added at the top of the page. Is this what you propose? On another note, there is a section on geo-discovery....has something been done with this respect (NEC)? 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: 23 January 2014 09:58 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Architecture: actions to manage quickly Importance: High Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) 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, 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, 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 Thu Jan 23 14:00:37 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 23 Jan 2014 13:00:37 +0000 Subject: [Fiware-iot] IoT Architecture: actions to manage quickly In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB9859FDD9A@EXMB05CMS.surrey.ac.uk> References: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCB9859FDD9A@EXMB05CMS.surrey.ac.uk> Message-ID: <16093_1390482037_52E11275_16093_479_1_976A65C5A08ADF49B9A8523F7F81925C17CF97@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tarek, Yes I think we need some sentences in the introduction to explain also the optional features. It will be easier for the reader to decide to jump directly to the optional features section if he finds them relevant. BR Thierry De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : jeudi 23 janvier 2014 11:45 ? : NAGELLEN Thierry IMT/OLPS Cc : fiware-iot at lists.fi-ware.eu Objet : RE: IoT Architecture: actions to manage quickly Hello Thierry, All the information that is specific to the IoT Discovery has been added in the "optional features". If I understand correctly, is that an introduction should be added at the top of the page. Is this what you propose? On another note, there is a section on geo-discovery....has something been done with this respect (NEC)? 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: 23 January 2014 09:58 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Architecture: actions to manage quickly Importance: High Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) 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, 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, 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, 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, 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 Thu Jan 23 16:38:19 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 23 Jan 2014 15:38:19 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture Message-ID: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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: ArchitecturePictureR3.2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 70639 bytes Desc: ArchitecturePictureR3.2.pptx URL: From matthias.thoma at sap.com Fri Jan 24 12:13:20 2014 From: matthias.thoma at sap.com (Thoma, Matthias) Date: Fri, 24 Jan 2014 11:13:20 +0000 Subject: [Fiware-iot] Small survey Message-ID: Hello all, I wish everyone (hope it is not too late for that) a happy and successful 2014. First, sorry for spamming the mailing list: There is a small IoT-related survey running about the usage of semantics in IoT for one of our students and we are looking for some more (professional and academic) participants. I know we are all very busy, but It should not take more than around 10min. The URL is: http://www.iot4bpm.de/iot-protocols-and-semantics-survey or direct link: http://tinyurl.com/pb4gw4g All the best, Matthias Matthias Thoma Research Associate | HCI | BIT PA&TS SAP (Switzerland) Inc. | Althardstrasse 80 | 8105 Regensdorf | Switzerland T +41 58 871 7843 | mailto: matthias.thoma at sap.com http://www.sap.com If you are working in the IoT-flied, please take part in our little IoT semantic survey: http://www.iot4bpm.de/iot-protocols-and-semantics-survey Please consider to send me encrypted mail: http://keys.sap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianpiero.fici at telecomitalia.it Fri Jan 24 12:20:04 2014 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Fri, 24 Jan 2014 12:20:04 +0100 Subject: [Fiware-iot] R: IoT Architecture: actions to manage quickly In-Reply-To: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: Hi Thierry, I updated the link to obtain the ETSI documentation. You were right, the previous link required an ETSI username and password and I did not notice it because I have my ETSI credentials saved in my PC (sorry), but in the meantime the way to acquire free documentation from ETSI changed, therefore with the opportunity I put the new correct procedure. I already checked the availability of the documentation using a colleague as a guinea pig, but in case let me know if you have any problems to follow the link provided. Regarding the "ETSI M2M Architecture Overview" I would not change it because it is already in a good shape, in my opinion. Ciao, 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: gioved? 23 gennaio 2014 10:58 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT Architecture: actions to manage quickly Priorit?: Alta Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) 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, 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, 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. -------------- 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 Fri Jan 24 13:56:34 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 24 Jan 2014 12:56:34 +0000 Subject: [Fiware-iot] IoT Architecture: actions to manage quickly In-Reply-To: References: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <13247_1390568195_52E26302_13247_10279_1_976A65C5A08ADF49B9A8523F7F81925C17D41F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Gian Piero OK thanks. I've checked the link, it is ok and with a request on ETI M2M you can find all documents. 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? : vendredi 24 janvier 2014 12:20 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] R: IoT Architecture: actions to manage quickly Hi Thierry, I updated the link to obtain the ETSI documentation. You were right, the previous link required an ETSI username and password and I did not notice it because I have my ETSI credentials saved in my PC (sorry), but in the meantime the way to acquire free documentation from ETSI changed, therefore with the opportunity I put the new correct procedure. I already checked the availability of the documentation using a colleague as a guinea pig, but in case let me know if you have any problems to follow the link provided. Regarding the "ETSI M2M Architecture Overview" I would not change it because it is already in a good shape, in my opinion. Ciao, 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: gioved? 23 gennaio 2014 10:58 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT Architecture: actions to manage quickly Priorit?: Alta Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) 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, 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, 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, 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, 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 Tobias.Jacobs at neclab.eu Fri Jan 24 14:45:25 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 24 Jan 2014 13:45:25 +0000 Subject: [Fiware-iot] IoT Architecture: actions to manage quickly In-Reply-To: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <16636_1390471080_52E0E7A8_16636_7383_1_976A65C5A08ADF49B9A8523F7F81925C17CED2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D47415576@DAPHNIS.office.hd> Hi Thierry, I am explaining below my changes in green. 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: Donnerstag, 23. Januar 2014 10:58 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Architecture: actions to manage quickly Importance: High Hi all, Here is the link for the architecture v3 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Architecture_v3 It took times to go through everything (especially all links) and here are the improvements we have to do. I put name of contributors (people or Companies) in red to be sure you can focus quickly on your own actions. There is some work for everybody! Deadline: tomorrow 24th January EOB SAP/Carsten: I do not retrieve the link for the Open Specs of the Template Handler could you resend it to me. And here are the main things to do: 1. Architecture overview: revised the picture (inclusion of Template Handler and update of NGSI interface for Protocol Adapter) => Thierry 2. ETSI-M2M: review architecture description => Gian-Piero 3. ETSI-M2M: Specs rel 1, check the links because many documents required login/password and the "open" one is not the release 1 but latest drafts & contributions for OneM2M => Gian-Piero 4. OMA NGSI - Context Management: first link error message => Tobias T: fixed 5. OMA NGSI - Context Management: in the two other links I do not find any reference to association of entities=> Tobias T: fixed, now pointing to the NGSI overview page. 6. OMA NGSI - Context Management: nothing on NGSI 9? => Tobias T: fixed, as link now goes to the overview page 7. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker => NEC a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? T: added a link to NGSI overview page and a link to e-learning platform b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association check that this page is up to date T: seems up-to-date c. Main interactions: enrich the introduction, key role of IoT broker between several backend (different platform providers) and many gateways (shared gateways or per silo) d. References: check the links that they are always ok 8. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConfMan => TELEFONICA/UniS a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement#Open_API_SpecificationsFI-WARE_NGSI link to API for Things Management GE to be changed! b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI_Context_Management_tutorial to be replaced by a course on the eLearning platform? c. ConfMan GE architecture: discovery features top level description is missing, do we need some introduction here for the optional features? => Tarek 9. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement => TELEFONICA a. ETSI M2M interface is missing In the architecture Picture b. FI-Ware NGSI: update the 2 first links (candidate release 2010 & NGSI9&10 page renamed) c. ETSI-M2M links: to be updated after info provided by Gian Piero 10. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement FRAUNHOFER a. To be updated, the current description is related to Ericsson Gateway 11. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling ORANGE a. Main interfaces NGSI 9/10 interfaces : add the interface with Protocol Adapters b. Graphical rules editor: update the picture c. SOL/CEP - NGSI: put correctly first link => ATOS 12. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_NGSI_Open_RESTful_API_Specification_%28PRELIMINARY%29 Tobias a. Transform NGSI preliminary into release 1 (move page because many links should point directly on this one) T: done. In the public wiki it was already non-preliminary, by the way. 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, 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, 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 Fri Jan 24 16:31:04 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 24 Jan 2014 15:31:04 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From carsten.magerkurth at sap.com Mon Jan 27 08:52:31 2014 From: carsten.magerkurth at sap.com (Magerkurth, Carsten) Date: Mon, 27 Jan 2014 07:52:31 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> Message-ID: <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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 Mon Jan 27 09:10:10 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 27 Jan 2014 08:10:10 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> Message-ID: <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Mon Jan 27 09:49:59 2014 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Mon, 27 Jan 2014 08:49:59 +0000 Subject: [Fiware-iot] Small survey In-Reply-To: References: Message-ID: <23241_1390812600_52E61DB8_23241_546_1_DC254E6D1212F24EAE0D7766A11FE289142B32F7@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Matthias, There's a FIWARE mailing list "fiware-semantics" dedicated to this topic here : https://forge.fi-ware.eu/mail/?group_id=7 You can browse the archive to look at what has been discussed so far and better contribute by sharing your views. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Thoma, Matthias Envoy? : vendredi 24 janvier 2014 12:13 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Small survey Importance : Faible Hello all, I wish everyone (hope it is not too late for that) a happy and successful 2014. First, sorry for spamming the mailing list: There is a small IoT-related survey running about the usage of semantics in IoT for one of our students and we are looking for some more (professional and academic) participants. I know we are all very busy, but It should not take more than around 10min. The URL is: http://www.iot4bpm.de/iot-protocols-and-semantics-survey or direct link: http://tinyurl.com/pb4gw4g All the best, Matthias Matthias Thoma Research Associate | HCI | BIT PA&TS SAP (Switzerland) Inc. | Althardstrasse 80 | 8105 Regensdorf | Switzerland T +41 58 871 7843 | mailto: matthias.thoma at sap.com http://www.sap.com If you are working in the IoT-flied, please take part in our little IoT semantic survey: http://www.iot4bpm.de/iot-protocols-and-semantics-survey Please consider to send me encrypted mail: http://keys.sap.com _________________________________________________________________________________________________________________________ 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon Jan 27 19:42:29 2014 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 27 Jan 2014 19:42:29 +0100 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> Message-ID: <52E6A895.3000806@tid.es> Dear Carsten, I agree with Tobias... It will be great to have some information about of Template Handler interacts with IoT Broker and ConfMan, such as sequence diagrams. Maybe it is a matter of passing us the proper links, if this information has been already put in some place in the FI-WARE wiki. In addition, it is not clear to my the meaning of "NGSI start event"... could you clarify, please? Thanks! Best regards, ------ Ferm?n El 27/01/2014 9:10, Tobias Jacobs escribi?: Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ 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 carsten.magerkurth at sap.com Tue Jan 28 09:07:33 2014 From: carsten.magerkurth at sap.com (Magerkurth, Carsten) Date: Tue, 28 Jan 2014 08:07:33 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> Message-ID: <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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 Jan 28 11:35:37 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 28 Jan 2014 10:35:37 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> Message-ID: <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Tue Jan 28 17:30:52 2014 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 28 Jan 2014 16:30:52 +0000 Subject: [Fiware-iot] Updated backlog dashboards - remaining issues Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90BA301303C@EX10-MB2-MAD.hi.inet> Dear IoT GEI owners, Please, have attached updated backlog dashboards with changes discussed with Thierry. Thierry, All, please, if there were still any issue, let me know. Let me bring to your attention the following GEIs, where there's nothing scheduled for this sprint. Let me also emphasize that I won't allow charging cost when there's no activity in the tracker. So, please, be diligent. Thanks!! [cid:image001.png at 01CF1C4D.9F4C9710] [cid:image002.png at 01CF1C4D.9F4C9710] [cid:image003.png at 01CF1C4E.39F99B00] [cid:image004.png at 01CF1C4E.39F99B00] Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 14808 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 15255 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 29020 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 14488 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.iot.dashboard.20140128.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 376765 bytes Desc: FIWARE.backlog.iot.dashboard.20140128.xlsx URL: From carsten.magerkurth at sap.com Wed Jan 29 08:35:22 2014 From: carsten.magerkurth at sap.com (Magerkurth, Carsten) Date: Wed, 29 Jan 2014 07:35:22 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> Message-ID: <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> Hi Tobias, >>Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense. best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Dienstag, 28. Januar 2014 11:36 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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 Jan 29 08:45:41 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 Jan 2014 07:45:41 +0000 Subject: [Fiware-iot] Today IoT weekly meeting Message-ID: <10339_1390981542_52E8B1A6_10339_13741_1_976A65C5A08ADF49B9A8523F7F81925C17DF18@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is the link for the minutes. We will focus on backlog management (sprint 3.3.1 to close for Friday) and Open Specs (deliverable to achieve) https://docs.google.com/document/d/1xzwt0fsPpESbLSIC53SZZMUc4T-Qw6OJwHiGhebi7UY/edit#heading=h.l48pvakxchke 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, 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, 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 Jan 29 08:46:43 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 29 Jan 2014 07:46:43 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> Message-ID: <8755F290097BD941865DC4245B335D2D47415DBB@DAPHNIS.office.hd> Hi Carsten, Thierry, all In the new architecture picture sent by Thierry last week I see a slight inconsistency, because the TH is connected to the IoT Broker GE at the Northbound interface (the one where data consumers are connected) and the TH is connected to the ConfMan GE via the interface where the data providers are connected. According to the current discussion the TH GE possibly plays both roles, but still we might consider making the NGSI 10 and NGSI 9 connections aligned. If the data consumer role is the more important one, this would mean connecting the TH to the ConfMan via the left-hand NGSI9 interface. Best regards Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Mittwoch, 29. Januar 2014 08:35 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, >>Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense. best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Dienstag, 28. Januar 2014 11:36 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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 Jan 29 09:16:10 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 Jan 2014 08:16:10 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D47415DBB@DAPHNIS.office.hd> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415DBB@DAPHNIS.office.hd> Message-ID: <22420_1390983371_52E8B8CA_22420_6558_1_976A65C5A08ADF49B9A8523F7F81925C17DF3C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tobias, all, Accordingly, the picture should be this one. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 29 janvier 2014 08:47 ? : Magerkurth, Carsten; NAGELLEN Thierry IMT/OLPS; fiware-iot at lists.fi-ware.eu Objet : RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thierry, all In the new architecture picture sent by Thierry last week I see a slight inconsistency, because the TH is connected to the IoT Broker GE at the Northbound interface (the one where data consumers are connected) and the TH is connected to the ConfMan GE via the interface where the data providers are connected. According to the current discussion the TH GE possibly plays both roles, but still we might consider making the NGSI 10 and NGSI 9 connections aligned. If the data consumer role is the more important one, this would mean connecting the TH to the ConfMan via the left-hand NGSI9 interface. Best regards Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Mittwoch, 29. Januar 2014 08:35 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, >>Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense. best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Dienstag, 28. Januar 2014 11:36 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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, 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, 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: ArchitecturePictureR3.2 v2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 70662 bytes Desc: ArchitecturePictureR3.2 v2.pptx URL: From fermin at tid.es Wed Jan 29 12:52:21 2014 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 29 Jan 2014 12:52:21 +0100 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> Message-ID: <52E8EB75.8090108@tid.es> Dear Carsten, "Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense." In that case, please update your sequence diagram in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide to include the interactions with ConfMan. As additional suggestion, I think it would be more clear if instead of "NGSI server" in the chart, you use the name of the actual GE (IoTBroker or ConfMan, depending the case). Thanks! Best regards, ------ Ferm?n El 29/01/2014 8:35, Magerkurth, Carsten escribi?: Hi Tobias, >>Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense. best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Dienstag, 28. Januar 2014 11:36 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ 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 Jan 29 14:35:34 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 Jan 2014 13:35:34 +0000 Subject: [Fiware-iot] Deliverables names for tracker Message-ID: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Regarding tickets we have to create in the tracker for documentation please put in comment the following: Unit Test Plan deliverable=D5.5.3 Inst&Admin Guide deliverable=D5.3.3 User&Prog Guide deliverable=D5.4.3 Architecture deliverable=D2.2.3 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, 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, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.artusio at orange.com Wed Jan 29 14:53:17 2014 From: laurent.artusio at orange.com (laurent.artusio at orange.com) Date: Wed, 29 Jan 2014 13:53:17 +0000 Subject: [Fiware-iot] Deliverables names for tracker In-Reply-To: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <32017_1391003601_52E907D1_32017_3130_1_f58bed7d-1dc6-4f4b-a108-b269271b1260@PEXCVZYH01.corporate.adroot.infra.ftgroup> Hi Thierry, I have just finished creating the following trackers: 6713 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.Architecture.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6712 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.InstAndAdminGuide.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6715 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.OpenSpecification.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6716 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.TechnicalRoadmap.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6710 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.UnitTestPlan.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6714 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData 6711 FIWARE.WorkItem.IoT.GatewayDataHandling-Esper4FastData.Documentation.UserAndProgrammerGuide.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Data Handling Esper4FastData I let you decide if the 6714 global documentation tracker is still relevant or not. Best Regards, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de thierry.nagellen at orange.com Envoy? : mercredi 29 janvier 2014 14:36 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Deliverables names for tracker Dear all, Regarding tickets we have to create in the tracker for documentation please put in comment the following: Unit Test Plan deliverable=D5.5.3 Inst&Admin Guide deliverable=D5.3.3 User&Prog Guide deliverable=D5.4.3 Architecture deliverable=D2.2.3 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, 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, 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, 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, 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 Jan 29 16:12:18 2014 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 29 Jan 2014 15:12:18 +0000 Subject: [Fiware-iot] R: Deliverables names for tracker In-Reply-To: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2FE5A14B0256E04A8E1E11135A41FA452D85B991@TELMBB001BA020.telecomitalia.local> Hi Thierry, as we agree I created these workitems as you requested. Let me know if they are ok or if it is needed to modify them. 6724 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.InstallationAndAdministrationGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6725 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UserAndProgrammerGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6726 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UnitTestPlan.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6727 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.Architecture.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Protocol Adapter ZPA 6728 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.OpenSpecification.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 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? 29 gennaio 2014 14:36 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Deliverables names for tracker Dear all, Regarding tickets we have to create in the tracker for documentation please put in comment the following: Unit Test Plan deliverable=D5.5.3 Inst&Admin Guide deliverable=D5.3.3 User&Prog Guide deliverable=D5.4.3 Architecture deliverable=D2.2.3 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, 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, 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. -------------- 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 Tobias.Jacobs at neclab.eu Wed Jan 29 16:31:31 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 29 Jan 2014 15:31:31 +0000 Subject: [Fiware-iot] New picture whole IoT Architecture In-Reply-To: <22420_1390983371_52E8B8CA_22420_6558_1_976A65C5A08ADF49B9A8523F7F81925C17DF3C@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <16419_1390491500_52E1376C_16419_2914_5_976A65C5A08ADF49B9A8523F7F81925C17D15E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8755F290097BD941865DC4245B335D2D47415655@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C544DC7@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D4741572E@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C545A8B@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415B3F@DAPHNIS.office.hd> <85A7992034599A4A83D05984B3A9EA712C5464CF@DEWDFEMB12A.global.corp.sap> <8755F290097BD941865DC4245B335D2D47415DBB@DAPHNIS.office.hd> <22420_1390983371_52E8B8CA_22420_6558_1_976A65C5A08ADF49B9A8523F7F81925C17DF3C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <8755F290097BD941865DC4245B335D2D474160D3@DAPHNIS.office.hd> Yes, this is how I imagined it :) Best Tobias From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: Mittwoch, 29. Januar 2014 09:16 To: Tobias Jacobs; Magerkurth, Carsten; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, all, Accordingly, the picture should be this one. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 29 janvier 2014 08:47 ? : Magerkurth, Carsten; NAGELLEN Thierry IMT/OLPS; fiware-iot at lists.fi-ware.eu Objet : RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thierry, all In the new architecture picture sent by Thierry last week I see a slight inconsistency, because the TH is connected to the IoT Broker GE at the Northbound interface (the one where data consumers are connected) and the TH is connected to the ConfMan GE via the interface where the data providers are connected. According to the current discussion the TH GE possibly plays both roles, but still we might consider making the NGSI 10 and NGSI 9 connections aligned. If the data consumer role is the more important one, this would mean connecting the TH to the ConfMan via the left-hand NGSI9 interface. Best regards Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Mittwoch, 29. Januar 2014 08:35 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, >>Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Ah I see, no, so far it is only a consumer, but I will check if we can register the templates in the Config Management, this would definitely make sense. best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Dienstag, 28. Januar 2014 11:36 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Thanks a lot for the link and the explanations! >From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data. Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Dienstag, 28. Januar 2014 09:08 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide best regards, Carsten From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Montag, 27. Januar 2014 09:10 To: Magerkurth, Carsten; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Carsten, Are there already flow charts and/or examples showing how the Template Handler interacts with the other components? Best Tobias From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com] Sent: Montag, 27. Januar 2014 08:53 To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] New picture whole IoT Architecture Hi Tobias, hi all, the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler. Best regards, Carsten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 24. Januar 2014 16:31 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] New picture whole IoT Architecture Hi Thierry, all, It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.). Can someone clarify? Thanks & best regards 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: Donnerstag, 23. Januar 2014 16:38 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] New picture whole IoT Architecture Hi All, Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong. 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, 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, 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, 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, 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 Jan 29 16:32:45 2014 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 29 Jan 2014 15:32:45 +0000 Subject: [Fiware-iot] IoT Broker tracker items Message-ID: <8755F290097BD941865DC4245B335D2D474160E0@DAPHNIS.office.hd> Hi Thierry, These are the new tracker items we created today. Best regards Tobias 6719 FIWARE.WorkItem.IoT.BackendIoTBroker.Documentation.UnitTestPlan.Update Closed Work Item None FIWARE.Sprint.3.3.1 3 Backend IoT Broker Default Impl 6720 FIWARE.WorkItem.IoT.BackendIoTBroker.Documentation.UserAndProgrammerGuide.Update Closed User Story None FIWARE.Sprint.3.3.1 3 Backend IoT Broker Default Impl 6721 FIWARE.WorkItem.IoT.BackendIoTBroker.Documentation.InstAndAdminGuide.Update Closed Work Item None FIWARE.Sprint.3.3.1 3 Backend IoT Broker Default Impl 6722 FIWARE.WorkItem.IoT.BackendIoTBroker.Documentation.Architecture.Contribute Closed Work Item None FIWARE.Sprint.3.3.1 3 Backend IoT Broker Default Impl 6723 FIWARE.WorkItem.IoT.BackendIoTBroker.Documentation.TechnicalRoadmap.Update Closed Work Item None FIWARE.Sprint.3.3.1 3 Backend IoT Broker Default Impl -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Jan 29 16:45:58 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 29 Jan 2014 15:45:58 +0000 Subject: [Fiware-iot] Deliverables names for tracker In-Reply-To: <2FE5A14B0256E04A8E1E11135A41FA452D85B991@TELMBB001BA020.telecomitalia.local> References: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2FE5A14B0256E04A8E1E11135A41FA452D85B991@TELMBB001BA020.telecomitalia.local> Message-ID: <29271_1391010359_52E92237_29271_18285_1_976A65C5A08ADF49B9A8523F7F81925C17E5F6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Sabrina, all, Maybe some misunderstanding on the numbering: ? We delivered Release 3.2 in sprint 3.2.3 ? We are closing now the sprint 3.3.1 during which one we were working on documentation for release 3.2.3, not documentation for release 3.3 BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : mercredi 29 janvier 2014 16:12 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] R: Deliverables names for tracker Hi Thierry, as we agree I created these workitems as you requested. Let me know if they are ok or if it is needed to modify them. 6724 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.InstallationAndAdministrationGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6725 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UserAndProgrammerGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6726 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UnitTestPlan.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6727 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.Architecture.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Protocol Adapter ZPA 6728 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.OpenSpecification.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 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? 29 gennaio 2014 14:36 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Deliverables names for tracker Dear all, Regarding tickets we have to create in the tracker for documentation please put in comment the following: Unit Test Plan deliverable=D5.5.3 Inst&Admin Guide deliverable=D5.3.3 User&Prog Guide deliverable=D5.4.3 Architecture deliverable=D2.2.3 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, 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, 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, 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, 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 sabrina.guerra at telecomitalia.it Wed Jan 29 16:57:42 2014 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 29 Jan 2014 15:57:42 +0000 Subject: [Fiware-iot] R: Deliverables names for tracker In-Reply-To: <29271_1391010359_52E92237_29271_18285_1_976A65C5A08ADF49B9A8523F7F81925C17E5F6@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <27211_1391002535_52E903A7_27211_3774_1_976A65C5A08ADF49B9A8523F7F81925C17E310@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2FE5A14B0256E04A8E1E11135A41FA452D85B991@TELMBB001BA020.telecomitalia.local> <29271_1391010359_52E92237_29271_18285_1_976A65C5A08ADF49B9A8523F7F81925C17E5F6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2FE5A14B0256E04A8E1E11135A41FA452D85BA46@TELMBB001BA020.telecomitalia.local> Hi Thierry, I updated the same workitems following your instructions. Let me know if they are ok. Best regards, Sabrina Da: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Inviato: mercoled? 29 gennaio 2014 16:46 A: Guerra Sabrina; fiware-iot at lists.fi-ware.eu Oggetto: RE: Deliverables names for tracker Hi Sabrina, all, Maybe some misunderstanding on the numbering: ? We delivered Release 3.2 in sprint 3.2.3 ? We are closing now the sprint 3.3.1 during which one we were working on documentation for release 3.2.3, not documentation for release 3.3 BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : mercredi 29 janvier 2014 16:12 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] R: Deliverables names for tracker Hi Thierry, as we agree I created these workitems as you requested. Let me know if they are ok or if it is needed to modify them. 6724 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.InstallationAndAdministrationGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6725 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UserAndProgrammerGuide.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6726 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.UnitTestPlan.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 6727 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.Architecture.Update Closed Work Item FIWARE.Release.3.2 FIWARE.Sprint.3.2.3 3 Gateway Protocol Adapter ZPA 6728 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.ZPA.Documentation.OpenSpecification.Update Open Work Item FIWARE.Release.3.3 FIWARE.Sprint.3.3.3 3 Gateway Protocol Adapter ZPA 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? 29 gennaio 2014 14:36 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Deliverables names for tracker Dear all, Regarding tickets we have to create in the tracker for documentation please put in comment the following: Unit Test Plan deliverable=D5.5.3 Inst&Admin Guide deliverable=D5.3.3 User&Prog Guide deliverable=D5.4.3 Architecture deliverable=D2.2.3 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, 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, 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, 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, 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 matthias.thoma at sap.com Wed Jan 29 18:33:29 2014 From: matthias.thoma at sap.com (Thoma, Matthias) Date: Wed, 29 Jan 2014 17:33:29 +0000 Subject: [Fiware-iot] SAP tracker items Message-ID: Hello Thierry, We just created the following items: 6737 FIWARE.WorkItem.IoT.BackendTemplateHandler.Documentation.Architecture.Contribute 6736 FIWARE.WorkItem.IoT.BackendTemplateHandler.Documentation.UnitTestPlan 6735 FIWARE.WorkItem.IoT.BackendTemplateHandler.Documentation.UserAndProgrammerGuide 6734 FIWARE.WorkItem.IoT.BackendTemplateHandler.Documentation.InstallationAndAdministrationGuide 6733 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.MRCoAP.Documentation.UnitTestPlan 6732 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.MRCoAP.Documentation.UserAndProgrammerGuide 6731 FIWARE.WorkItem.IoT.GatewayProtocolAdapter.MRCoAP.Documentation.InstallationAndAdministrationGuide -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Thu Jan 30 16:28:37 2014 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 30 Jan 2014 15:28:37 +0000 Subject: [Fiware-iot] Backlog status Message-ID: <28696_1391095720_52EA6FA6_28696_8381_1_976A65C5A08ADF49B9A8523F7F81925C17EA83@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is the status providing by Manuel this morning. We are now in a good shape so please, think to close the sprint 3.3.1. What does it mean? ? All tickets currently with status open or scheduled should be updated for sprint 3.3.2 , except workitems which have to be closed ? Tickets with status under execution or under validation could also be transferred in 3.3.2 but the next status would usually be closed Thanks for the work you have done. BR Thierry De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Envoy? : jeudi 30 janvier 2014 08:59 ? : NAGELLEN Thierry IMT/OLPS Objet : RE: Dashboard IoT Hi Thierry, True it looks nice! A bit of some effort next days to close the sprint!! ? and you?ll have a perfect closing!! Good!!!! [cid:image001.png at 01CF1D99.6CB0C680] Kind regards, Manuel From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: jueves, 30 de enero de 2014 8:05 To: MANUEL ESCRICHE VICENTE Subject: Dashboard IoT Hi Manuel, I think that many partners did their homework yesterday. Could you create a new version of the dashboard so it will be easier for me to check what is missing this afternoon? BR Thierry 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, 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, 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 _________________________________________________________________________________________________________________________ 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, 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, 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: 13573 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.iot.dashboard.20140130.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 387460 bytes Desc: FIWARE.backlog.iot.dashboard.20140130.xlsx URL: