View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007294 | 10000-006: Mappings | Spec | public | 2021-09-22 18:51 | 2021-09-24 12:25 |
| Reporter | Martin Regen | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.00 RC1 | ||||
| Summary | 0007294: Clarify non reversible JSON can not omit default values (for numbers) or information may be lost | ||||
| Description | Follow up on discussion 09/22/21 face 2 face on Part6 5.1.2 Built in Types default values. In the reversible JSON encoding fields can be omitted without losing information, because the decoder can fill in the default value, e.g. 0.0 for a float. In the non reversible case if a field with a default value is omitted, there might be information loss. At least numbers should not be omitted in such a case. e.g. a sensor may produce values of 0,1,0, with a minimal PubSub encoding, the value might be omitted and the decoder may loose the 0 alues because they were not encoded. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Added clear rules that explain how fields are encoded for Structures in 5.4.6 and 5.4.7 in Draft 6. |
|
|
Agreed to changes in 1.05.1 Draft 6. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-09-22 18:51 | Martin Regen | New Issue | |
| 2021-09-22 18:57 | Randy Armstrong | Project | 10000-005: Information Model => 10000-006: Mappings |
| 2021-09-24 05:26 | Randy Armstrong | Assigned To | => Randy Armstrong |
| 2021-09-24 05:26 | Randy Armstrong | Status | new => resolved |
| 2021-09-24 05:26 | Randy Armstrong | Resolution | open => fixed |
| 2021-09-24 05:26 | Randy Armstrong | Note Added: 0014990 | |
| 2021-09-24 12:25 | Jim Luth | Status | resolved => closed |
| 2021-09-24 12:25 | Jim Luth | Fixed in Version | => 1.05 |
| 2021-09-24 12:25 | Jim Luth | Note Added: 0014999 |
