View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008544 | 10000-006: Mappings | Spec | public | 2022-12-28 12:51 | 2023-03-23 20:55 |
Reporter | Frank Fischer | Assigned To | Randy Armstrong | ||
Priority | high | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | 1.05.01 | ||||
Fixed in Version | 1.05.03 RC1 | ||||
Summary | 0008544: 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. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
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 |