Proposal: URML (substrate-neutral robot intent) capability-manifest mapping for Roboception rc_visard / rc_cube

[idoco2003]

Hi @roboception team,

Proposing a URML v0.1 capability-manifest mapping for Roboception rc_visard (3D camera) and rc_cube (compute box) over cvkit and the GenICam-compliant API surface. URML (Apache-2.0) is a substrate-neutral spec for robot intent.

rc_visard's industrial 3D-vision posture (GenICam compliance, in-process pose-estimation, vendor-supported MoveIt integration) places it cleanly in URML's cameras + sensors manifest blocks, with the same color + per-point-attributes gap on point clouds.

This is proposal-only, part of URML's Move #10 outreach (perception-vendor wave, 29 engageable RFCs).

Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0112-roboception-outreach.md

Questions worth maintainer input on:

1. GenICam compliance declaration. Should URML's manifest declare GenICam compliance as a sensor capability so generic GenICam adapters interoperate?
2. In-process detection / pose-estimation declaration. Manifest field for vendor-supported detection classes?
3. Adapter home. URML repo, Roboception-maintained, or both?
4. Conformance listing. README link to URML's compatible-runtimes registry once a working adapter ships?
5. Anything else.

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

---

Authoring disclosure: URML is the invention of Ido Yahalomi. The outreach prose is AI-assisted (Claude, under the maintainer's review). See VIBE.md. The maintainer reads and approves every post before it ships. Reviewers who prefer human-only correspondence are welcome to say so.