View Issue Details

IDProjectCategoryView StatusLast Update
001034810000-014: PubSubSpecpublic2025-07-01 15:53
ReporterRandy Armstrong Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Version1.05.05 RC2 
Target Version1.05.06 
Summary0010348: DataSetFieldId serves no purpose in JSON encoding.
Description

Fields are uniquely identified by their Name and every value has the the Name in it.
The order cannot be used to determine the relationship between a field value and the field metadata because JSON objects are unordered sets.

The DataSetFieldId should be optional when using the JSON encoding.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2025-05-30 10:01

developer   ~0022809

The DataSetFieldId is essential for the handling of configuration changes between versions where a Reader is configured to process one version and to be able to check if the fields he is using are still in the dataset even if the order may have changed.

Jim Luth

2025-07-01 15:53

administrator   ~0023055

Agreed to no-fix in web meeting. (Randy reluctantly agreed too.)

Issue History

Date Modified Username Field Change
2025-05-30 08:26 Randy Armstrong New Issue
2025-05-30 10:00 Matthias Damm Assigned To => Matthias Damm
2025-05-30 10:00 Matthias Damm Status new => assigned
2025-05-30 10:01 Matthias Damm Status assigned => resolved
2025-05-30 10:01 Matthias Damm Resolution open => won't fix
2025-05-30 10:01 Matthias Damm Note Added: 0022809
2025-07-01 15:53 Jim Luth Status resolved => closed
2025-07-01 15:53 Jim Luth Note Added: 0023055