Hi IOES-Lab DAVE maintainers,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: it validates a request against a capability manifest and a safety envelope, then dispatches. DAVE is interesting to URML as an open, ROS 2 / Gazebo underwater simulation and test environment for AUVs and manipulators — a place a URML-validated command can drive a vehicle with no hardware.
Nothing here asks DAVE to adopt, host, or maintain anything. This is a request for comment.
A URML program drives a DAVE vehicle through its ROS 2 / Gazebo interface, the same ROS 2 surface URML's runtime already targets; the sim-first posture matches URML's own. URML's optional validation block records the simulation-fidelity context; DAVE's underwater environment and sensor models make it concrete. Validate-before-actuate behaves identically in sim and on hardware.
Two real questions: (1) Is a validated natural-language intent layer above DAVE interesting as a demonstration / test surface for underwater scenarios? (2) What should a URML manifest declare to describe an underwater deployment honestly (depth rating, buoyancy, thruster configuration, current/visibility limits)?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0400-dave-outreach.md
Thanks for keeping DAVE alive and on modern ROS 2 / Gazebo; an open underwater test bed is genuinely valuable.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi IOES-Lab DAVE maintainers,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: it validates a request against a capability manifest and a safety envelope, then dispatches. DAVE is interesting to URML as an open, ROS 2 / Gazebo underwater simulation and test environment for AUVs and manipulators — a place a URML-validated command can drive a vehicle with no hardware.
Nothing here asks DAVE to adopt, host, or maintain anything. This is a request for comment.
A URML program drives a DAVE vehicle through its ROS 2 / Gazebo interface, the same ROS 2 surface URML's runtime already targets; the sim-first posture matches URML's own. URML's optional validation block records the simulation-fidelity context; DAVE's underwater environment and sensor models make it concrete. Validate-before-actuate behaves identically in sim and on hardware.
Two real questions: (1) Is a validated natural-language intent layer above DAVE interesting as a demonstration / test surface for underwater scenarios? (2) What should a URML manifest declare to describe an underwater deployment honestly (depth rating, buoyancy, thruster configuration, current/visibility limits)?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0400-dave-outreach.md
Thanks for keeping DAVE alive and on modern ROS 2 / Gazebo; an open underwater test bed is genuinely valuable.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.