Hi Unity Robotics team,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: English sentence -> typed primitive -> static validation against a capability manifest and a safety envelope -> dispatch. URML composes above the simulator: validated intent -> ROS-TCP-Connector -> a Unity-simulated robot, with the URDF Importer aligning the robot model to URML's capability manifest.
Before anything else, an honest question: the repo's last push is from late 2024, so I want to check whether Unity Robotics Hub is still maintained and whether this is the right venue, or whether the project has moved. A clear "unmaintained" is a useful answer too.
If it is live: nothing here asks you to change or maintain anything. The one real mapping question is whether ROS-TCP-Connector is the boundary you would expect for "URML primitive -> Unity robot", and at what grain the URDF Importer's output should align with a capability manifest.
Full write-up, with the manifest mapping table: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0326-unity-robotics-hub-outreach.md
One small thing: the GitHub API did not surface an SPDX license id at our verification time. What is the current license?
Thanks for the ROS-TCP and URDF Importer tooling; it shaped how a lot of people bridge Unity and ROS.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi Unity Robotics team,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: English sentence -> typed primitive -> static validation against a capability manifest and a safety envelope -> dispatch. URML composes above the simulator: validated intent -> ROS-TCP-Connector -> a Unity-simulated robot, with the URDF Importer aligning the robot model to URML's capability manifest.
Before anything else, an honest question: the repo's last push is from late 2024, so I want to check whether Unity Robotics Hub is still maintained and whether this is the right venue, or whether the project has moved. A clear "unmaintained" is a useful answer too.
If it is live: nothing here asks you to change or maintain anything. The one real mapping question is whether ROS-TCP-Connector is the boundary you would expect for "URML primitive -> Unity robot", and at what grain the URDF Importer's output should align with a capability manifest.
Full write-up, with the manifest mapping table: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0326-unity-robotics-hub-outreach.md
One small thing: the GitHub API did not surface an SPDX license id at our verification time. What is the current license?
Thanks for the ROS-TCP and URDF Importer tooling; it shaped how a lot of people bridge Unity and ROS.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.