View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006672 | 10000-003: Address Space | Spec | public | 2021-03-19 13:46 | 2021-09-27 19:02 |
Reporter | Herbert Oppmann | Assigned To | Jeff Harding | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Summary | 0006672: Types which represent a collection of bits | ||||
Description | For types, which represent a collection of bits, OPC UA offers three possibilities: 1) The OptionSet DataType defined in Part 3 While the 3rd possibility is often used in namespace 0, it is barely visible in the specification. Only in Part 3, Table 16, at the OptionSetValues property, does it say "applies for OptionSet DataTypes and UInteger DataTypes". It's just these three words. And in Part 5, OptionSetType mentions the OptionSet DataType and gives advice when to use what, but does not mention the third possibility. Suggestion: Create a general chapter about "Types which represent a collection of bits", e.g. in Part 3, chapter 8.1. Mention the three possibilities and give advice when to use what. Then the paragraph with the advice in Part 5 at OptionSetType can be removed. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0007309 | assigned | Jeff Harding | OptionSet Examples needed |
|
Not for 1.05.0 RC |
|
During 1.05 RC review we agreed that in future a section which provides examples of when the alternative approaches for OptionSet should be considered. |
Date Modified | Username | Field | Change |
---|---|---|---|
2021-03-19 13:46 | Herbert Oppmann | New Issue | |
2021-04-06 15:52 | Jim Luth | Note Added: 0014166 | |
2021-04-06 15:52 | Jim Luth | Assigned To | => Jeff Harding |
2021-04-06 15:52 | Jim Luth | Status | new => assigned |
2021-09-27 19:01 | Jeff Harding | Note Added: 0015034 | |
2021-09-27 19:02 | Jeff Harding | Relationship added | related to 0007309 |