View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005589 | 10000-003: Address Space | Spec | public | 2020-04-24 10:48 | 2020-04-28 17:46 |
| Reporter | Hock, Christian | Assigned To | Jeff Harding | ||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0005589: Clarification for the abstract DataTypes "BaseDataType", "Number", "UInteger" and "Integer" needed | ||||
| Description | An customer created an SubType from UInteger named "halfByte".
The argumentation from him - as it is described in Part 3-V1.04 - he should be able (allowed) to do this:
A good Solution - especially for interoperability of de-/encoding which is defined by our OPC UA Specs:
| ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Abstract datatypes which do not have an encoding defined in Part 6 can't actually be subtyped since there is no way for the code to determine what concrete encoding should be used. The concrete types defined for an abstract type can subtyped. Added the following sentence to Part 3's definitions of BaseDataType, Number, Integer and UInteger. "This abstract DataType does not have an encoding defined in OPC 10000-6 and therefore can not be directly subtyped." |
|
|
Agreed to changes in telecon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-04-24 10:48 | Hock, Christian | New Issue | |
| 2020-04-28 16:37 | Jim Luth | Assigned To | => Jeff Harding |
| 2020-04-28 16:37 | Jim Luth | Status | new => assigned |
| 2020-04-28 16:43 | Jeff Harding | Status | assigned => resolved |
| 2020-04-28 16:43 | Jeff Harding | Resolution | open => fixed |
| 2020-04-28 16:43 | Jeff Harding | Fixed in Version | => 1.05 |
| 2020-04-28 16:43 | Jeff Harding | Note Added: 0012006 | |
| 2020-04-28 17:46 | Jim Luth | Status | resolved => closed |
| 2020-04-28 17:46 | Jim Luth | Note Added: 0012010 |