View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010153 | 10000-006: Mappings | Spec | public | 2025-02-12 11:34 | 2025-02-13 16:27 |
Reporter | BjarneBostrom | Assigned To | Randy Armstrong | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 1.05.04 | ||||
Summary | 0010153: Section 5.4.1 text (JSON General) should clarifiy 'fields' to be Structure or JSON fields | ||||
Description | https://reference.opcfoundation.org/Core/Part6/v105/docs/5.4.1 first says: It is possible to interpret that to mean ALL JSON fields. However, based on the PubSub new JSON formats Plugfest, I think here actually 'Structure fields' are intended instead. Because e.g. DataValue (https://reference.opcfoundation.org/Core/Part6/v105/docs/5.4.2.18) e.g. for the status field it says "Not encoded if the value is Good (0).", which would have conflicted the wording if it would have been about JSON fields (i.e. do you or not put it in Verbose when it is 0). If the wording is changed to something like: | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Agreed in MQTT plug-fest wrap up that "The CompactEncoding omits all fields with" should be more precise since fields in built-in types have their own rules |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-02-12 11:34 | BjarneBostrom | New Issue | |
2025-02-13 14:36 | Matthias Damm | Assigned To | => Randy Armstrong |
2025-02-13 14:36 | Matthias Damm | Status | new => assigned |
2025-02-13 14:37 | Matthias Damm | Note Added: 0022393 |