View Issue Details

IDProjectCategoryView StatusLast Update
0010020Part 81: UAFX Connecting Devices and Information Model [sg.BaseFacet]Specpublic2025-08-01 12:33
ReporterPaul Hunkar Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionreopened 
Product Version1.00.02 
Target VersionNextMaintenanceFixed in Version1.00.03 
Summary0010020: 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.

TagsNo tags attached.

Relationships

related to 0010310 new Part 84: UAFX Profiles AliasName Client Base - should it be mandatory from the beginning? 

Activities

Paul Hunkar

2024-11-19 06:06

manager   ~0022074

Changed word as requested

Paul Hunkar

2024-11-19 14:25

manager   ~0022075

reviewed updated in call, agreed to text and closed issue

Greg Majcher

2024-11-22 13:37

manager   ~0022096

This issue needs further discussion since it introduces a new requirement

Paul Hunkar

2024-12-06 09:03

manager   ~0022201

the requirement has been present since the start - since the profiles where already listed as mandator in the initial release - but we can discuss the change of will to shall in a future meeting i.e. this change doe snot result in a profile /Facet change)

Paul Hunkar

2025-07-05 16:14

manager   ~0023080

Agreed call to delay any decision on this until after prototyping has a chance to work with Aliasnames (Sept workshop)

Issue History

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
2024-11-22 13:37 Greg Majcher Status closed => feedback
2024-11-22 13:37 Greg Majcher Resolution fixed => reopened
2024-11-22 13:37 Greg Majcher Note Added: 0022096
2024-12-06 09:03 Paul Hunkar Note Added: 0022201
2024-12-06 09:03 Paul Hunkar Assigned To Paul Hunkar => Greg Majcher
2025-06-13 12:24 Greg Majcher Relationship added related to 0010310
2025-06-13 12:24 Greg Majcher Assigned To Greg Majcher =>
2025-07-05 16:14 Paul Hunkar Note Added: 0023080
2025-07-05 16:14 Paul Hunkar Status feedback => new
2025-07-05 16:47 Paul Hunkar Target Version 1.00.03 => NextMaintenance
2025-07-09 15:57 Paul Hunkar Target Version => NextMaintenance
2025-08-01 12:33 Paul Hunkar Assigned To => Paul Hunkar
2025-08-01 12:33 Paul Hunkar Status new => acknowledged