View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009811 | 10000-003: Address Space | Spec | public | 2024-09-02 12:29 | 2025-02-04 16:48 |
Reporter | Thomas Merk | Assigned To | Jim Luth | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
Product Version | 1.05.03 | ||||
Summary | 0009811: Unclear behaviour on importing value on VariableType | ||||
Description | In specification the Value attribute is mentioned as "optional". It is not clearly specifioed what shall be the result when importing a NodeSet2.xml file containing a VariableType where the <Value> tag is missing. Does this mean that the attribute is not supported at al for such a VariableType? However it seems that .Net Stack default te value to Bad_AttributeIdInvalid. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
The Value attribute is mandatory for variables. https://reference.opcfoundation.org/Core/Part3/v105/docs/5.9 |
|
We recently clarified what is used as Value if it is not provided in the nodeset. See 0007307 This is independent of the question if the optional attribute should be filled/provided. |
|
The Value attribute is optional on VariableTypes so if it is missing then the proper return value is Bad_AttributeIdInvalid as implemented in the .NET stack. |
|
Part 3 is clear on the required behavior. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-09-02 12:29 | Thomas Merk | New Issue | |
2024-09-02 13:47 | Peter Wehrfritz | Note Added: 0021646 | |
2024-09-24 13:33 | Matthias Damm | Note Added: 0021801 | |
2025-02-04 16:46 | Jim Luth | Note Added: 0022361 | |
2025-02-04 16:48 | Jim Luth | Assigned To | => Jim Luth |
2025-02-04 16:48 | Jim Luth | Status | new => closed |
2025-02-04 16:48 | Jim Luth | Resolution | open => no change required |
2025-02-04 16:48 | Jim Luth | Note Added: 0022362 |