Hello Pier and Roberto, It would be really helpful if you guys share the document with your view, as we did on Friday before having the next call. Are you guys still on for tomorrow at 10 for the robotics call? We are ok with that time, and pretty much all day, except for 12:00 to 14:00. Talk to you soon. De: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] En nombre de Fernando Herranz Enviado el: martes, 11 de noviembre de 2014 10:55 Para: fiware-robotics at lists.fi-ware.org Asunto: Re: [Fiware-robotics] R: Notes from Robotics call Hello guys, I'm revising the document that we sent you last Friday. I've noticed that there are some comments regarding the use of two GEs and the role of RCM. Since the description of RCM that we presented in the document is only our assumption, I encourage you all to modify the document. Please add your point of view and information about RCM to keep moving forward in the development of RCM and FIROS. Cheers! On 07/11/14 15:38, Jose Jaime Ariza wrote: Hi all, I'm sorry I made a mistake in the email: I've written FIWARE instead of FIROS. Bests, José On 07/11/14 15:34, Jose Jaime Ariza wrote: Hi all, I'm sending you a link with a shared Google document where we show our description of what we think FIWARE and RCM should be. This is only our point of view and in some cases we make some assumptions. Please, feel free to correct the document and modify the assumptions that are not correct. https://docs.google.com/document/d/1F1CVpW1hNfMN6ugw0oeRN_QQ9iPrLWlgmQgewHvTwZw/edit?usp=sharing Bests, José On 04/11/14 12:50, Garino Pierangelo wrote: Dear Jose and Roberto (and All), Please find attached a template document you can use to provide the description we agreed in the call yesterday. I wish to thank Gianmario for preparing this draft ToC and for focusing on the three main questions that the sections should answer to. The main purpose of the document is collecting most of the information we have so far circulated in a different way (e.g. slides, discussions), to create an overall vision of the offer we are promoting. Probably Sections 2 and 3 are the most important at this time for getting your contribution, while we can discuss later Section 1, however any draft input to this section is also welcome to later discuss this item with already details available. I particularly believe that contributing to this document will produce not only relevant information to let us define the robotics details, but it will also provide helpful contents for the next deliverables we need to describe in the project (e.g. architecture deliverable); I encourage therefore everybody to do their best doing the exercise, because we'll hopefully be able to exploit it in several ways in the project. In case you have any doubt about the expected contributions, please send a mail or call us for discussing together the issue. Many thanks and BR Pier Da: Garino Pierangelo Inviato: martedì 4 novembre 2014 08:50 A: 'Jose Jaime Ariza' Cc: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: R: [Fiware-robotics] Notes from Robotics call Hi Jose, We are indeed working with my colleague Gianmario to provide a common template for these contributions. We should distribute it by today afternoon. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org<mailto:fiware-robotics-bounces at lists.fi-ware.org> [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: lunedì 3 novembre 2014 18:25 A: fiware-robotics at lists.fi-ware.org<mailto:fiware-robotics at lists.fi-ware.org> Oggetto: Re: [Fiware-robotics] Notes from Robotics call Hi Pier, It would be great to have the same structure for both documents. Do you have any particular structure in mind for the documents? Is there any layout guide for Fi-Ware documents? I suppose that it exists but I cannot find any. Thank you very much, José On 03/11/14 14:33, Garino Pierangelo wrote: Hi All, here are few notes I took during of today's call (please correct if I reported something wrong). - Discussion on proposal to use CoAP protocol for FIROS o Presentation of slides (particularly 11 and 12) by Fernando & Jose - Comment by Pier o Will FIROS have in the short term CoAP and in the long term NGSI interface? - Messages exchanged through the FIROS Interface o Pdf Document by Fernando & Jose § Position of the robot § PointStamped § Etc - Comment by Roberto: with this definition FIROS seems a sort of driver, rather than a bridge o In his opinion it should really become a bridge, and not only a driver, to make the connection to CB o It should also extend to other kind of data § This is what is assumed by ET too o Since ROS is based on pbsub paradigm, and CB does the same, FIROS should be able to translate from northbound to southbound keeping the paradigm o ROSBridge is an example of socket-based translation in ROS - Comment by Fernando: it is not valuable translate everything · There are CB limitations in size of messages · ROS doesn't have context information, which is required by CB - Roberto: there are kind of data that should be conveyed to CB, take example of roomba device (position, battery, etc) - Fernando: but batterly level is probably to ba managed by RCM - We agree that there was a misalignment: o Pier/Roberto considered the use of FIROS without RCM o Fernando/Jose with it We should answer the question 'What kind of information we want to publish on CB' - Comment by Pier: o In addition to FIROS interfacing, a further interface needs to be available in RCM for management of platform components lifecycle o This doesn't duplicate the connection through FIROS (i.e. no data conveyed to CB are passing through it), but it is complementary - Roberto: o The high availability of robots is to be managed by the RCM § e.g. watchdog system to check network connections - Pier: o Proposal of AP to describe the capabilities of the robotics components in a textual format (Word Document) o This will help clarify the functionality and interfacing expected, as well as list the possible unknowns to be addressed AP: Provide document to be exchanged by the end of the week containing: - A List of capabilities of FIROS and RCM: - A list of questions/comments/doubts which we should then address: o AP: ET to describe the part concerning FIROS o AP: TI to describe the part concerning RCM o Deadline: Fri 7th, then document is shared 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: <https://lists.fiware.org/private/fiware-robotics/attachments/20141112/7af743ba/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy