WG SXL Core 2024-06-18

[emiltin]

Participants

Toni, Henri, Christophe, Matti, Martin, David, Emil

Core 3.2.2

rsmp_schema: We're missing a PR for 3.2.2, uodate rsmp gem code to support 3.2.2.
rsmp: pull in latest schema.
validator: pull in latest gems, update connect tests to support 3.2.2.
simulator: ready, but release awaits core spec release.

cO attribute

The intention was to be make the implementation easier, by referencing a RPC in an internal API. But that's history now. In fact this attribute is not needed, because each function always uses the same cO.
But some commands use the same cO, so they are not currently unique between commands.

Originally the ideas was to make it easier for the suppliers because you could directly address their internal function, but it's fragile and not might differ between vendors.

cO could be viewed as a subcommand, which could be made optional:
M0001
M0001/force
M0001/schedule

Remove: Need changes to both senders and receivers
Optional: Need changes to receivers, but senders don't need changes.

We will mark cO as depreciated, and remove it in a later version.

ntsOId and xNId attributes

rsmp-nordic/rsmp_core#9
They are used in Sweden for grouping/nesting of components. But the ntsOId always just refers to the main component,. And xNId refers to the supervisor system, and this complicates configuration of the device.

For RSMP 4 build on MQTT, topic paths will handle nested component ids, an there is no longer any need for ntsOId and xNId to deal with grouping/nesting:

KK+2342/tc/1/sg/7
KK+2342/tc/2/sg/1

We will mark them depreciated, and remove it in a later version.