Proposal: URML (substrate-neutral robot intent) capability-manifest mapping for Emlid Reach RTK GNSS

[idoco2003]

Hi @emlid team,

Proposing a URML v0.1 capability-manifest mapping for the Emlid Reach RS3 / M2 / RX low-cost multi-band RTK GNSS receivers over ntripbrowser and the standard NMEA / UBX output. URML (Apache-2.0) is a substrate-neutral spec for robot intent.

Shared GNSS-class Spec-RFC gap with RFC-0119 / RFC-0120 / RFC-0133.

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/0134-emlid-rtk-outreach.md

Questions worth maintainer input on:

1. Engagement-channel preference. GitHub Issue on ntripbrowser or other active repo, Emlid forum, or vendor support email?
2. GitHub cadence. Vendor org cadence remain as-is, or planned for revival?
3. GNSS-class manifest fields (shared with RFC-0119 / RFC-0120 / RFC-0133).
4. NTRIP correction-source declaration. Manifest pattern for caster URL / mountpoint / auth-method-class?
5. Adapter home. URML repo (reference/sensor-runtime/), Emlid-maintained, or cross-citation only?
6. 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.