Discussed in MQTT plug-fest wrap-up meeting:

We decided to skip (c) and just sent the value plus Uncertain_SubNormal in this case.
Still need to describe the cases in the extended DataSetMessage clarification section.

One open issue is left for RawData and Minimal layout:
The table defines that a bad status results in use of default value for the field and a uncertain code in the header. But the Minimal layout does not have a header.

Solution:
We copy the table, change the old one to be just valid for UADP.
The JSON version would handle RawData like Variant and would send the bad status instead of the value.

Renamed existing table
Table 34 – DataSetMessage field representation options
to
Table 34 – UADP DataSetMessage field representation options

Adde new table
Table 35 – JSON DataSetMessage field representation options
as copy of Table 34

Made following changes:
Remove the RawData rows from the table
Added RawData as equal to Variant
For Variant with Uncertain Status changed handling to "A uncertain status is ignored on the field level and results in a header status of Uncertain_SubNormal"

Agreed to changes in F2F meeting.