Proposal: URML (substrate-neutral robot intent) cross-citation for SimpleFOC — community FOC library substrate

[idoco2003]

Hi @simplefoc team,

Proposing a URML v0.1 capability-manifest mapping for SimpleFOC over simplefoc/Arduino-FOC. URML (Universal Robot Language, Apache-2.0) is an open spec for substrate-neutral robot intent.

SimpleFOC is the community FOC implementation library URML's manifest can declare for maker / educational brushless deployments where commercial controllers (ODrive, Moteus) are overspec'd or out of budget. URML's manifest declares the FOC-library substrate class + MCU host + driver IC + sensor class as a three-axis declaration; SimpleFOC's library-on-MCU shape is structurally different from vendor-direct hardware controllers, and the community-vs-vendor distinction is informative for downstream consumers.

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/0179-simplefoc-outreach.md

Questions worth simplefoc maintainer input on:

1. FOC-library actuator-class manifest fields. URML's v0.1 has no foc_library actuator class. Spec RFC queued. Manifest field expectations from the SimpleFOC perspective?
2. MCU-host + driver-IC + sensor-class declaration. Three-axis declaration — what granularity is useful?
3. Community-vs-vendor library distinction. Should URML's manifest declare this as a separate field, or implicit via the library identifier?
4. Bridge home. Cross-citation only (recommended), URML repo (reference/actuator-runtime/SimpleFOCAdapter), or community-maintained simplefoc/Arduino-FOC-urml?
5. Conformance listing. Would the simplefoc maintainers 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.