From thierry.nagellen at orange.com Wed Nov 6 08:51:03 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 6 Nov 2013 07:51:03 +0000 Subject: [Fiware-iot] Today weekly meeting Message-ID: <20906_1383724263_5279F4E7_20906_7106_1_976A65C5A08ADF49B9A8523F7F81925C14402E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all Here is the link for the minutes for the weekly meeting today. https://docs.google.com/document/d/1GvJFySdc2Wo0mbuvDv-jqIZpy62tMm00BeSvENnbkMA/edit BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Nov 6 11:06:26 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 6 Nov 2013 10:06:26 +0000 Subject: [Fiware-iot] validation analysis wiki Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB982DD6F8C@EXMB05CMS.surrey.ac.uk> Hi Salvatore, Could you please send me the link where you provided input for the validation analysis (the one due by 15th November)? ...I thought the analysis in the wiki was UC-oriented rather than (fiware) chapter-oriented? Best regards, Tarek From: Salvatore Longo [mailto:Salvatore.Longo at neclab.eu] Sent: 30 October 2013 09:36 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: PhC today? Hi Tarek, I don't think so. I was in the Phc but there was not Carlos or Thierry. So in the end we decided to left. 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 t.elsaleh at surrey.ac.uk Sent: Mittwoch, 30. Oktober 2013 10:20 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] PhC today? Hello All, Will there be a PhC today? Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Nov 6 11:13:00 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 6 Nov 2013 10:13:00 +0000 Subject: [Fiware-iot] Amending item names in Backlog Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB982DD6F8E@EXMB05CMS.surrey.ac.uk> Hello Thierry, With regards to IoT Discovery, I can change the naming convention for all the items in release 2, to what is used now. Can we clarify what docs this will affect? * Technical roadmap? * Materializing....? * Unit test plan? ...This will definitely not take 5 seconds. Best regards, Tarek -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Wed Nov 6 11:57:19 2013 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 6 Nov 2013 10:57:19 +0000 Subject: [Fiware-iot] R: Today weekly meeting In-Reply-To: <20906_1383724263_5279F4E7_20906_7106_1_976A65C5A08ADF49B9A8523F7F81925C14402E@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <20906_1383724263_5279F4E7_20906_7106_1_976A65C5A08ADF49B9A8523F7F81925C14402E@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <2FE5A14B0256E04A8E1E11135A41FA450F4DC42E@TELMBB001BA020.telecomitalia.local> Hi Thierry, as you asked I updated the google doc page adding the issue (raised by a request from WP2 of FINESCE) related the usage of a physical gateway box on which to install the IoT gateway GEs. Please, let me know if there will be an evolution about this argument. Best regards, Sabrina Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: mercoled? 6 novembre 2013 08:51 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Today weekly meeting Priorit?: Alta Hi all Here is the link for the minutes for the weekly meeting today. https://docs.google.com/document/d/1GvJFySdc2Wo0mbuvDv-jqIZpy62tMm00BeSvENnbkMA/edit BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From thierry.nagellen at orange.com Tue Nov 12 10:17:33 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 12 Nov 2013 09:17:33 +0000 Subject: [Fiware-iot] Wiki available for documentation R3.X Message-ID: <29223_1384247854_5281F22E_29223_1825_1_976A65C5A08ADF49B9A8523F7F81925C1460B7@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I've updated the wiki pages for Release 3 documentation. Please tell me if you find any mistake. I remind all of you that we have to use the private wiki and this specific place to update all deliverables regarding documentation (UTP, UPG, IAG) and that the review will be done on what you will put here. One of the key criteria is the reference to any feature we have described in the Technical Roadmap/Materializing the vision to maintain consistency between the wiki and the docs. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR3#FI-WARE_Project_R3_Deliverables_Placeholders_for_common_edition Please describe a workitem to track your activity when working on a specific document and be aware that workitem is available for one sprint. 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 Nov 13 07:17:46 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 13 Nov 2013 06:17:46 +0000 Subject: [Fiware-iot] Links to minutes for IoT weekly meeting. Message-ID: <19560_1384323466_5283198A_19560_16791_1_976A65C5A08ADF49B9A8523F7F81925C1464B8@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all Here is the link for the meeting today. Urgent actions are expected on the tracker (I will provide the new links from Manuel) and for eLearning platform. https://docs.google.com/document/d/16RRliFWvo0qcSlMV2YNUzTPznZn1kPy_y9j8hTMhCYQ/edit Talk to you later. 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 ralli at tid.es Wed Nov 13 07:47:00 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 13 Nov 2013 06:47:00 +0000 Subject: [Fiware-iot] Conference Call Today at 10:30 Message-ID: Dear colleagues. Today we will have our regular conf call and during the first 30-40 minutes, Manuel Eschiche will let us know the tricks and tips to address IoT backlog issues. This is quite important as IoT is having the worse backlog status at the moment and the EC is carefully watching our activities/tasks/efforts as drawn in the chapter backlogs. Here you have the googledoc: https://docs.google.com/document/d/1Yt4xJkr1QJ9VRKVPh362u-cbw3rXNbNb9Ti9UPsI70g/edit The most important slot is the following: 10-10:45 Addressing IoT Backlog (Manuel Escriche and all of us) The links to the spredashits that Manuel will refer to during the slot are: https://forge.fi-ware.eu/docman/view.php/27/2953/FIWARE.backlog.iot.dashboard.20131028-1014.xlsx https://forge.fi-ware.eu/docman/view.php/27/2947/FIWARE.backlog.iot.review.20131028-0857.xlsx Please download those files as Manuel will go into details within them. Thanks in advance. 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 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 ralli at tid.es Wed Nov 13 09:42:29 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 13 Nov 2013 08:42:29 +0000 Subject: [Fiware-iot] Conference Call Today at 10:30 --> Sorry, It is at 10h as usual, I've just got wrong In-Reply-To: Message-ID: Sorry about that! De: Carlos Ralli Ucendo > Fecha: mi?rcoles, 13 de noviembre de 2013 07:47 Para: "fiware-iot at lists.fi-ware.eu" > CC: MANUEL ESCRICHE VICENTE > Asunto: Conference Call Today at 10:30 Dear colleagues. Today we will have our regular conf call and during the first 30-40 minutes, Manuel Eschiche will let us know the tricks and tips to address IoT backlog issues. This is quite important as IoT is having the worse backlog status at the moment and the EC is carefully watching our activities/tasks/efforts as drawn in the chapter backlogs. Here you have the googledoc: https://docs.google.com/document/d/1Yt4xJkr1QJ9VRKVPh362u-cbw3rXNbNb9Ti9UPsI70g/edit The most important slot is the following: 10-10:45 Addressing IoT Backlog (Manuel Escriche and all of us) The links to the spredashits that Manuel will refer to during the slot are: https://forge.fi-ware.eu/docman/view.php/27/2953/FIWARE.backlog.iot.dashboard.20131028-1014.xlsx https://forge.fi-ware.eu/docman/view.php/27/2947/FIWARE.backlog.iot.review.20131028-0857.xlsx Please download those files as Manuel will go into details within them. Thanks in advance. 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 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 thierry.nagellen at orange.com Wed Nov 13 09:56:15 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 13 Nov 2013 08:56:15 +0000 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <5399_1384332976_52833EB0_5399_13545_1_976A65C5A08ADF49B9A8523F7F81925C146608@PEXCVZYM13.corporate.adroot.infra.ftgroup> Quand : mercredi 13 novembre 2013 10:30-12:00 (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, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2972 bytes Desc: not available URL: From thierry.nagellen at orange.com Wed Nov 13 12:06:56 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 13 Nov 2013 11:06:56 +0000 Subject: [Fiware-iot] Tracker:TC1 done Message-ID: <9736_1384340817_52835D51_9736_8719_1_976A65C5A08ADF49B9A8523F7F81925C146A5B@PEXCVZYM13.corporate.adroot.infra.ftgroup> Except If I did some mistakes all items are now ok. BR Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Wed Nov 13 12:35:33 2013 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Wed, 13 Nov 2013 11:35:33 +0000 Subject: [Fiware-iot] Backlog cleaning for IoT Broker Message-ID: <8755F290097BD941865DC4245B335D2D473A3966@Hydra.office.hd> Hi Thierry, we have - Moved the wiki pages to the version without dot between 'Backend' and , and o Changed the references in the tracker items o Changed the references in the 'materializing' page o Changed the references in the unit test plan o Changed the references on the technical roadmap - Took care of all other issues mentioned in the spreadsheet o except for the missing parent/children because we have not defined them in all cases and it seems to be optional anyway. I hope we did not introduce too many new bugs.... Best regards Tobias PS: Like a famous German proverb says, this is work for someone who has murdered mother and father ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Nov 13 13:57:14 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 13 Nov 2013 12:57:14 +0000 Subject: [Fiware-iot] Backlog cleaning for IoT Broker In-Reply-To: <8755F290097BD941865DC4245B335D2D473A3966@Hydra.office.hd> References: <8755F290097BD941865DC4245B335D2D473A3966@Hydra.office.hd> Message-ID: <28967_1384347436_5283772C_28967_4230_1_976A65C5A08ADF49B9A8523F7F81925C146BD9@PEXCVZYM13.corporate.adroot.infra.ftgroup> Thanks a lot Tobias De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoy? : mercredi 13 novembre 2013 12:36 ? : NAGELLEN Thierry IMT/OLPS Cc : fiware-iot at lists.fi-ware.eu; Raihan Ul-Islam; Salvatore Longo Objet : Backlog cleaning for IoT Broker Hi Thierry, we have - Moved the wiki pages to the version without dot between 'Backend' and , and o Changed the references in the tracker items o Changed the references in the 'materializing' page o Changed the references in the unit test plan o Changed the references on the technical roadmap - Took care of all other issues mentioned in the spreadsheet o except for the missing parent/children because we have not defined them in all cases and it seems to be optional anyway. I hope we did not introduce too many new bugs.... Best regards Tobias PS: Like a famous German proverb says, this is work for someone who has murdered mother and father ;-) _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Thu Nov 14 15:00:05 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 14 Nov 2013 14:00:05 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Thu Nov 14 15:20:23 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 14 Nov 2013 14:20:23 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> Hello Tarek, We've got some patterns we're defining based on person's views with experience for topic. Please, find them in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Patterns about Training Material were agreed with Davide Patterns about Documentation with Miguel Carrillo Patterns about Catalogue based on Stephano's control sheet. We have identified them recently, I mean this week. About testbed deployment we don't have currently identified any pattern. We can do it based on somebody's knowledge and experience in the matter. Let me contact Miguel. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:00 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 Thu Nov 14 15:58:15 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 14 Nov 2013 14:58:15 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D109@EXMB05CMS.surrey.ac.uk> Hello Manuel, Thank you for this. I would also like to document in the backlog items that were done before Release 3. Should I only use the "Old_Release" field for these items, or can I use the selectables at the top (sprint/release)? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 14:20 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Tarek, We've got some patterns we're defining based on person's views with experience for topic. Please, find them in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Patterns about Training Material were agreed with Davide Patterns about Documentation with Miguel Carrillo Patterns about Catalogue based on Stephano's control sheet. We have identified them recently, I mean this week. About testbed deployment we don't have currently identified any pattern. We can do it based on somebody's knowledge and experience in the matter. Let me contact Miguel. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:00 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 mev at tid.es Thu Nov 14 16:00:43 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 14 Nov 2013 15:00:43 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D109@EXMB05CMS.surrey.ac.uk> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D109@EXMB05CMS.surrey.ac.uk> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B02C@EX10-MB2-MAD.hi.inet> Yes, use the new ones. The old ones are there for compatibility with items created before June this year. They are waiting for me to have time to migrate them to the new field. So, please, use the new ones. Welcome! From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:58 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Thank you for this. I would also like to document in the backlog items that were done before Release 3. Should I only use the "Old_Release" field for these items, or can I use the selectables at the top (sprint/release)? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 14:20 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Tarek, We've got some patterns we're defining based on person's views with experience for topic. Please, find them in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Patterns about Training Material were agreed with Davide Patterns about Documentation with Miguel Carrillo Patterns about Catalogue based on Stephano's control sheet. We have identified them recently, I mean this week. About testbed deployment we don't have currently identified any pattern. We can do it based on somebody's knowledge and experience in the matter. Let me contact Miguel. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:00 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 t.elsaleh at surrey.ac.uk Thu Nov 14 16:45:34 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 14 Nov 2013 15:45:34 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B02C@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D109@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B02C@EX10-MB2-MAD.hi.inet> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D112@EXMB05CMS.surrey.ac.uk> Hello Manuel, Thanks again. When appending actions to items such as create, and update, how can new updates for the same" item" be differentiated in the backlog, even though each one will be a different workitem? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 15:01 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Yes, use the new ones. The old ones are there for compatibility with items created before June this year. They are waiting for me to have time to migrate them to the new field. So, please, use the new ones. Welcome! From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:58 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Thank you for this. I would also like to document in the backlog items that were done before Release 3. Should I only use the "Old_Release" field for these items, or can I use the selectables at the top (sprint/release)? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 14:20 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Tarek, We've got some patterns we're defining based on person's views with experience for topic. Please, find them in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Patterns about Training Material were agreed with Davide Patterns about Documentation with Miguel Carrillo Patterns about Catalogue based on Stephano's control sheet. We have identified them recently, I mean this week. About testbed deployment we don't have currently identified any pattern. We can do it based on somebody's knowledge and experience in the matter. Let me contact Miguel. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:00 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 mev at tid.es Thu Nov 14 17:34:04 2013 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Thu, 14 Nov 2013 16:34:04 +0000 Subject: [Fiware-iot] Backlogs content - usefulness & visibility In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D112@EXMB05CMS.surrey.ac.uk> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B890E7961@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D0FB@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911AF73@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D109@EXMB05CMS.surrey.ac.uk> <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B02C@EX10-MB2-MAD.hi.inet> <2AAC0B6FF99A064C853BFB1C9295F3CCB982F7D112@EXMB05CMS.surrey.ac.uk> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90B8911B074@EX10-MB2-MAD.hi.inet> Hi Tarek, Well, when creating the patterns I also thought of this. So I share my thoughts. I don't think we need to put every differentiator in the name (=reference). In addition to the name, you've got the timeframe, and have the description field. I thought of adding the release to the reference, but to me it was redundant with the timeframe. Additionally, in the description you can add the document ID, example D2.1.6, or the Release Id, or whatever you need. I recall talking to Davide of the patterns for TrainingMaterial. We had FIWARE.WorkItem...TrainingMaterial.Course..Preparation Then, we decided to simplify it by removing , which could be specified in the description. The longer the pattern, the more difficult to maintain. So, I think we need a balance, between usefulness and detail (cost). If needed we can adapt the patterns, we've bet to keep the simplest useful patterns. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 16:46 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Thanks again. When appending actions to items such as create, and update, how can new updates for the same" item" be differentiated in the backlog, even though each one will be a different workitem? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 15:01 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Yes, use the new ones. The old ones are there for compatibility with items created before June this year. They are waiting for me to have time to migrate them to the new field. So, please, use the new ones. Welcome! From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:58 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Thank you for this. I would also like to document in the backlog items that were done before Release 3. Should I only use the "Old_Release" field for these items, or can I use the selectables at the top (sprint/release)? Best regards, Tarek From: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Sent: 14 November 2013 14:20 To: Elsaleh T Mr (Electronic Eng) Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Tarek, We've got some patterns we're defining based on person's views with experience for topic. Please, find them in the link below: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Patterns about Training Material were agreed with Davide Patterns about Documentation with Miguel Carrillo Patterns about Catalogue based on Stephano's control sheet. We have identified them recently, I mean this week. About testbed deployment we don't have currently identified any pattern. We can do it based on somebody's knowledge and experience in the matter. Let me contact Miguel. Kind regards, Manuel From: t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Sent: jueves, 14 de noviembre de 2013 15:00 To: MANUEL ESCRICHE VICENTE Cc: fiware-iot at lists.fi-ware.eu Subject: RE: Backlogs content - usefulness & visibility Hello Manuel, Would you happen to have a reference for each type of work item? ...since the one shown below in your email are only a few. For example, I understood yesterday that elearning tutorials should come under "TrainingMaterial". Have you declared this before in a previous correspondence to the project? I want to also create items related to the testbed deployment. What should they come under? Also, how do we link user stories to features? Best regards, Tarek From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: 30 October 2013 13:43 To: fiware at lists.fi-ware.eu Subject: [Fiware] Backlogs content - usefulness & visibility Dear Partners, Let me use this channel for conveying this message about the backlogs usage. You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken. For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone. In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving. Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct. At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics. Some of the topics requiring visibility in the chapter's backlogs are the following: * Work/Tasks done for the catalogue - and its associated QA process * Work/Tasks done for delivery documentation - and its associated QA process * New features/tasks derived from Luzt's reports We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point. In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views. My proposal/directions for the topics above are the following: * Catalogue -> FIWARE.WorkItem... Catalogue.<...> * Delivery -> FIWARE.WorkItem...Documentation.UserGuide.<.....> * New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report Hoping you also find it sensible and useful. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Fri Nov 15 07:59:08 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Fri, 15 Nov 2013 06:59:08 +0000 Subject: [Fiware-iot] URGENT: LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III Message-ID: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, I do not know if you have heard about this FITMAN webinar. Going quickly through the short description of each module it seems that as FI-Ware we must attend some of them because they propose some Specific Enablers which are close to some Generic Enablers: typically for my part (IoT) the ShopFloor DATA Collection could be replace by some IoT GEs but we could be also interested by the one working on Semantic interface. Juanjo, Stefano (as member of the Architecture Board because I could not attend the last meeting): do we have some clear architecture picture from FITMAN explaining how their Specific Enablers would interact/use some Generic Enablers? BR Thierry De : Celine Vergne [mailto:celine.vergne at interop-vlab.eu] Envoy? : jeudi 14 novembre 2013 14:58 ? : dissemination at interop-vlab.eu Objet : LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III ------------------------------------------------------------------------------------------------------------------------------------------------------- ------ Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son carnet d'adresses. Vous pouvez le faire en utilisant ce modele d'email. Merci Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? You can use this email template if you like. Thanks ------------------------------------------------------------------------------------------------------------------------------------------------------- ------ INTEROP-VLab Communication (partner of the FITMAN project) [cid:image002.png at 01CEE13F.8B37EB10] Invitation to the FITMAN FI-PPP Phase III Webinar (Nov. 19TH, 2013) And to Specific Enablers Webinars (see schedule below) Free online webinars We would like to invite you to join the FITMAN Phase III webinar on Tuesday 19 November 2013 at 12pm CET. The webinar is for FI-PPP Phase III participants who wish to build on FITMAN work and/or address ICT in manufacturing. It will provide information about FITMAN deliverables, methodologies for SME and web entrepreneur engagement, and other Phase III related information. For a detailed agenda, please click here For registration link, click here For more information on the FITMAN Specific Enablers benefits and functionalities, you are invited to join the series of webinars scheduled over the coming days (see programme below). Programme of FITMAN Specific Enablers webinars Tittle Presenter/contact Date/time Secure Event Management Salvatore Piccione (TXT E-Solutions) 15-11-2013 - 11h CET Unstructured and Social Data Analytics Fenareti Lampathaki (National Technical University of Athens) 25-11-2013- 11h CET Data Interoperability Platform Services Michele Sesana (TXT E-Solutions) 19-11-2013- 11h CET Collaborative Business Process Management Mauro Isaja (Engineering) 21-11-2013- 11h CET Metadata and Ontologies Semantic Matching Sotiris Kousouris (National Technical University of Athens) 22-11-2013- 11h CET Supply Chain & Business Ecosystem Apps Michele Sesana (TXT E-Solutions) 22-11-2013 - 15h CET Shopfloor Data Collection Sudeep Ghimire (UNINOVA) 27-11-2013- 11h CET Collaborative Assets Management Mauro Isaja (Engineering) 05-12-2013- 11h CET Click on the title to view the full description and registration link. If you are interested in engaging with Phase III in the area of ICT for Manufacturing, please book that date on your calendar and participate in the FITMAN Phase III webinar! You can send any question about the FITMAN Phase III webinar to: fitman-phase-iii-info at txtgroup.com Best regards, Cathy LIEU, INTEROP-VLab Assistant Manager in charge of the communication www.interop-vlab.eu [logo1sansfond7pct] This email is sent by the INTEROP-VLab Management. If you do not wish to receive message from INTEROP-VLab, please write to cathy.lieu at interop-vlab.eu to be unsubscribed of the mailing list. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 10766 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 2153 bytes Desc: image003.gif URL: From thomas.bohnert at zhaw.ch Fri Nov 15 08:08:59 2013 From: thomas.bohnert at zhaw.ch (Thomas Michael Bohnert) Date: Fri, 15 Nov 2013 08:08:59 +0100 Subject: [Fiware-iot] [Fiware-wpl] URGENT: LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III In-Reply-To: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <27266_1384498750_5285C63E_27266_376_1_976A65C5A08ADF49B9A8523F7F81925C149038@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <1384499339.2977.0.camel@Hjalmar> Thierry, We'll make this an action item for the next AB meeting. Cheers, Thomas -- Thomas Michael Bohnert www: www.cloudcomp.ch www: http://tmb.nginet.de twitter: tmbohnert On Fri, 2013-11-15 at 06:59 +0000, thierry.nagellen at orange.com wrote: > Dear all, > > I do not know if you have heard about this FITMAN webinar. Going quickly through the short description of each module it seems that as FI-Ware we must attend some of them because they propose some Specific Enablers which are close to some Generic Enablers: typically for my part (IoT) the ShopFloor DATA Collection could be replace by some IoT GEs but we could be also interested by the one working on Semantic interface. > > Juanjo, Stefano (as member of the Architecture Board because I could not attend the last meeting): do we have some clear architecture picture from FITMAN explaining how their Specific Enablers would interact/use some Generic Enablers? > > BR > Thierry > > De : Celine Vergne [mailto:celine.vergne at interop-vlab.eu] > Envoy? : jeudi 14 novembre 2013 14:58 > ? : dissemination at interop-vlab.eu > Objet : LAST REMINDER: Invitation to FITMAN Webinars on FI PPP Phase III > > > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > ------ > > > > Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son > > carnet d'adresses. Vous pouvez le faire en utilisant ce modele d'email. Merci > > > > > > Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? > > You can use this email template if you like. Thanks > > > > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > ------ > > > > INTEROP-VLab Communication (partner of the FITMAN project) > > [cid:image002.png at 01CEE13F.8B37EB10] > > Invitation to the FITMAN FI-PPP Phase III Webinar (Nov. 19TH, 2013) > And to Specific Enablers Webinars (see schedule below) > Free online webinars > > We would like to invite you to join the FITMAN Phase III webinar on Tuesday 19 November 2013 at 12pm CET. The webinar is for FI-PPP Phase III participants who wish to build on FITMAN work and/or address ICT in manufacturing. It will provide information about FITMAN deliverables, methodologies for SME and web entrepreneur engagement, and other Phase III related information. > For a detailed agenda, please click here > For registration link, click here > > For more information on the FITMAN Specific Enablers benefits and functionalities, you are invited to join the series of webinars scheduled over the coming days (see programme below). > > Programme of FITMAN Specific Enablers webinars > > Tittle > > Presenter/contact > > Date/time > > Secure Event Management > > Salvatore Piccione (TXT E-Solutions) > > 15-11-2013 - 11h CET > > Unstructured and Social Data Analytics > > Fenareti Lampathaki (National Technical University of Athens) > > 25-11-2013- 11h CET > > Data Interoperability Platform Services > > Michele Sesana (TXT E-Solutions) > > 19-11-2013- 11h CET > > Collaborative Business Process Management > > Mauro Isaja (Engineering) > > 21-11-2013- 11h CET > > Metadata and Ontologies Semantic Matching > > Sotiris Kousouris (National Technical University of Athens) > > 22-11-2013- 11h CET > > Supply Chain & Business Ecosystem Apps > > Michele Sesana (TXT E-Solutions) > > 22-11-2013 - 15h CET > > Shopfloor Data Collection > > Sudeep Ghimire (UNINOVA) > > 27-11-2013- 11h CET > > Collaborative Assets Management > > Mauro Isaja (Engineering) > > 05-12-2013- 11h CET > > > Click on the title to view the full description and registration link. > > If you are interested in engaging with Phase III in the area of ICT for Manufacturing, please book that date on your calendar and participate in the FITMAN Phase III webinar! > You can send any question about the FITMAN Phase III webinar to: fitman-phase-iii-info at txtgroup.com > > Best regards, > > Cathy LIEU, INTEROP-VLab > Assistant Manager > in charge of the communication > www.interop-vlab.eu > [logo1sansfond7pct] > This email is sent by the INTEROP-VLab Management. If you do not wish to receive message from INTEROP-VLab, please write to cathy.lieu at interop-vlab.eu to be unsubscribed of the mailing list. > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-wpl From ralli at tid.es Fri Nov 15 09:45:27 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Fri, 15 Nov 2013 08:45:27 +0000 Subject: [Fiware-iot] BE Dev Man GE/GEi totally updated in the IoT Tracker Message-ID: Thierry, All, As stated in our conf.call this week, we have finalized our work to give visibility to all the activities/tasks related to this GE/Gei. Totally, we've created 80 tickets with activities spread since April 2013 (R2.3.1) till R3.3 plan. All this is explained in the below-linked document that we use within the IDAS team to keep track of all those tasks: https://docs.google.com/document/d/1eC64ISKLV3AJJZ6s042xMUFb8FX_pGDoh_LmQaVuOu8/edit Basically, the timeline that we will share with the EC to explain ourselves is the following: - April-May: As per Nokia withdrawal a decision is taken to replace the Gei and the partners working out the overall GE specifications/API - Jun-Jul: A new architecture is envisaged and discussed in Paris meeting for the whole chapter and particularly for this GE (architecture+APIs+implementation). Development tasks for this GEi kick off - Aug-Sep-Oct: Focus on development, update related wiki sections, update manuals (users, programmers, testing ?) and take the Gei to the Hackathons. Also the catalogue entry is generated. - Nov: Update all related tracker entries so the GE7GEi are fully synchronized with the FI-WARE agile methodology. I hope with all this we get back to track fully regarding this GE from a management standpoint. 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 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 thierry.nagellen at orange.com Tue Nov 19 17:21:57 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 19 Nov 2013 16:21:57 +0000 Subject: [Fiware-iot] tomorrow: IoT weekly meeting Message-ID: <27734_1384878118_528B9026_27734_19972_1_976A65C5A08ADF49B9A8523F7F81925C149F78@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Nov 20 11:00:08 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 20 Nov 2013 10:00:08 +0000 Subject: [Fiware-iot] Integration Plan - access Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Wed Nov 20 18:19:20 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 20 Nov 2013 18:19:20 +0100 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> Message-ID: <528CEF18.8020303@tid.es> Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Wed Nov 20 19:27:19 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Wed, 20 Nov 2013 18:27:19 +0000 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <528CEF18.8020303@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Wed Nov 20 20:21:24 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 20 Nov 2013 20:21:24 +0100 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> Message-ID: <528D0BB4.3000603@tid.es> Dear Tarek, As far as I understand, the inputs in the test steps are either produced by a GEi (as a consequence of some stimuli) or by simple scripts or testing tools (e.g. curl, RESTClient, etc.) running or not in the testbed (as least for TID's GEis, the mentioned ports will remain open from any IP). So probably I'm more confused than you, as I don't know what do you mean by "test client"... ;) Best regards, ------ Ferm?n El 20/11/2013 19:27, t.elsaleh at surrey.ac.uk escribi?: Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.artusio at orange.com Thu Nov 21 08:29:13 2013 From: laurent.artusio at orange.com (laurent.artusio at orange.com) Date: Thu, 21 Nov 2013 07:29:13 +0000 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <528D0BB4.3000603@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> <528D0BB4.3000603@tid.es> Message-ID: <30628_1385018954_528DB64A_30628_10978_1_ADCB0720D5A0114384E4F982EFCDBAA910F44218@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi, Here is the Data Handling main URL, which runs on TCP port 80: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2 For queryContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/queryContext For updateContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/updateContext For registerContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI9/registerContext Best regards, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : mercredi 20 novembre 2013 20:21 ? : t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Integration Plan - access Dear Tarek, As far as I understand, the inputs in the test steps are either produced by a GEi (as a consequence of some stimuli) or by simple scripts or testing tools (e.g. curl, RESTClient, etc.) running or not in the testbed (as least for TID's GEis, the mentioned ports will remain open from any IP). So probably I'm more confused than you, as I don't know what do you mean by "test client"... ;) Best regards, ------ Ferm?n El 20/11/2013 19:27, t.elsaleh at surrey.ac.uk escribi?: Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurent.artusio at orange.com Thu Nov 21 08:38:45 2013 From: laurent.artusio at orange.com (laurent.artusio at orange.com) Date: Thu, 21 Nov 2013 07:38:45 +0000 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <30628_1385018954_528DB64A_30628_10978_1_ADCB0720D5A0114384E4F982EFCDBAA910F44218@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> <528D0BB4.3000603@tid.es> <30628_1385018954_528DB64A_30628_10978_1_ADCB0720D5A0114384E4F982EFCDBAA910F44218@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <22960_1385019526_528DB886_22960_18018_1_ADCB0720D5A0114384E4F982EFCDBAA910F45230@PEXCVZYM12.corporate.adroot.infra.ftgroup> And I add the testbed internal IP for Data Handling: For queryContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI10/queryContext For updateContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI10/updateContext For registerContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI9/registerContext BR, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de laurent.artusio at orange.com Envoy? : jeudi 21 novembre 2013 08:29 ? : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Integration Plan - access Hi, Here is the Data Handling main URL, which runs on TCP port 80: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2 For queryContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/queryContext For updateContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/updateContext For registerContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI9/registerContext Best regards, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : mercredi 20 novembre 2013 20:21 ? : t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Integration Plan - access Dear Tarek, As far as I understand, the inputs in the test steps are either produced by a GEi (as a consequence of some stimuli) or by simple scripts or testing tools (e.g. curl, RESTClient, etc.) running or not in the testbed (as least for TID's GEis, the mentioned ports will remain open from any IP). So probably I'm more confused than you, as I don't know what do you mean by "test client"... ;) Best regards, ------ Ferm?n El 20/11/2013 19:27, t.elsaleh at surrey.ac.uk escribi?: Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.elsaleh at surrey.ac.uk Thu Nov 21 09:22:29 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 21 Nov 2013 08:22:29 +0000 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <528D0BB4.3000603@tid.es> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> <528D0BB4.3000603@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F4266@EXMB05CMS.surrey.ac.uk> Sorry, by test client, I mean the GEi initiating a particular integration test. Best regards, Tarek From: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: 20 November 2013 19:21 To: Elsaleh T Mr (Electronic Eng); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Dear Tarek, As far as I understand, the inputs in the test steps are either produced by a GEi (as a consequence of some stimuli) or by simple scripts or testing tools (e.g. curl, RESTClient, etc.) running or not in the testbed (as least for TID's GEis, the mentioned ports will remain open from any IP). So probably I'm more confused than you, as I don't know what do you mean by "test client"... ;) Best regards, ------ Ferm?n El 20/11/2013 19:27, t.elsaleh at surrey.ac.uk escribi?: Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 Thu Nov 21 10:05:51 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 21 Nov 2013 09:05:51 +0000 Subject: [Fiware-iot] Integration Plan - access In-Reply-To: <22960_1385019526_528DB886_22960_18018_1_ADCB0720D5A0114384E4F982EFCDBAA910F45230@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F41B9@EXMB05CMS.surrey.ac.uk> <528CEF18.8020303@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F425F@EXMB05CMS.surrey.ac.uk> <528D0BB4.3000603@tid.es> <30628_1385018954_528DB64A_30628_10978_1_ADCB0720D5A0114384E4F982EFCDBAA910F44218@PEXCVZYM12.corporate.adroot.infra.ftgroup> <22960_1385019526_528DB886_22960_18018_1_ADCB0720D5A0114384E4F982EFCDBAA910F45230@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F426C@EXMB05CMS.surrey.ac.uk> Hello, For IoT Discovery: Convenience Operation: ? RegisterContext (Data Handling, Backend Device Mgmt): o POST - http://172.30.1.131:8080/ngsi9/contextEntities/Sensor1 ? DiscoverContext (IoT Broker): o GET - http://172.30.1.131:8080/ngsi9/contextEntities/Sensor1 Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of laurent.artusio at orange.com Sent: 21 November 2013 07:39 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access And I add the testbed internal IP for Data Handling: For queryContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI10/queryContext For updateContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI10/updateContext For registerContext requests: http://172.30.1.55/Esper4FastData-3.2.2/NGSI9/registerContext BR, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de laurent.artusio at orange.com Envoy? : jeudi 21 novembre 2013 08:29 ? : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Integration Plan - access Hi, Here is the Data Handling main URL, which runs on TCP port 80: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2 For queryContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/queryContext For updateContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI10/updateContext For registerContext requests: http://gwdatahdl2.testbed.fi-ware.eu/Esper4FastData-3.2.2/NGSI9/registerContext Best regards, Laurent De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ferm?n Gal?n M?rquez Envoy? : mercredi 20 novembre 2013 20:21 ? : t.elsaleh at surrey.ac.uk; fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Integration Plan - access Dear Tarek, As far as I understand, the inputs in the test steps are either produced by a GEi (as a consequence of some stimuli) or by simple scripts or testing tools (e.g. curl, RESTClient, etc.) running or not in the testbed (as least for TID's GEis, the mentioned ports will remain open from any IP). So probably I'm more confused than you, as I don't know what do you mean by "test client"... ;) Best regards, ------ Ferm?n El 20/11/2013 19:27, t.elsaleh at surrey.ac.uk escribi?: Thanks Fermin for the clarification. I got confused. I was thinking that the test client will be local to the partner, but actually the test client will run within the FI-PPP testbed. So basically we should follow what is in the Implementation Cockpit. Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ferm?n Gal?n M?rquez Sent: 20 November 2013 17:19 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Integration Plan - access Hi, In the case of TID's elements, these are the IPs and ports: * ContextBroker: orion-psb.testbed.fi-ware.eu:1026 * ConfMan: orion-cm.testbed.fi-ware.eu:1027 * IDAS: 130.206.82.130:1029 Best regards, ------ Ferm?n El 20/11/2013 11:00, t.elsaleh at surrey.ac.uk escribi?: Hello All, I assume we will conduct the tests via the IP addresses that we defined in the Testbed V2 Operations Cockpit. 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: 19 November 2013 16:22 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] tomorrow: IoT weekly meeting Hi all, Here is the link for the minutes tomorrow. An urgent point: integration test for the validation report (WP10) https://docs.google.com/document/d/1W1vugISGWk32IqWt0l48vU92hC2wYN4ivX8hABPIlO0/edit Talk to you tomorrow Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Thu Nov 21 16:49:07 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 21 Nov 2013 16:49:07 +0100 Subject: [Fiware-iot] Today integration session results (TID's components) Message-ID: <528E2B73.5080306@tid.es> Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoTIntegration-TID.zip Type: application/x-zip-compressed Size: 1162250 bytes Desc: not available URL: From Salvatore.Longo at neclab.eu Thu Nov 21 17:30:01 2013 From: Salvatore.Longo at neclab.eu (Salvatore Longo) Date: Thu, 21 Nov 2013 16:30:01 +0000 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <528E2B73.5080306@tid.es> References: <528E2B73.5080306@tid.es> Message-ID: <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ID3.jpg Type: image/jpeg Size: 203104 bytes Desc: ID3.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ID4.jpg Type: image/jpeg Size: 294398 bytes Desc: ID4.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ID5_idas.jpg Type: image/jpeg Size: 91615 bytes Desc: ID5_idas.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ID5_dataHandling.jpg Type: image/jpeg Size: 172726 bytes Desc: ID5_dataHandling.jpg URL: From t.elsaleh at surrey.ac.uk Thu Nov 21 18:03:09 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Thu, 21 Nov 2013 17:03:09 +0000 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> References: <528E2B73.5080306@tid.es> <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F42F8@EXMB05CMS.surrey.ac.uk> Hello Fermin, Laurent and Salvatore, Sorry for today's confusion. Look like I'm focusing more on the "added value" services than the basics. :) 1. Tests I6 and I8 (Data Handling / Backend Device Mgmt) Ok, so now I have added the Standard Operation for RegisterContext. This means tests I6 and I8 can be done. ? http://172.30.1.131:8080/ngsi9/registerContext Please go ahead with the tests when you are ready. If you think we should be connected during the test, then let me know you preferable channel. If Skype, my ID is "elsaleh_74". Also it would be useful to send me a copy of what you registered. 2. Test I7: I'm still working on this Salvatore, and will try get back to you early tomorrow. Just a quick question (maybe Fermin can help), when you provide multiple attributes in the discovery request, do you expect an entity with all the attributes (AND), or an entity that has any of these attributes (OR)? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Salvatore Longo Sent: 21 November 2013 16:30 To: Ferm?n Gal?n M?rquez Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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 t.elsaleh at surrey.ac.uk Fri Nov 22 13:46:21 2013 From: t.elsaleh at surrey.ac.uk (t.elsaleh at surrey.ac.uk) Date: Fri, 22 Nov 2013 12:46:21 +0000 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F42F8@EXMB05CMS.surrey.ac.uk> References: <528E2B73.5080306@tid.es> <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F42F8@EXMB05CMS.surrey.ac.uk> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F4396@EXMB05CMS.surrey.ac.uk> Hello Salvatore, I have enabled the Standard Operation "discoverContextAvailability", and I believe test I7 is ready for testing. Please use: http://172.30.1.131:8080/ngsi9/discoverContextAvailability I haven't heard back from either Laurent or Fermin, which probably indicates that they are busy...so I guess we need to wait for them. I hope we can still do the tests. I hope in future when it comes to integration tests, we should be ready to expect issues, errors unaccounted for, misunderstanding etc. and work around that. But anyway, I do apologize from my part. >From my opinion I don't think we need to hang around on the phone. Can still use email. The instances are deployed and ready to be tested, aren't they? If there is an error then please just copy and paste it in an email, then report it. That's what I did with the testbed team when it came to sanity checks, and that went well. But if you still want to contact me directly via IM/VoIP/Phone, please let me know. Just to note, I will be unavailable today between 2-4pm (European time). Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk Sent: 21 November 2013 17:03 To: Salvatore.Longo at neclab.eu; fermin at tid.es; laurent.artusio at orange.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Hello Fermin, Laurent and Salvatore, Sorry for today's confusion. Look like I'm focusing more on the "added value" services than the basics. :) 1. Tests I6 and I8 (Data Handling / Backend Device Mgmt) Ok, so now I have added the Standard Operation for RegisterContext. This means tests I6 and I8 can be done. ? http://172.30.1.131:8080/ngsi9/registerContext Please go ahead with the tests when you are ready. If you think we should be connected during the test, then let me know you preferable channel. If Skype, my ID is "elsaleh_74". Also it would be useful to send me a copy of what you registered. 2. Test I7: I'm still working on this Salvatore, and will try get back to you early tomorrow. Just a quick question (maybe Fermin can help), when you provide multiple attributes in the discovery request, do you expect an entity with all the attributes (AND), or an entity that has any of these attributes (OR)? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Salvatore Longo Sent: 21 November 2013 16:30 To: Ferm?n Gal?n M?rquez Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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 laurent.artusio at orange.com Fri Nov 22 15:15:05 2013 From: laurent.artusio at orange.com (laurent.artusio at orange.com) Date: Fri, 22 Nov 2013 14:15:05 +0000 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F4396@EXMB05CMS.surrey.ac.uk> References: <528E2B73.5080306@tid.es> <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F42F8@EXMB05CMS.surrey.ac.uk> <2AAC0B6FF99A064C853BFB1C9295F3CCB9843F4396@EXMB05CMS.surrey.ac.uk> Message-ID: <8457_1385129706_528F66EA_8457_172_1_ADCB0720D5A0114384E4F982EFCDBAA910F45617@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi Tarek, I'm sorry I did not pay attention to your mail, as I'm also working on a separate network with no email access. I will be available until 7pm. Let me know when you want to perform additional tests. Best regards, Laurent +33.492.945.239 De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk] Envoy? : vendredi 22 novembre 2013 13:46 ? : Salvatore.Longo at neclab.eu; fermin at tid.es; ARTUSIO Laurent IMT/OLPS Cc : fiware-iot at lists.fi-ware.eu Objet : RE: [Fiware-iot] Today integration session results (TID's components) Hello Salvatore, I have enabled the Standard Operation "discoverContextAvailability", and I believe test I7 is ready for testing. Please use: http://172.30.1.131:8080/ngsi9/discoverContextAvailability I haven't heard back from either Laurent or Fermin, which probably indicates that they are busy...so I guess we need to wait for them. I hope we can still do the tests. I hope in future when it comes to integration tests, we should be ready to expect issues, errors unaccounted for, misunderstanding etc. and work around that. But anyway, I do apologize from my part. >From my opinion I don't think we need to hang around on the phone. Can still use email. The instances are deployed and ready to be tested, aren't they? If there is an error then please just copy and paste it in an email, then report it. That's what I did with the testbed team when it came to sanity checks, and that went well. But if you still want to contact me directly via IM/VoIP/Phone, please let me know. Just to note, I will be unavailable today between 2-4pm (European time). Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of t.elsaleh at surrey.ac.uk Sent: 21 November 2013 17:03 To: Salvatore.Longo at neclab.eu; fermin at tid.es; laurent.artusio at orange.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Hello Fermin, Laurent and Salvatore, Sorry for today's confusion. Look like I'm focusing more on the "added value" services than the basics. :) 1. Tests I6 and I8 (Data Handling / Backend Device Mgmt) Ok, so now I have added the Standard Operation for RegisterContext. This means tests I6 and I8 can be done. ? http://172.30.1.131:8080/ngsi9/registerContext Please go ahead with the tests when you are ready. If you think we should be connected during the test, then let me know you preferable channel. If Skype, my ID is "elsaleh_74". Also it would be useful to send me a copy of what you registered. 2. Test I7: I'm still working on this Salvatore, and will try get back to you early tomorrow. Just a quick question (maybe Fermin can help), when you provide multiple attributes in the discovery request, do you expect an entity with all the attributes (AND), or an entity that has any of these attributes (OR)? Best regards, Tarek From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Salvatore Longo Sent: 21 November 2013 16:30 To: Ferm?n Gal?n M?rquez Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Today integration session results (TID's components) Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin at tid.es Mon Nov 25 10:53:00 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 25 Nov 2013 10:53:00 +0100 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> References: <528E2B73.5080306@tid.es> <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> Message-ID: <52931DFC.6090604@tid.es> Hi, Both Salvatore's and Tarek's contributions added to the .zip, which has been uploaded to docman at: https://forge.fi-ware.eu/docman/view.php/11/3144/IntegrationIoT_2013-11-25.zip In addition, wiki page has been updated (a link to the .zip files has been included). Thanks! Best regards, ------ Ferm?n El 21/11/2013 17:30, Salvatore Longo escribi?: Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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 Salvatore.Longo at neclab.eu Mon Nov 25 10:59:03 2013 From: Salvatore.Longo at neclab.eu (Salvatore Longo) Date: Mon, 25 Nov 2013 09:59:03 +0000 Subject: [Fiware-iot] Today integration session results (TID's components) In-Reply-To: <52931DFC.6090604@tid.es> References: <528E2B73.5080306@tid.es> <5DCCEFAAAAD37745A888BC14F42BF4A547302FA2@Hydra.office.hd> <52931DFC.6090604@tid.es> Message-ID: <5DCCEFAAAAD37745A888BC14F42BF4A5473041D7@Hydra.office.hd> Thanks. - 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Montag, 25. November 2013 10:53 To: Salvatore Longo; t.elsaleh at surrey.ac.uk Cc: fiware-iot at lists.fi-ware.eu Subject: Re: Today integration session results (TID's components) Hi, Both Salvatore's and Tarek's contributions added to the .zip, which has been uploaded to docman at: https://forge.fi-ware.eu/docman/view.php/11/3144/IntegrationIoT_2013-11-25.zip In addition, wiki page has been updated (a link to the .zip files has been included). Thanks! Best regards, ------ Ferm?n El 21/11/2013 17:30, Salvatore Longo escribi?: Dear Fermin, Attached there are the screenshot that I did for the ID3, ID4 and ID5 cases. Could you please add to the zip file and attach it to the wiki page. Thanks a lot. 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: Ferm?n Gal?n M?rquez [mailto:fermin at tid.es] Sent: Donnerstag, 21. November 2013 16:49 To: Salvatore Longo Cc: fiware-iot at lists.fi-ware.eu Subject: Today integration session results (TID's components) Hi, As discussed this morning, please find attached (in the .zip) the captures we have gathered related with TID's elements both in screen snapshots and text files (the later extracted from GEis text logs) during today's integration session, using the following naming convention: [BDM-|DH-]ID--[In|Out].[txt.png] The "BDM-" or "DH-" prefix is used only for test cases in which there was different XMLs for Backend Device Management GEi (BDM) or Data Handling (DH) GEi (actually: ID1, ID4 and ID5). Some additional remarks: 1. The reference for test IDs and steps numbers are in the wiki page at https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2 2. As far as I know, ID6 to ID10 wasn't executed today (ID6 to ID8 not executed given that IoTDiscovery GEi is not supporting the required API calls for integration). 3. We haven't recorded the DH-ID1-1-Out case. Laurent, could you provide it, please? 4. We haven't recorded any ID3 case. Salvatore, could you provide these, please? 5. We haven't recorded the the [BDM-|DH-]ID4-1-Out cases. Salvatore, could you provide these, please? 6. We have edited the test cases in the wiki in which we have participated (in particular ID1, ID2, ID4 and ID5) to update test information at the start of each section (Date, status, etc.) and references to the final XMLs used for "Input Data" and "Actual result". Given that XML has problems to be correctly rendered in this wiki (anybody is able to solve it?), we have opted by citing XML from a (currently not existing) IoTIntegration.zip file (that could be uploaded to docman or passed directly to the person in charge of testing in FI-WARE). * This "IoTIntegration.zip" files doesn't exist yet, but I volunteer to create, upload and link it from the wiki if the other partners provide me the needed screen snapshots for that (bullets 3, 4 and 5 above) (We = TID above) I'm CCing the whole chapter, as I think integration is a general topic. 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 Salvatore.Longo at neclab.eu Tue Nov 26 13:40:06 2013 From: Salvatore.Longo at neclab.eu (Salvatore Longo) Date: Tue, 26 Nov 2013 12:40:06 +0000 Subject: [Fiware-iot] IoT Integration Deliverable Message-ID: <5DCCEFAAAAD37745A888BC14F42BF4A5473044C5@Hydra.office.hd> Dear Thierry, After the WP10 phc I started to change the Integration deliverable for the Tests where the IoT Broker was involved. Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2#TEST_ID:_I3 I think for the overall Integration tests still the Test 9 and Test 10 are missed. Please have look to it and let me know your feedback. Best Regards, - 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 ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Tue Nov 26 14:27:07 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 26 Nov 2013 13:27:07 +0000 Subject: [Fiware-iot] IoT Integration Deliverable In-Reply-To: <5DCCEFAAAAD37745A888BC14F42BF4A5473044C5@Hydra.office.hd> References: <5DCCEFAAAAD37745A888BC14F42BF4A5473044C5@Hydra.office.hd> Message-ID: <9474_1385472428_5294A1AC_9474_877_1_976A65C5A08ADF49B9A8523F7F81925C14B532@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Salvatore, For me it seems ok regarding presentation and should fit at the end in a deliverable. Just a minor point in ID7 in the response file, you have a large space in a value chain I was not able to correct (provid..............................ing...) But I think we can fulfil the other tests in the same way. Thanks BR Thierry De : Salvatore Longo [mailto:Salvatore.Longo at neclab.eu] Envoy? : mardi 26 novembre 2013 13:40 ? : NAGELLEN Thierry IMT/OLPS Cc : fiware-iot at lists.fi-ware.eu Objet : IoT Integration Deliverable Dear Thierry, After the WP10 phc I started to change the Integration deliverable for the Tests where the IoT Broker was involved. Link: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Internet_Of_Things_Service_Enablement_-_V2#TEST_ID:_I3 I think for the overall Integration tests still the Test 9 and Test 10 are missed. Please have look to it and let me know your feedback. Best Regards, - 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 ________________________________ _________________________________________________________________________________________________________________________ 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 Nov 27 07:44:29 2013 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 27 Nov 2013 06:44:29 +0000 Subject: [Fiware-iot] IoT weekly meeting cancelled today Message-ID: <12602_1385534669_529594CD_12602_9178_1_976A65C5A08ADF49B9A8523F7F81925C14B8B2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Dear all, Because of an urgent meeting with top level management in Orange, I'm not able to organize the IoT weekly meeting. I apologize for the short delay. Best regards, 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 Thu Nov 28 11:40:39 2013 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Thu, 28 Nov 2013 10:40:39 +0000 Subject: [Fiware-iot] FW: Roadmap of IoT - Easy things to solve in the Wiki - I need your action on this In-Reply-To: <5295D370.9070600@tid.es> Message-ID: Dear Colleagues, My colleague Miguel pointed out some mistakes in our Wiki (see his mail below). Wiki is at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services I solved myself the first issue (brackets) and the second issue ("3.x") for my GE. I need the following from your side: - "Conf.Man": Solve the "3x" issue. - "Gateway Device Management GE": Solve the "3x" issue. - "Gateway Data Handling GE": Solve the "3x" issue. - "Gateway Protocol Adapter GE": Solve the "3x" issue. - "Backend IoT Business Process Execution GE": Solve the Broken link plus the "3.x" issue. Please, do confirm in the list once you update this. Thanks for your collaboration! Cheers, De: MIGUEL CARRILLO PACHECO > Fecha: mi?rcoles, 27 de noviembre de 2013 12:11 Para: "thierry.nagellen at orange.com" > CC: Carlos Ralli Ucendo >, JUAN JOSE HIERRO SUREDA >, MANUEL ESCRICHE VICENTE > Asunto: Roadmap of IoT Hi, This needs a bit of touching up: * http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services To be more precise: * Please fix the extra brackets in the GE names * "Release 3.x" and "Other Releases 3.X " is not easy to interpret for me - so I am sure than an external reader will not understand it! - please fix everywhere, it is on any GEs * Backend IoT Business Process Execution GE is a broken link Thanks! 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: