Hi GoPiGo3 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 GoPiGo3 is a lovely, clear beginner robot, and a simple well-defined platform is an ideal place to show the natural-language-to-validated-intent path end to end.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The mapping: the GoPiGo3 has a small, clear set of capabilities (drive, turn, sensors). That maps cleanly onto a URML capability manifest, so "drive forward two metres, then stop if you see an obstacle" can become a typed, validated intent and then GoPiGo3 API calls. URML adds the typed validation and the English layer; the GoPiGo3 API stays the runtime. For a learner, seeing an instruction become a checked plan -- and seeing why an impossible instruction is rejected -- is exactly the kind of thing a small platform makes vivid.
Two real questions: (1) is an English-to-validated-intent front door useful for a beginner robot like the GoPiGo3? (2) Does the GoPiGo3's capability set map cleanly onto a URML capability manifest?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0572-gopigo3-outreach.md
Thanks for the GoPiGo3; an approachable robot with a clean API is exactly where an English front door is easiest to make real.
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 GoPiGo3 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 GoPiGo3 is a lovely, clear beginner robot, and a simple well-defined platform is an ideal place to show the natural-language-to-validated-intent path end to end.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The mapping: the GoPiGo3 has a small, clear set of capabilities (drive, turn, sensors). That maps cleanly onto a URML capability manifest, so "drive forward two metres, then stop if you see an obstacle" can become a typed, validated intent and then GoPiGo3 API calls. URML adds the typed validation and the English layer; the GoPiGo3 API stays the runtime. For a learner, seeing an instruction become a checked plan -- and seeing why an impossible instruction is rejected -- is exactly the kind of thing a small platform makes vivid.
Two real questions: (1) is an English-to-validated-intent front door useful for a beginner robot like the GoPiGo3? (2) Does the GoPiGo3's capability set map cleanly onto a URML capability manifest?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0572-gopigo3-outreach.md
Thanks for the GoPiGo3; an approachable robot with a clean API is exactly where an English front door is easiest to make real.
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.