This is related to 1.05.06 Draft 3 (but such version doesn't exist in the Product Version dropdown above)

Table 186 "DataSet field VerboseEncoding examples" within Part 14 '7.2.5.4 DataSetMessage' doesn't contain examples of DataValue JSON form.
For the Int32 in ValueRank Any example it is:
{
"Value": 11
}
(Variant form due to Any, but no UaType since it is known from the metadata). The question is that should DataValue form behave similarly? Or should it be:
{
"UaType" : 6,
"Value" : 11,
"SourceTimestamp" : "2025-05-22T12:27:03.000Z",
"ServerTimestamp" : "2025-05-22T12:27:03.174Z"
}
i.e. Should the UaType field be present or not.

In 6.2.4.2 in Table 32 for the DataSetFieldContentMask before bit-rows begin it is said If the RawData flag is set, the fields are represented as RawData and all other bits are ignored. However later in the rawdata row itself "All other field related flags shall be ignored if this flag is set for UADP message mapping.".

Thus, is RawData useable in JSON together with the other bits? If yes, at least when RawData is then set the UaType/UaTypeId doesn't appear, but it is still ambiguous should it follow the same rules as normal Variant encoding (i.e. field not used when it would be the same as in the metadata).