View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008666 | 10000-006: Mappings | Spec | public | 2023-01-31 14:31 | 2023-04-04 16:15 |
Reporter | Frank Fischer | Assigned To | Randy Armstrong | ||
Priority | high | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
Product Version | 1.05.01 | ||||
Summary | 0008666: JSON encoding rules for built-in types are confusing and inconsistent | ||||
Description | For Structures the rules are quite simple and clearly described in "Table 38 – JSON Encoding Rules for Structures": It seems the intention is to apply these rules also to built-in types which are encoded as JSON objects, as many of these state similar rules for their fields. However these rules differ in details from the above rules, e.g. the DataValue states "If a field has a null or DefaultValue it is omitted" without distinguishing between reversible and non-reversible encoding which means it must be omitted in both encodings. So if the intention is to use the Structure rules for the built-in types this should be explicitly stated in the General section and the rules stated for individual built-in types should be removed unless the built-in type actually deviates from the general rules. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Built in types have special rules which is why they are built in types. |
|
Agreed to no-fix in web meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-01-31 14:31 | Frank Fischer | New Issue | |
2023-03-23 18:06 | Randy Armstrong | Assigned To | => Randy Armstrong |
2023-03-23 18:06 | Randy Armstrong | Status | new => resolved |
2023-03-23 18:06 | Randy Armstrong | Resolution | open => no change required |
2023-03-23 18:06 | Randy Armstrong | Note Added: 0019004 | |
2023-04-04 16:15 | Jim Luth | Status | resolved => closed |
2023-04-04 16:15 | Jim Luth | Note Added: 0019100 |