View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010020 | Part 81: UAFX Connecting Devices and Information Model | Spec | public | 2024-11-19 06:06 | 2024-11-19 14:25 |
Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.00.02 | ||||
Target Version | 1.00.03 | Fixed in Version | 1.00.03 | ||
Summary | 0010020: ConnectionManager and manner of identifying Nodes | ||||
Description | The specification describes resolving browsepaths , looking up AliasNames and using defined NodeIds to identify variable/Objects in the configuraiton of an external server. The specification of states with a will that the ConnectionManager has to be able to resolve all of these - this should be changed to a shall, since the addressing in an external server if governed by that server and a CM / engineering tool might only have an AliasName for a node or only have a BrowsePath, the CM has to be able to resolve all of these at run time. The statement in section 13.3.1 describing it as "will be required to be able" should be "shall be able" | ||||
Additional Information | This resulted from discussion in test development. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-11-19 06:06 | Paul Hunkar | New Issue | |
2024-11-19 06:06 | Paul Hunkar | Status | new => assigned |
2024-11-19 06:06 | Paul Hunkar | Assigned To | => Paul Hunkar |
2024-11-19 06:06 | Paul Hunkar | Status | assigned => resolved |
2024-11-19 06:06 | Paul Hunkar | Resolution | open => fixed |
2024-11-19 06:06 | Paul Hunkar | Fixed in Version | => 1.00.03 |
2024-11-19 06:06 | Paul Hunkar | Note Added: 0022074 | |
2024-11-19 14:25 | Paul Hunkar | Description Updated | |
2024-11-19 14:25 | Paul Hunkar | Status | resolved => closed |
2024-11-19 14:25 | Paul Hunkar | Note Added: 0022075 |