View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009610 | Part 83: UAFX Offline Engineering | Spec | public | 2024-06-17 15:30 | 2024-10-11 18:37 |
Reporter | Marco Hoch | Assigned To | Jim Luth | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Product Version | 1.00.02 | ||||
Target Version | 1.00.03 | ||||
Summary | 0009610: Reference Type Mapping - Which attributes should be used on an instance | ||||
Description | Table A.7 – Attributes of References InterfaceClass lists all possible attributes of an InterfaceClass. However, it does not describe which attributes are required on an instance. The question is whether any of the attributes are needed on an instance or whether it is sufficient to have them on the type definition as a reference. The Opc2Aml converter creates currently the following attributes on an InterfaceClass:
Since this information is always the same for each InterfaceClassType, this results in redundant information at the instance level. | ||||
Tags | No tags attached. | ||||
|
None of these attributes are useful on an instance. One solution would be to provide these attributes only on as second "type definition" library as proposed in related issue 0009514. |
|
In my revised proposal in the related Mantis issue all four attributes would be marked "OPCUA:TypeOnly": |
|
|
Date Modified | Username | Field | Change |
---|---|---|---|
2024-06-17 15:30 | Marco Hoch | New Issue | |
2024-06-17 15:30 | Marco Hoch | Status | new => assigned |
2024-06-17 15:30 | Marco Hoch | Assigned To | => Jim Luth |
2024-09-16 14:14 | Jim Luth | Relationship added | related to 0009514 |
2024-09-16 14:16 | Jim Luth | Note Added: 0021722 | |
2024-10-11 14:50 | Jim Luth | Note Added: 0021878 | |
2024-10-11 18:37 | Jim Luth | Note Edited: 0021878 | |
2024-10-11 18:37 | Jim Luth | Note Added: 0021882 | |
2024-10-11 18:37 | Jim Luth | File Added: image.png |