Hi iRobot Education maintainers,
URML (urml.dev) is a small, Apache-2.0 language for robot intent: an English instruction becomes a typed primitive, validated against the robot's declared capabilities and a safety envelope, then dispatched. The Create 3 is a clean, well-documented educational robot with a ROS 2 interface, which makes it an ideal place to show the natural-language-to-validated-intent path.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The mapping: the Create 3 exposes a well-defined set of actions over ROS 2. That maps onto a URML capability manifest, so "drive a square, then dock" can become a typed, validated intent that dispatches through the Create 3's existing ROS 2 interface. URML adds the typed validation and the English layer; the Create 3 stays the runtime. As a teaching robot with strong docs, it is a natural place to make the intent-and-validation story visible to learners.
Two real questions: (1) is an English-to-validated-intent front door useful for the Create 3 in an educational setting? (2) Does the Create 3's ROS 2 action set map cleanly onto a URML capability manifest?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0575-create3-docs-outreach.md
Thanks for the Create 3 docs; a well-documented ROS 2 teaching robot is exactly where an English front door can be both useful and honest about what it does.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see https://github.com/URML-MARS/URML/blob/main/VIBE.md). Human-only correspondence available on request.
Hi iRobot Education maintainers,
URML (urml.dev) is a small, Apache-2.0 language for robot intent: an English instruction becomes a typed primitive, validated against the robot's declared capabilities and a safety envelope, then dispatched. The Create 3 is a clean, well-documented educational robot with a ROS 2 interface, which makes it an ideal place to show the natural-language-to-validated-intent path.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The mapping: the Create 3 exposes a well-defined set of actions over ROS 2. That maps onto a URML capability manifest, so "drive a square, then dock" can become a typed, validated intent that dispatches through the Create 3's existing ROS 2 interface. URML adds the typed validation and the English layer; the Create 3 stays the runtime. As a teaching robot with strong docs, it is a natural place to make the intent-and-validation story visible to learners.
Two real questions: (1) is an English-to-validated-intent front door useful for the Create 3 in an educational setting? (2) Does the Create 3's ROS 2 action set map cleanly onto a URML capability manifest?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0575-create3-docs-outreach.md
Thanks for the Create 3 docs; a well-documented ROS 2 teaching robot is exactly where an English front door can be both useful and honest about what it does.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see https://github.com/URML-MARS/URML/blob/main/VIBE.md). Human-only correspondence available on request.