Hi micro-ROS team,
URML (urml.dev) is a small open language (Apache-2.0) for robot intent: an English sentence becomes a validated primitive that is checked against the robot's capabilities before dispatch. URML already has a micro-class robot story (a micro:bit-class manifest and a conservative educational profile); micro-ROS is the substrate that would actually carry that intent onto a real MCU agent. It also extends the same engagement we have at the full DDS layer (Fast DDS, Cyclone DDS) one tier down.
One real question: what grain should a URML manifest use to declare the MCU-tier substrate, just naming micro-ROS, or the agent topology and micro-XRCE-DDS transport?
Full write-up if useful: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0308-micro-ros-outreach.md
Thanks for bringing ROS 2 to microcontrollers.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi micro-ROS team,
URML (urml.dev) is a small open language (Apache-2.0) for robot intent: an English sentence becomes a validated primitive that is checked against the robot's capabilities before dispatch. URML already has a micro-class robot story (a micro:bit-class manifest and a conservative educational profile); micro-ROS is the substrate that would actually carry that intent onto a real MCU agent. It also extends the same engagement we have at the full DDS layer (Fast DDS, Cyclone DDS) one tier down.
One real question: what grain should a URML manifest use to declare the MCU-tier substrate, just naming micro-ROS, or the agent topology and micro-XRCE-DDS transport?
Full write-up if useful: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0308-micro-ros-outreach.md
Thanks for bringing ROS 2 to microcontrollers.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.