RELAY spec v1.9 (release) adds §13.7, a normative cross-language library-architecture convention so the same protocol in Go/Rust/C++ is structurally common (same module taxonomy, identical module names, idiomatic packaging aside). go-LIN currently targets spec 1.0 and passes relay conform.
§13.7 alignment for go-LIN
Confirm §13.7 module names (adapt, mock, …).
§13.7 essentials: the RELAY adapter module is named adapt (entry point adapt(<iface>) → Node); the in-process virtual transport is virtual (not virtual_bus); mock is mandatory; the standard module-name registry (socketcan, safety, dbc, isotp, j1939, obdii, uds, recorder, codegen, the RCP control-plane set, bridges, capi) uses identical names across languages.
Spec-version uplift
Uplift the targeted spec version from 1.0 to 1.9 (SpecVersion/version output) once aligned, so relay versions shows the fleet converged on the current spec.
No changes are requested to RELAY. Verify with relay conform --strict <binary> after.
RELAY spec v1.9 (release) adds §13.7, a normative cross-language library-architecture convention so the same protocol in Go/Rust/C++ is structurally common (same module taxonomy, identical module names, idiomatic packaging aside). go-LIN currently targets spec 1.0 and passes
relay conform.§13.7 alignment for go-LIN
Confirm §13.7 module names (adapt, mock, …).
§13.7 essentials: the RELAY adapter module is named
adapt(entry pointadapt(<iface>) → Node); the in-process virtual transport isvirtual(notvirtual_bus);mockis mandatory; the standard module-name registry (socketcan,safety,dbc,isotp,j1939,obdii,uds,recorder,codegen, the RCP control-plane set, bridges,capi) uses identical names across languages.Spec-version uplift
Uplift the targeted spec version from 1.0 to 1.9 (
SpecVersion/versionoutput) once aligned, sorelay versionsshows the fleet converged on the current spec.No changes are requested to RELAY. Verify with
relay conform --strict <binary>after.