View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010138 | 10000-006: Mappings | Spec | public | 2025-02-04 13:20 | 2025-02-04 17:19 |
| Reporter | BjarneBostrom | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.05.04 | ||||
| Summary | 0010138: JSON new encodings do not define the "non-reversible-use-body-only Variant" encoding that is used by Part 14 | ||||
| Description | The https://reference.opcfoundation.org/Core/Part14/v105/docs/A.3.2 defines http://opcfoundation.org/UA/PubSub-Layouts/JSON-Minimal HeaderLayoutURI and gives an example That line is missing from the new COMPACT/VERBOSE encodings. I could only find the Part 14 saying in https://reference.opcfoundation.org/Core/Part14/v105/docs/7.2.5.4: The https://reference.opcfoundation.org/Core/Part6/v105/docs/5.4.1, has mention of "The VerboseEncoding also supports the RawData mode..." that UaType + UaTypeId fields are excluded (btw, could this be used with the COMPACT encoding?), but that leaves the JSON Object with sole Value field (+Dimensions for multidim fields) like: In my opinion most likely the RawData format should be specified that the 'Value' field of Variant is in-lined (for the top-lvl Variants) for scalar and 1-dim array cases (and for multidim it should be what would currently happen, JSON object with Value and Dimension fields of the Variant). | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-04 13:20 | BjarneBostrom | New Issue | |
| 2025-02-04 17:18 | Jim Luth | Note Added: 0022365 | |
| 2025-02-04 17:19 | Jim Luth | Status | new => closed |
| 2025-02-04 17:19 | Jim Luth | Resolution | open => no change required |