From sergg at tid.es Tue Apr 2 17:39:48 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 02 Apr 2013 15:39:48 +0000 Subject: [Fiware-data] IoT Chapter architecture review Message-ID: <03BE306058976141B4883174DF62D54D5273FF15@EX10-MB2-MAD.hi.inet> Dear all, As I advanced last week, we have to make the second peer review of the IoT chapter architecture. Attending the volunteers and previous reviewers, I have assigned the following reviews: Sergio (TID) Common sections Sergio (TID, not delivered yet by NSN) FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker Boris (TI) FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement.split.ConfMan Mauricio (ATOS) FIWARE.ArchitectureDescription.IoT.Backend.DiscoveryEngine Francisco (TID) FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement Francisco (TID FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement Peter Amon (SIEMENS) FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling Fano (Orange) FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter This task should have started last Wednesday and should finish tomorrow. Therefore, if we finish this week, it would be a good performance. You can find the document at: https://forge.fi-ware.eu/docman/view.php/27/2012/D232_WP5_IoT_Generated_2013-04-01.docx Just download the document, add the changes and comments on track mode, and send it back to me so that I can upload it and notify. Best Regards, Sergio -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Wed Apr 3 19:49:25 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 03 Apr 2013 17:49:25 +0000 Subject: [Fiware-data] Reminder Message-ID: <03BE306058976141B4883174DF62D54D52740627@EX10-MB2-MAD.hi.inet> Dear partners, Just to remind you that this week we have the PPP architects meeting in Madrid and tomorrow there will not be WP6 call . Best Regards, Sergio -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Fri Apr 5 23:29:49 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Fri, 05 Apr 2013 21:29:49 +0000 Subject: [Fiware-data] Second review of comments Message-ID: <03BE306058976141B4883174DF62D54D8656C102@EX10-MB1-MAD.hi.inet> Dear partners, You can find the reviews of the Architecture of the deliverables in the cockpit page [1]. For your convenience, I copy the table below. A couple of the GEs are still missing. Given that the deadline for this delivery is next Friday, and I need to generate the document, please update the wiki pages before Thursday 11th EOB and let me know when you're done. Best Regards, Sergio Data Chapter Chapter page: Andreas (SAP) https://forge.fi-ware.eu/docman/view.php/27/2032/D232_WP6_R2_Chapter.docx Publish/Subscribe Broker https://forge.fi-ware.eu/docman/view.php/27/2051/D232_WP6_v3_generated_review_pub_sub_context_brk_GE_UPM.docx Complex Event Processing https://forge.fi-ware.eu/docman/view.php/27/2047/D232_WP6_v3_generated_ComplexEventProcessing_ECP_ReviewedByAtos.docx BigData Analysis https://forge.fi-ware.eu/docman/view.php/27/2056/D232_WP6_v2_generated+-+BigData+Review.docx Compressed Domain Video Analysis https://forge.fi-ware.eu/docman/view.php/27/2033/D232_WP6_R2_CompressedDomainVideo.docx Query Broker THALES Meta-data Pre-processing Horst/Andreas (DT) Location Platform https://forge.fi-ware.eu/docman/view.php/27/2009/D232_WP6_v3_TI_Data_Location_Review_28Mar.docx Semantic Application Support https://forge.fi-ware.eu/docman/view.php/27/2038/D232_WP6_v3_generated_SWAS-GE_Review_UPM.docx Semantic Annotation Joaquin (ATOS) https://forge.fi-ware.eu/docman/view.php/27/2042/D232_WP6_v3_generated_SemanticAnnotationByAtos.docx Rafael (UPM) has also reviewed this GE by mistake :D https://forge.fi-ware.eu/docman/view.php/27/2036/D232_WP6_v3_generated_SemanticAnnotationGE_Review_UPM.docx [1] https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Tue Apr 9 11:38:19 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 09 Apr 2013 09:38:19 +0000 Subject: [Fiware-data] FW: [Fiware-wpa] AP from yesterday: putting the links on the private wiki In-Reply-To: <5163CACE.2030002@tid.es> References: <5163CACE.2030002@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D8657C67A@EX10-MB2-MAD.hi.inet> Dear all, I forward you Miguel's request to add the proper links to the manuals we have to deliver by the 22nd. So please go to the following pages and add the proper link to the page where you're going to edit them, following his instructions below. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.3.2_FIWARE_Installation_and_Administration_Guide%22_WP6_Data/Context_Contribution https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.4.2_FIWARE_User_and_Programmers_Guide%22_WP6_Data/Context_Contribution https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.5.2_FIWARE_Unit_Testing_Plan_and_Report%22_WP6_Data/Context_Contribution Manuel & Miguel will check it tomorrow, so try to do it along today. Apologies for the haste. If you have any doubt, please let me know. Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Tuesday, April 09, 2013 10:01 AM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] AP from yesterday: putting the links on the private wiki Dear all, I see very little activity in the WP lists and we have little time. Yesterday we urged you to make the wiki links of 3 deliverables point at the place where they will edit them. Please instruct your teams to go to * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 and make them point their links to : * the place where they are editing the 3 documents (in principle, the private wiki) * or alternatively ... if they have not started, point at the place where they will edit the 3 documents If the page is blank because they have not started, put a note there with an "ongoing work" or someting. If we point at a blank page I will never know if it is intentional and this is the future space for the page or that the partner did not update the link! If there are particular circumstances why the doc is not going to be edited on the wiki (very exceptional case), the page must not remain blank. We need an explanatory note there to save us a check with the GE owner. The reason is that there are 40 GEs approximately, and 3 manuals. So 120 checks is too much for anyone if not properly organized. Tomorrow Manuel and myself will start our review of this and will assess it chapter by chapter. I enclose the general guidelines as a reminder. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: [Fiware] Guidelines for Release 2 Date: Thu, 28 Mar 2013 02:24:26 +0100 Size: 12961 URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sergg at tid.es Tue Apr 9 11:38:46 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 09 Apr 2013 09:38:46 +0000 Subject: [Fiware-data] WP6 Weekly call Message-ID: <03BE306058976141B4883174DF62D54D8657C69D@EX10-MB2-MAD.hi.inet> Hi all, This week we will keep the call on Thursday. Later on I will send the agenda + cooked minutes. Best Regards, Sergio. ________________________________ 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: not available Type: text/calendar Size: 1915 bytes Desc: not available URL: From sergg at tid.es Tue Apr 9 12:35:36 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 09 Apr 2013 10:35:36 +0000 Subject: [Fiware-data] FW: [Fiware-wpl] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B551FAF46@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B551FAF46@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D8657D7E9@EX10-MB2-MAD.hi.inet> Dear all, One of the topics for next Thursday call will be the status of the backlog. Please, proceed with the update of the tracker information of your user stories, and check that the items in the wiki page are consistent. Best Regards, Sergio. From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Wednesday, March 27, 2013 4:33 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpl] Backlog - Sprint transition: from S2.2.3-M23 to S2.3.1-M24 -Release 2.2 is finished - Release2.3 is opened Dear Partners, As you know we are about to finish Sprint 2.2.3 corresponding to M23. This sprint closes Release 2.2 Next 1.April (M24) Sprint 2.3.1 (1st sprint of Release 2.3) is opened. Please, update your backlog items accordingly. 1. Close the tickets you finished along M23 (if not already done) 2. Update tickets under execution not finished to belong to Sprint 2.3.1 3. Open those new tickets you have scheduled/planned for Release 2.3 Sprint 2.3.1 - be aware Release 2.3 is the last release available for the current reporting period. Let me stress agile is obsessed with delivery, so there's need to commit to the backlog content allocated for a sprint (step 3), then few tickets are moved to next sprint (step 2). During this month we have updated the wiki templates for the public backlog items, please, check your content is consistent. Now there're fewer fields than before but still some content is missing or not correct. The templates have categories, please, check your team is using them properly. If anything, please, let me know. Thanks for cooperation! 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sergg at tid.es Wed Apr 10 17:32:50 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 10 Apr 2013 15:32:50 +0000 Subject: [Fiware-data] New schedule for weekly meetings Message-ID: <03BE306058976141B4883174DF62D54D86582039@EX10-MB2-MAD.hi.inet> Dear all, As you know, the Kiara consortium has joined to the WP to provide a new GE. In order to accommodate their attendance, and also mine (so far I used to skip other meetings to attend WP6's one), I have created a survey to know your availability. I have define some slots of 90 minutes, even though it usually doesn't take so long. Please fill in the survey to see if we find a slot that will often fit everyone, i.e, leave unmarked only those slots that you know you will not be usually able to attend. We can talk about it tomorrow during the call. https://docs.google.com/forms/d/1GlduaoLgnz_5A5hE8kXbUWfo4cpGtFfk1LqRxVAOGyY/viewform Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Thu Apr 11 00:08:36 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 10 Apr 2013 22:08:36 +0000 Subject: [Fiware-data] FW: Review of WP6 links In-Reply-To: <5165A0A2.5060606@tid.es> References: <5163CACE.2030002@tid.es> <5165A0A2.5060606@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D8658226A@EX10-MB2-MAD.hi.inet> Dear partners, We have failed with this task. Let's try again. Fermin, Tali, Thomas, Mauricio, thanks, your're done. For all the others, I will simplify Miguel's request: 1. Go to the wiki pages of your GE. There are three, one for each deliverable. a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.3.2_FIWARE_Installation_and_Administration_Guide%22_WP6_Data/Context_Contribution b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.4.2_FIWARE_User_and_Programmers_Guide%22_WP6_Data/Context_Contribution c. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.5.2_FIWARE_Unit_Testing_Plan_and_Report%22_WP6_Data/Context_Contribution 2. Update the page: a. If you have the content, include it. b. If the content is somewhere else, change the link in the wiki page. (Links to the public wiki are not allowed (-> Tanguy)) c. If you plan to write the content there but in the following days, just add a comment "In progress, to be delivered in Release 2.2 " or 2.3 if that's the case. E.g.: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Publish_Subscribe_Context_Broker_-_Installation_and_Administration_Guide_R2 Tomorrow I will explain it during the WP6 call. Best Regards, Sergio. From: MIGUEL CARRILLO PACHECO Sent: Wednesday, April 10, 2013 7:26 PM To: SERGIO GARCIA GOMEZ Cc: MANUEL ESCRICHE VICENTE; MIGUEL CARRILLO PACHECO Subject: Review of WP6 links Dear WPL/WPA, Please find our review of the structure of the docs. The review is only for the links addresses , not for content, structure, etc. This will come on April, 22. By providing the links, you (and the GE owner) commit yourself to edit each doc there. Changes to (for instance) the public wiki will not be allowed. If there are justifiable changes, these must be communicated now (not on the 22nd). Note that if you proactively added the link and the GE owner did not do it himself, you must check with him/her! Deliverables provided on different links will not be reviewed until put on the right place on the private wiki. The situation is very bad and this is very simple to fix. Please push your partners and come back to us when this is complete. Please also be aware that the Location enabler is doing something wrong that would ultimately cause the rejection of their contributions should not they work on the right place. So please fix and come back to us. Best regards, Miguel El 09/04/2013 10:01, Miguel Carrillo escribi?: Dear all, I see very little activity in the WP lists and we have little time. Yesterday we urged you to make the wiki links of 3 deliverables point at the place where they will edit them. Please instruct your teams to go to * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 and make them point their links to : * the place where they are editing the 3 documents (in principle, the private wiki) * or alternatively ... if they have not started, point at the place where they will edit the 3 documents If the page is blank because they have not started, put a note there with an "ongoing work" or someting. If we point at a blank page I will never know if it is intentional and this is the future space for the page or that the partner did not update the link! If there are particular circumstances why the doc is not going to be edited on the wiki (very exceptional case), the page must not remain blank. We need an explanatory note there to save us a check with the GE owner. The reason is that there are 40 GEs approximately, and 3 manuals. So 120 checks is too much for anyone if not properly organized. Tomorrow Manuel and myself will start our review of this and will assess it chapter by chapter. I enclose the general guidelines as a reminder. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergg at tid.es Thu Apr 11 00:18:30 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 10 Apr 2013 22:18:30 +0000 Subject: [Fiware-data] Review of WP6 links References: <5163CACE.2030002@tid.es> <5165A0A2.5060606@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D8658229B@EX10-MB2-MAD.hi.inet> Sorry, I attach Miguel's report. From: /O=HI/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=SERGG On Behalf Of SERGIO GARCIA GOMEZ Sent: Thursday, April 11, 2013 12:09 AM To: fiware-data at lists.fi-ware.eu Subject: FW: Review of WP6 links Dear partners, We have failed with this task. Let's try again. Fermin, Tali, Thomas, Mauricio, thanks, your're done. For all the others, I will simplify Miguel's request: 1. Go to the wiki pages of your GE. There are three, one for each deliverable. a. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.3.2_FIWARE_Installation_and_Administration_Guide%22_WP6_Data/Context_Contribution b. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.4.2_FIWARE_User_and_Programmers_Guide%22_WP6_Data/Context_Contribution c. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI-WARE_Deliverable_%22D3-8.5.2_FIWARE_Unit_Testing_Plan_and_Report%22_WP6_Data/Context_Contribution 2. Update the page: a. If you have the content, include it. b. If the content is somewhere else, change the link in the wiki page. (Links to the public wiki are not allowed (-> Tanguy)) c. If you plan to write the content there but in the following days, just add a comment "In progress, to be delivered in Release 2.2 " or 2.3 if that's the case. E.g.: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Publish_Subscribe_Context_Broker_-_Installation_and_Administration_Guide_R2 Tomorrow I will explain it during the WP6 call. Best Regards, Sergio. From: MIGUEL CARRILLO PACHECO Sent: Wednesday, April 10, 2013 7:26 PM To: SERGIO GARCIA GOMEZ Cc: MANUEL ESCRICHE VICENTE; MIGUEL CARRILLO PACHECO Subject: Review of WP6 links Dear WPL/WPA, Please find our review of the structure of the docs. The review is only for the links addresses , not for content, structure, etc. This will come on April, 22. By providing the links, you (and the GE owner) commit yourself to edit each doc there. Changes to (for instance) the public wiki will not be allowed. If there are justifiable changes, these must be communicated now (not on the 22nd). Note that if you proactively added the link and the GE owner did not do it himself, you must check with him/her! Deliverables provided on different links will not be reviewed until put on the right place on the private wiki. The situation is very bad and this is very simple to fix. Please push your partners and come back to us when this is complete. Please also be aware that the Location enabler is doing something wrong that would ultimately cause the rejection of their contributions should not they work on the right place. So please fix and come back to us. Best regards, Miguel El 09/04/2013 10:01, Miguel Carrillo escribi?: Dear all, I see very little activity in the WP lists and we have little time. Yesterday we urged you to make the wiki links of 3 deliverables point at the place where they will edit them. Please instruct your teams to go to * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 and make them point their links to : * the place where they are editing the 3 documents (in principle, the private wiki) * or alternatively ... if they have not started, point at the place where they will edit the 3 documents If the page is blank because they have not started, put a note there with an "ongoing work" or someting. If we point at a blank page I will never know if it is intentional and this is the future space for the page or that the partner did not update the link! If there are particular circumstances why the doc is not going to be edited on the wiki (very exceptional case), the page must not remain blank. We need an explanatory note there to save us a check with the GE owner. The reason is that there are 40 GEs approximately, and 3 manuals. So 120 checks is too much for anyone if not properly organized. Tomorrow Manuel and myself will start our review of this and will assess it chapter by chapter. I enclose the general guidelines as a reminder. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Link_Status - WP6.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 9640 bytes Desc: Link_Status - WP6.xlsx URL: From sergg at tid.es Thu Apr 11 09:01:46 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Thu, 11 Apr 2013 07:01:46 +0000 Subject: [Fiware-data] WP6 Weekly call Message-ID: <03BE306058976141B4883174DF62D54D86582419@EX10-MB2-MAD.hi.inet> Hi, The link to the agenda+minutes: https://docs.google.com/document/d/1B6Tqy-GrN9Xro8KZd2-4cmhz84aAWCjLHKklsrNWS-o/edit Best Regards, Sergio ________________________________ 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: not available Type: text/calendar Size: 2652 bytes Desc: not available URL: From sergg at tid.es Mon Apr 15 16:16:00 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 14:16:00 +0000 Subject: [Fiware-data] Chapter architecture diagram Message-ID: <03BE306058976141B4883174DF62D54D86583B61@EX10-MB2-MAD.hi.inet> Dear partners, Following an peer review recommendation, I have created a new diagram for the whole chapter architecture. Please have a look and let me know your feedback. Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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: DataArchOverview.png Type: image/png Size: 144500 bytes Desc: DataArchOverview.png URL: From sergg at tid.es Mon Apr 15 16:25:26 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 14:25:26 +0000 Subject: [Fiware-data] New schedule for weekly meetings Message-ID: <03BE306058976141B4883174DF62D54D86583B88@EX10-MB2-MAD.hi.inet> Dear all, Most of you have reported that you could make it on Wednesday's at 15.00h. If, instead, you could make it on Wednesdays from 14.30h to 16.00h it would be an almost perfect match for everyone. Moreover, take into account that if we are punctual, it will not likely last until 16h. Please let me know whether you could attend at that time slot or not. Best Regards, Sergio. From: SERGIO GARCIA GOMEZ Sent: Wednesday, April 10, 2013 5:33 PM To: fiware-data at lists.fi-ware.eu Subject: New schedule for weekly meetings Dear all, As you know, the Kiara consortium has joined to the WP to provide a new GE. In order to accommodate their attendance, and also mine (so far I used to skip other meetings to attend WP6's one), I have created a survey to know your availability. I have define some slots of 90 minutes, even though it usually doesn't take so long. Please fill in the survey to see if we find a slot that will often fit everyone, i.e, leave unmarked only those slots that you know you will not be usually able to attend. We can talk about it tomorrow during the call. https://docs.google.com/forms/d/1GlduaoLgnz_5A5hE8kXbUWfo4cpGtFfk1LqRxVAOGyY/viewform Best Regards, Sergio. -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Mon Apr 15 17:18:58 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 15:18:58 +0000 Subject: [Fiware-data] FW: April software release status in WP6 In-Reply-To: <516C197F.4020507@tid.es> References: <516C197F.4020507@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D86583C30@EX10-MB2-MAD.hi.inet> Dear partners, The date for the delivery of software and documents is approaching (next Monday 22nd). Since you are aware and I have no further news, I assume that the activity is on track. Nevertheless, if there were any issue with the delivery of software and documents, please let me know ASAP to notify Miguel and Fermin. Best Regards, Sergio. From: FERMIN GALAN MARQUEZ Sent: Monday, April 15, 2013 5:15 PM To: SERGIO GARCIA GOMEZ Subject: April software release status in WP6 Hi, As far as I understand, the following GEis from WP6 are included in the April release: * Complex Event Processing * Compressed Domain Video Analysis * Media-enhanced Query Broker * Location Platform * Semantic Application Support * Meta-data Pre-processing * Middleware However, as far as I have checked in FI-WARE PPP Restricted Files (https://forge.fi-ware.eu/frs/?group_id=23) and FI-WARE Files (https://forge.fi-ware.eu/frs/?group_id=7), none of them has been yet released. Note that although there is a DATA-CEP package in https://forge.fi-ware.eu/frs/?group_id=23 it has "No releases". Given that the deadline for the release (April 22nd) is only one week ahead we wonder if you WP will be able to release them on time. As WPL/WPA, could you tell me the status of the releasing process within your WP, please? Thanks! Best regards, ------ Ferm?n PD. For your convenience, this is the link to the releasing procedure to follow: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware -------- Mensaje original -------- Asunto: [Fiware] Guidelines for Release 2 Fecha: Thu, 28 Mar 2013 02:24:26 +0100 De: Miguel Carrillo Responder a: Organizaci?n: Miguel Carrillo Para: fiware at lists.fi-ware.eu Dear all, Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message. This is strictly about : * Delivery of the Software itself * Installation and Administration manual * User and Programmer manual * Unit Testing Plan and report The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call. The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines is here(you need to this them before editing the deliverables): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Please note that: * The guidelines for the docs are basically the same ones as for Release 1 * The guidelines for the software delivery are completely different and were sent by Ferm?n to this list ages ago Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki. I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff). Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet) * This will ease the work of copying the definite versions of the manuals to their final destinations. * Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work. Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process. Best regards, Miguel ________________________________ 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 sergg at tid.es Mon Apr 15 17:22:36 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 15:22:36 +0000 Subject: [Fiware-data] FIWARE WP6 Call Message-ID: <03BE306058976141B4883174DF62D54D86583C79@EX10-MB2-MAD.hi.inet> Until we decide the new WP6 call slot, we'll keep the Thursdays at 10.30h. Best Regards, Sergio. ________________________________ 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: not available Type: text/calendar Size: 1874 bytes Desc: not available URL: From sergg at tid.es Mon Apr 15 17:43:17 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 15:43:17 +0000 Subject: [Fiware-data] FIWARE WP6 Call In-Reply-To: <03BE306058976141B4883174DF62D54D86583C79@EX10-MB2-MAD.hi.inet> References: <03BE306058976141B4883174DF62D54D86583C79@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86583D10@EX10-MB2-MAD.hi.inet> Sorry for the mess. It's me who cannot make it on Thursday. So, if I have enough Yes, it will be on Wednesday at 14.30h. -----Original Appointment----- From: SERGIO GARCIA GOMEZ Sent: Monday, April 15, 2013 5:23 PM To: fiware-data at lists.fi-ware.eu Subject: FIWARE WP6 Call When: jueves, 18 de abril de 2013 10:30-12:00 (UTC+01:00) Brussels, Copenhagen, Madrid, Paris. Where: Until we decide the new WP6 call slot, we'll keep the Thursdays at 10.30h. Best Regards, Sergio. ________________________________ 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 sergg at tid.es Mon Apr 15 17:46:26 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 15:46:26 +0000 Subject: [Fiware-data] Canceled: FIWARE WP6 Call Message-ID: <03BE306058976141B4883174DF62D54D86583D54@EX10-MB2-MAD.hi.inet> ________________________________ 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: not available Type: text/calendar Size: 1874 bytes Desc: not available URL: From boris.moltchanov at telecomitalia.it Mon Apr 15 19:30:48 2013 From: boris.moltchanov at telecomitalia.it (Moltchanov Boris) Date: Mon, 15 Apr 2013 19:30:48 +0200 Subject: [Fiware-data] Fwd: [Fiware-ngsi] how to represent associations References: <516C2721.9060604@tid.es> Message-ID: <3FD1A3EC-FBC9-4249-93FE-FAFFC285BB1E@telecomitalia.it> FYI ????: Ferm??n Gal??n M??rquez > ????????: 15 aprile 2013 18:13:21 CEST ????????: Raihan Ul-Islam > ??????????: "fiware-ngsi at lists.fi-ware.eu" >, "fiware-iot at lists.fi-ware.eu" > ????????: ??????????: [Fiware-ngsi] how to represent associations Dear Raihan, Thank you for your document update. Things are getting clearer in each new iteration :) I have some feedback/comments on the document. I think all them are minor ones. * In the picture in page 1 you use bidirectional arrows. I think it would be clearer to use uni-directional arrows (from source to target). * I understand that you propose "recursive" associations in both senses. I mean, your example only shows that for the "SOURCES" scope, but I understand that if the example also include an association foo1 -> sensor5, then a discoverContextAvailability on room2 will return both sensor5 and foo1, isnt't it? * I understand that the default scope (the one that a NGSI9 server instance will use if no is included in the ) is "NONE" to preserver interoperability among NGSI implementations. I mean, the normal behaviour that a client implement standard NGSI but not the association extension we are discussing correspond to the "NONE" case. Right? * In query case iteration 4 you use SOURCES as scope. However, according to the scope description (if I'm understanding correctly :) this should return the entities to which house_3/indoorTemperature is a source. An house_3/indoorTemperature is not a source of any entity in your example. Thus, I think this is an errata and that to be coherent you should change the document in either one of the following ways: * Fix the errata in page 1 in the case it works in the oposite way * Use TARGET scope in XML in iteration 4 * Define the association in the opposite way in registerContext (iteration 2) * I think a similar problem happens in update case. In addition, in order to set implementation expectations, I would like to know until which extend your use case needs the following: * Do you plan to use recursive associations? (query and update cases don't use such recursion) * Do you plan to use the ALL scope? (query and update cases don't use ALL scope) * Do you plan to use entity associations (i.e. not using the AttributeAssociationList in registerContext time or AttributeList in discoverContextAvailability with scopes TARGET or SOURCE)? (query and update cases always use attribute associations) Thanks! Best regards, ------ Ferm??n El 10/04/2013 9:59, Raihan Ul-Islam escribi??: Hi Fermin, Thanks for your feedback. Please find our view below respectively on the feedback ?? Associations are both ways. It is not only B to A. It can be also A to B. For better understanding I am adding an example of update scenario in the attached document. ?? About the second feedback. We are suggesting a ScopeType named ???IncludeAssociations???. Details about is also described in the attached document. Thanks Raihan ========================================================== Raihan Ul Islam Software Engineer NEC Europe Ltd. NEC Laboratories Europe Kurf??rsten-Anlage 36 D-69115 Heidelberg, Germany Phone: +49 (6221) 4342 - 256 Fax: +49 (6221) 4342 - 155 Mobile: +49 (0) 17679030334 EMail: raihan.ul-islam at neclab.eu http://www.netlab.nec.de ========================================================== | NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End Road, London, HA4 6QE, GB | Registered in England 2832014 From: Ferm??n Gal??n M??rquez [mailto:fermin at tid.es] Sent: 05 April 2013 16:06 To: Raihan Ul-Islam Cc: fiware-ngsi at lists.fi-ware.eu; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] how to represent associations Dear Raihan, Just to check if I'm understanding correctly your proposal (please, tell me otherwise): * Apart from registerContext and discoverContextAvailability it doesn't affect any other NGSI operation. * For registerContext, the NGSI server processing the request has to record the association expressed in the metadata * For discoverContextAvailability on entity/attribute B (assuming that A->B association has been previously created with registerContext), the NGSI server process the request of in the following way: * If B is not the end of an association, then B is returned (standard NGSI behavior) * If B is the end of an association, then the start of the association (A) is returned along with association information as metadata. Now, assuming that above is correct, this is our (TID's) feedback: * The usual semantics for an A->B association (e.g. a UML-like association) is that navigability goes from A to B. I mean, that from A I'm able to reach B. Thus, we think is a bit strange that a discoverContextAvailability on B results in A. In our opinion, the natural way should be in the opposite way, so the algorithm for discoverContextAvailability should be as follows: * For discoverContextAvailability on entity/attribute B (assuming that B->A association has been previously created with registerContext), the NGSI server process the request of in the following way: * If B is not the start of an association, then B is returned (standard NGSI behavior) * If B is the start of an association, then the end of the association (A) is returned along with association information as metadata. * How this would affect to the scenario is shown in the attached file, using Word change control. * An orthogonal problem (no matter if your original algorithm or our modified version in the previous bullet) is how to retrieve the "entity itself" when it is the end (in your original algorithm) or the end (in our modified version) of the association. For example, in your scenario, which discoverContextAvailability request (I mean, the XML) should the client send in the case it wants to get house_3 (not the associated sensor_5)? How to solve this problem? Maybe using the Scope field within discoverContextAvailability request Restriction? I hope this feedback be useful. Best regards, ------ Ferm??n El 02/04/2013 14:14, Raihan Ul-Islam escribi??: Hi All, For representing the association we are proposing a metadata type ???Association???. It will have two elements ???entityAssociation??? and ???attributeAssociationList???. The ???entityAssociation??? has two elements ???sourceEntityId??? and "targetEntityId". Usually devices will be used as ???sourceEntityId??? and things will be used as ???targetEntityId???. The elements ???sourceEntityId??? and "targetEntityId" are of ???EntityId??? type. But the attribute ???isPattern??? of ???EntityId??? will be omitted. Therefore, it will always have the value false. (As for example, if we consider the below scenario ???sourceEntityId??? will be he sensor5 and ???targetEntityId??? will be house_3.) The ???attributeAssociationList??? is a list of ???attributeAssociation??? element . It also has two elements. These are "sourceAttribute" and "targetAttribute". The elements are a type of ???xs:string???. The "sourceAttribute" and "targetAttribute" will contain the attribute of the corresponding ???sourceEntityId??? and "targetEntityId". We proposed two types of associations(https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/NGSI_association). These are entity and attribute association. An entity association will be represented by ???entityAssociation??? element of the metadata. ???entityAssociation??? and ???attributeAssociationList??? both are needed to represent an attribute association. For better understanding association the following scenario is considered. Scenario In this scenario, pop/sub broker asks for the indoor temperature of a house(e.g. house_3) and a sensor (e.g. sensor5) available in house_3. The sensor5 provides the indoor temperature as an attribute ???measurement???. ???indoorTemperature??? attribute of house_3 provides indoor temperature. Therefore, to get the indoor temperature of the house_3 there should be an association between ???indoorTemperature??? attribute of house_3 and ???measurement??? attribute of sensor5. I am attaching a complete example of an association scenario in the attachment with sample request and response. Also attaching the xsd file for the metadata tag. I am looking forward for your opinion about this topic. Thanks Raihan From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: 22 March 2013 09:58 To: Ferm??n Gal??n M??rquez Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: [Fiware-ngsi] how to represent associations Hi Fermin, Thanks for your feedback. We will come up with a proposal of a metadata type definition for representing associations in the week before Easter. I think also from an implementation point of view this approach is easier than the previous ones, because there is a more clear distinction between association registrations and context provider registrations. Best regards Tobias From: Ferm??n Gal??n M??rquez [mailto:fermin at tid.es] Sent: Freitag, 22. M??rz 2013 09:00 To: Tobias Jacobs Cc: fiware-ngsi at lists.fi-ware.eu Subject: Re: how to represent associations Dear Tobias, In principle, it seems more flexible than the original approach. However, in order to get a complete understanding of the idea and its implications (specially from the implementation point of view) we would need to have a look to a more detailed definition and examples (something in the same style as in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/OMA_NGSI_Association_concept). Are you planning to provide that definition/examples? Best regards, ------ Ferm??n El 20/03/2013 16:01, Tobias Jacobs escribi??: Dear Fermin, dear all, In the IoT F2F meeting last week we have been discussing about how to represent associations using the NGSI ContextRegistration structure, and we had not reached a conclusion yet. I would like to take the chance to propose a radically new and simplistic concept of doing this. How about we simply define some structured metadata types for associations where both the Thing-level entities/attributes and the Device-level entities/attributes are mentioned. These pieces of metadata are then put into the RegistrationMetadata list of the ContextRegistration structure, and the entityList and attributeList fields can stay empty. This gives us any flexibility of how to structure the associations. We can start with simple entityAssociations and attributeAssociations as metadata types, but further and more complex associations can be defined later in the same way. What do you think? Best Tobias ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol??tica de env??o y recepci??n de correo electr??nico en el enlace situado m??s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol??tica de env??o y recepci??n de correo electr??nico en el enlace situado m??s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol??tica de env??o y recepci??n de correo electr??nico en el enlace situado m??s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-ngsi mailing list Fiware-ngsi at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-ngsi 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 sergg at tid.es Mon Apr 15 23:46:59 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 15 Apr 2013 21:46:59 +0000 Subject: [Fiware-data] FW: [Fiware-wpa] Architecture: final iteration In-Reply-To: <516C3E9B.1030900@tid.es> References: <516C3E9B.1030900@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D86584113@EX10-MB2-MAD.hi.inet> Hi all, As you can read below, it's time to check if the reviews that we made have been appropriately taken into account. We reviewed Security and IoT chapters. IoT document is already finished and available, so the reviewers of those GEs can start already having a look at the final document at https://forge.fi-ware.eu/docman/view.php/27/2101/D232_WP5_final_afterPR2.docx and check the changes vs. your comments. Let me remind you who reviewed what: Sergio (TID) Common sections Sergio (TID, FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker Boris (TI) FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement.split.ConfMan Mauricio (ATOS) FIWARE.ArchitectureDescription.IoT.Backend.DiscoveryEngine Francisco (TID) FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement Francisco (TID FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement Peter Amon (SIEMENS) FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling Fano (Orange) FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter As soon as we have the security chapter, I will let you know. These were the reviewers. Sergio, common sections, Sergio, Identity Management Sergio, Privacy Sergio, Data Handling Boris, Context-based security & compliance Boris, Security Monitoring Siemens (various), Access Control Siemens (various), DB Anonymizer Siemens (various), Malware Detection Service Siemens (various), Android Flow Monitoring Siemens (various), Content-based Security If you detect any important issue, please let me know ASPA. Keep in mind that we should finish before Wednesday EOB. Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Monday, April 15, 2013 7:54 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Architecture: final iteration Dear all, Sorry, the previous message came out a bit too early in the middle of the edition! This is the one I was willing to send =================== The final check must start now. The idea is that each one of the two reviewers of each part of the Architecture should take a look at the final doc and complain if there is a serious objection not taken into account (they are welcome to discuss it privately with the GE owner first if they like). Note that a given GE owner can refuse to address a comment becuse he disagrees. If there is a conflict and the reviewer insists that there is a serious thing to change, he can write an e-mail to the WPL in charge of the WP putting me in CC and we will see what to do. For instance, if there is a conflic in the part of Data, the e-mail would go to Sergio. We will only take into account serious things, not details. Note that the quality of each part is the responsibility of the editor and the corresponding reviewers... * https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 Schedule * We have until Wednesday EOB to address this. * On Thursday I will check with you one by one and you will confirm that your teams have performed the check - please be ready by then, a "I will look into it today EOB" is not meeting the deadline I see the contributions from I2ND and IoT. I miss the final version of Apss, Cloud, Data and Security. Can you please finish this today EOB? Please send this urgently to all your teams. Best regards Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sergg at tid.es Tue Apr 16 10:39:44 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 16 Apr 2013 08:39:44 +0000 Subject: [Fiware-data] WP6 call Message-ID: <03BE306058976141B4883174DF62D54D865842B1@EX10-MB2-MAD.hi.inet> Hi all, Finally, given the number of confirmations and that the TID team cannot make it on Thursday, I set it up for tomorrow at 14.30h I will send the link to the minutes and agenda later on. Thanks for your understanding and flexibility. Best Regards, Sergio. ________________________________ 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: not available Type: text/calendar Size: 2042 bytes Desc: not available URL: From sergg at tid.es Tue Apr 16 13:19:12 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Tue, 16 Apr 2013 11:19:12 +0000 Subject: [Fiware-data] FW: FI-WARE: Periodic Report - M13 - M24 (WP6) In-Reply-To: <77A22C1085494D48B4018F06A40DB2C72FA07A1D@EX10-MB2-MAD.hi.inet> References: <77A22C1085494D48B4018F06A40DB2C72FA07A1D@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86584495@EX10-MB2-MAD.hi.inet> Dear partners, Please, find bellow the instructions and calendar that we have to follow to provide the information for the periodic report of Period 2. Let's make a first round to collect data from each partner, and each of the tasks. In order to make your work and also mine easier, let's do it in the WP google sheet https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=7 For each of the enablers, please, fill in the columns (progress, results, deviations, corrective actions). If there are contributing partners to the GE others than what I mentioned, please add them to the column Other contributors. As usual, the schedule is tight :( . We talk about it tomorrow during the WP call. Best Regards, Sergio. De: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: lunes, 15 de abril de 2013 23:07 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: subsidies at tid.es Asunto: [Fiware-wpl] FI-WARE: Periodic Report - M13 - M24 Importancia: Alta Dear all As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)). I will kindly ask you in another particularized e-mail to update as WPL the information about your WP. The schedule is the following: 1. First request of information to WPL with estimated effort per partner: April 15th, 2013 2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013 3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013 4. WPL send first version of his updated report to Coordinator (subsidies at tid.es): May 6th, 2013 5. Coordinator asks to each partner to update its current effort: April 30th, 2013 6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013 7. Coordinator sends updated data of effort to each WPL: May 15th, 2013 8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013 9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es): May 17th, 2013 10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013 11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013 12. Review: June 10th, 2013 At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said: [cid:image001.jpg at 01CE3A2F.0F2B6860] Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 39114 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP6 (to be updated).docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 233712 bytes Desc: WP6 (to be updated).docx URL: From sergg at tid.es Wed Apr 17 09:10:22 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 17 Apr 2013 07:10:22 +0000 Subject: [Fiware-data] [Fiware-wpa] Architecture: final iteration References: <516C3E9B.1030900@tid.es> Message-ID: <03BE306058976141B4883174DF62D54D865847CB@EX10-MB2-MAD.hi.inet> Dear *, The Security chapter is now available for final check: https://forge.fi-ware.eu/docman/view.php/27/2114/D232_WP8_v4_generated-final.doc Kind regards, Sergio From: SERGIO GARCIA GOMEZ Sent: Monday, April 15, 2013 11:47 PM To: fiware-data at lists.fi-ware.eu Subject: FW: [Fiware-wpa] Architecture: final iteration Hi all, As you can read below, it's time to check if the reviews that we made have been appropriately taken into account. We reviewed Security and IoT chapters. IoT document is already finished and available, so the reviewers of those GEs can start already having a look at the final document at https://forge.fi-ware.eu/docman/view.php/27/2101/D232_WP5_final_afterPR2.docx and check the changes vs. your comments. Let me remind you who reviewed what: Sergio (TID) Common sections Sergio (TID, FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker Boris (TI) FIWARE.ArchitectureDescription.IoT.Backend.ThingsManagement.split.ConfMan Mauricio (ATOS) FIWARE.ArchitectureDescription.IoT.Backend.DiscoveryEngine Francisco (TID) FIWARE.ArchitectureDescription.IoT.Backend.DeviceManagement Francisco (TID FIWARE.ArchitectureDescription.IoT.Gateway.DeviceManagement Peter Amon (SIEMENS) FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling Fano (Orange) FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter As soon as we have the security chapter, I will let you know. These were the reviewers. Sergio, common sections, Sergio, Identity Management Sergio, Privacy Sergio, Data Handling Boris, Context-based security & compliance Boris, Security Monitoring Siemens (various), Access Control Siemens (various), DB Anonymizer Siemens (various), Malware Detection Service Siemens (various), Android Flow Monitoring Siemens (various), Content-based Security If you detect any important issue, please let me know ASPA. Keep in mind that we should finish before Wednesday EOB. Best Regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: Monday, April 15, 2013 7:54 PM To: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpa] Architecture: final iteration Dear all, Sorry, the previous message came out a bit too early in the middle of the edition! This is the one I was willing to send =================== The final check must start now. The idea is that each one of the two reviewers of each part of the Architecture should take a look at the final doc and complain if there is a serious objection not taken into account (they are welcome to discuss it privately with the GE owner first if they like). Note that a given GE owner can refuse to address a comment becuse he disagrees. If there is a conflict and the reviewer insists that there is a serious thing to change, he can write an e-mail to the WPL in charge of the WP putting me in CC and we will see what to do. For instance, if there is a conflic in the part of Data, the e-mail would go to Sergio. We will only take into account serious things, not details. Note that the quality of each part is the responsibility of the editor and the corresponding reviewers... * https://docs.google.com/spreadsheet/ccc?key=0AhTmk3UgJVcbdFFLVmJtcC03NWU3LVdtN0VSNl96a2c#gid=0 Schedule * We have until Wednesday EOB to address this. * On Thursday I will check with you one by one and you will confirm that your teams have performed the check - please be ready by then, a "I will look into it today EOB" is not meeting the deadline I see the contributions from I2ND and IoT. I miss the final version of Apss, Cloud, Data and Security. Can you please finish this today EOB? Please send this urgently to all your teams. Best regards Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 4 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From sergg at tid.es Wed Apr 17 12:59:18 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 17 Apr 2013 10:59:18 +0000 Subject: [Fiware-data] WP6 call In-Reply-To: <03BE306058976141B4883174DF62D54D865842B1@EX10-MB2-MAD.hi.inet> References: <03BE306058976141B4883174DF62D54D865842B1@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86584B46@EX10-MB2-MAD.hi.inet> The agenda for the meeting: https://docs.google.com/document/d/1qlkKUh6eNX8OqgoqgiM9xqoEnPdU4kqv0WM4oS5QNmw/edit Best Regards, Sergio. -----Original Appointment----- From: SERGIO GARCIA GOMEZ Sent: Tuesday, April 16, 2013 10:40 AM To: fiware-data at lists.fi-ware.eu Subject: WP6 call When: mi?rcoles, 17 de abril de 2013 14:30-16:00 (UTC+01:00) Brussels, Copenhagen, Madrid, Paris. Where: Hi all, Finally, given the number of confirmations and that the TID team cannot make it on Thursday, I set it up for tomorrow at 14.30h I will send the link to the minutes and agenda later on. Thanks for your understanding and flexibility. Best Regards, Sergio. ________________________________ 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 sergg at tid.es Wed Apr 17 14:31:39 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 17 Apr 2013 12:31:39 +0000 Subject: [Fiware-data] KIARA slides Message-ID: <03BE306058976141B4883174DF62D54D86584BF3@EX10-MB2-MAD.hi.inet> Dear all, Please find attached some slides about KIARA that we will use right now in the call. Best Regards, Sergio ________________________________ 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 -------------- A non-text attachment was scrubbed... Name: 2013-04-17_KIARA-Shortpresentation_WP6_meeting.pdf Type: application/pdf Size: 1578767 bytes Desc: 2013-04-17_KIARA-Shortpresentation_WP6_meeting.pdf URL: From fermin at tid.es Tue Apr 23 13:33:10 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Tue, 23 Apr 2013 13:33:10 +0200 Subject: [Fiware-data] Issues with software release in WP6 In-Reply-To: <516C197F.4020507@tid.es> References: <516C197F.4020507@tid.es> Message-ID: <51767176.3080601@tid.es> Hi, (This email is addressed to Data Chapter WPL, but given he is off due to local holiday and this is an urgent issue, I'm CCing the whole chapter. Sorry for the inconveniences this may cause). I'm checking the sw release of WP6 and I have seen the following GEis are missing: * LOCS * Semantic Application Support In addition, I found some issues with GEis actually released: * According to https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware#Release_Management: "Naming convention: use X.Y.Z format". In the "DATA-Middleware" release you use "R2.2", which is not right. Change if to "2.2" (without "R"). We are now beyond deadline (it was April 22nd) so, please solve the above issues as soon as possible. Thank you very much! Best regards, ------ Ferm?n PD. My check is based in information gathered at 12:30 today. El 15/04/2013 17:15, Ferm?n Gal?n M?rquez escribi?: Hi, As far as I understand, the following GEis from WP6 are included in the April release: * Complex Event Processing * Compressed Domain Video Analysis * Media-enhanced Query Broker * Location Platform * Semantic Application Support * Meta-data Pre-processing * Middleware However, as far as I have checked in FI-WARE PPP Restricted Files (https://forge.fi-ware.eu/frs/?group_id=23) and FI-WARE Files (https://forge.fi-ware.eu/frs/?group_id=7), none of them has been yet released. Note that although there is a DATA-CEP package in https://forge.fi-ware.eu/frs/?group_id=23 it has "No releases". Given that the deadline for the release (April 22nd) is only one week ahead we wonder if you WP will be able to release them on time. As WPL/WPA, could you tell me the status of the releasing process within your WP, please? Thanks! Best regards, ------ Ferm?n PD. For your convenience, this is the link to the releasing procedure to follow: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware -------- Mensaje original -------- Asunto: [Fiware] Guidelines for Release 2 Fecha: Thu, 28 Mar 2013 02:24:26 +0100 De: Miguel Carrillo Responder a: Organizaci?n: Miguel Carrillo Para: fiware at lists.fi-ware.eu Dear all, Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message. This is strictly about : * Delivery of the Software itself * Installation and Administration manual * User and Programmer manual * Unit Testing Plan and report The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call. The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines is here(you need to this them before editing the deliverables): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Please note that: * The guidelines for the docs are basically the same ones as for Release 1 * The guidelines for the software delivery are completely different and were sent by Ferm?n to this list ages ago Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki. I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff). Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet) * This will ease the work of copying the definite versions of the manuals to their final destinations. * Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work. Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process. Best regards, Miguel ________________________________ 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 mach at zhaw.ch Tue Apr 23 17:34:33 2013 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 23 Apr 2013 15:34:33 +0000 Subject: [Fiware-data] Issues with software release in WP6 In-Reply-To: <51767176.3080601@tid.es> References: <516C197F.4020507@tid.es> <51767176.3080601@tid.es> Message-ID: <90A42480-29FA-4EA6-8844-AF8F00DAEC47@zhaw.ch> Hi Fermin, Sergio I fixed the release numbering of the DATA-Middleware. Best regards Christof Am 23.04.2013 um 13:33 schrieb Ferm?n Gal?n M?rquez > : Hi, (This email is addressed to Data Chapter WPL, but given he is off due to local holiday and this is an urgent issue, I'm CCing the whole chapter. Sorry for the inconveniences this may cause). I'm checking the sw release of WP6 and I have seen the following GEis are missing: * LOCS * Semantic Application Support In addition, I found some issues with GEis actually released: * According to https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware#Release_Management: "Naming convention: use X.Y.Z format". In the "DATA-Middleware" release you use "R2.2", which is not right. Change if to "2.2" (without "R"). We are now beyond deadline (it was April 22nd) so, please solve the above issues as soon as possible. Thank you very much! Best regards, ------ Ferm?n PD. My check is based in information gathered at 12:30 today. El 15/04/2013 17:15, Ferm?n Gal?n M?rquez escribi?: Hi, As far as I understand, the following GEis from WP6 are included in the April release: * Complex Event Processing * Compressed Domain Video Analysis * Media-enhanced Query Broker * Location Platform * Semantic Application Support * Meta-data Pre-processing * Middleware However, as far as I have checked in FI-WARE PPP Restricted Files (https://forge.fi-ware.eu/frs/?group_id=23) and FI-WARE Files (https://forge.fi-ware.eu/frs/?group_id=7), none of them has been yet released. Note that although there is a DATA-CEP package in https://forge.fi-ware.eu/frs/?group_id=23 it has "No releases". Given that the deadline for the release (April 22nd) is only one week ahead we wonder if you WP will be able to release them on time. As WPL/WPA, could you tell me the status of the releasing process within your WP, please? Thanks! Best regards, ------ Ferm?n PD. For your convenience, this is the link to the releasing procedure to follow: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware -------- Mensaje original -------- Asunto: [Fiware] Guidelines for Release 2 Fecha: Thu, 28 Mar 2013 02:24:26 +0100 De: Miguel Carrillo Responder a: Organizaci?n: Miguel Carrillo Para: fiware at lists.fi-ware.eu Dear all, Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message. This is strictly about : * Delivery of the Software itself * Installation and Administration manual * User and Programmer manual * Unit Testing Plan and report The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call. The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines is here(you need to this them before editing the deliverables): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2 Please note that: * The guidelines for the docs are basically the same ones as for Release 1 * The guidelines for the software delivery are completely different and were sent by Ferm?n to this list ages ago Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki. I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff). Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet) * This will ease the work of copying the definite versions of the manuals to their final destinations. * Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work. Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process. Best regards, Miguel ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-data mailing list Fiware-data at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-data From sergg at tid.es Wed Apr 24 09:32:03 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 24 Apr 2013 07:32:03 +0000 Subject: [Fiware-data] FI-WARE WP6 Call Message-ID: <03BE306058976141B4883174DF62D54D86586CBA@EX10-MB2-MAD.hi.inet> Please be aware of the change of PIN. Bridge: PIN 001633 * Belgium 070 35 99 94 * France 0821 230 748 * Germany 01803 001 178 * Italy 848 390 166 * Netherlands 0870 001 909 * Spain 902 885 318 * Sweden 0939 2066 400 * Switzerland 0848 560 190 * United Kingdom 0844 4 73 73 73 cell number 87373 * Other countries and details http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf * Worldwide & SkypeOut +49 1803 001 178 +44 844 4 73 73 73 https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=6 ________________________________ 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: not available Type: text/calendar Size: 2568 bytes Desc: not available URL: From sergg at tid.es Wed Apr 24 10:32:01 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 24 Apr 2013 08:32:01 +0000 Subject: [Fiware-data] FI-WARE: Periodic Report - M13 - M24 (WP6) References: <77A22C1085494D48B4018F06A40DB2C72FA07A1D@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86586D52@EX10-MB2-MAD.hi.inet> Hi all, This is a kind reminder to all the chapter partners to complete the periodic report information in the sheet, so that I can compile the word document. Thanks in advance. Best Regards, Sergio. From: SERGIO GARCIA GOMEZ Sent: Tuesday, April 16, 2013 1:19 PM To: fiware-data at lists.fi-ware.eu Subject: FW: FI-WARE: Periodic Report - M13 - M24 (WP6) Importance: High Dear partners, Please, find bellow the instructions and calendar that we have to follow to provide the information for the periodic report of Period 2. Let's make a first round to collect data from each partner, and each of the tasks. In order to make your work and also mine easier, let's do it in the WP google sheet https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=7 For each of the enablers, please, fill in the columns (progress, results, deviations, corrective actions). If there are contributing partners to the GE others than what I mentioned, please add them to the column Other contributors. As usual, the schedule is tight :( . We talk about it tomorrow during the WP call. Best Regards, Sergio. De: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] En nombre de JAVIER DE PEDRO SANCHEZ Enviado el: lunes, 15 de abril de 2013 23:07 Para: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu CC: subsidies at tid.es Asunto: [Fiware-wpl] FI-WARE: Periodic Report - M13 - M24 Importancia: Alta Dear all As you know we have to deliver the Periodic Report which has to give an overview of the second year of the project (months from M13 (May12) to M24 (Apr13)). I will kindly ask you in another particularized e-mail to update as WPL the information about your WP. The schedule is the following: 1. First request of information to WPL with estimated effort per partner: April 15th, 2013 2. Period to request each WPL to each involved partner its contribution to WP: April 16th, 2013 - Apr 19th, 2013 3. Integration of received information from by each WPL: April 22nd, 2013 - May 5th, 2013 4. WPL send first version of his updated report to Coordinator (subsidies at tid.es): May 6th, 2013 5. Coordinator asks to each partner to update its current effort: April 30th, 2013 6. Each partner sends its current effort according FORM-C 2: May 1st, 2013 - May 10th, 2013 7. Coordinator sends updated data of effort to each WPL: May 15th, 2013 8. Updating of the second version of each report by each WPL: May 16th, 2013 - May 17th, 2013 9. WPL sends final version of his updated report to Coordinator (subsidies at tid.es): May 17th, 2013 10. Integrating and revision by Coordinator: May 20th, 2013 - May 24th, 2013 11. Coordinator sends the Periodic Report to Project Officer: May 28th, 2013 12. Review: June 10th, 2013 At last but not least, please, I kindly ask you to follow the template in order to have a homogeneous report as a team. In the last review report they said: [cid:image001.jpg at 01CE40D1.D81AF170] Thank you in advance. BR Javier. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 39114 bytes Desc: image001.jpg URL: From sergg at tid.es Wed Apr 24 14:32:06 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 24 Apr 2013 12:32:06 +0000 Subject: [Fiware-data] New PIN for WP6 Call: 001633 Message-ID: <03BE306058976141B4883174DF62D54D86586F29@EX10-MB2-MAD.hi.inet> Same bridge numbers. https://docs.google.com/document/d/1prAHMD1eNmOkv96dYoqaZMToWL7zcU_GXNNDeVLZX0c/edit -- Sergio Garcia Gomez Telefonica Digital (TID/PDI) - Enablers & Technology Parque Tecnologico de Boecillo. Abraham Zacuto, 10. 47151 Boecillo (Valladolid), SPAIN. E-mail: sergg at tid.es Phone: (+34) 983367709 / (+34) 913129098 (IP) ________________________________ 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 sergg at tid.es Wed Apr 24 17:07:56 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Wed, 24 Apr 2013 15:07:56 +0000 Subject: [Fiware-data] Canceled: FI-WARE WP6 Call Message-ID: <03BE306058976141B4883174DF62D54D86587048@EX10-MB2-MAD.hi.inet> Please be aware of the change of PIN. Bridge: PIN 001633 * Belgium 070 35 99 94 * France 0821 230 748 * Germany 01803 001 178 * Italy 848 390 166 * Netherlands 0870 001 909 * Spain 902 885 318 * Sweden 0939 2066 400 * Switzerland 0848 560 190 * United Kingdom 0844 4 73 73 73 cell number 87373 * Other countries and details http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf * Worldwide & SkypeOut +49 1803 001 178 +44 844 4 73 73 73 https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=6 ________________________________ 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: not available Type: text/calendar Size: 3181 bytes Desc: not available URL: From sergg at tid.es Mon Apr 29 12:36:33 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 29 Apr 2013 10:36:33 +0000 Subject: [Fiware-data] FW: [Fiware-wpa] Backlog - Sprint transition: from S2.3.1-M24 to S2.3.2-M25 In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B8904821C@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8904821C@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86588A27@EX10-MB2-MAD.hi.inet> Dear partners, It's time to update the backlog, close this sprint items if finished, or shift them to the next sprint, and create new ones. Please follow the instructions bellow before tomorrow at 16.00h, as it was decided today during the WPL/WPA call. Best regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Monday, April 29, 2013 9:32 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Backlog - Sprint transition: from S2.3.1-M24 to S2.3.2-M25 Dear Partners, Let me remind you that we are finishing sprint S2.3.1-M24 and about to start S2.3.2-M25, which places us in the last two months before closing the Second Major Release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog items accordingly: 1. Close the backlog items finished during M24 (if not already done) 2. Update items under execution not finished to belong to S2.3.2 3. Proceed to identify the backlog items to be delivered during S2.3.2. This task should be finished the first week of S2.3.2-M25 Let me inform you that I'm about to get a snapshot of the backlog to produce the corresponding deliverable today. I assume you didn't miss my previous messages about sprint transitions, so there shouldn't be major concern about the tracker containing the actual state of the backlog!! To WPLeaders, please, distribute the message to your teams!! Thanks for cooperation! 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sergg at tid.es Mon Apr 29 13:18:34 2013 From: sergg at tid.es (SERGIO GARCIA GOMEZ) Date: Mon, 29 Apr 2013 11:18:34 +0000 Subject: [Fiware-data] [Fiware-wpa] Backlog - Sprint transition: from S2.3.1-M24 to S2.3.2-M25 References: <65CDBE2E7E5A964BB8BC5F4328FDE90B8904821C@EX10-MB2-MAD.hi.inet> Message-ID: <03BE306058976141B4883174DF62D54D86588B2C@EX10-MB2-MAD.hi.inet> Hi again, In order to make it easier, as soon as you have closed/planned the sprints, write down a YES in the red/green column of your GE. https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=3 Best Regards, Sergio. From: SERGIO GARCIA GOMEZ Sent: Monday, April 29, 2013 12:37 PM To: fiware-data at lists.fi-ware.eu Subject: FW: [Fiware-wpa] Backlog - Sprint transition: from S2.3.1-M24 to S2.3.2-M25 Dear partners, It's time to update the backlog, close this sprint items if finished, or shift them to the next sprint, and create new ones. Please follow the instructions bellow before tomorrow at 16.00h, as it was decided today during the WPL/WPA call. Best regards, Sergio. From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of MANUEL ESCRICHE VICENTE Sent: Monday, April 29, 2013 9:32 AM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Backlog - Sprint transition: from S2.3.1-M24 to S2.3.2-M25 Dear Partners, Let me remind you that we are finishing sprint S2.3.1-M24 and about to start S2.3.2-M25, which places us in the last two months before closing the Second Major Release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog items accordingly: 1. Close the backlog items finished during M24 (if not already done) 2. Update items under execution not finished to belong to S2.3.2 3. Proceed to identify the backlog items to be delivered during S2.3.2. This task should be finished the first week of S2.3.2-M25 Let me inform you that I'm about to get a snapshot of the backlog to produce the corresponding deliverable today. I assume you didn't miss my previous messages about sprint transitions, so there shouldn't be major concern about the tracker containing the actual state of the backlog!! To WPLeaders, please, distribute the message to your teams!! Thanks for cooperation! 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: