View Issue Details

IDProjectCategoryView StatusLast Update
000854410000-006: MappingsSpecpublic2023-03-23 20:55
ReporterFrank Fischer Assigned ToRandy Armstrong  
PriorityhighSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product Version1.05.01 
Fixed in Version1.05.03 RC1 
Summary0008544: Clarification for the order of fields in json objects
Description

In the json encoding structures (and also some built-in types like NodeId) are encoded as json objects, which are key-value pairs without ordering. For the binary and XML encoding however the order of fields in structures is important and must be preserved and also in the examples for json encoded values the order is always the same as in the definition. This could easily lead to the impression that json objects are ordered, however a decoder relying on the order would not be correct and could be incompatible with certain encoders.

Thus the json description should explicitly state that json objects are of arbitrary order and decoders cannot rely on the order given by the datatype definition.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2023-03-21 15:44

administrator   ~0018927

Fixed in Draft 3.

Jim Luth

2023-03-23 20:55

administrator   ~0019022

Agreed to changes in Dallas meeting.

Issue History

Date Modified Username Field Change
2022-12-28 12:51 Frank Fischer New Issue
2023-03-21 15:44 Randy Armstrong Assigned To => Randy Armstrong
2023-03-21 15:44 Randy Armstrong Status new => resolved
2023-03-21 15:44 Randy Armstrong Resolution open => fixed
2023-03-21 15:44 Randy Armstrong Note Added: 0018927
2023-03-23 20:55 Jim Luth Status resolved => closed
2023-03-23 20:55 Jim Luth Fixed in Version => 1.05.03 RC1
2023-03-23 20:55 Jim Luth Note Added: 0019022