View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009860 | 10000-003: Address Space | Spec | public | 2024-09-24 13:43 | 2025-02-04 16:31 |
Reporter | Matthias Damm | Assigned To | Jeff Harding | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Product Version | 1.05.03 | ||||
Summary | 0009860: Clarification needed for AllowNulls property | ||||
Description | From OPC UA Part 4 it was always invalid to have DataValue with a NULL Variant value with a Good StatusCode. We recently added a dedicated Bad_NoValue StatusCode for the case where no value is provided 0007307 e.g. when loading variables from a nodeset that does not provide a value. The AllowNulls property implies that a NULL Variant is a valid value for any DataType as long as the server has AllowNulls set to True. As discussed in the working group F2F meeting today, this makes only sense for null-able DataTypes. The null-able DataTypes are defined in OPC UA Part 6. Null Variant would only be valid for BaseDataType. | ||||
Tags | No tags attached. | ||||
Commit Version | 1.05.06 RC1 | ||||
Fix Due Date | 2025-04-15 | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-09-24 13:43 | Matthias Damm | New Issue | |
2025-02-04 16:30 | Jim Luth | Assigned To | => Jeff Harding |
2025-02-04 16:30 | Jim Luth | Status | new => assigned |
2025-02-04 16:31 | Jim Luth | Commit Version | => 1.05.06 RC1 |
2025-02-04 16:31 | Jim Luth | Fix Due Date | => 2025-04-15 |