View Issue Details

IDProjectCategoryView StatusLast Update
001014610000-014: PubSubSpecpublic2025-02-13 16:26
ReporterMatthias Damm Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version1.05.04 
Target Version1.05.06 RC1 
Summary0010146: Rules for DataSetMessage JSON encoding need more details
Description

7.2.5.4 DataSetMessage
There is text that defines special handling on top level:
If the FieldEncoding1 is FALSE in the DataSetMessageContentMask, the Variant at the top level of a field is encoded as a JSON value containing only the value of the Body field. If this Variant contains an ExtensionObject, the ExtensionObject shall be encoded as a Structure without the UaTypeId field. This also applies to the Variant in a DataValue at the top level of a field.

This does not cover the special cases of having fields with abstract type or allow subtype.
We need to describe all special cases

Additional Information

Attached is a proposal from Randy

TagsNo tags attached.
Attached Files
Commit Version
Fix Due Date

Relationships

related to 0009987 assignedMatthias Damm JSON field with multidimensional arrays with RawData-Flag 
related to 0010147 assignedMatthias Damm Discovery messages do not define the JSON encoding to use 
related to 0010150 assignedMatthias Damm JSON Encoding of Enumeration in a DataSetMessage field 
related to 0010154 assignedMatthias Damm Describe handling of Bad and Uncertain status in JSON Variant field encoding 

Activities

Issue History

Date Modified Username Field Change
2025-02-11 12:48 Matthias Damm New Issue
2025-02-11 12:48 Matthias Damm File Added: CompactVerboseRawDiscussion.docx
2025-02-11 12:48 Matthias Damm Relationship added related to 0009987
2025-02-11 13:54 Matthias Damm Relationship added related to 0010147
2025-02-12 09:02 Matthias Damm Relationship added related to 0010150
2025-02-12 16:18 Matthias Damm Relationship added related to 0010154