From Martin.Bauer at neclab.eu Mon Jun 3 09:58:21 2013 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Mon, 3 Jun 2013 07:58:21 +0000 Subject: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week Message-ID: Hi all, After coming back from my vacation, I had a look at the IoT Week agenda and the planned IERC AC1/FI-Ware meeting. The organizers had suggested to synchronize with AC4 activities, however it seems that IERC AC4 has already planned a full day meeting on the topics of service openness and interoperability on Tuesday 18th, also there are IoT-A activities in parallel that in one case I should and in the other I have to attend. I now discussed with the organizers and I suggest moving the IERC AC1 / FI-WARE meeting to Wednesday 19th morning. Could the people who plan to attend this meeting please give me feedback whether this is possible for them? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From domenico.rotondi at txtgroup.com Mon Jun 3 11:23:59 2013 From: domenico.rotondi at txtgroup.com (Domenico Rotondi) Date: Mon, 3 Jun 2013 11:23:59 +0200 Subject: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week In-Reply-To: References: Message-ID: <51AC60AF.8031.2A38EB@domenico.rotondi.txtgroup.com> Hi Martin (and all), on Wednesday 19th I already have other sessions scheduled (in the morning the session on IoT for Manufacturing FITMAN organised, in the afternoon I have another duty but the Sergio Gusmeroli could attend the session). So let's try to phase having the IoT for Manufacturing (in the morning) not overlapped with the Fi-Ware/IoT session. Ciao Domenico On 3 Jun 2013 at 7:58, Martin Bauer wrote: Hi all, After coming back from my vacation, I had a look at the IoT Week agenda and the planned IERC AC1/FI-Ware meeting. The organizers had suggested to synchronize with AC4 activities, however it seems that IERC AC4 has already planned a full day meeting on the topics of service openness and interoperability on Tuesday 18th, also there are IoT-A activities in parallel that in one case I should and in the other I have to attend. I now discussed with the organizers and I suggest moving the IERC AC1 / FI-WARE meeting to Wednesday 19th morning. Could the people who plan to attend this meeting please give me feedback whether this is possible for them? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Tue Jun 4 09:58:01 2013 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Tue, 4 Jun 2013 07:58:01 +0000 Subject: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week In-Reply-To: <51AC60AF.8031.2A38EB@domenico.rotondi.txtgroup.com> References: <51AC60AF.8031.2A38EB@domenico.rotondi.txtgroup.com> Message-ID: Hi all, Due to various overlaps, I?d suggest to schedule the IERC AC1 / FI-WARE meeting on architecture on Wednesday between 08:00 and 10:00 EEST ? this would mean getting up early , but would result in only a partial overlap for a few people. I also still need confirmation from the organizers and Laure is out-of-office today ? but apart from that ? are there any objections? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 From: Domenico Rotondi [mailto:domenico.rotondi at txtgroup.com] Sent: Monday, June 03, 2013 11:24 AM To: Martin Bauer Cc: Peter.FRIESS at ec.europa.eu; Le Gall, Franck; levent.gurgen at cea.fr; ac_architecture at internet-of-things-research.eu; fiware-iot at lists.fi-ware.eu Subject: Re: IERC AC1 / FI-WARE meeting on architecture @ IoT Week Importance: High Hi Martin (and all), on Wednesday 19th I already have other sessions scheduled (in the morning the session on IoT for Manufacturing FITMAN organised, in the afternoon I have another duty but the Sergio Gusmeroli could attend the session). So let's try to phase having the IoT for Manufacturing (in the morning) not overlapped with the Fi-Ware/IoT session. Ciao Domenico ________________________________ On 3 Jun 2013 at 7:58, Martin Bauer wrote: Hi all, After coming back from my vacation, I had a look at the IoT Week agenda and the planned IERC AC1/FI-Ware meeting. The organizers had suggested to synchronize with AC4 activities, however it seems that IERC AC4 has already planned a full day meeting on the topics of service openness and interoperability on Tuesday 18th, also there are IoT-A activities in parallel that in one case I should and in the other I have to attend. I now discussed with the organizers and I suggest moving the IERC AC1 / FI-WARE meeting to Wednesday 19th morning. Could the people who plan to attend this meeting please give me feedback whether this is possible for them? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Tue Jun 4 16:27:06 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Tue, 04 Jun 2013 14:27:06 +0000 Subject: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week In-Reply-To: Message-ID: <1971FF81B8E01C45991F6F92B9E3B25089095ACF@EX10-MB2-MAD.hi.inet> Hi Martin, As discussed in our meeting at Dublin FIA I have set a wiki-page with the necessary links and info from both sides: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities_IERC For IERC completing its section we have two possibilities: 1) You (as member of the FI-PPP and FI-WARE) have editing rights for that page. 2) Someone can send me an e-mail and I can update it for you. What we need first is a set of links to the most updated IoT-A architecture to understand common and different points. Cheers, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ De: Martin Bauer > Fecha: martes, 4 de junio de 2013 09:58 Para: "ac_architecture at internet-of-things-research.eu" >, "fiware-iot at lists.fi-ware.eu" > CC: "Quintin, Laure (laure.quintin at vdivde-it.de)" >, "Peter.FRIESS at ec.europa.eu" > Asunto: Re: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week Hi all, Due to various overlaps, I?d suggest to schedule the IERC AC1 / FI-WARE meeting on architecture on Wednesday between 08:00 and 10:00 EEST ? this would mean getting up early , but would result in only a partial overlap for a few people. I also still need confirmation from the organizers and Laure is out-of-office today ? but apart from that ? are there any objections? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 From: Domenico Rotondi [mailto:domenico.rotondi at txtgroup.com] Sent: Monday, June 03, 2013 11:24 AM To: Martin Bauer Cc: Peter.FRIESS at ec.europa.eu; Le Gall, Franck; levent.gurgen at cea.fr; ac_architecture at internet-of-things-research.eu; fiware-iot at lists.fi-ware.eu Subject: Re: IERC AC1 / FI-WARE meeting on architecture @ IoT Week Importance: High Hi Martin (and all), on Wednesday 19th I already have other sessions scheduled (in the morning the session on IoT for Manufacturing FITMAN organised, in the afternoon I have another duty but the Sergio Gusmeroli could attend the session). So let's try to phase having the IoT for Manufacturing (in the morning) not overlapped with the Fi-Ware/IoT session. Ciao Domenico ________________________________ On 3 Jun 2013 at 7:58, Martin Bauer wrote: Hi all, After coming back from my vacation, I had a look at the IoT Week agenda and the planned IERC AC1/FI-Ware meeting. The organizers had suggested to synchronize with AC4 activities, however it seems that IERC AC4 has already planned a full day meeting on the topics of service openness and interoperability on Tuesday 18th, also there are IoT-A activities in parallel that in one case I should and in the other I have to attend. I now discussed with the organizers and I suggest moving the IERC AC1 / FI-WARE meeting to Wednesday 19th morning. Could the people who plan to attend this meeting please give me feedback whether this is possible for them? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail:Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 ________________________________ 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 Jun 4 16:33:13 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 4 Jun 2013 14:33:13 +0000 Subject: [Fiware-iot] Weekly meeting tommorow Message-ID: <3375_1370356393_51ADFAA9_3375_662_1_976A65C5A08ADF49B9A8523F7F81925C0F2A1E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Here is the link for the telco minutes for tomorrow. Please add your topics in the AOB section. https://docs.google.com/document/d/1HaTtbRWZV9JC05-xURhPtDNIU8zKftLFC7LW5H7lvd8/edit?pli=1 I will quickly introduce the agenda for the review also so if you have any point you want I put on the table for the review feel free to propose it. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From konrad.campowsky at fokus.fraunhofer.de Tue Jun 4 16:52:35 2013 From: konrad.campowsky at fokus.fraunhofer.de (Konrad Campowsky) Date: Tue, 4 Jun 2013 16:52:35 +0200 Subject: [Fiware-iot] Weekly meeting tommorow In-Reply-To: <3375_1370356393_51ADFAA9_3375_662_1_976A65C5A08ADF49B9A8523F7F81925C0F2A1E@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <3375_1370356393_51ADFAA9_3375_662_1_976A65C5A08ADF49B9A8523F7F81925C0F2A1E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51ADFF33.3090909@fokus.fraunhofer.de> Dear Thierry, Since both Sebastian and me are occupied tomorrow morning, FOKUS will be unable to join the telco. Best regards, Konrad Am 04.06.2013 16:33, schrieb thierry.nagellen at orange.com: > Hi all > > > > Here is the link for the telco minutes for tomorrow. Please add your > topics in the AOB section. > > https://docs.google.com/document/d/1HaTtbRWZV9JC05-xURhPtDNIU8zKftLFC7LW5H7lvd8/edit?pli=1 > > > > I will quickly introduce the agenda for the review also so if you have > any point you want I put on the table for the review feel free to > propose it. > > > > BR > > *Thierry Nagellen* > > */Program Manager Future Internet/* > *Orange Labs Networks & Carriers* > 905 rue Albert Einstein > 06921 Sophia Antipolis Cedex > +33 492 94 52 84 > +33 679 85 08 44 > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-iot > From Martin.Bauer at neclab.eu Tue Jun 4 17:24:43 2013 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Tue, 4 Jun 2013 15:24:43 +0000 Subject: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week In-Reply-To: <1971FF81B8E01C45991F6F92B9E3B25089095ACF@EX10-MB2-MAD.hi.inet> References: <1971FF81B8E01C45991F6F92B9E3B25089095ACF@EX10-MB2-MAD.hi.inet> Message-ID: Hi Carlos, all, Thanks for putting up the wiki page. I indeed can edit the page and I added a link to the current public version of the IoT-A Architectural Reference Model. (http://tinyurl.com/cnwq62o). Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Tuesday, June 04, 2013 4:27 PM To: Martin Bauer Cc: Quintin, Laure (laure.quintin at vdivde-it.de); Peter.FRIESS at ec.europa.eu; ac_architecture at internet-of-things-research.eu; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week Hi Martin, As discussed in our meeting at Dublin FIA I have set a wiki-page with the necessary links and info from both sides: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities_IERC For IERC completing its section we have two possibilities: 1) You (as member of the FI-PPP and FI-WARE) have editing rights for that page. 2) Someone can send me an e-mail and I can update it for you. What we need first is a set of links to the most updated IoT-A architecture to understand common and different points. Cheers, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ De: Martin Bauer > Fecha: martes, 4 de junio de 2013 09:58 Para: "ac_architecture at internet-of-things-research.eu" >, "fiware-iot at lists.fi-ware.eu" > CC: "Quintin, Laure (laure.quintin at vdivde-it.de)" >, "Peter.FRIESS at ec.europa.eu" > Asunto: Re: [Fiware-iot] IERC AC1 / FI-WARE meeting on architecture @ IoT Week Hi all, Due to various overlaps, I'd suggest to schedule the IERC AC1 / FI-WARE meeting on architecture on Wednesday between 08:00 and 10:00 EEST - this would mean getting up early , but would result in only a partial overlap for a few people. I also still need confirmation from the organizers and Laure is out-of-office today - but apart from that - are there any objections? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 From: Domenico Rotondi [mailto:domenico.rotondi at txtgroup.com] Sent: Monday, June 03, 2013 11:24 AM To: Martin Bauer Cc: Peter.FRIESS at ec.europa.eu; Le Gall, Franck; levent.gurgen at cea.fr; ac_architecture at internet-of-things-research.eu; fiware-iot at lists.fi-ware.eu Subject: Re: IERC AC1 / FI-WARE meeting on architecture @ IoT Week Importance: High Hi Martin (and all), on Wednesday 19th I already have other sessions scheduled (in the morning the session on IoT for Manufacturing FITMAN organised, in the afternoon I have another duty but the Sergio Gusmeroli could attend the session). So let's try to phase having the IoT for Manufacturing (in the morning) not overlapped with the Fi-Ware/IoT session. Ciao Domenico ________________________________ On 3 Jun 2013 at 7:58, Martin Bauer wrote: Hi all, After coming back from my vacation, I had a look at the IoT Week agenda and the planned IERC AC1/FI-Ware meeting. The organizers had suggested to synchronize with AC4 activities, however it seems that IERC AC4 has already planned a full day meeting on the topics of service openness and interoperability on Tuesday 18th, also there are IoT-A activities in parallel that in one case I should and in the other I have to attend. I now discussed with the organizers and I suggest moving the IERC AC1 / FI-WARE meeting to Wednesday 19th morning. Could the people who plan to attend this meeting please give me feedback whether this is possible for them? Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail:Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 ________________________________ 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 Wed Jun 5 11:45:34 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 05 Jun 2013 09:45:34 +0000 Subject: [Fiware-iot] FW: [Fiware-wpl] Populating the catalogue In-Reply-To: <51AE1B10.4050504@tid.es> Message-ID: <1971FF81B8E01C45991F6F92B9E3B25089097120@EX10-MB2-MAD.hi.inet> FYI De: Miguel Carrillo > Fecha: martes, 4 de junio de 2013 18:51 Para: "fiware-wpa at lists.fi-ware.eu" >, "fiware-wpl at lists.fi-ware.eu" > Asunto: [Fiware-wpl] Populating the catalogue Dear all, After a bit of struggling we have delivered WP8 ? this completes the set of deliverables associated to the SW. Now we can look into the catalogue. As Juanjo anticipated, the reference is: ? http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Working_with_the_FI-WARE_catalogue#Guidelines_on_what_to_write and a good example, kindly modified today by the UPM to be 100% compliant is: ? http://catalogue.fi-ware.eu/enablers/application-mashup-wirecloud (use this one as a template and you will be safe) This is how we are going to proceed: 1) I will go entry by entry blindly approving all the ones for GEs in R1 (with no review). I will start right now. 2) Talk to your teams and a. Ask them to update all the catalogue entries for entries in R1 ? if they were redelivered in R2, modify accordingly b. Ask them also to create new the new GEis. Agree with them to create a subset of the new ones or maybe all. Up to you. Insist a lot on reading the guidelines and using wirecloud as a good example. Please avoid the mess of non-compliances that we had to face in many installation manuals, etc. mostly caused by not reading or ignoring the guidelines. We can use our time better. c. Please send me the list of new GEi from R2 that you are adding by the end of tomorrow Deadline for all this : end of thursday 6/06/2013 Then we will review the ones in R1 and ask for urgent changes if needed. As many of them are present in R1 and in R2 I will never be completely sure of what I am approving but let us get out of this paralysing situation! I expect the messages by the end of Thursday confirming the GEis from R2 that you are adding. On previous iterations for any of the docs, reviews, etc. I had to chase up people one by one (with exceptions) and waste hours and hours for each step. This is not a serious behaviour. Your responsibility is very high and we cannot be so inefficient, particularly when we have a review looming upon us. In summary, ACTION POINTS ? AP on GE owners: update GEis from R1 on the catalogue (deadline 6/06/2013) ? AP on GE owners: create (or update) a subset or all the GEis in R2 on the catalogue (on GE owners - deadline 6/06/2013) ? AP on WPL: please circulate this info immediately! ? AP on WPL: send me an email with the new GEi from R2 on the catalogue (deadline: 6/06/2013) ? AP on me: approve pending edits from GEis in R1 (deadline: tomorrow at noon - 12am) - I'll try to have irt sooner, starting now! Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From thierry.nagellen at orange.com Wed Jun 5 14:44:26 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 5 Jun 2013 12:44:26 +0000 Subject: [Fiware-iot] IMPORTANT: Spreadsheet to follow dev status Message-ID: <15579_1370436267_51AF32AB_15579_91_1_976A65C5A08ADF49B9A8523F7F81925C0F2DA6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As explained this morning, here is the spreadsheet where you have to put, per week the status for each feature we promised for release 2.3. I've assumed that all features planned for release 2.2 were delivered. We have several instances for some GEs (Gateway Data Handling, Backend Configuration Management). You have to create your own instance with the name for your GEi (the name we will use in the catalogue) and copy and paste all features. If an instance is not able to cover everything it should not be a major issue but all features have to be covered by the different instances. https://docs.google.com/file/d/0BwpTc4w8NwVTc21xYzZDcDJfUzg/edit?usp=sharing BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at gmail.com Wed Jun 5 16:24:56 2013 From: thierry.nagellen at gmail.com (Thierry Nagellen) Date: Wed, 5 Jun 2013 16:24:56 +0200 Subject: [Fiware-iot] Spreadsheet for Roadmap status Message-ID: Hi all maybe using by gmail mailbox it would work for edition... BR Thierry R23-TechRoadmap-Status.xlsx - https://docs.google.com/file/d/0BwpTc4w8NwVTc21xYzZDcDJfUzg/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Wed Jun 5 19:27:58 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 05 Jun 2013 19:27:58 +0200 Subject: [Fiware-iot] IMPORTANT: Spreadsheet to follow dev status In-Reply-To: <15579_1370436267_51AF32AB_15579_91_1_976A65C5A08ADF49B9A8523F7F81925C0F2DA6@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <15579_1370436267_51AF32AB_15579_91_1_976A65C5A08ADF49B9A8523F7F81925C0F2DA6@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <51AF751E.7010405@tid.es> Dear Thierry, I have edited (attached) the Excel to include the following things: 1. I have changed the list of Features coming to ConfMan due to TID's implementation, marked in blue. Note that the set if not same that is actually in the public wiki. As you know (see details in my email sent on April 12th to fiware-iot list) we needed to change the roadmap to accommodate the associations functionality but until know we haven't had the time to update public wiki. 2. Roadmap was achieved some weeks ago so I have marked "YES" in our roadmap entries. I have used "Not applicable" (N/A) to entries that are not part of TID's ConfMan roadmap. In addition, it would be great if you could convert this Excel in a shared document (that it not the same that an Excel uploaded to google drive, where it seems there is option for online edition). Best regards, ------ Ferm?n El 05/06/2013 14:44, thierry.nagellen at orange.com escribi?: Dear all, As explained this morning, here is the spreadsheet where you have to put, per week the status for each feature we promised for release 2.3. I've assumed that all features planned for release 2.2 were delivered. We have several instances for some GEs (Gateway Data Handling, Backend Configuration Management). You have to create your own instance with the name for your GEi (the name we will use in the catalogue) and copy and paste all features. If an instance is not able to cover everything it should not be a major issue but all features have to be covered by the different instances. https://docs.google.com/file/d/0BwpTc4w8NwVTc21xYzZDcDJfUzg/edit?usp=sharing BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: R23-TechRoadmap-Status+OrionContextBroker.xlsx Type: application/x-zip-compressed Size: 13970 bytes Desc: not available URL: From fermin at tid.es Wed Jun 5 21:43:05 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 05 Jun 2013 21:43:05 +0200 Subject: [Fiware-iot] "SAMSON Broker" is now "Orion Context Broker" Message-ID: <51AF94C9.2090101@tid.es> Hi, Due to a changes in Telef?nica's branding, the software component previous known as "SAMSON Broker" (implementing both Pub/Sub Context Broker GE and Configuration Manager GEI) is now named "Orion Context Broker". This change also affect to other TID's components as you probably have noticed (in particular, "SAMSON BigData" was renamed to "COSMOS BigData"). In fact, the name "Orion Context Broker" has been around for a time, but with the update in the FI-WARE catalog we could say that now is has become "official". Probably some "SAMSON Broker" occurrence still appearing in wiki and other online documentation pieces, we would change it as soon as we spot them. 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 From thierry.nagellen at orange.com Tue Jun 11 13:11:15 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 11 Jun 2013 11:11:15 +0000 Subject: [Fiware-iot] URGENT update for OIL Message-ID: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Here is a new cockpit to provide the view for the OIL (end of July). I have to use a picture of this cockpit for the review presentation tomorrow. Could you update it quickly in the afternoon? I will take the content as it is this evening. https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Tue Jun 11 14:08:58 2013 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 11 Jun 2013 14:08:58 +0200 Subject: [Fiware-iot] R: URGENT update for OIL In-Reply-To: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5B0D62579@GRFMBX702BA020.griffon.local> Hi Thierry, the cockpit is updated. 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: marted? 11 giugno 2013 13:11 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT update for OIL Dear all, Here is a new cockpit to provide the view for the OIL (end of July). I have to use a picture of this cockpit for the review presentation tomorrow. Could you update it quickly in the afternoon? I will take the content as it is this evening. https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From Salvatore.Longo at neclab.eu Tue Jun 11 14:20:32 2013 From: Salvatore.Longo at neclab.eu (Salvatore Longo) Date: Tue, 11 Jun 2013 12:20:32 +0000 Subject: [Fiware-iot] URGENT update for OIL In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5B0D62579@GRFMBX702BA020.griffon.local> References: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> <36A93B31228D3B49B691AD31652BCAE9A5B0D62579@GRFMBX702BA020.griffon.local> Message-ID: <5DCCEFAAAAD37745A888BC14F42BF4A538EAB049@DAPHNIS.office.hd> Hi Thierry, The IoT Broker information are already updated. BR, - Salvatore Longo ________________________________ Salvatore Longo Software Engineer NEC Europe Ltd. Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel. +49/(0) 62 21/43 42 - 246 Fax. +49/(0) 62 21/43 42 - 115 E-Mail: Salvatore.longo at neclab.eu NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Guerra Sabrina Sent: Dienstag, 11. Juni 2013 14:09 To: thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] R: URGENT update for OIL Hi Thierry, the cockpit is updated. 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: marted? 11 giugno 2013 13:11 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] URGENT update for OIL Dear all, Here is a new cockpit to provide the view for the OIL (end of July). I have to use a picture of this cockpit for the review presentation tomorrow. Could you update it quickly in the afternoon? I will take the content as it is this evening. https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. 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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fermin at tid.es Tue Jun 11 16:52:41 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 11 Jun 2013 16:52:41 +0200 Subject: [Fiware-iot] Associations in Release 2.3 of ConfMan GE In-Reply-To: <8755F290097BD941865DC4245B335D2D38F6351B@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38F52326@DAPHNIS.office.hd> <51681A4F.2030003@tid.es> <8755F290097BD941865DC4245B335D2D38F6351B@DAPHNIS.office.hd> Message-ID: <51B739B9.4010607@tid.es> Hi, I has take a long time (other more priority things arisen in the middle) but, finally, the roadmap has been updated: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services#Backend Materializaing has been updated accordingly: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_%28IoT%29_Services_Enablement_in_FI-WARE#Backend_Configuration_Management_GE I have defined a Feature for the Associations feature in ConfMan inspired in you (actually I have copy-pasted part of the text): https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.ContextBroker.Associations Best regards, ------ Ferm?n El 12/04/2013 17:17, Tobias Jacobs escribi?: Dear Fermin, all, Thanks a lot for you answer. We are very glad about your decision and we are looking forward to have a working IoT Backend with association support. We just have an association epic defined for the IoT Broker https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.IoT.Backend.IoTBroker.Associations. Best Tobias From: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Freitag, 12. April 2013 16:30 To: Tobias Jacobs Cc: Juanjo Hierro; KEN GUNNAR ZANGELIN (kzangeli at tid.es); CARLOS RALLI UCENDO (ralli at tid.es); fiware-iot at lists.fi-ware.eu; Martin Bauer; Salvatore Longo; Raihan Ul-Islam; thierry.nagellen at orange.com Subject: Re: Associations in Release 2.3 of ConfMan GE Dear Tobias, We have been discussing internally this issue and we (TID) agree in changing the existing Technical Roadmap (table) of Configuration Manager GE to include the support of associations for R2.3. As a consequence, some of the Features in the existing R2.3 will be deferred for the future. We will change Technical Roadmap (table) of Configuration Manager GE in the FIWARE public wiki in the next days accordingly. Is this sense, is there any feature page or trac item for thing-device associations? In positive case, could you provide the URLs, please? We think that NEC proposal to accomplish this is ok in general, although some details needs to be polished yet. We can continue the discussion of these technical details in the NGSI mailing list. Best regards, ------ Ferm?n El 08/04/2013 11:34, Tobias Jacobs escribi?: Dear Colleagues from TID, Could you provide us some information related to your current plans related to the releases of the Configuration Management GE? 1) We understand that the next release of the ConfMan GE will be 2.3. How does this match with the integration plans that were discussed in the F2F meeting? We planned the integration of the WP5 components, but without the ConfMan GE no integration will be able to work. 2) In the technical roadmap (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services), there is a slight mismatch between the features list in the table and what is described in the bullet points when it comes to association support. We are concerned that there is no feature in the table on association support of the ConfMan GE. As the discussions with Juanjo last year have shown, the ability of translating between device-level and thing-level information is one of the essential abilities of the IoT Backend. The support of associations by ConfMan GE is an essential prerequisite for it. We can also discuss this point in the phone conference this week. Thanks and best regards Ernoe, Martin, Raihan, Salvatore, and Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue Jun 11 20:30:23 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 11 Jun 2013 20:30:23 +0200 Subject: [Fiware-iot] [Fiware] TASK FORCE for FI-WARE GEi owners towards the 2nd year project review In-Reply-To: <51B1B86D.8080902@tid.es> References: <51B1B86D.8080902@tid.es> Message-ID: <51B76CBF.3020103@tid.es> Dear all, First of all, let me rather thank all of you who have already completed the requested exercise ... This is a clear sign of your commitment. There are few partners who haven't completed the task force, and the reviewers will notice: * Cloud chapter: * INRIA: Job Scheduler * Technicolor: Cloud Proxy * IoT chapter: * Surrey University: IoT Discovery * Fraunhofer: IoT Gateway Device Management * Security chapter: * Thales: Secure Storage * I2ND chapter: * ALU-I: VNEIC * Technicolor: Cloud Proxy Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 07/06/13 12:39, Juanjo Hierro wrote: Dear all, As you know, we are facing the 2nd year official project review next week. During the last preparation meeting we had this Wednesday, we agreed to prepare a revision of the FI-WARE GEi planned availability and usage cockpit that we are currently sharing with the UC projects. This revision would be enriched with information about status, planned terms and conditions in the different environments, base line assets, etc. Please we need to complete this task force by EOB Monday at the latest. It is a pretty simple exercise, so it won't take so much time. I have prepared a shared spreadsheet in Google docs that will help us to work in the new version of the cockpit without creating so much noise in front of the UC projects. You can find it available at the following link: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 You have to complete columns N (already filled, just double-check) and the new columns, namely columns O to X. Columns O-Q deal with info about availability for the FI-PPP partners (which includes availability on the FI-WARE Testbed being used by UC projects to run their experiments). All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Columns R-T deal with info about availability within the FI-WARE Open Innovation Lab (OIL). I guess you all know about the FI-WARE OIL so I don't need to elaborate. Despite the concrete legal terms and conditions are under definition, you can assume that this will be an environment where GEis will be offered (in whatever mode is decided per GEi) for free to third parties (i.e., anyone) who wish to experiment with the technology. The GEis will be provided "as-is" without no warranty and only committing a best-effort support. They will be provided for non-comercial experimental-only use by those third parties. All relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Why is there a distinction between availability within the FI-PPP and within OIL ? Mainly because the mode in which you will offer a GEi may vary. Actually, within the FI-PPP you are more constrained and have to comply with the signed Collaboration Agreement. Thus, you may decide to support "Dedicated SaaS instance, binaries" for FI-PPP partners, but may decide to only support "Dedicated SaaS instance" to users of the FI-WARE OIL. Columns U-V deal with info about availability beyond the FI-PPP. Again, all relevant notes that will help you to complete your exercise are provided. Please read them carefully and try to follow them. Column W has to contain a link to the place in the "materializing the FI-WARE vision" part of the wiki where you described the baseline assets used for your GEi. Adding the proper link is pretty straight forward. Go to the wiki page associated to "materializing the FI-WARE vision" for your chapter and then, click on the "Baseline assets" section of your GEi in the Table of Contents of that wiki page. That action, besides it will place you at the right place in the wiki page, will imply that the URL in your browser will then be precisely pointing to that section. Column X has to contain the link to the corresponding entry in the FI-WARE Catalogue. I guess I don't need to explain how to fill it. WPLs are encouraged to follow-up this process and make sure it gets finalized on time for GEis in their chapters. Don't hesitate to ask if you have any doubt on how to fill the spreadsheet. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware ________________________________ 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 Tue Jun 11 21:25:29 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Tue, 11 Jun 2013 20:25:29 +0100 Subject: [Fiware-iot] URGENT update for OIL In-Reply-To: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <31171_1370949076_51B705D4_31171_6179_1_976A65C5A08ADF49B9A8523F7F81925C0F3E5C@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D696@EXMB05CMS.surrey.ac.uk> Hello Thierry, Apologies for the delay, as the requirement of this spreadsheet wasn't clear to me. Anyway I have filled in the part for UNIS if it's not too late. 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 June 2013 12:11 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] URGENT update for OIL Dear all, Here is a new cockpit to provide the view for the OIL (end of July). I have to use a picture of this cockpit for the review presentation tomorrow. Could you update it quickly in the afternoon? I will take the content as it is this evening. https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEQ4TlBJT1JwT1ZfMVUwQzhzRWExOEE#gid=8 Thanks for your support. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Wed Jun 12 09:20:12 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Wed, 12 Jun 2013 07:20:12 +0000 Subject: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE In-Reply-To: <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789B68E6C@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> Message-ID: <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : jeudi 18 avril 2013 16:37 ? : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Jun 12 11:50:57 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 12 Jun 2013 10:50:57 +0100 Subject: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE In-Reply-To: <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789B68E6C@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D701@EXMB05CMS.surrey.ac.uk> Hello Fano, Yes we are planning to support this epic and its respective features. I think we need to clarify what exactly do you want to query for? ...what information, what ontology? Currently we are supporting the IoT-A ontologies that describe Resources (Sensors, Actuators, Processing unit, Storage, Tag), Virtual Entities (i.e. Things) and Services (what the user interacts with to access the Resource). Attached is a paper that illustrates the ontologies. If you are interested in using of these please let me know. On another note, a discussion we had in the WP previously was how to map the IoT-A ontologies to the FIWARE IoT Concepts (Thing, IoT Resource, Device) and vice-versa. For: ? IoT-A Virtual Entity -> FIWARE Thing ? IoT-A Resource -> FIWARE IoT Resource ? The IoT-A Service will be embedded in the FIWARE Thing and IoT Resource using the NGSI-9 "ProvidingApplication" element, i.e. a URL to an web application/service endpoint. In the case of translating, from ontology to NGSI is doable, but vice-versa is near impossible unless a registered NGSI-9 Description complies with a specific format for naming. Please let me know your opinion on this. Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 08:20 To: Tobias Jacobs; CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : jeudi 18 avril 2013 16:37 ? : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: AN INTERNET OF THINGS PLATFORM FOR REAL-WORLD AND DIGITAL OBJECTS.pdf Type: application/pdf Size: 673521 bytes Desc: AN INTERNET OF THINGS PLATFORM FOR REAL-WORLD AND DIGITAL OBJECTS.pdf URL: From thierry.nagellen at orange.com Wed Jun 12 12:12:07 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 12 Jun 2013 10:12:07 +0000 Subject: [Fiware-iot] Summer vacations Message-ID: <4372_1371031928_51B84977_4372_113_3_976A65C5A08ADF49B9A8523F7F81925C0F44E9@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Here is a doodle to fulfill to be aware of when you will be on vacation to be able to manage urgent issues if there are some along the summer. http://www.doodle.com/iyruw6nuv9r7smdw BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Wed Jun 12 15:37:12 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Wed, 12 Jun 2013 13:37:12 +0000 Subject: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D701@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789B68E6C@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D701@EXMB05CMS.surrey.ac.uk> Message-ID: <18565_1371044233_51B87989_18565_1409_5_DC254E6D1212F24EAE0D7766A11FE2890CB6AC@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Tarek, So far we've decided to use standard (eventually de-facto) ontologies if they exist (e.g. for location information we plan to use geonames). We haven't commited to any as far as resources and things are concerned. So we can use IoT-A ontologies. Is there a web site where the corresponding owl files can be retrieved? We plan to use SPARQL to explore the ontologies and the instances and the relations, mainly for tuning the NGSi to RDF translation (see below). I agree that transforming from RDF/OWL to NGSi is easier because the former is more expressive than the latter, so transforming is just dropping some info from the source document to produce the target document, but I think that transforming NGSi to RDF is doable as this is what we're actually working on after having successfully transformed CML (PubSub CAP native context modeling language) into RDF. However this transformation has to be partly hardcoded and on a scope by scope basis, because semantics of the document in the source language is mainly implicit and has to be made explicit in the target language. Best regards, Fano De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : mercredi 12 juin 2013 11:51 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; p.barnaghi at surrey.ac.uk Objet : RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hello Fano, Yes we are planning to support this epic and its respective features. I think we need to clarify what exactly do you want to query for? ...what information, what ontology? Currently we are supporting the IoT-A ontologies that describe Resources (Sensors, Actuators, Processing unit, Storage, Tag), Virtual Entities (i.e. Things) and Services (what the user interacts with to access the Resource). Attached is a paper that illustrates the ontologies. If you are interested in using of these please let me know. On another note, a discussion we had in the WP previously was how to map the IoT-A ontologies to the FIWARE IoT Concepts (Thing, IoT Resource, Device) and vice-versa. For: ? IoT-A Virtual Entity -> FIWARE Thing ? IoT-A Resource -> FIWARE IoT Resource ? The IoT-A Service will be embedded in the FIWARE Thing and IoT Resource using the NGSI-9 "ProvidingApplication" element, i.e. a URL to an web application/service endpoint. In the case of translating, from ontology to NGSI is doable, but vice-versa is near impossible unless a registered NGSI-9 Description complies with a specific format for naming. Please let me know your opinion on this. Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 08:20 To: Tobias Jacobs; CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : jeudi 18 avril 2013 16:37 ? : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Jun 12 16:28:59 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 12 Jun 2013 15:28:59 +0100 Subject: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE In-Reply-To: <18565_1371044233_51B87989_18565_1409_5_DC254E6D1212F24EAE0D7766A11FE2890CB6AC@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789B68E6C@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D701@EXMB05CMS.surrey.ac.uk> <18565_1371044233_51B87989_18565_1409_5_DC254E6D1212F24EAE0D7766A11FE2890CB6AC@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D7A8@EXMB05CMS.surrey.ac.uk> Hello Fano, The owl files can be found at: http://iot3.ee.surrey.ac.uk/S2W/IoTA-Models/. There are also files that provide an example of an instance (individual) of the model. For location, we also plan to link the models to Geonames as well. The property we use for this is called "hasGlobalLocation". With regards to translation, I understand that the CML that you receive complies with a naming convention for attributes e.g. "temperature" and not "temp". Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 14:37 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; Barnaghi P Dr (Electronic Eng) Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, So far we've decided to use standard (eventually de-facto) ontologies if they exist (e.g. for location information we plan to use geonames). We haven't commited to any as far as resources and things are concerned. So we can use IoT-A ontologies. Is there a web site where the corresponding owl files can be retrieved? We plan to use SPARQL to explore the ontologies and the instances and the relations, mainly for tuning the NGSi to RDF translation (see below). I agree that transforming from RDF/OWL to NGSi is easier because the former is more expressive than the latter, so transforming is just dropping some info from the source document to produce the target document, but I think that transforming NGSi to RDF is doable as this is what we're actually working on after having successfully transformed CML (PubSub CAP native context modeling language) into RDF. However this transformation has to be partly hardcoded and on a scope by scope basis, because semantics of the document in the source language is mainly implicit and has to be made explicit in the target language. Best regards, Fano De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : mercredi 12 juin 2013 11:51 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; p.barnaghi at surrey.ac.uk Objet : RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hello Fano, Yes we are planning to support this epic and its respective features. I think we need to clarify what exactly do you want to query for? ...what information, what ontology? Currently we are supporting the IoT-A ontologies that describe Resources (Sensors, Actuators, Processing unit, Storage, Tag), Virtual Entities (i.e. Things) and Services (what the user interacts with to access the Resource). Attached is a paper that illustrates the ontologies. If you are interested in using of these please let me know. On another note, a discussion we had in the WP previously was how to map the IoT-A ontologies to the FIWARE IoT Concepts (Thing, IoT Resource, Device) and vice-versa. For: ? IoT-A Virtual Entity -> FIWARE Thing ? IoT-A Resource -> FIWARE IoT Resource ? The IoT-A Service will be embedded in the FIWARE Thing and IoT Resource using the NGSI-9 "ProvidingApplication" element, i.e. a URL to an web application/service endpoint. In the case of translating, from ontology to NGSI is doable, but vice-versa is near impossible unless a registered NGSI-9 Description complies with a specific format for naming. Please let me know your opinion on this. Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 08:20 To: Tobias Jacobs; CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : jeudi 18 avril 2013 16:37 ? : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fano.ramparany at orange.com Thu Jun 13 10:15:49 2013 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Thu, 13 Jun 2013 08:15:49 +0000 Subject: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D7A8@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789B68E6C@EXMB05CMS.surrey.ac.uk> <8755F290097BD941865DC4245B335D2D38F713F5@DAPHNIS.office.hd> <30623_1371021614_51B8212E_30623_2572_1_DC254E6D1212F24EAE0D7766A11FE2890CB47E@PEXCVZYM12.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D701@EXMB05CMS.surrey.ac.uk> <18565_1371044233_51B87989_18565_1409_5_DC254E6D1212F24EAE0D7766A11FE2890CB6AC@PEXCVZYM12.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1D7A8@EXMB05CMS.surrey.ac.uk> Message-ID: <30220_1371111351_51B97FB6_30220_4461_16_DC254E6D1212F24EAE0D7766A11FE2890CB838@PEXCVZYM12.corporate.adroot.infra.ftgroup> Thank you for the owl files. About the translation issue, our module support proprietary/non-standard naming convention. It uses a parsing mechanism which recognizes and interprets elements of the XML document (CML document in our case) and transforms them into properties or instances or values, depending on the ontology they relate to. We're currently documenting all this. Regards, Fano De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : mercredi 12 juin 2013 16:29 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; p.barnaghi at surrey.ac.uk Objet : RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hello Fano, The owl files can be found at: http://iot3.ee.surrey.ac.uk/S2W/IoTA-Models/. There are also files that provide an example of an instance (individual) of the model. For location, we also plan to link the models to Geonames as well. The property we use for this is called "hasGlobalLocation". With regards to translation, I understand that the CML that you receive complies with a naming convention for attributes e.g. "temperature" and not "temp". Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 14:37 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; Barnaghi P Dr (Electronic Eng) Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, So far we've decided to use standard (eventually de-facto) ontologies if they exist (e.g. for location information we plan to use geonames). We haven't commited to any as far as resources and things are concerned. So we can use IoT-A ontologies. Is there a web site where the corresponding owl files can be retrieved? We plan to use SPARQL to explore the ontologies and the instances and the relations, mainly for tuning the NGSi to RDF translation (see below). I agree that transforming from RDF/OWL to NGSi is easier because the former is more expressive than the latter, so transforming is just dropping some info from the source document to produce the target document, but I think that transforming NGSi to RDF is doable as this is what we're actually working on after having successfully transformed CML (PubSub CAP native context modeling language) into RDF. However this transformation has to be partly hardcoded and on a scope by scope basis, because semantics of the document in the source language is mainly implicit and has to be made explicit in the target language. Best regards, Fano De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : mercredi 12 juin 2013 11:51 ? : RAMPARANY Fano OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; Tobias.Jacobs at neclab.eu; ralli at tid.es; p.barnaghi at surrey.ac.uk Objet : RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hello Fano, Yes we are planning to support this epic and its respective features. I think we need to clarify what exactly do you want to query for? ...what information, what ontology? Currently we are supporting the IoT-A ontologies that describe Resources (Sensors, Actuators, Processing unit, Storage, Tag), Virtual Entities (i.e. Things) and Services (what the user interacts with to access the Resource). Attached is a paper that illustrates the ontologies. If you are interested in using of these please let me know. On another note, a discussion we had in the WP previously was how to map the IoT-A ontologies to the FIWARE IoT Concepts (Thing, IoT Resource, Device) and vice-versa. For: ? IoT-A Virtual Entity -> FIWARE Thing ? IoT-A Resource -> FIWARE IoT Resource ? The IoT-A Service will be embedded in the FIWARE Thing and IoT Resource using the NGSI-9 "ProvidingApplication" element, i.e. a URL to an web application/service endpoint. In the case of translating, from ontology to NGSI is doable, but vice-versa is near impossible unless a registered NGSI-9 Description complies with a specific format for naming. Please let me know your opinion on this. Best regards, Tarek From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] Sent: 12 June 2013 08:20 To: Tobias Jacobs; CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, About the semantic support, do you still plan to support the requirements FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.* mentioned in the backlog? >From the PubSub GE perspective we specially need functions related to: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.IoT.Backend.DiscoveryEngine.SemanticSearch.Discover.Sparql We can discuss it further (in the future dedicated mailing list :)) but to give you a quick gist, the PubSub semantic extension implements context entities as instances of concepts corresponding to physical entities (person, objects,...) which I presume corresponds to a specific concept in your ontology. So having access to a SPARQL endpoint would enable the sharing of ontologies and instance URIs for such context entities / things between our respective GEs. Regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Tobias Jacobs Envoy? : jeudi 18 avril 2013 16:37 ? : CARLOS RALLI UCENDO; t.elsaleh at surrey.ac.uk Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastian.wahle at fokus.fraunhofer.de Thu Jun 13 10:19:54 2013 From: sebastian.wahle at fokus.fraunhofer.de (Wahle, Sebastian) Date: Thu, 13 Jun 2013 08:19:54 +0000 Subject: [Fiware-iot] Goodbye Message-ID: Dear all, I just wanted to let you know that I will leave the Fraunhofer association and wanted to introduce to you my colleagues Adel and Konrad (both CCed) who are now responsible for the M2M and IoT solutions within Fraunhofer FOKUS. Konrad will be the primary contact for all IoT chapter activities. I wish you all the best and great success with the project! Best regards from Berlin, Sebastian --------------------------------------------------------------------------------- Dr. Sebastian Wahle Head of M2M Solutions Fraunhofer Institute for Open Communication Systems - FOKUS Kaiserin-Augusta-Allee 31, 10589 Berlin, Germany Phone: +493034637365 Mobile: +491757222698 XING: https://www.xing.com/profile/Sebastian_Wahle2 LinkedIn: www.linkedin.com/profile/view?id=11811761 --------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Fri Jun 14 11:39:24 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 14 Jun 2013 09:39:24 +0000 Subject: [Fiware-iot] FW: [Fiware-wpa] Notes of the preliminary feedback of the review meeting In-Reply-To: <51B9F876.7000006@tid.es> Message-ID: <1971FF81B8E01C45991F6F92B9E3B250890A31D7@EX10-MB2-MAD.hi.inet> IoT is finally in the positive points! :-) Good work, congrats to all and let's keep on improving!! Cheers, De: Juanjo Hierro > Fecha: jueves, 13 de junio de 2013 18:51 Para: "fiware-wpl at lists.fi-ware.eu" >, "fiware-wpa at lists.fi-ware.eu" >, "fiware-wpl at lists.fi-ware.eu" >, "fiware-demo at lists.fi-ware.eu" > Asunto: [Fiware-wpa] Notes of the preliminary feedback of the review meeting Dear colleagues, Here it goes my notes regarding the early feedback provided by the EC/reviewers after the review meeting. Overall statement: Technology is there but go to market requires improvement. Positive points: * Technology work has been improved and this has to be recognized * New technology implementations - a whole good package * GEs with potential are there * I2ND has improved a lot addressing concerns in the past despite still some references to legacies * IoT has improved also a lot - more focus between integration of IoT and BigData is necessary * They look for the delivery of the State of the Art deliverable as a mean to check how the GEi owners see their GEis benchmark with those of incumbent players * Attention for smart cities is welcome because it helps to bring focus * Live Demo is good - lot of GEis - it shows that integration was not that much an issue as reviewers initially were afraid * The potential of some GEis is backed by the market analysis * Market analysis is very good deliverable * Seems not to be big delays regarding delivery of Release 2 - which is excellent - they feel more confident that the Release 2 will be ready for the launch of OIL in the planned dates * OIL is the very focus and that is right * Indeed, they see a real commitment of the consortium towards launch of the FI-WARE OIL in the Campus Party (providing the pressure they hadn't manage to achieve during previous reviews) * Impression of team work * Consortium shows confidence and commitment specially certain individuals * They appreciate that we are looking for ways to on-board new projects / third-parties although we have to be careful (see not so-positive points) * Overall: quite good impression Not so-positive points: * Some missing deliverables * Periodic report should be available prior the meeting * Backlog might be more clean but there are some indications that it still requires some work * Technical roadmap still a wish list * Open Specs that were rejected were improved although still they are difficult to read. This doesn't only apply to document deliverables but also the wiki. * Validation has to be improved. Acceptable that is how it was defined in the AB but some improvement is possible there - note: I believe that the recommendations by the reviewers to the EC, explained by Man-sze Li (see below) may have to do with this opportunity to improve * Third party involvement: they like to see the deliverable submitted * Some concerns about limiting third parties to Campus Party is like putting all eggs in one basket so that we have to avoid that. * FI-WARE Catalogue is the window to the world and has to be more appealing and, of course, clear terms and conditions should be there for the GEis * Concerns about attitude towards some recommendations ("we are big so we decide") - note: I guess that this mostly apply to the accountability issue * More needs and effort on evangelism * About expanding FI-WARE to allow other GEis and overall othe GEis from third parties you have to be careful to avoid that what you are going to provide now gets diluted - Useful to have some guidelines/rules about what will be considered a GE * Some concern about how FI-WARE can really gain the attention of the campuseros community - you should find a strategy to connect to the geeks that attend, maybe involve people (the youngers in your development teams) that can speak their same language Formal request by the EC: Each company has to submit their individual exploitation plans in few weeks. Even those who said they would not be different to the already submitted (a letter stating so would be enough). Don't need many pages, just some paragraphs. Information will be treated as confidential. Regarding acceptance/rejection of deliverables they said that they haven't finished their evaluation and that they couldn't provide us a report yet. Man-Sze Li took the floor and informed us about recommendations that the reviewers will officially submit to the EC. In particular the following two: * They will recommend to the EC that it takes actions to ensure that UC projects really assume their mission to use as many GEis as they can, validate GEis, provide feedback and work together with FI-WARE to solve those issues that may appear. * They will recommend to the EC that it takes actions to ensure that the OIL/XiFi facilities will continue available after the FI-WARE and XiFi projects finish I believe this is all. If someone else took more notes, please circulate so that we can all share them. Last but not least, let me thank to all of you for your contribution to this review. Let's cross fingers for the best. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From thierry.nagellen at orange.com Mon Jun 17 13:32:34 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 17 Jun 2013 11:32:34 +0000 Subject: [Fiware-iot] URGENT: update SOTA references Message-ID: <28148_1371468755_51BEF3D3_28148_4718_1_976A65C5A08ADF49B9A8523F7F81925C0F501F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I have to update for today EOB the table of references for the SOTA of IoT. I was able to rebuild the list of references except for some of them. For these missing references (the one in yellow) If people who added these references could provide the details it would be very useful. If I have no detail, I have to delete them in the final document. 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, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Iot-SOTA-references.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 32157 bytes Desc: Iot-SOTA-references.docx URL: From t.elsaleh at surrey.ac.uk Mon Jun 17 14:07:35 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Mon, 17 Jun 2013 13:07:35 +0100 Subject: [Fiware-iot] URGENT: update SOTA references In-Reply-To: <28148_1371468755_51BEF3D3_28148_4718_1_976A65C5A08ADF49B9A8523F7F81925C0F501F@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <28148_1371468755_51BEF3D3_28148_4718_1_976A65C5A08ADF49B9A8523F7F81925C0F501F@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1DAC1@EXMB05CMS.surrey.ac.uk> Hello Thierry, I have included the missing references that were highlighted. 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: 17 June 2013 12:33 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] URGENT: update SOTA references Importance: High Dear all, I have to update for today EOB the table of references for the SOTA of IoT. I was able to rebuild the list of references except for some of them. For these missing references (the one in yellow) If people who added these references could provide the details it would be very useful. If I have no detail, I have to delete them in the final document. 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, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Iot-SOTA-references-missing refs.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 37705 bytes Desc: Iot-SOTA-references-missing refs.docx URL: From thierry.nagellen at orange.com Mon Jun 17 15:00:04 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Mon, 17 Jun 2013 13:00:04 +0000 Subject: [Fiware-iot] URGENT: update SOTA references In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1DAC1@EXMB05CMS.surrey.ac.uk> References: <28148_1371468755_51BEF3D3_28148_4718_1_976A65C5A08ADF49B9A8523F7F81925C0F501F@PEXCVZYM13.corporate.adroot.infra.ftgroup> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F1DAC1@EXMB05CMS.surrey.ac.uk> Message-ID: <16493_1371474005_51BF0855_16493_81_1_976A65C5A08ADF49B9A8523F7F81925C0F50B4@PEXCVZYM13.corporate.adroot.infra.ftgroup> Thanks a lot Tarek BR Thierry De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : lundi 17 juin 2013 14:08 ? : NAGELLEN Thierry OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu Objet : RE: URGENT: update SOTA references Hello Thierry, I have included the missing references that were highlighted. 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: 17 June 2013 12:33 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] URGENT: update SOTA references Importance: High Dear all, I have to update for today EOB the table of references for the SOTA of IoT. I was able to rebuild the list of references except for some of them. For these missing references (the one in yellow) If people who added these references could provide the details it would be very useful. If I have no detail, I have to delete them in the final document. 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, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Jun 19 06:21:55 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 19 Jun 2013 04:21:55 +0000 Subject: [Fiware-iot] =?iso-8859-1?q?Annul=E9=3A_IoT_weekly_meeting?= Message-ID: <2562_1371615722_51C131EA_2562_4709_5_216b45d1-a58a-4be9-b99a-45362f580915@PEXCVZYH01.corporate.adroot.infra.ftgroup> Quand : mercredi 19 juin 2013 10:00-11:30 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Emplacement : Powwownow facilities Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Regular meeting till the end of the project powwownow PIN dedicated to the FI-WARE IoT chapter: 028919 http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2879 bytes Desc: not available URL: From thierry.nagellen at orange.com Wed Jun 19 06:24:23 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 19 Jun 2013 04:24:23 +0000 Subject: [Fiware-iot] R2.3 deadline and internal review Message-ID: <22633_1371615864_51C13278_22633_4817_1_976A65C5A08ADF49B9A8523F7F81925C0F56CA@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear partners Many of us are at the IoT week in Helsinki so we cannot have the weekly meeting today. Please take into account the last message from Miguel that the deadline for software delivery AND documentation is for the 28th of June and that Carlos and myself have to check everything before. Thanks for your support. BR Thierry De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 18 juin 2013 16:46 ? : fiware at lists.fi-ware.eu Objet : [Fiware] Deadline for delivery of GEs in June: 28TH of JUNE Dear all, A reminder and also to ensure that you are aware if it not communicated in your WP at the time. As agreed in June, 3rd (WPL/WPA weekly call) the final delivery of major release R2 (once concluded R2.3) is the 28th of June. Each WPL/WPA will organize it internally as he thinks it's best. All we need is the deliverables in good shape - complying with the guidelines on : * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 So we expect the Install & admin Manual, the User & Programmers manual, Unit Testing plan & Software itself for all the GEs to be delivered in R2.3. I guess that many ones delivered in R2.2 will be "refreshed" as well since those with backlog items in R2.3 (most) will have to deliver software. There you also have the links to the placeholders where you have to link the manuals. Obviously, the block we will use now for each manual will be the one named "Contributions for June/2013 " Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From t.elsaleh at surrey.ac.uk Fri Jun 21 16:00:08 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Fri, 21 Jun 2013 15:00:08 +0100 Subject: [Fiware-iot] Mandatory/Optional support for ConfMan GE In-Reply-To: <5177ED61.3060906@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789D5ABFC@EXMB05CMS.surrey.ac.uk> <5177ED61.3060906@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F924A9@EXMB05CMS.surrey.ac.uk> Hello Fermin, Could you tell me if the spreadsheet below is up to date with regards to the implementation of the operations that you will support for release 2.3? https://docs.google.com/spreadsheet/ccc?key=0Aj_S9VF3rt5DdEhqZHlBaGVURmhZRDY3aDRBdlpHS3c#gid=0 Best regards, Tarek From: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: 24 April 2013 15:34 To: Elsaleh T Mr (Electronic Eng) Cc: Tobias.Jacobs at neclab.eu; fiware-iot at lists.fi-ware.eu; Barnaghi P Dr (Electronic Eng) Subject: Re: Mandatory/Optional support for ConfMan GE Dear Tarek, Sorry for the delay in the answer. Please, find my comments inline. What is functional and non fucntional is very clear for me. However, I'm not sure if I'm the right one to decide wether "mandatory" or "optional". What can I do (in the hope it would be useful) is tell you what we have include in TID's ConfMan roadmap for 2.3. El 24/04/2013 12:24, t.elsaleh at surrey.ac.uk escribi?: Hello Tobias, Fermin, Thanks for the reply Tobias. It would good if Fermin can give his opinion on this as well. Let's start with asserting what features/epics are mandatory and what are optional. As I mentioned, and what you (Tobias) confirmed is that non-functional features should be optional. This takes us to the Epics/Features defined for the ConfMan by TID which are: * FIWARE.EPIC.ContextBroker.ParallelProcessingSupport, o I believe this is non-functional related epic therefore it should be optional. [FGM1] Right. It is not functional. Included in 2.3 roadmap. * FIWARE.EPIC.ContextBroker.MassiveDataSupport, o I believe this is non-functional related epic therefore it should be optional. [FGM2] Right. It is not functional. Included in 2.3 roadmap. * FIWARE.EPIC.ContextBroker.DataChapterGEsIntegration * I am not sure how D/C chapter here are a special case, since I guess they will also take the role of a NGSI-9 client. From the description, it hints to performance-related issues. But Fermin please correct me if I am wrong. [FGM3] This is an EPIC yet to be refined. It has to do with how ContexBroker (in its Pub/Sub Broker GE role) will integrate with other GEs in the Data Chapter (CEP, BigData, etc.). It hasn't to do with IoT chapter (in fact, in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_%28IoT%29_Services_Enablement_in_FI-WARE#Backend_Configuration_Management_GE it is not included). * FIWARE.Feature.ContextBroker.AvailabilityContextSubscription&Notification, o This is a functional requirement and is therefore mandatory [FGM4] Right. It is functional. Included in 2.3 roadmap. * FIWARE.Feature.ContextBroker.JSONSupport o Is this mandatory, since the main support is in XML? [FGM5] This is functional, but secondary. In fact, we have drop this feature from 2.3 roadmap to accommodate the more priority feature on associations implementation. * FIWARE.Feature.ContextBroker.ConvenienceOperations, o This is a functional requirement and is therefore mandatory [FGM6] There are 41 different convenience operations (including both NGSI9 and NGSI10). We have defined a subset of around 20 operations to be implemented for 2.3, the rest will be referred to release 3. You can check the detail at https://docs.google.com/spreadsheet/ccc?key=0Aj_S9VF3rt5DdEhqZHlBaGVURmhZRDY3aDRBdlpHS3c#gid=0 (pay attention only to NGSI9). This is my analysis of the epic/features. What is your take on this? Best regards, Tarek From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: 18 April 2013 15:37 To: CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: FERMIN GALAN MARQUEZ; fiware-iot at lists.fi-ware.eu; Barnaghi P Dr (Electronic Eng) Subject: RE: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek 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 fermin at tid.es Fri Jun 21 16:00:31 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Fri, 21 Jun 2013 16:00:31 +0200 Subject: [Fiware-iot] Mandatory/Optional support for ConfMan GE In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F924A9@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789D5ABFC@EXMB05CMS.surrey.ac.uk> <5177ED61.3060906@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCA789F924A9@EXMB05CMS.surrey.ac.uk> Message-ID: <51C45C7F.9030606@tid.es> Dear Tarek, I do confirm it's up to date. The operations included in 2.3 are the ones marked with "Release 2". Best regards, ------ Ferm?n El 21/06/2013 16:00, t.elsaleh at surrey.ac.uk escribi?: Hello Fermin, Could you tell me if the spreadsheet below is up to date with regards to the implementation of the operations that you will support for release 2.3? https://docs.google.com/spreadsheet/ccc?key=0Aj_S9VF3rt5DdEhqZHlBaGVURmhZRDY3aDRBdlpHS3c#gid=0 Best regards, Tarek From: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: 24 April 2013 15:34 To: Elsaleh T Mr (Electronic Eng) Cc: Tobias.Jacobs at neclab.eu; fiware-iot at lists.fi-ware.eu; Barnaghi P Dr (Electronic Eng) Subject: Re: Mandatory/Optional support for ConfMan GE Dear Tarek, Sorry for the delay in the answer. Please, find my comments inline. What is functional and non fucntional is very clear for me. However, I'm not sure if I'm the right one to decide wether "mandatory" or "optional". What can I do (in the hope it would be useful) is tell you what we have include in TID's ConfMan roadmap for 2.3. El 24/04/2013 12:24, t.elsaleh at surrey.ac.uk escribi?: Hello Tobias, Fermin, Thanks for the reply Tobias. It would good if Fermin can give his opinion on this as well. Let's start with asserting what features/epics are mandatory and what are optional. As I mentioned, and what you (Tobias) confirmed is that non-functional features should be optional. This takes us to the Epics/Features defined for the ConfMan by TID which are: * FIWARE.EPIC.ContextBroker.ParallelProcessingSupport, o I believe this is non-functional related epic therefore it should be optional. [FGM1] Right. It is not functional. Included in 2.3 roadmap. * FIWARE.EPIC.ContextBroker.MassiveDataSupport, o I believe this is non-functional related epic therefore it should be optional. [FGM2] Right. It is not functional. Included in 2.3 roadmap. * FIWARE.EPIC.ContextBroker.DataChapterGEsIntegration * I am not sure how D/C chapter here are a special case, since I guess they will also take the role of a NGSI-9 client. From the description, it hints to performance-related issues. But Fermin please correct me if I am wrong. [FGM3] This is an EPIC yet to be refined. It has to do with how ContexBroker (in its Pub/Sub Broker GE role) will integrate with other GEs in the Data Chapter (CEP, BigData, etc.). It hasn't to do with IoT chapter (in fact, in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_%28IoT%29_Services_Enablement_in_FI-WARE#Backend_Configuration_Management_GE it is not included). * FIWARE.Feature.ContextBroker.AvailabilityContextSubscription&Notification, o This is a functional requirement and is therefore mandatory [FGM4] Right. It is functional. Included in 2.3 roadmap. * FIWARE.Feature.ContextBroker.JSONSupport o Is this mandatory, since the main support is in XML? [FGM5] This is functional, but secondary. In fact, we have drop this feature from 2.3 roadmap to accommodate the more priority feature on associations implementation. * FIWARE.Feature.ContextBroker.ConvenienceOperations, o This is a functional requirement and is therefore mandatory [FGM6] There are 41 different convenience operations (including both NGSI9 and NGSI10). We have defined a subset of around 20 operations to be implemented for 2.3, the rest will be referred to release 3. You can check the detail at https://docs.google.com/spreadsheet/ccc?key=0Aj_S9VF3rt5DdEhqZHlBaGVURmhZRDY3aDRBdlpHS3c#gid=0 (pay attention only to NGSI9). This is my analysis of the epic/features. What is your take on this? Best regards, Tarek From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: 18 April 2013 15:37 To: CARLOS RALLI UCENDO; Elsaleh T Mr (Electronic Eng) Cc: FERMIN GALAN MARQUEZ; fiware-iot at lists.fi-ware.eu; Barnaghi P Dr (Electronic Eng) Subject: RE: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek, Your proposal sound pretty much complete operation-wise, and I would agree (but it is not me who decides that) that it is ok not to implement the nonfunctional features. In summary, your GE implementation would be less tailored to performance, but instead have additional semantic discovery support. I am also curious how semantic support will look like and how it is accessed with NGSI. What I imagine is that registrations could be annotated with some metadata describing semantics, while discovery and subscribe-operations could use a specially defined scope type for making semantic queries. Best regards Tobias From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Mittwoch, 17. April 2013 19:10 To: t.elsaleh at surrey.ac.uk Cc: FERMIN GALAN MARQUEZ; Tobias Jacobs; fiware-iot at lists.fi-ware.eu; p.barnaghi at surrey.ac.uk Subject: Re: Full "architectural" support for (UoSurrey) ConfMan GE Hi Tarek Thanks for your mail. I need to check carefully and discuss internally but looks much better than before! Regarding docs, I'm almost sure it gets delayed too but I need to check agree this with the overall coordination. I'll come back to you on this matter ASAP. BR El 17/04/2013, a las 18:28, "t.elsaleh at surrey.ac.uk" > escribi?: Hello Carlos, Fermin, Tobias, After discussing the matter internally, we (UoSurrey) will aim to provide our implementation for the GE by the end of Release 2.3, which I understand is end of June. This is due to the change in the IoT architecture last month in the F2F meeting, which has resulted in the removal of our original GE from the IoT architecture. We will aim to support the functions and interactions that are "architecturally" required for the ConfMan GE, meaning the ability to serve an NGSI-9 client that involves the following: * NGSI-9 standard operations o Register, discover, subscribe/notify * NGSI-9 convenience operations o Register, discover, subscribe/notify * NGSI-9 associations * NGSI-9 discovery restrictions (scopes) * NGSI-9 subscription restrictions Fermin, Tobias, have I missed something? I understand there are other features in the ConfMan GE that are concerned with internal performance, such as multithreading. These type of features we will not plan to support. I hope this still makes our GE compliant, from an architecture point-of-view. Carlos, is the proposal OK? If so, can we confirm that UoSurrey will provide the GE implementation of ConfMan by end of June? This will mean that I will need to shift some of our features set in the Technical Roadmap to 2.3, as it doesn't make sense to provide these without the main functions of the ConfMan GE. Please can you also confirm whether the software documentation for our GE is still due on the 22nd of April or not? Because from what I understand that this will be delayed until June as well. Best regards, Tarek 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 ________________________________ 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 Martin.Bauer at neclab.eu Fri Jun 21 16:30:37 2013 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Fri, 21 Jun 2013 14:30:37 +0000 Subject: [Fiware-iot] IERC / FI-WARE and FI-PPP interactions Message-ID: Hi IoT enthusiasts, At IoT Week in Helsinki we had a meeting between IERC AC1 "Architecture" and the IoT Chapter of FI-WARE. We discussed the mapping of the FI-WARE architecture to the IoT-A Architectural Reference Model. You can find the slides presented during the meeting here: https://project.sintef.no/eRoom/ikt2/IERC/0_31728 At the meeting, we also discussed the next steps of interactions between IERC and FI-WARE and the whole PPP - which is why I decided to copy this to the whole IERC list. 1) There is now a stable version of FI-WARE IoT GEs, so it is time to check whether there are additional assets from which FI-WARE and the FI-PPP could benefit. This especially pertains to AC01 and AC02. ACTION POINT: IERC projects need to check the FI-WARE architecture and its mapping to the IoT-A ARM and evaluate whether there are assets not yet present that they could provide from which FI-WARE could benefit. Please map to the IoT-A ARM for easier assessment. To be considered by FI-WARE (or its follow-up) it is important that a GE based on such an asset could be provided also to external partners under FI-WARE conditions, i.e. as open-source or under suitable commercial conditions. 2) (Semantic) Interoperability (AC04) was identified as a further area of collaboration. ACTION POINT: FI-WARE will nominate a representative for interaction with AC04, who will try to attend the next AC04 meeting. There is the possibility of joint testing events. 3) The new FI-PPP application projects are relevant for AC03. Starting from September 2013 Btw. the IoT-A Architectural Reference Model will be sustained and further developed by the IoT Forum (www.iot-forum.eu), which was formally founded during IoT Week. This will enable all interested parties to contribute. The IoT Forum will also organize future IoT Weeks, the next one will be in London in June 2013. Best regards, Martin Bauer ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu ************************************************************* NEC Europe Limited Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, Great Britain Registered in England 2832014 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed Jun 26 08:19:21 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 26 Jun 2013 06:19:21 +0000 Subject: [Fiware-iot] ConfCall Message-ID: <8755F290097BD941865DC4245B335D2D38FB9685@DAPHNIS.office.hd> Hi all, will there be an IoT Confcall today? Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Jun 26 08:22:57 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 26 Jun 2013 06:22:57 +0000 Subject: [Fiware-iot] ConfCall In-Reply-To: <8755F290097BD941865DC4245B335D2D38FB9685@DAPHNIS.office.hd> References: <8755F290097BD941865DC4245B335D2D38FB9685@DAPHNIS.office.hd> Message-ID: <29292_1372227778_51CA88C2_29292_687_1_976A65C5A08ADF49B9A8523F7F81925C0FCDD1@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Yes we will have the call today. The main point will be the status of delivery for the 28th of June (software and documentation, as well as trackers update). I'm sending the link for the googledocs in few minutes. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 26 juin 2013 08:19 ? : fiware-iot at lists.fi-ware.eu; NAGELLEN Thierry OLNC/OLPS; CARLOS RALLI UCENDO (ralli at tid.es) Objet : ConfCall Hi all, will there be an IoT Confcall today? Best Tobias _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, 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 mcp at tid.es Wed Jun 26 08:51:23 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 26 Jun 2013 08:51:23 +0200 Subject: [Fiware-iot] [Fiware] Important messages in yesterday's coordination call In-Reply-To: <51C9807E.3060507@tid.es> References: <51C9807E.3060507@tid.es> Message-ID: <51CA8F6B.9080604@tid.es> Dear all, I suspect that there are many people out of the general list (fiware at lists.fi-ware.eu). All people should be there. Those who did not receive the message at the bottom contact me privately and I will add you to this list. There is a presentation with general background on the use of our resources in FI-WARE here: https://forge.fi-ware.eu/docman/view.php/27/1982/FI-WARE-Forge+and+tools.pptx The presentation is on the private project on the forge. I remind you that all of you should have access to the project "FI-WARE Private" and that this is managed in each WP by the respective WPL/WPA. As them to add you if you do not have access to this file. Best regards, Miguel El 25/06/2013 13:35, Miguel Carrillo escribi?: Dear all, I would like to circulate the minutes of meeting of yesterday's coordination call, there are too important messages to miss them. I am sure the WPL/WPA will circulate them but I want to ensure that it gets to all of you in any case. The link is here: * https://docs.google.com/document/d/1NGqZPL0uNvsmpnrJI5x-MxdN6YJi0hBePs6euimoUrs Incidentally, we keep the list of links to the minutes of the WPL/WPA calls on the private wiki. There is a direct link on the private wiki home page that takes you there: * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Minutes_of_WPL/WPA_Meetings If someone cannot access the private wiki, I remind you that the WPL/WPA are the ones in charge of granting you access to this repository. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware mailing list Fiware at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Wed Jun 26 09:08:35 2013 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Wed, 26 Jun 2013 07:08:35 +0000 Subject: [Fiware-iot] Ericsson IoT gateway soon to be released as open source Message-ID: <0B1670B04B59D249B28C0746C8885DDF15F8D3@ESESSMB307.ericsson.se> Dear Thierry, As discussed during the IoT Week in Helsinki last week, we are finalizing our steps to release our IoT gateway software as open source. That means that Fi-ware IoT would get access to use the software and integrate in whatever way needed for achieving the objectives of the project, e.g. integration of Fraunhofer ETSI M2M, TI ZigBee in addition to the existing support for IETF CoRE/CoAP devices etc. I will keep you posted on the progress as well as the content of what will be open sourced. Best regards, Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Jun 26 09:20:25 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 26 Jun 2013 07:20:25 +0000 Subject: [Fiware-iot] IoT weekly meeting link to minutes Message-ID: <5107_1372231225_51CA9639_5107_39_5_976A65C5A08ADF49B9A8523F7F81925C0FCE00@PEXCVZYM13.corporate.adroot.infra.ftgroup> Here is the link for the minutes today https://docs.google.com/document/d/1PE1cuj6_qxU_ELB5whShxDYkh756LyPQgBL-19-xDRQ/edit# And the link to WPL/WPA minutes regarding R2.3 delivery https://docs.google.com/document/d/1NGqZPL0uNvsmpnrJI5x-MxdN6YJi0hBePs6euimoUrs 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 ralli at tid.es Wed Jun 26 09:33:26 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 26 Jun 2013 07:33:26 +0000 Subject: [Fiware-iot] ConfCall In-Reply-To: <29292_1372227778_51CA88C2_29292_687_1_976A65C5A08ADF49B9A8523F7F81925C0FCDD1@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <8755F290097BD941865DC4245B335D2D38FB9685@DAPHNIS.office.hd> <29292_1372227778_51CA88C2_29292_687_1_976A65C5A08ADF49B9A8523F7F81925C0FCDD1@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <6462CAAB-7CF5-4135-B7AE-3A534317E286@tid.es> Thanks Thierry, I'll connect too reporting status of BE Dev Man GE status. BR El 26/06/2013, a las 08:22, "thierry.nagellen at orange.com" > escribi?: Hi all Yes we will have the call today. The main point will be the status of delivery for the 28th of June (software and documentation, as well as trackers update). I?m sending the link for the googledocs in few minutes. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 26 juin 2013 08:19 ? : fiware-iot at lists.fi-ware.eu; NAGELLEN Thierry OLNC/OLPS; CARLOS RALLI UCENDO (ralli at tid.es) Objet : ConfCall Hi all, will there be an IoT Confcall today? Best Tobias _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, 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 fermin at tid.es Wed Jun 26 10:30:45 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 26 Jun 2013 10:30:45 +0200 Subject: [Fiware-iot] ConfCall In-Reply-To: <6462CAAB-7CF5-4135-B7AE-3A534317E286@tid.es> References: <8755F290097BD941865DC4245B335D2D38FB9685@DAPHNIS.office.hd> <29292_1372227778_51CA88C2_29292_687_1_976A65C5A08ADF49B9A8523F7F81925C0FCDD1@PEXCVZYM13.corporate.adroot.infra.ftgroup> <6462CAAB-7CF5-4135-B7AE-3A534317E286@tid.es> Message-ID: <51CAA6B5.90601@tid.es> Dear Thierry, I will not attend to the audio, but I can tell you the status of ConfMan GE: * Manuals: submitted yesterday * Software: on track, it will updloaded to the forge on June 28th morning * Catalog: ready at http://catalogue.fi-ware.eu/enablers/publishsubscribe-context-broker-orion-context-broker * Integration: Salvatore and me will have an integration session on July 2th using IDAS. We would like to use also the DataHanding GE but during June 14th integration attempt there was problems in that component and we don't have news from Laurent telling us that he is ready (we have tried to contact him by email on June 21th, but we haven't received any answer yet) * Testbed installation: 40% progress (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Implementation_Cockpit) Best regards, ------ Ferm?n El 26/06/2013 9:33, CARLOS RALLI UCENDO escribi?: Thanks Thierry, I'll connect too reporting status of BE Dev Man GE status. BR El 26/06/2013, a las 08:22, "thierry.nagellen at orange.com" > escribi?: Hi all Yes we will have the call today. The main point will be the status of delivery for the 28th of June (software and documentation, as well as trackers update). I'm sending the link for the googledocs in few minutes. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 26 juin 2013 08:19 ? : fiware-iot at lists.fi-ware.eu; NAGELLEN Thierry OLNC/OLPS; CARLOS RALLI UCENDO (ralli at tid.es) Objet : ConfCall Hi all, will there be an IoT Confcall today? Best Tobias _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, 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 _______________________________________________ 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 Jun 26 11:18:59 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 26 Jun 2013 09:18:59 +0000 Subject: [Fiware-iot] Doodle for summer vacations Message-ID: <28307_1372238340_51CAB204_28307_1011_1_976A65C5A08ADF49B9A8523F7F81925C0FCE94@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, As discussed during the IoT weekly meeting please update the Doodle so Carlos and me will be able to know what will be the status of the team during the Summer. http://doodle.com/iyruw6nuv9r7smdwc63ivtv5/admin?#table 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 Wed Jun 26 13:44:03 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 26 Jun 2013 11:44:03 +0000 Subject: [Fiware-iot] Doodle for summer vacations In-Reply-To: <28307_1372238340_51CAB204_28307_1011_1_976A65C5A08ADF49B9A8523F7F81925C0FCE94@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <28307_1372238340_51CAB204_28307_1011_1_976A65C5A08ADF49B9A8523F7F81925C0FCE94@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <19687_1372247044_51CAD404_19687_5004_1_976A65C5A08ADF49B9A8523F7F81925C0FCEF2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all To answer a good question from Martin, you have to tick days when you will be on vacation so green is when you are... not there! BR Thierry 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 26 juin 2013 11:19 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Doodle for summer vacations Dear all, As discussed during the IoT weekly meeting please update the Doodle so Carlos and me will be able to know what will be the status of the team during the Summer. http://doodle.com/iyruw6nuv9r7smdwc63ivtv5/admin?#table 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 Tobias.Jacobs at neclab.eu Thu Jun 27 16:41:27 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 27 Jun 2013 14:41:27 +0000 Subject: [Fiware-iot] Association in public wiki Message-ID: <8755F290097BD941865DC4245B335D2D38FB996E@DAPHNIS.office.hd> Hi all, I now put our NGSI association concept description into the public wiki under https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/OMA_NGSI_Association_concept Please feel free to refer to it in the documentation of your GEs if needed. Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Thu Jun 27 17:39:45 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 27 Jun 2013 15:39:45 +0000 Subject: [Fiware-iot] Delivery of the "Backend Device Management GE" (and GEi) for R2.3 Message-ID: <1971FF81B8E01C45991F6F92B9E3B250890BDC7D@EX10-MB2-MAD.hi.inet> Dear Thierry et all, Together with TID IoT team we have updated the following resources to complete the delivery of this on time: ** Important notice: The GE name is "BE Device Management". Our GEi is named "IDAS" for simplicity and it is actually the combination of two assets: The IoT-Agent (NGSI connector) and the DCA-IDAS M2M platform. 1) Installation Manual. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Device_Management_-_Installation_and_Administration_Guide_R2 2) User Manual. The information included is pretty extensive, however there are two documents linked for more details that I will be uploading tomorrow. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Device_Management_-_User_and_Programmers_Guide_R2#NGSI9.2F10_REST_API 3) Unit-tests: With 6 tests and their results validating all new features we have defined. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Device_Management_-_Unit_Testing_Plan_and_Report_R2 4) Software delivery. It is made of the two assets mentioned above and available at: https://forge.fi-ware.eu/frs/?group_id=23 (Package IOT-IDAS) 5) Roadmap: Totally new version of the Epics and Features. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services 6) Materializing the Fi-ware vision: Update on the assets and plans for the future related to this GE/GEi. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE 7) BE Device Management GE Architecture: Minor updates in the diagrams. Work to be done in the coming days: - Catalogue entry (expected for tomorrow). - Open Specifications (include 2 new API pages, expected tomorrow) - New tracker for IDAS GEi synchronized with the new Roadmap (Epics & Features). This will be done next Monday/Tuesday. I think we are not forgetting anything. Should you have comments or new items to cover, please, let us know. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli IPv6 Blog: http://the-internet6.blogspot.com.es Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ 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 Fri Jun 28 13:29:38 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Fri, 28 Jun 2013 12:29:38 +0100 Subject: [Fiware-iot] ConfMan GEI - IoT Discovery (UniSurrey) Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F92B62@EXMB05CMS.surrey.ac.uk> Hello Thierry, Here are the links for the Configuration Management GEI for UniSurrey. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_GE_-_IoT_Discovery_-_Installation_and_Administration_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_User_and_Programmers_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_Unit_Testing_Plan_and_Report_R2 I have noticed that in the public "Materializing ...." Section that the features/epics I have defined are missing from the Configuration Management GE. These are the missing ones: Release 2.3 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.AdvDescription FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Discover.TemplateBased FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.EngineTraining FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Register.FoldingIn FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.AssociationMatching FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.Discover.Sparql FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.NGSI9 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.WebUI FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.ProbabilisticSearch FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.SemanticSearch Can someone please explain why? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Jun 28 14:21:08 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 28 Jun 2013 12:21:08 +0000 Subject: [Fiware-iot] ConfMan GEI - IoT Discovery (UniSurrey) In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F92B62@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F92B62@EXMB05CMS.surrey.ac.uk> Message-ID: <18504_1372422068_51CD7FB4_18504_8331_1_976A65C5A08ADF49B9A8523F7F81925C102531@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Tarek Thanks for the links, I'm going through all of them ASPA. Regarding features and EPICS you can find them in the Technical Roadmap (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services#Backend ) because in Materializing... section we keep only what was in the first release and we decided to provide everything in the technical Roadmap for UC projects. They can find what we will deliver in new releases in this place. Iv' just have a look on it but I think that all you items are there. BR Thierry De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : vendredi 28 juin 2013 13:30 ? : NAGELLEN Thierry OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; ralli at tid.es Objet : ConfMan GEI - IoT Discovery (UniSurrey) Hello Thierry, Here are the links for the Configuration Management GEI for UniSurrey. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_GE_-_IoT_Discovery_-_Installation_and_Administration_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_User_and_Programmers_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_Unit_Testing_Plan_and_Report_R2 I have noticed that in the public "Materializing ...." Section that the features/epics I have defined are missing from the Configuration Management GE. These are the missing ones: Release 2.3 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.AdvDescription FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Discover.TemplateBased FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.EngineTraining FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Register.FoldingIn FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.AssociationMatching FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.Discover.Sparql FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.NGSI9 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.WebUI FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.ProbabilisticSearch FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.SemanticSearch Can someone please explain why? Best regards, Tarek _________________________________________________________________________________________________________________________ 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 Fri Jun 28 16:07:53 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Fri, 28 Jun 2013 15:07:53 +0100 Subject: [Fiware-iot] ConfMan GEI - IoT Discovery (UniSurrey) In-Reply-To: <18504_1372422068_51CD7FB4_18504_8331_1_976A65C5A08ADF49B9A8523F7F81925C102531@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F92B62@EXMB05CMS.surrey.ac.uk> <18504_1372422068_51CD7FB4_18504_8331_1_976A65C5A08ADF49B9A8523F7F81925C102531@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA789F92BA5@EXMB05CMS.surrey.ac.uk> Hello Thierry, Many thanks for the clarification. Yes, the features/epics are in the Technical Roadmap. Best regards, Tarek From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: 28 June 2013 13:21 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu; ralli at tid.es Subject: RE: ConfMan GEI - IoT Discovery (UniSurrey) Hi Tarek Thanks for the links, I'm going through all of them ASPA. Regarding features and EPICS you can find them in the Technical Roadmap (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services#Backend ) because in Materializing... section we keep only what was in the first release and we decided to provide everything in the technical Roadmap for UC projects. They can find what we will deliver in new releases in this place. Iv' just have a look on it but I think that all you items are there. BR Thierry De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : vendredi 28 juin 2013 13:30 ? : NAGELLEN Thierry OLNC/OLPS Cc : fiware-iot at lists.fi-ware.eu; ralli at tid.es Objet : ConfMan GEI - IoT Discovery (UniSurrey) Hello Thierry, Here are the links for the Configuration Management GEI for UniSurrey. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_GE_-_IoT_Discovery_-_Installation_and_Administration_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_User_and_Programmers_Guide_R2 https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Configuration_Management_-_IoT_Discovery_-_Unit_Testing_Plan_and_Report_R2 I have noticed that in the public "Materializing ...." Section that the features/epics I have defined are missing from the Configuration Management GE. These are the missing ones: Release 2.3 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.AdvDescription FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Discover.TemplateBased FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.EngineTraining FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.ProbabalisticSearch.Register.FoldingIn FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.AssociationMatching FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.SemanticSearch.Discover.Sparql FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.NGSI9 FIWARE.Feature.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt.WebUI FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.IoTDescriptionMgmt FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.ProbabilisticSearch FIWARE.Epic.IoT.Backend.IoTDiscoveryEngine.SemanticSearch Can someone please explain why? Best regards, Tarek _________________________________________________________________________________________________________________________ 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 Jun 28 19:40:56 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 28 Jun 2013 17:40:56 +0000 Subject: [Fiware-iot] IoT Broker Software deliverable Message-ID: <8755F290097BD941865DC4245B335D2D38FB9B45@DAPHNIS.office.hd> Hi Thierry, As part of the Software deliverable, we - uploaded version 2.3.0 of the IoT Broker GE - updated the technical roadmap with some features that had previously been only in the backlog, see (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_%28IoT%29_Services) - closed the tracker items corresponding to the implemented features in version 2.3 - updated the NGSI associations page in the public wiki as part of the open specification: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/OMA_NGSI_Association_concept - updated the Unit Test Plan: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Backend_IoT_Broker_GE_-_Unit_Testing_Plan_and_Report - updated the Install & Admin Guide: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/IoT_Broker_-_Installation_and_Administration_Guide - updated the User and Programmers Guide: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/IoT_Broker_-_User_and_Programmers_Guide Best regards and have a nice weekend! Salvatore, Raihan, Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From konrad.campowsky at fokus.fraunhofer.de Sat Jun 29 09:43:06 2013 From: konrad.campowsky at fokus.fraunhofer.de (Konrad Campowsky) Date: Sat, 29 Jun 2013 09:43:06 +0200 Subject: [Fiware-iot] Gateway Device Management GE Message-ID: <51CE900A.2070001@fokus.fraunhofer.de> Hello Thierry, I've created these pages for the Gateway Device Management GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/IoT.Gateway.DeviceManagement_-_Installation_and_Administration_Guide http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Backend_Things_Management_-_Configuration_Management_User_and_Programmers_Guide https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/IoT.Gateway.DeviceManagement_-_Unit_Testing_Plan_and_Report_R2#Test_description Regarding the unit testing plan: I'm not sure what to put as "tested featurs". Where do I find information about that? Thanks, Konrad