From pierangelo.garino at telecomitalia.it Tue Mar 3 22:36:18 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 3 Mar 2015 21:36:18 +0000 Subject: [Fiware-robotics] Live demo - trial to merge into a single demo description Message-ID: Hi All, I eventually made the exercise to combine together the two demos originally provided concerning the robotics GE, which were put in the live demo draft deliverable. By adopting the incremental approach, I have split the robotics demo in three steps: the first is the original teleoperation as a service case, I then added a second step which is an intermediate one where navigation to a given target is shown (no fire extinguisher yet nor sensors), then the third one is the original full firefighting robots case. You can find the result in the attached document first version is with my modifications shown, the second (clean version) is with changes accepted to make it understandable. Please have a look and tell me if this is a consistent idea to provide a common demo setting for the deliverable. I have put a number of comments to be managed, have a look and propose something as well. When you need to modify the doc, please do it in the clean version and activate the 'track changes', so that I can check what has been modified. Later I'll put the resulting doc in the shared google docs version (hopefully by Wed evening if you send me your feedback along the day). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED.11.5.1LiveDemos-Joint_RoboticsDemo.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1624726 bytes Desc: FIWARED.11.5.1LiveDemos-Joint_RoboticsDemo.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED.11.5.1LiveDemos-Joint_RoboticsDemo-clean.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1587295 bytes Desc: FIWARED.11.5.1LiveDemos-Joint_RoboticsDemo-clean.docx 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 ahernandez at ikergune.com Wed Mar 4 16:44:17 2015 From: ahernandez at ikergune.com (Angel Hernandez) Date: Wed, 4 Mar 2015 16:44:17 +0100 Subject: [Fiware-robotics] Live demo - trial to merge into a single demo description In-Reply-To: References: Message-ID: Hello Pier, Thank you for your effort, I think you did a very good job at merging the demos. I am attaching a new file with minor corrections and responding to your comments. One thing I am concerned about is how to manage three different stages when the demo must be ready for M13 anyway. The firefighting demo will definitely be ready, so shall we propose intermediate dates for the other 2? Thank you! De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 3 de marzo de 2015 22:36 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] Live demo - trial to merge into a single demo description Hi All, I eventually made the exercise to combine together the two demos originally provided concerning the robotics GE, which were put in the live demo draft deliverable. By adopting the incremental approach, I have split the robotics demo in three steps: the first is the original teleoperation as a service case, I then added a second step which is an intermediate one where navigation to a given target is shown (no fire extinguisher yet nor sensors), then the third one is the original full firefighting robots case. You can find the result in the attached document first version is with my modifications shown, the second (clean version) is with changes accepted to make it understandable. Please have a look and tell me if this is a consistent idea to provide a common demo setting for the deliverable. I have put a number of comments to be managed, have a look and propose something as well. When you need to modify the doc, please do it in the clean version and activate the 'track changes', so that I can check what has been modified. Later I'll put the resulting doc in the shared google docs version (hopefully by Wed evening if you send me your feedback along the day). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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:image001.gif at 01D0569A.745EB320]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED 11 5 1LiveDemos-Joint_RoboticsDemo-clean- IKG rev1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1586451 bytes Desc: FIWARED 11 5 1LiveDemos-Joint_RoboticsDemo-clean- IKG rev1.docx URL: From pierangelo.garino at telecomitalia.it Wed Mar 4 17:00:26 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 4 Mar 2015 16:00:26 +0000 Subject: [Fiware-robotics] R: Live demo - trial to merge into a single demo description In-Reply-To: References: Message-ID: Hi Angel, Thanks a lot for your feedback! We still need to improve some of the descriptions, but I believe that we are already at a good stage of description. In my view the three stages should be managed exactly as you might expect, i.e. proposing intermediate dates for the first two and keeping the third one for M13. This also implies in my opinion that each stage should build a piece of 'infrastructure' which can be used later in the next stage(s), to avoid duplicating the work. Here I can take the example of Kurento: if we integrate it in the demo at stage 1, then it will be worth for the other two as well. This however requires that we detail better the three stages, and make sure we link them very well in terms of components, functionalities and necessary developments. That's in my view the goal of the improvements to the description I mentioned above. If this approach is agreed, then this evening I'll put the new description in the Live Demo deliverable's google docs. Of course any other opinion is welcome. BR Pier Da: Angel Hernandez [mailto:ahernandez at ikergune.com] Inviato: mercoled? 4 marzo 2015 16:44 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: RE: [Fiware-robotics] Live demo - trial to merge into a single demo description Hello Pier, Thank you for your effort, I think you did a very good job at merging the demos. I am attaching a new file with minor corrections and responding to your comments. One thing I am concerned about is how to manage three different stages when the demo must be ready for M13 anyway. The firefighting demo will definitely be ready, so shall we propose intermediate dates for the other 2? Thank you! De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Garino Pierangelo Enviado el: martes, 3 de marzo de 2015 22:36 Para: fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] Live demo - trial to merge into a single demo description Hi All, I eventually made the exercise to combine together the two demos originally provided concerning the robotics GE, which were put in the live demo draft deliverable. By adopting the incremental approach, I have split the robotics demo in three steps: the first is the original teleoperation as a service case, I then added a second step which is an intermediate one where navigation to a given target is shown (no fire extinguisher yet nor sensors), then the third one is the original full firefighting robots case. You can find the result in the attached document first version is with my modifications shown, the second (clean version) is with changes accepted to make it understandable. Please have a look and tell me if this is a consistent idea to provide a common demo setting for the deliverable. I have put a number of comments to be managed, have a look and propose something as well. When you need to modify the doc, please do it in the clean version and activate the 'track changes', so that I can check what has been modified. Later I'll put the resulting doc in the shared google docs version (hopefully by Wed evening if you send me your feedback along the day). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Wed Mar 4 17:00:46 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 4 Mar 2015 16:00:46 +0000 Subject: [Fiware-robotics] R: Live demo - trial to merge into a single demo description In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCE81D5@TELMBB001BA020.telecomitalia.local> Hi Pier, here attached is my "two cents" some corrections and answers to questions you pose ... R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: marted? 3 marzo 2015 22:36 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo - trial to merge into a single demo description Hi All, I eventually made the exercise to combine together the two demos originally provided concerning the robotics GE, which were put in the live demo draft deliverable. By adopting the incremental approach, I have split the robotics demo in three steps: the first is the original teleoperation as a service case, I then added a second step which is an intermediate one where navigation to a given target is shown (no fire extinguisher yet nor sensors), then the third one is the original full firefighting robots case. You can find the result in the attached document first version is with my modifications shown, the second (clean version) is with changes accepted to make it understandable. Please have a look and tell me if this is a consistent idea to provide a common demo setting for the deliverable. I have put a number of comments to be managed, have a look and propose something as well. When you need to modify the doc, please do it in the clean version and activate the 'track changes', so that I can check what has been modified. Later I'll put the resulting doc in the shared google docs version (hopefully by Wed evening if you send me your feedback along the day). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED 11 5 1LiveDemos-Joint_RoboticsDemo-cleanAR.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1590992 bytes Desc: FIWARED 11 5 1LiveDemos-Joint_RoboticsDemo-cleanAR.docx URL: From jjaime at ikergune.com Wed Mar 4 18:06:30 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Wed, 4 Mar 2015 18:06:30 +0100 Subject: [Fiware-robotics] R: Live demo - trial to merge into a single demo description In-Reply-To: <246C286B275B1B46A255552CD236DA863BCE81D5@TELMBB001BA020.telecomitalia.local> References: , <246C286B275B1B46A255552CD236DA863BCE81D5@TELMBB001BA020.telecomitalia.local> Message-ID: Hi Pier, Here you have the corrected images. I've also included a little process diagram for stage 2. Since this document is still a draft, I think it'll be enough. You can find the original images in the following links: https://docs.google.com/document/d/1yuygp5fvqT4m91aqw1d2wz69HQSIwHcffxQ4MCB5K-g/edit# https://docs.google.com/drawings/d/1rfa7rVekI4sE1CoT1tyXLiLclsCOJ1DbcKoFX2WAUsA/edit?usp=sharing BR, Pepe ________________________________________ De: fiware-robotics-bounces at lists.fi-ware.org [fiware-robotics-bounces at lists.fi-ware.org] En nombre de Antonini Roberto [roberto1.antonini at telecomitalia.it] Enviado el: mi?rcoles, 04 de marzo de 2015 17:00 Para: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Asunto: [Fiware-robotics] R: Live demo - trial to merge into a single demo description Hi Pier, here attached is my ?two cents? some corrections and answers to questions you pose ? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: marted? 3 marzo 2015 22:36 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo - trial to merge into a single demo description Hi All, I eventually made the exercise to combine together the two demos originally provided concerning the robotics GE, which were put in the live demo draft deliverable. By adopting the incremental approach, I have split the robotics demo in three steps: the first is the original teleoperation as a service case, I then added a second step which is an intermediate one where navigation to a given target is shown (no fire extinguisher yet nor sensors), then the third one is the original full firefighting robots case. You can find the result in the attached document first version is with my modifications shown, the second (clean version) is with changes accepted to make it understandable. Please have a look and tell me if this is a consistent idea to provide a common demo setting for the deliverable. I have put a number of comments to be managed, have a look and propose something as well. When you need to modify the doc, please do it in the clean version and activate the ?track changes?, so that I can check what has been modified. Later I?ll put the resulting doc in the shared google docs version (hopefully by Wed evening if you send me your feedback along the day). Thanks and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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:image001.gif at 01D0569C.BE8A83A0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. From pierangelo.garino at telecomitalia.it Wed Mar 11 12:39:27 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 11 Mar 2015 11:39:27 +0000 Subject: [Fiware-robotics] Live demo on Robotics - Update description Message-ID: Hi All, As I agreed with the Live Demo Task coordinator (Ilknur from Atos), I have reviewed the description of live demo on Robotics, you can find the updated version in the doc attached (it's easier to identify the changes). I have also attempted to create a high level block diagram, where I have put the main GEs being involved in the demo. However, there might be updates to the picture which you feel necessary: e.g. I didn't include the Identity Management GE, as it seems difficult to me maintaining the drawing simple, but if you find a clever way to include it in the picture would be great. Moreover, I drafted the Robotics GE in a 'strange' way to represent the fact it is somehow distributed between the platform and the robot, with a wireless connectivity link in between. I include the original .pptx picture in this mail as well. Please have a look at both text and diagram(s), and tell me if there are parts to be corrected/modified. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED.11.5.1LiveDemos_11-Mar-15.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1755492 bytes Desc: FIWARED.11.5.1LiveDemos_11-Mar-15.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Live_Demo_Diagram.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 50084 bytes Desc: Live_Demo_Diagram.pptx 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 pierangelo.garino at telecomitalia.it Wed Mar 11 16:42:41 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 11 Mar 2015 15:42:41 +0000 Subject: [Fiware-robotics] Review of Robotics GE architecture Message-ID: Hi All again, I reviewed the Robotics GE architecture in the I2ND wiki, which looks already at a good stage. I introduced some minor updates, typically uppercase/lowercase adjustments, minor text rephrasing making text hopefully more readable, etc. After a talk I had with Thomas I also added a textual description concerning the interface to the Cloud Hosting GEs (I,.e. DCRM), which is expected to be developed at a later stage. There are however two items among other minor ones, I believe need to be addressed, i.e.: - The 'Robotics data' component in the MASTER entity is in my view (mis)leading the reader to consider this the place where all the data concerning a robot (i.e. sensor data, position, etc) is stored, hence the RDAPI interface would be used to access this information. Can we define it in a different manner, e.g. 'Robotics Data Settings' or (my preferred option) 'Robotics Configuration data'? - The FIROS block diagram shown at the I2ND meeting in Torino provided additional interfaces which are not described in the current architecture diagram: if they are necessary to interact with the Robotics GE and its components, we have to insert them in the diagram. Can you please provide a feedback on those two items (I expect that the group in Torino provides it for item 1, and the group at ET provides it for item 2), thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From igonzalez at ikergune.com Wed Mar 11 16:58:59 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Wed, 11 Mar 2015 16:58:59 +0100 Subject: [Fiware-robotics] Review of Robotics GE architecture References: Message-ID: Hi, that diagram was an internal document of the current status of our development. That was a need we had before, but Firos continues evolving, and that diagram doesn't fit with the current development state any more. So don't worry about that, we hope that the final product will be very similar to the defined in the architecture. Regards, I?igo On 11/03/15 16:42, Garino Pierangelo wrote: Hi All again, I reviewed the Robotics GE architecture in the I2ND wiki, which looks already at a good stage. I introduced some minor updates, typically uppercase/lowercase adjustments, minor text rephrasing making text hopefully more readable, etc. After a talk I had with Thomas I also added a textual description concerning the interface to the Cloud Hosting GEs (I,.e. DCRM), which is expected to be developed at a later stage. There are however two items among other minor ones, I believe need to be addressed, i.e.: - The ?Robotics data? component in the MASTER entity is in my view (mis)leading the reader to consider this the place where all the data concerning a robot (i.e. sensor data, position, etc) is stored, hence the RDAPI interface would be used to access this information. Can we define it in a different manner, e.g. ?Robotics Data Settings? or (my preferred option) ?Robotics Configuration data?? - The FIROS block diagram shown at the I2ND meeting in Torino provided additional interfaces which are not described in the current architecture diagram: if they are necessary to interact with the Robotics GE and its components, we have to insert them in the diagram. Can you please provide a feedback on those two items (I expect that the group in Torino provides it for item 1, and the group at ET provides it for item 2), thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Thu Mar 12 08:31:03 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 12 Mar 2015 07:31:03 +0000 Subject: [Fiware-robotics] R: Review of Robotics GE architecture In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCFF08B@TELMBA001BA020.telecomitalia.local> Hi Pier, ok, as you propose we could change that name to Robotics Configuration data, even though sensor and robot position data usually refer to "robot data", but you're right when you say this could mislead the readers. Thanks for your revising. Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: mercoled? 11 marzo 2015 16:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Review of Robotics GE architecture Hi All again, I reviewed the Robotics GE architecture in the I2ND wiki, which looks already at a good stage. I introduced some minor updates, typically uppercase/lowercase adjustments, minor text rephrasing making text hopefully more readable, etc. After a talk I had with Thomas I also added a textual description concerning the interface to the Cloud Hosting GEs (I,.e. DCRM), which is expected to be developed at a later stage. There are however two items among other minor ones, I believe need to be addressed, i.e.: - The 'Robotics data' component in the MASTER entity is in my view (mis)leading the reader to consider this the place where all the data concerning a robot (i.e. sensor data, position, etc) is stored, hence the RDAPI interface would be used to access this information. Can we define it in a different manner, e.g. 'Robotics Data Settings' or (my preferred option) 'Robotics Configuration data'? - The FIROS block diagram shown at the I2ND meeting in Torino provided additional interfaces which are not described in the current architecture diagram: if they are necessary to interact with the Robotics GE and its components, we have to insert them in the diagram. Can you please provide a feedback on those two items (I expect that the group in Torino provides it for item 1, and the group at ET provides it for item 2), thanks. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Thu Mar 12 10:31:19 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 12 Mar 2015 09:31:19 +0000 Subject: [Fiware-robotics] R: Live demo on Robotics - Update description In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA863BCFF215@TELMBA001BA020.telecomitalia.local> Hi Pier Here attached is my revision to the document, mainly comments. For what concerns the block diagram, in my view is a very effective representation, the only notation is that I wouldn't put at this stage two connections btw Robotics and Kurento GE, I see robots as being part of the whole robotics GE, so I would put the connection that doesn't break symmetry :) Thanks, Roberto Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: mercoled? 11 marzo 2015 12:39 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Live demo on Robotics - Update description Hi All, As I agreed with the Live Demo Task coordinator (Ilknur from Atos), I have reviewed the description of live demo on Robotics, you can find the updated version in the doc attached (it's easier to identify the changes). I have also attempted to create a high level block diagram, where I have put the main GEs being involved in the demo. However, there might be updates to the picture which you feel necessary: e.g. I didn't include the Identity Management GE, as it seems difficult to me maintaining the drawing simple, but if you find a clever way to include it in the picture would be great. Moreover, I drafted the Robotics GE in a 'strange' way to represent the fact it is somehow distributed between the platform and the robot, with a wireless connectivity link in between. I include the original .pptx picture in this mail as well. Please have a look at both text and diagram(s), and tell me if there are parts to be corrected/modified. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARED 11 5 1LiveDemos_11-Mar-15_AR.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1756121 bytes Desc: FIWARED 11 5 1LiveDemos_11-Mar-15_AR.docx URL: From davide.colombatto at telecomitalia.it Thu Mar 12 12:25:15 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 12 Mar 2015 11:25:15 +0000 Subject: [Fiware-robotics] FIROS - outbound ports Message-ID: <069906BED271EB4A883BD9578DCDD3540372D5@TELMBA006RM001.telecomitalia.local> Hi Inigo, Can you tell us which are the outbound (to Internet) ports used by FIROS when it contacts the CB (and the CB-proxy in your dev machine). We see the core.py has set 1026 but I suppose it is not used yet. We need to know them in order to ask their opening for our company Firewall. Moreover, for what concern inbound ports, do you confirm that it is only one for each FIROS (default: 10100)? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From igonzalez at ikergune.com Thu Mar 12 13:06:22 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Thu, 12 Mar 2015 13:06:22 +0100 Subject: [Fiware-robotics] FIROS - outbound ports References: <069906BED271EB4A883BD9578DCDD3540372D5@TELMBA006RM001.telecomitalia.local> Message-ID: Hi Davide, the outbound port is 1026 and is the port used to connect to the context broker. the inbound port is the 10100, you can change to the value that better fits to your network in the line 31 of the core.py file. This port registered in the context broker and that will listen to the context brokers notifications. About the CB-proxy, as I said in a previous mail don't worry, because it is a tool we are currently using but is going to disappear from firos in a future and wasn't included in the firos version you have to avoid making complex to deploy everything. Regards, I?igo On 12/03/15 12:25, Colombatto Davide wrote: Hi Inigo, Can you tell us which are the outbound (to Internet) ports used by FIROS when it contacts the CB (and the CB-proxy in your dev machine). We see the core.py has set 1026 but I suppose it is not used yet. We need to know them in order to ask their opening for our company Firewall. Moreover, for what concern inbound ports, do you confirm that it is only one for each FIROS (default: 10100)? Thank you, Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Thu Mar 12 13:26:16 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Thu, 12 Mar 2015 12:26:16 +0000 Subject: [Fiware-robotics] R: FIROS - outbound ports In-Reply-To: References: <069906BED271EB4A883BD9578DCDD3540372D5@TELMBA006RM001.telecomitalia.local> Message-ID: <069906BED271EB4A883BD9578DCDD354037357@TELMBA006RM001.telecomitalia.local> Ok Inigo, but if we want to test our current environment using the current version of FIROS that we have (that of first demo) which port is used to contact your CB-Proxy? Obviously if we'll need to do some tests I'll ask you before if we can to use your CB-Proxy (in order to avoid parallel tests). Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 12 marzo 2015 13:06 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: FIROS - outbound ports Hi Davide, the outbound port is 1026 and is the port used to connect to the context broker. the inbound port is the 10100, you can change to the value that better fits to your network in the line 31 of the core.py file. This port registered in the context broker and that will listen to the context brokers notifications. About the CB-proxy, as I said in a previous mail don't worry, because it is a tool we are currently using but is going to disappear from firos in a future and wasn't included in the firos version you have to avoid making complex to deploy everything. Regards, I?igo On 12/03/15 12:25, Colombatto Davide wrote: Hi Inigo, Can you tell us which are the outbound (to Internet) ports used by FIROS when it contacts the CB (and the CB-proxy in your dev machine). We see the core.py has set 1026 but I suppose it is not used yet. We need to know them in order to ask their opening for our company Firewall. Moreover, for what concern inbound ports, do you confirm that it is only one for each FIROS (default: 10100)? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From igonzalez at ikergune.com Thu Mar 12 16:32:15 2015 From: igonzalez at ikergune.com (=?Windows-1252?Q?I=F1igo_Gonzalez?=) Date: Thu, 12 Mar 2015 16:32:15 +0100 Subject: [Fiware-robotics] R: FIROS - outbound ports References: <069906BED271EB4A883BD9578DCDD3540372D5@TELMBA006RM001.telecomitalia.local> <069906BED271EB4A883BD9578DCDD354037357@TELMBA006RM001.telecomitalia.local> Message-ID: The proxy's port is 10101, but it is a server that is hosted in my computer. An that proxy isn't always up and soon will be deprecated. That doesn't matter too much, since the proxy is only to avoid the context broker's cross origin policy, so you can do your tests doing a native app or disabling chrome's security if you are using a web page. Regards, I?igo On 12/03/15 13:26, Colombatto Davide wrote: Ok Inigo, but if we want to test our current environment using the current version of FIROS that we have (that of first demo) which port is used to contact your CB-Proxy? Obviously if we?ll need to do some tests I?ll ask you before if we can to use your CB-Proxy (in order to avoid parallel tests). Davide Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: gioved? 12 marzo 2015 13:06 A: Colombatto Davide Cc: fiware-robotics at lists.fi-ware.org Oggetto: Re: FIROS - outbound ports Hi Davide, the outbound port is 1026 and is the port used to connect to the context broker. the inbound port is the 10100, you can change to the value that better fits to your network in the line 31 of the core.py file. This port registered in the context broker and that will listen to the context brokers notifications. About the CB-proxy, as I said in a previous mail don't worry, because it is a tool we are currently using but is going to disappear from firos in a future and wasn't included in the firos version you have to avoid making complex to deploy everything. Regards, I?igo On 12/03/15 12:25, Colombatto Davide wrote: Hi Inigo, Can you tell us which are the outbound (to Internet) ports used by FIROS when it contacts the CB (and the CB-proxy in your dev machine). We see the core.py has set 1026 but I suppose it is not used yet. We need to know them in order to ask their opening for our company Firewall. Moreover, for what concern inbound ports, do you confirm that it is only one for each FIROS (default: 10100)? Thank you, Davide 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. [data:image/jpeg;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: