View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
001015010000-014: PubSubSpecpublic2025-02-12 09:022025-03-13 15:04
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.04 
Target Version1.05.06 RC1Fixed in Version1.05.06 RC1 
Summary0010150: JSON Encoding of Enumeration in a DataSetMessage field
Description

The DataSetMessage field is a Variant and Part 6 defines:
When an Enumeration is encoded in a Variant the Type field is Int32.

This is becaus a pure Variant does not have the Enumeration information since the value is Int32 in the Variant.

But in the DataSetMessage field we have the MetaData available. Therefore we would be able to use the string encoding form as we would do in a structure. Since we want to handle the fields of a DataSetMessage like a Structure, it would make sense to use the string encoding.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0010146 closedMatthias Damm Rules for DataSetMessage JSON encoding need more details 

Activities

Matthias Damm

2025-02-13 14:31

developer   ~0022392

Discussed in MQTT plug-fest wrap-up - we have the informaiton and therefore encode the name_number format for all value ranks.

TBD: Add to clarification table with examples

Matthias Damm

2025-02-27 21:33

developer   ~0022423

Added following clarificaiton to new text in
7.2.5.4 DataSetMessage
Therefore the DataSet fields in a DataSetMessage for VerbosetEncoding are encoded like the fields of a Structure where the fields are described by the FieldMetaData. This includes fields with Enumeration DataTypes which are encoded as Verbose Enumeration with the knowledge about the Enumeration DataType.

Added example to
Table 186 – DataSet field VerboseEncoding examples

Jim Luth

2025-03-13 15:04

administrator   ~0022530

Agreed to changes in F2F meeting.

Issue History

Date Modified Username Field Change
2025-02-12 09:02 Matthias Damm New Issue
2025-02-12 09:02 Matthias Damm Relationship added related to 0010146
2025-02-13 14:29 Matthias Damm Assigned To => Matthias Damm
2025-02-13 14:29 Matthias Damm Status new => assigned
2025-02-13 14:31 Matthias Damm Note Added: 0022392
2025-02-27 21:33 Matthias Damm Status assigned => resolved
2025-02-27 21:33 Matthias Damm Resolution open => fixed
2025-02-27 21:33 Matthias Damm Fixed in Version => 1.05.06 RC1
2025-02-27 21:33 Matthias Damm Note Added: 0022423
2025-03-13 15:04 Jim Luth Status resolved => closed
2025-03-13 15:04 Jim Luth Note Added: 0022530