Proposal: URML (substrate-neutral robot intent) cross-citation for VESC — and a license-clarification ask

[idoco2003]

Hi @vedderb,

Proposing a URML v0.1 capability-manifest cross-citation for the VESC Project over vedderb/bldc. URML (Universal Robot Language, Apache-2.0) is an open spec for substrate-neutral robot intent.

VESC is the open-source brushless ESC widely deployed in e-bikes, e-scooters, e-skateboards, and increasingly in robotics applications (mobile-base drive, hub motors, high-power applications where ODrive / Moteus are overspec'd or undersized). URML's manifest can declare VESC class controllers with their distinctive power-scalability — sub-kilowatt to multi-kilowatt — and protocol class (VESC-CAN, VESC-UART, VESC-USB). License-clarification ask is the gating fact: the repo's license is not visible via the GitHub SPDX API; an explicit declaration would clarify URML's adapter-grade reuse boundaries.

This is proposal-only, posted as part of URML's Move #13 outreach (15 engageable RFCs in this wave).

Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0180-vesc-bldc-outreach.md

Questions worth maintainer input on:

1. License clarification. Can vedderb/bldc get an explicit OSI license declaration (GPL-3.0 per LICENSE file; SPDX visibility upstream)?
2. Actuator-controller substrate manifest fields. Same shared question across the Move-13 motor-controller RFCs.
3. Power-class declaration. Should URML's manifest declare VESC's power-class (sub-kilowatt to multi-kilowatt)?
4. Bridge home. Cross-citation only (recommended pending license), URML repo (reference/actuator-runtime/VescAdapter), or VESC-maintained?
5. Conformance listing. Would the VESC project consider a README link to URML's compatible-runtimes registry once a working cross-citation ships?
6. Anything else.

Ido Yahalomi (URML maintainer, urml.dev, greenvh@gmail.com)

---

AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.