Hi Prof. Corke,
Posting this as a research-collaboration proposal. I'm Ido Yahalomi, maintainer of URML, an Apache 2.0 specification for substrate-neutral robot intent.
robotics-toolbox-python is the global standard educational robotics teaching codebase. URML proposes a complementary surface: URML primitive vocabulary at the intent layer composed above the Toolbox's kinematics-and-dynamics math layer. Programs written against the Toolbox in a course or RVC3 example chapter can compile to URML primitives, then retarget to ROS 2 / Isaac / MuJoCo substrates without re-teaching the underlying math.
A speculative ask: would a future edition of Robotics, Vision and Control consider a URML primitive-vocabulary appendix or worked example? URML expects this is below the base case but documents the ask honestly. The more realistic asks are (a) a documented cross-citation in the Toolbox README, (b) URML primitive vocabulary as a module in QUT's AuSRoS 2025+ ROS 2 labs, (c) URML mention in ARC Centre of Excellence outreach materials (where Centre leadership decides).
This is proposal-only, part of URML's Move #6 outreach (US-friendly university robotics labs). Twelfth and final RFC; closes the wave.
Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0091-qut-centre-for-robotics-outreach.md
Feedback we'd value
- robotics-toolbox-python cross-link. Documented cross-citation in URML's reference/cobot-runtime/ README welcome (vice versa, would the Toolbox mention URML)?
- RVC3 chapter (speculative). Future edition or workshop URML primitive-vocabulary content?
- AuSRoS 2025+ teaching integration. Candidate teaching module in QUT's annual ROS 2 labs?
- Centre for Robotics outreach materials. URML mention in ARC Centre outreach (where Centre leadership decides)?
- Personal handle vs institutional org. Is petercorke/* the right URML engagement surface, or a separate Centre-level GitHub?
- Conformance lane?
- Anything else.
Thanks for the Robotics Toolbox lineage (MATLAB → Python → ROS 2), RVC3, and the QUT Centre's institutional role in Australian robotics. URML's teaching-artifact story benefits enormously from the foundation the Toolbox built.
Ido Yahalomi (URML maintainer, urml.dev)
Hi Prof. Corke,
Posting this as a research-collaboration proposal. I'm Ido Yahalomi, maintainer of URML, an Apache 2.0 specification for substrate-neutral robot intent.
robotics-toolbox-pythonis the global standard educational robotics teaching codebase. URML proposes a complementary surface: URML primitive vocabulary at the intent layer composed above the Toolbox's kinematics-and-dynamics math layer. Programs written against the Toolbox in a course or RVC3 example chapter can compile to URML primitives, then retarget to ROS 2 / Isaac / MuJoCo substrates without re-teaching the underlying math.A speculative ask: would a future edition of Robotics, Vision and Control consider a URML primitive-vocabulary appendix or worked example? URML expects this is below the base case but documents the ask honestly. The more realistic asks are (a) a documented cross-citation in the Toolbox README, (b) URML primitive vocabulary as a module in QUT's AuSRoS 2025+ ROS 2 labs, (c) URML mention in ARC Centre of Excellence outreach materials (where Centre leadership decides).
This is proposal-only, part of URML's Move #6 outreach (US-friendly university robotics labs). Twelfth and final RFC; closes the wave.
Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0091-qut-centre-for-robotics-outreach.md
Feedback we'd value
Thanks for the Robotics Toolbox lineage (MATLAB → Python → ROS 2), RVC3, and the QUT Centre's institutional role in Australian robotics. URML's teaching-artifact story benefits enormously from the foundation the Toolbox built.
Ido Yahalomi (URML maintainer, urml.dev)