From thierry.nagellen at orange.com Mon Sep 2 22:55:20 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 2 Sep 2013 20:55:20 +0000 Subject: [Fiware-iot] Info about Campus Party Message-ID: <1956_1378155320_5224FB38_1956_13199_1_976A65C5A08ADF49B9A8523F7F81925C10CBB3@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here are the last information I have about Campus Party. You can see that we use a new logo and we have now a policy for communication (specific colors) https://docs.google.com/document/d/1K_xvd2eDXU2_AtW1OXFnclXFBYiqQCt9ekonN78BDGg/edit?pli=1# And a picture to show that we are really visible as a platinum sponsor of the event. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: P1030563r.JPG Type: image/jpeg Size: 161364 bytes Desc: P1030563r.JPG URL: From Tobias.Jacobs at neclab.eu Wed Sep 4 15:53:27 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 4 Sep 2013 13:53:27 +0000 Subject: [Fiware-iot] new tracker / R3 features Message-ID: <8755F290097BD941865DC4245B335D2D38FE8F72@PALLENE.office.hd> Hi Thierry, all, I started to put our R3 features into the private wiki. (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/TechnicalRoadmapR3-IoT) I guess we also need to create tracker items for them. Should I use the tracker for that as always, or is this what should go into the new tracker system? Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Tue Sep 10 10:13:19 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 10 Sep 2013 08:13:19 +0000 Subject: [Fiware-iot] telco tomorrow? Message-ID: <8755F290097BD941865DC4245B335D2D38FEA442@PALLENE.office.hd> Dear all, Will we have a telco tomorrow morning? Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Tue Sep 10 12:37:01 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 10 Sep 2013 10:37:01 +0000 Subject: [Fiware-iot] telco tomorrow? In-Reply-To: <8755F290097BD941865DC4245B335D2D38FEA442@PALLENE.office.hd> Message-ID: Ok, from my side, but after the Campus Party I think Thierry may suggest better the agenda. I can summarize the IoT challenge during the Campus (I would need some 20-30'). Best regards, De: Tobias Jacobs > Fecha: martes, 10 de septiembre de 2013 10:13 Para: "fiware-iot at lists.fi-ware.eu" > Asunto: [Fiware-iot] telco tomorrow? Dear all, Will we have a telco tomorrow morning? Best Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Sep 11 08:38:18 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 11 Sep 2013 06:38:18 +0000 Subject: [Fiware-iot] telco tomorrow? In-Reply-To: References: <8755F290097BD941865DC4245B335D2D38FEA442@PALLENE.office.hd> Message-ID: <31992_1378881499_52300FDB_31992_2785_1_976A65C5A08ADF49B9A8523F7F81925C10FD03@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is the link for the minutes today. After a very good Campus Party, we have now to come back on concrete points for R3 developments. https://docs.google.com/document/d/1Samgk6109uCduCxdiacja2FAMbQSGCLf3zWdajHSa-s/edit?usp=sharing BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de CARLOS RALLI UCENDO Envoy? : mardi 10 septembre 2013 12:37 ? : Tobias Jacobs; fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] telco tomorrow? Ok, from my side, but after the Campus Party I think Thierry may suggest better the agenda. I can summarize the IoT challenge during the Campus (I would need some 20-30'). Best regards, De: Tobias Jacobs > Fecha: martes, 10 de septiembre de 2013 10:13 Para: "fiware-iot at lists.fi-ware.eu" > Asunto: [Fiware-iot] telco tomorrow? Dear all, Will we have a telco tomorrow morning? Best Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ 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 Sep 11 10:17:16 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 11 Sep 2013 08:17:16 +0000 Subject: [Fiware-iot] Pictures from Campus Party Message-ID: <14683_1378887438_5230270D_14683_581_1_976A65C5A08ADF49B9A8523F7F81925C10FDB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> To have a look on how it was 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: NellyKroesStandFiWare.jpg Type: image/jpeg Size: 351948 bytes Desc: NellyKroesStandFiWare.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2ndWorkshop.JPG Type: image/jpeg Size: 371458 bytes Desc: 2ndWorkshop.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: crowdy.jpg Type: image/jpeg Size: 179151 bytes Desc: crowdy.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FiWareSponsor.jpg Type: image/jpeg Size: 368057 bytes Desc: FiWareSponsor.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fiware-workshop.jpg Type: image/jpeg Size: 162908 bytes Desc: fiware-workshop.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hackaton.JPG Type: image/jpeg Size: 172625 bytes Desc: hackaton.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NeelieKroes-CarlosDomingo.jpg Type: image/jpeg Size: 159216 bytes Desc: NeelieKroes-CarlosDomingo.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NeelieKroes-FiwareStand.jpg Type: image/jpeg Size: 152026 bytes Desc: NeelieKroes-FiwareStand.jpg URL: From t.elsaleh at surrey.ac.uk Wed Sep 11 12:59:27 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 11 Sep 2013 11:59:27 +0100 Subject: [Fiware-iot] Feedback about CampusParty Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8730F7@EXMB05CMS.surrey.ac.uk> Hello Carlos, Looking back at the workshops, a guess a few points to look at would be: * To emphasize on example use cases on how the GEs can be used, in order to help better understand the purpose of the GEs and to stimulate ideas, by. The use case projects from at least the previous phase should provide a good reference for this. * To provide a "getting started" booklet (hard copy...not just slides and wikis), from FI-LAB access to GE installation and instantiation to assure developers on how to setup, so they can focus on their idea and its implementation. * A running example for IoT. Please correct me if any of these points were covered. By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward? 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: 11 September 2013 09:17 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Pictures from Campus Party To have a look on how it was 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 Wed Sep 11 16:08:12 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 11 Sep 2013 14:08:12 +0000 Subject: [Fiware-iot] IoT Backlog: actions to do Message-ID: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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: FIWARE.backlog.iot.report.20130909-1531-TNA.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 246492 bytes Desc: FIWARE.backlog.iot.report.20130909-1531-TNA.xlsx URL: From thierry.nagellen at orange.com Wed Sep 11 16:20:30 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 11 Sep 2013 14:20:30 +0000 Subject: [Fiware-iot] Tools and links for the eLearning platform Message-ID: <23580_1378909232_52307C30_23580_7500_1_976A65C5A08ADF49B9A8523F7F81925C10FF48@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, I've updated the minutes of today meeting with the relevant links and tools you can use to prepare the courses, thanks to Davide ( davide.dallecarbonare at eng.it ) who is your support for more specific questions. There I no urgent issue except that we have to populate the eLearning platform for the next review (November) so do not wait for the last minute and describe work items in the backlog for that. Thanks. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, 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 Sep 11 16:53:20 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 11 Sep 2013 14:53:20 +0000 Subject: [Fiware-iot] Update technical Roadmap R3 Message-ID: <21912_1378911201_523083E1_21912_166_1_976A65C5A08ADF49B9A8523F7F81925C10FF9A@PEXCVZYM13.corporate.adroot.infra.ftgroup> Based on what we discussed this morning, I've build the 2 tables (Backend + Gateway) in the public wiki so you can fulfill them now. Using what Tobias did in the private page, I've just deleted the sub-titles Release 3.2 and Release 3.3 and grouped everything under Other Releases 3.X http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services#Future_Releases 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 Wed Sep 11 18:01:40 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 11 Sep 2013 18:01:40 +0200 Subject: [Fiware-iot] Feedback about CampusParty [bad feedback regarding no JSON support in NGSI API...] In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8730F7@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8730F7@EXMB05CMS.surrey.ac.uk> Message-ID: <523093E4.1060106@tid.es> Dear Talek, (I'm CCing fiware-ngsi list, as I think the topic lies within its scope) "By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward?" I have direct feedback in that point from several talk with developers at Campus Party... and I'm afraid to tell that developers don't like XML rendering in REST APIs, as our current NGSI API is. In other words, developers love JSON (as is really easy to use from very popular languages as Python and JavaScript) and hate XML. However, nothing new here: we have been getting the same feedback from developers during about one year. I think we desperately need a JSON rendering for NGSI to remove this adoption barrier. In this sense, our (TID) plan is the following: 1. Work on a .json "translation" for each one of the .xml in https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/ and https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-10/ 2. Get feedback from you (i.e. people involved in NGSI in FI-WARE) in the hope we can reach a common agreement on the format 3. Implement the support of that format in Orion Context Broker Best regards, ------ Ferm?n El 11/09/2013 12:59, t.elsaleh at surrey.ac.uk escribi?: Hello Carlos, Looking back at the workshops, a guess a few points to look at would be: ? To emphasize on example use cases on how the GEs can be used, in order to help better understand the purpose of the GEs and to stimulate ideas, by. The use case projects from at least the previous phase should provide a good reference for this. ? To provide a "getting started" booklet (hard copy...not just slides and wikis), from FI-LAB access to GE installation and instantiation to assure developers on how to setup, so they can focus on their idea and its implementation. ? A running example for IoT. Please correct me if any of these points were covered. By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward? 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: 11 September 2013 09:17 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Pictures from Campus Party To have a look on how it was 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. _______________________________________________ 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 jhierro at tid.es Thu Sep 12 12:42:55 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 12 Sep 2013 12:42:55 +0200 Subject: [Fiware-iot] Feedback about CampusParty [bad feedback regarding no JSON support in NGSI API...] In-Reply-To: <523093E4.1060106@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8730F7@EXMB05CMS.surrey.ac.uk> <523093E4.1060106@tid.es> Message-ID: <52319AAF.2050101@tid.es> Hi all, I agree that defining a JSON binding for NGSI should be assigned the highest priority. It will definitively lower the barriers for adoption. Please start the discussion on the matter (I believe that fiware-ngsi is the proper list for doing so) so that we can publish a final open spec asap. Best regards, -- Juanjo On 11/09/13 18:01, Ferm?n Gal?n M?rquez wrote: Dear Talek, (I'm CCing fiware-ngsi list, as I think the topic lies within its scope) "By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward?" I have direct feedback in that point from several talk with developers at Campus Party... and I'm afraid to tell that developers don't like XML rendering in REST APIs, as our current NGSI API is. In other words, developers love JSON (as is really easy to use from very popular languages as Python and JavaScript) and hate XML. However, nothing new here: we have been getting the same feedback from developers during about one year. I think we desperately need a JSON rendering for NGSI to remove this adoption barrier. In this sense, our (TID) plan is the following: 1. Work on a .json "translation" for each one of the .xml in https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/ and https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-10/ 2. Get feedback from you (i.e. people involved in NGSI in FI-WARE) in the hope we can reach a common agreement on the format 3. Implement the support of that format in Orion Context Broker Best regards, ------ Ferm?n El 11/09/2013 12:59, t.elsaleh at surrey.ac.uk escribi?: Hello Carlos, Looking back at the workshops, a guess a few points to look at would be: ? To emphasize on example use cases on how the GEs can be used, in order to help better understand the purpose of the GEs and to stimulate ideas, by. The use case projects from at least the previous phase should provide a good reference for this. ? To provide a "getting started" booklet (hard copy...not just slides and wikis), from FI-LAB access to GE installation and instantiation to assure developers on how to setup, so they can focus on their idea and its implementation. ? A running example for IoT. Please correct me if any of these points were covered. By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward? 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: 11 September 2013 09:17 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Pictures from Campus Party To have a look on how it was 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. _______________________________________________ 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 _______________________________________________ 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 ralli at tid.es Thu Sep 12 14:55:28 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 12 Sep 2013 12:55:28 +0000 Subject: [Fiware-iot] Feedback about CampusParty [bad feedback regarding no JSON support in NGSI API...] In-Reply-To: <52319AAF.2050101@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8730F7@EXMB05CMS.surrey.ac.uk> <523093E4.1060106@tid.es> <52319AAF.2050101@tid.es> Message-ID: <8E02457F-B8ED-4979-A94B-7498687FC1B7@tid.es> +1 Thx for your feedback Tarek/Fermin. Cheers, El 12/09/2013, a las 12:39, "Juanjo Hierro" > escribi?: Hi all, I agree that defining a JSON binding for NGSI should be assigned the highest priority. It will definitively lower the barriers for adoption. Please start the discussion on the matter (I believe that fiware-ngsi is the proper list for doing so) so that we can publish a final open spec asap. Best regards, -- Juanjo On 11/09/13 18:01, Ferm?n Gal?n M?rquez wrote: Dear Talek, (I'm CCing fiware-ngsi list, as I think the topic lies within its scope) "By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward?" I have direct feedback in that point from several talk with developers at Campus Party... and I'm afraid to tell that developers don't like XML rendering in REST APIs, as our current NGSI API is. In other words, developers love JSON (as is really easy to use from very popular languages as Python and JavaScript) and hate XML. However, nothing new here: we have been getting the same feedback from developers during about one year. I think we desperately need a JSON rendering for NGSI to remove this adoption barrier. In this sense, our (TID) plan is the following: 1. Work on a .json "translation" for each one of the .xml in https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-9/ and https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/schemes/xml_examples/ngsi-10/ 2. Get feedback from you (i.e. people involved in NGSI in FI-WARE) in the hope we can reach a common agreement on the format 3. Implement the support of that format in Orion Context Broker Best regards, ------ Ferm?n El 11/09/2013 12:59, t.elsaleh at surrey.ac.uk escribi?: Hello Carlos, Looking back at the workshops, a guess a few points to look at would be: ? To emphasize on example use cases on how the GEs can be used, in order to help better understand the purpose of the GEs and to stimulate ideas, by. The use case projects from at least the previous phase should provide a good reference for this. ? To provide a ?getting started? booklet (hard copy?not just slides and wikis), from FI-LAB access to GE installation and instantiation to assure developers on how to setup, so they can focus on their idea and its implementation. ? A running example for IoT. Please correct me if any of these points were covered. By the way, how did the developers find editing the NGSI descriptions? Was it straight-forward? 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: 11 September 2013 09:17 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Pictures from Campus Party To have a look on how it was 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. _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 t.elsaleh at surrey.ac.uk Mon Sep 16 12:43:50 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Mon, 16 Sep 2013 11:43:50 +0100 Subject: [Fiware-iot] IoT Backlog: actions to do In-Reply-To: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C8733B0@EXMB05CMS.surrey.ac.uk> Hello Thierry, Just to confirm with regards to the backlog, I will change the items that belong to "Backend IoT Discovery" Generic Enabler to "Backend ConfManager", and the GE Implementation field to "IoT Discovery". Also, I am having a problem changing the "workflow state" for the items for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed". Is there a reason for this, or somewhere I can refer to for clarification? 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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 Sep 17 17:34:49 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 17 Sep 2013 15:34:49 +0000 Subject: [Fiware-iot] IoT Conference call tomorrow at 10h Message-ID: Dear colleagues, Just to confirm our meeting tomorrow. The googledoc we're using is hereby linked: https://docs.google.com/document/d/1LyYb89yfnV6ozqJtDPPksR_hDMdZNSvOB_JwdRMW_Yw/edit Agenda is currently almost empty, but Thierry and myself will be completing it ASAP. Should you have suggestions, please do use the AoB section and we will re-arrange it before the call. BR. -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ 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 Sep 17 19:04:08 2013 From: carsten.magerkurth at sap.com (Magerkurth, Carsten) Date: Tue, 17 Sep 2013 17:04:08 +0000 Subject: [Fiware-iot] NGSI Test Tool In-Reply-To: <85A7992034599A4A83D05984B3A9EA710D0A3367@DEWDFEMB12A.global.corp.sap> References: <85A7992034599A4A83D05984B3A9EA710D090481@DEWDFEMB12A.global.corp.sap> <2DBE6F3EB08E3B41AABF6F593309AE420143D045@EX01.APAOS.local> <85A7992034599A4A83D05984B3A9EA710D091EDB@DEWDFEMB12A.global.corp.sap> <85A7992034599A4A83D05984B3A9EA710D0A3367@DEWDFEMB12A.global.corp.sap> Message-ID: <85A7992034599A4A83D05984B3A9EA710D0B6FA1@DEWDFEMB12A.global.corp.sap> Dear all, the NGSI test tool is now (in addition to our own hosting) finally also officially available in the FIWARE testbed at http://130.206.81.55/NGSI10. to get started, please find a skeleton Eclipse project from Klaus that could help implementing a client calling the server. Attached for your reference is also the current test coverage / implementation status. Please let us know if you need any help / features / etc. best regards! Carsten -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NGSI10-Server-Implementation Status.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 19753 bytes Desc: NGSI10-Server-Implementation Status.xlsx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ExampleClient.zip Type: application/x-zip-compressed Size: 2658626 bytes Desc: ExampleClient.zip URL: From konrad.campowsky at fokus.fraunhofer.de Wed Sep 18 09:24:50 2013 From: konrad.campowsky at fokus.fraunhofer.de (Konrad Campowsky) Date: Wed, 18 Sep 2013 09:24:50 +0200 Subject: [Fiware-iot] IoT Conference call tomorrow at 10h In-Reply-To: References: Message-ID: <52395542.3060903@fokus.fraunhofer.de> Dear Carlos, My apologies, I won't be able to join the call today since I'm travelling. Best regards, Konrad Am 17.09.2013 17:34, schrieb CARLOS RALLI UCENDO: > Dear colleagues, > > Just to confirm our meeting tomorrow. The googledoc we're using is > hereby linked: > https://docs.google.com/document/d/1LyYb89yfnV6ozqJtDPPksR_hDMdZNSvOB_JwdRMW_Yw/edit > > Agenda is currently almost empty, but Thierry and myself will be > completing it ASAP. > Should you have suggestions, please do use the AoB section and we will > re-arrange it before the call. > > BR. > -- > > ------------------------------------------------------------------------------------------------------------------------ > > Carlos Ralli Ucendo (ralli at tid.es ) > > Cell: +34696923588 > > Twitter: @carlosralli > > IPv6 Blog: http://the-internet6.blogspot.com.es > > > Product Development & Innovation > > Telef?nica I+D SAU > > Madrid, Spain > > ------------------------------------------------------------------------------------------------------------------------ > > Follow FI-WARE project (Future Internet Services Core Platform): > > Website: http://www.fi-ware.eu > > Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > > Twitter: @fiware > > LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace > situado m?s abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-iot > From t.elsaleh at surrey.ac.uk Wed Sep 18 10:53:35 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 18 Sep 2013 09:53:35 +0100 Subject: [Fiware-iot] FW: IoT Backlog: actions to do References: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873595@EXMB05CMS.surrey.ac.uk> Hello Carlos, All, For backlog cleaning, I am having a problem changing the "workflow state" for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed". Is there a reason for this, or somewhere I can refer to for clarification? By the way, does "closed" mean it is done? 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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 Wed Sep 18 11:00:16 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 18 Sep 2013 09:00:16 +0000 Subject: [Fiware-iot] IoT Backlog: actions to do In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873595@EXMB05CMS.surrey.ac.uk> Message-ID: I have forwarded your question to my colleague Manuel to see if he can help you. Best regards De: "t.elsaleh at surrey.ac.uk" > Fecha: mi?rcoles, 18 de septiembre de 2013 10:53 Para: Carlos Ralli Ucendo >, "thierry.nagellen at orange.com" > CC: "fiware-iot at lists.fi-ware.eu" > Asunto: FW: IoT Backlog: actions to do Hello Carlos, All, For backlog cleaning, I am having a problem changing the ?workflow state? for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can?t select). For example, if there is an item with ?under execution?, I cannot change it to ?closed?. Is there a reason for this, or somewhere I can refer to for clarification? By the way, does ?closed? mean it is done? 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which ?old? GE and in which GE the existing features should go. We have to provide for October the new deliverable ?Backlog? so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2?), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I?ve asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.artusio at orange.com Wed Sep 18 11:05:05 2013 From: laurent.artusio at orange.com (laurent.artusio at orange.com) Date: Wed, 18 Sep 2013 09:05:05 +0000 Subject: [Fiware-iot] IoT Backlog: actions to do In-Reply-To: References: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873595@EXMB05CMS.surrey.ac.uk> Message-ID: <18566_1379495105_52396CC1_18566_5241_1_ADCB0720D5A0114384E4F982EFCDBAA9087999@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hello Tarek, It is normal that you can't directly switch from "under execution" to "closed". There is a workflow to follow. At first, try to switch from "under execution" to "under verification". After that you should be able to close the tracker. BR, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de CARLOS RALLI UCENDO Envoy? : mercredi 18 septembre 2013 11:00 ? : t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] IoT Backlog: actions to do I have forwarded your question to my colleague Manuel to see if he can help you. Best regards De: "t.elsaleh at surrey.ac.uk" > Fecha: mi?rcoles, 18 de septiembre de 2013 10:53 Para: Carlos Ralli Ucendo >, "thierry.nagellen at orange.com" > CC: "fiware-iot at lists.fi-ware.eu" > Asunto: FW: IoT Backlog: actions to do Hello Carlos, All, For backlog cleaning, I am having a problem changing the "workflow state" for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed". Is there a reason for this, or somewhere I can refer to for clarification? By the way, does "closed" mean it is done? 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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: From mev at tid.es Wed Sep 18 11:15:36 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Wed, 18 Sep 2013 09:15:36 +0000 Subject: [Fiware-iot] IoT Backlog: actions to do In-Reply-To: References: <18566_1379495105_52396CC1_18566_5241_1_ADCB0720D5A0114384E4F982EFCDBAA9087999@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B890B0B12@EX10-MB2-MAD.hi.inet> Hi Tarek, Let me confirm what Laurent reported. The workflow expects there's some verification after execution was done. If the normal worlflow wouldn't be it, please, let me know. Additionally, Closed means it's finished. If any other related question, please, don't hesitate to let me know. Kind regards, Manuel De: "laurent.artusio at orange.com" > Fecha: mi?rcoles, 18 de septiembre de 2013 11:05 Para: Carlos Ralli Ucendo >, "t.elsaleh at surrey.ac.uk" > CC: "fiware-iot at lists.fi-ware.eu" > Asunto: RE: [Fiware-iot] IoT Backlog: actions to do Hello Tarek, It is normal that you can't directly switch from "under execution" to "closed". There is a workflow to follow. At first, try to switch from "under execution" to "under verification". After that you should be able to close the tracker. BR, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de CARLOS RALLI UCENDO Envoy? : mercredi 18 septembre 2013 11:00 ? : t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] IoT Backlog: actions to do I have forwarded your question to my colleague Manuel to see if he can help you. Best regards De: "t.elsaleh at surrey.ac.uk" > Fecha: mi?rcoles, 18 de septiembre de 2013 10:53 Para: Carlos Ralli Ucendo >, "thierry.nagellen at orange.com" > CC: "fiware-iot at lists.fi-ware.eu" > Asunto: FW: IoT Backlog: actions to do Hello Carlos, All, For backlog cleaning, I am having a problem changing the "workflow state" for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed". Is there a reason for this, or somewhere I can refer to for clarification? By the way, does "closed" mean it is done? 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed Sep 18 11:50:17 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 18 Sep 2013 09:50:17 +0000 Subject: [Fiware-iot] IoT Backlog: actions to do In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873595@EXMB05CMS.surrey.ac.uk> References: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873595@EXMB05CMS.surrey.ac.uk> Message-ID: <8755F290097BD941865DC4245B335D2D39001732@DAPHNIS.office.hd> Hi Tarek, As far as I figured out you can always only go the next possible state. So you first have to set your item to "under verification" and after that you can set it to "closed". Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk Sent: Mittwoch, 18. September 2013 10:54 To: ralli at tid.es; thierry.nagellen at orange.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: IoT Backlog: actions to do Hello Carlos, All, For backlog cleaning, I am having a problem changing the "workflow state" for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed". Is there a reason for this, or somewher ification? By the way, does "closed" mean it is done? Best regards, Tarek From: mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to tran n another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who :p> For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir de s inform 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. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Sep 18 18:43:16 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 18 Sep 2013 17:43:16 +0100 Subject: [Fiware-iot] Tools and links for the eLearning platform In-Reply-To: <23580_1378909232_52307C30_23580_7500_1_976A65C5A08ADF49B9A8523F7F81925C10FF48@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <23580_1378909232_52307C30_23580_7500_1_976A65C5A08ADF49B9A8523F7F81925C10FF48@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873664@EXMB05CMS.surrey.ac.uk> Hello Thierry, All, How should we name the work item in the backlog for the eLearningPlatform. Should it be something like this: "FIWARE.Epic.IoT.Backend.{GE name}.{GEI name}.eLearningPlatform" ? 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: 11 September 2013 15:21 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Tools and links for the eLearning platform Hi all, I've updated the minutes of today meeting with the relevant links and tools you can use to prepare the courses, thanks to Davide ( davide.dallecarbonare at eng.it ) who is your support for more specific questions. There I no urgent issue except that we have to populate the eLearning platform for the next review (November) so do not wait for the last minute and describe work items in the backlog for that. Thanks. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, 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 Wed Sep 18 19:02:48 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 18 Sep 2013 18:02:48 +0100 Subject: [Fiware-iot] FW: IoT Backlog: actions to do In-Reply-To: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <12690_1378908494_5230794D_12690_5741_1_976A65C5A08ADF49B9A8523F7F81925C10FF31@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB07C873666@EXMB05CMS.surrey.ac.uk> Hello Fermin, (Thierry), In relation to the point by Thierry about: "For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features." We had a similar discussion about this a few months ago about "functional and non-functional features". I guess the common features will lie with the functional features, meaning the ones related to implementation of the NGSI spec. I believe these are (at least): ? Standard operations ? Convenience operations ? Associations ? JSON support Now I am not sure about the next step. There are some features you have defined in release 2 that relate to the above features, but under "ContextBroker". The conflict with what Thierry wants is that the GE instance is used in the naming of the feature. Even if we don't chose an GE Implementation in the tracker, the GE implementation is still referred to in the name (or "summary") itself. Does this mean we need to rename some or all the features we have described in Release 2, so that all features come under: "FIWARE.Feature.IoT.Backend.ConfManager..."? Also, how do we differentiate when it comes to the progress (workflow state) for each common feature (or it's work items) of a GEi? For example, there some that might have been completed for one GEi, and another has not yet been completed. 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: 11 September 2013 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT Backlog: actions to do Hi all, Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go. We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content. Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before. For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance. This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features. I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap). Thanks for your support. BR Thierry PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check. _________________________________________________________________________________________________________________________ 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: FIWARE.backlog.iot.report.20130909-1531-TNA.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 246492 bytes Desc: FIWARE.backlog.iot.report.20130909-1531-TNA.xlsx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From matthias.thoma at sap.com Tue Sep 24 14:36:52 2013 From: matthias.thoma at sap.com (Thoma, Matthias) Date: Tue, 24 Sep 2013 12:36:52 +0000 Subject: [Fiware-iot] ZPA protocol adapter / GAL Message-ID: Hello all, I am kind of lost in the million places the FI-WARE software can be downloaded from. I am currently trying to setup the Zigbee Protocol Adapter on Linux and need the GAL software (as described here http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ZigBee_GAL). I found a version on the FI-WARE site which contains an exe file and bunch of DLLs, but I am looking for the Linux or (even better) Java version as described on the wiki. 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 Please consider to send me encrypted mail: http://keys.sap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Sep 25 09:23:18 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 25 Sep 2013 07:23:18 +0000 Subject: [Fiware-iot] No weekly meeting today Message-ID: <4991_1380093799_52428F67_4991_1437_1_976A65C5A08ADF49B9A8523F7F81925C111F54@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi All, I'm too busy with some dissemination activities (Orange internal and external too) to organize the meeting today. I'm coming to you by email tomorrow after checking the Tech Roadmap and revising the main deadlines we have for the coming weeks. I have a meeting tomorrow afternoon with Manuel about the backlog. I received many automatic emails about some tickets so I expect that we are in a good shape now. For some of you who did not clean the backlog, please do it because this is one deliverable we have to do for the end of September! Thanks for your support. 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: