WG Core 2026-01-27

[emiltin]

Participants

Marc Le-Douarain
Rafael Figueiredo
Marek Zukal
Emil Tin

Always send StatusUpdate after subscription request

PR at rsmp-nordic/rsmp_core#270
Historically status was always send after subscription, but it was changed to to special cases related to traffic data. But this creates issues.
We will change it back to always sending a status update after a subscription is received.
PR merged.

Multiple SXLs

PR rsmp-nordic/rsmp_core#261.

What problem could arise?
How can it be tested?

Reasons:
Ability to split large SXL into smaller, reusable modules
To avoid duplications between SXLs
Avoid issue with incompatible SXL version, if they rely on each other

If we split SXLs, can we add parameters to existing object? No.

Explain that dependencies between SXL can be, like signal plan being an integer, not a string. It's dependencies between specifications.
It's hard to automatically test dependencies between SXLs if it can be about behaviour, etc.

Do we need this kind of dependency system, or can it be simplified?
SXLs can define parts, and you choose which parts you implement. We would not have any dependencies between SXLs. But this mean you cannot create independent extensions, drop-in replacements, etc.

We'll consider the options until the next meeting, and continue this important disussion.

SXL name or id?

SXL Prefix in Version message

Uppercase letters