**Information model**, the documentation that will describe how to create standard robot modules.
I would like to share with all of you the Lightning Talk I made at ROSCon 2017: the transcript + slides. Feel free to ask any questions or give your feedback:
irati@erlerobotics.com
Thanks!
**Information model**
Good evening, I am Irati Zamalloa, an industrial design engineer from [Erle Robotics](
http://erlerobotics.com/blog/).
As all of you know, we are working on H-ROS, the [Hardware Robot Operating System](
http://h-ros.com), to offer the world standard modules for building robots.
The standardization require that every detail fit like a tetris, so I would like to introduce one of the key pieces, the information model.
**What is an H-ROS Information model?**
It is a set of rules and specifications to create an standard robot modules.
H-ROS remove components integration, we eliminate the necessary effort to achieve communication between devices, almost 70% time over the total.
If we translate this to ROS, we need all the modules to contain the same topics, messages services, actions and parameters, to make sure that all of them speak the same language at all levels.
And the information model is the document that describes all the details.
**Building process**
We are pushing ROS to get standardized. We believe in ROS, but we also believe that it needs a step more, and get the next level of acceptance. That is why we are working actively with international organizations like ISO or OMG.
It will help to build a solid infrastructure from the ground up and make the H-ROS information model a reference document to create standard robotic modules.
Thank you for your time! And if anybody wants to know more about the **H-ROS information model**, come talk to me! Thank you!
Irati Zamalloa
_Industrial Design Engineer_
irati@erlerobotics.com
---
[Visit Topic](
https://discourse.ros.org/t/pushing-ros-to-get-standardized-roscon-2017-lightning-talk/2812/1) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
%0A>%20%0A>%20Good%20evening,%20I%20am%20Irati%20Zamalloa,%20an%20industrial%20design%20engineer%20from%20%5BErle%20Robotics%5D(http://erlerobotics.com/blog/).%0A>%20%0A>%20As%20all%20of%20you%20know,%20we%20are%20working%20on%20H-ROS,%20the%20%5BHardware%20Robot%20Operating%20System%5D(http://h-ros.com),%20to%20offer%20the%20world%20standard%20modules%20for%20building%20robots.%0A>%20%0A>%20The%20standardization%20require%20that%20every%20detail%20fit%20like%20a%20tetris,%20so%20I%20would%20like%20to%20introduce%20one%20of%20the%20key%20pieces,%20the%20information%20model.%0A>%20%0A>%20!%5Bimage%7C690x194%5D(upload://r4YdkJJgK0QBXlVcoIUNq0YERY0.jpg)%0A>%20%0A>%20**What%20is%20an%20H-ROS%20Information%20model?**%0A>%20%0A>%20It%20is%20a%20set%20of%20rules%20and%20specifications%20to%20create%20an%20standard%20robot%20modules.%20%0A>%20%0A>%20H-ROS%20remove%20components%20integration,%20we%20eliminate%20the%20necessary%20effort%20to%20achieve%20communication%20between%20devices,%20almost%2070%%20time%20over%20the%20total.%20%20%0A>%20%0A>%20If%20we%20translate%20this%20to%20ROS,%20we%20need%20all%20the%20modules%20to%20contain%20the%20same%20topics,%20messages%20services,%20actions%20and%20parameters,%20to%20make%20sure%20that%20all%20of%20them%20speak%20the%20same%20language%20at%20all%20levels.%20%0A>%20%0A>%20And%20the%20information%20model%20is%20the%20document%20that%20describes%20all%20the%20details.%0A>%20%0A>%20%0A>%20**Building%20process**%0A>%20%0A>%20%0A>%20We%20are%20pushing%20ROS%20to%20get%20standardized.%20We%20believe%20in%20ROS,%20but%20we%20also%20believe%20that%20it%20needs%20a%20step%20more,%20and%20get%20the%20next%20level%20of%20acceptance.%20That%20is%20why%20we%20are%20working%20actively%20with%20international%20organizations%20like%20ISO%20or%20OMG.%0A>%20%0A>%20It%20will%20help%20to%20build%20a%20solid%20infrastructure%20from%20the%20ground%20up%20and%20make%20the%20H-ROS%20information%20model%20a%20reference%20document%20to%20create%20standard%20robotic%20modules.%0A>%20%0A>%20%0A>%20Thank%20you%20for%20your%20time!%20And%20if%20anybody%20wants%20to%20know%20more%20about%20the%20**H-ROS%20information%20model**,%20come%20talk%20to%20me!%20Thank%20you!%20%0A>%20%0A>%20%0A>%20%0A>%20Irati%20Zamalloa%0A>%20_Industrial%20Design%20Engineer_%0A>%20irati@erlerobotics.com%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20---%0A>%20%5BVisit%20Topic%5D(https://discourse.ros.org/t/pushing-ros-to-get-standardized-roscon-2017-lightning-talk/2812/1)%20or%20reply%20to%20this%20email%20to%20respond.%0A>%20%0A>%20%0A>%20If%20you%20do%20not%20want%20to%20receive%20messages%20from%20ros-users%20please%20use%20the%20unsubscribe%20link%20below.%20If%20you%20use%20the%20one%20above,%20you%20will%20stop%20all%20of%20ros-users%20from%20receiving%20updates.%0A>%20______________________________________________________________________________%0A>%20ros-users%20mailing%20list%0A>%20ros-users@lists.ros.org%0A>%20http://lists.ros.org/mailman/listinfo/ros-users%0A>%20Unsubscribe:%20<http://lists.ros.org/mailman//options/ros-users>%0A>%20%0A>%20 "Besvar denne besked")
(text/plain)