View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010150 | 10000-014: PubSub | Spec | public | 2025-02-12 09:02 | 2025-02-13 14:31 |
| Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Product Version | 1.05.04 | ||||
| Target Version | 1.05.06 RC1 | ||||
| Summary | 0010150: JSON Encoding of Enumeration in a DataSetMessage field | ||||
| Description | The DataSetMessage field is a Variant and Part 6 defines: 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. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| related to | 0010146 | new | Rules for DataSetMessage JSON encoding need more details |
|
|
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 |
| 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 |
