View Issue Details

IDProjectCategoryView StatusLast Update
0009573Part 81: UAFX Connecting Devices and Information ModelSpecpublic2024-08-16 12:30
ReporterBrian Batke Assigned ToPaul Hunkar  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionno change required 
Summary0009573: Usage of ApplicationUri in CM is not clear
Description

ApplicationUri is a mandatory component of the ServerAddress, which itself is a mandatory component of the CCS.

If the ApplicationUri is part of the CCS then it would need to be present in the offline descriptor. However it is not clear whether all implementations will have generated an ApplicationUri at OED-creation time. Consider a device that has a "type" OED that is used in offline engineering. SInce every device of the same type will have the same OED, there is no way to know a unique ApplicationUri.

Further, it is not clear why the CM needs to have the ApplicationUri prior to connection time. In normal UA client/server operation, this seems to be something discovered at run time from the server.

TagsNo tags attached.

Activities

Paul Hunkar

2024-08-16 12:29

manager   ~0021570

After discussion in a call - the string is already listed as be able to be a NULL string. This allow it to be effectively not set.

Paul Hunkar

2024-08-16 12:29

manager   ~0021571

Agreed that with the NULL option - no changes are required to the specification.

Paul Hunkar

2024-08-16 12:30

manager   ~0021572

reviewed in call and closed issue

Issue History

Date Modified Username Field Change
2024-06-04 16:53 Brian Batke New Issue
2024-08-16 12:29 Paul Hunkar Note Added: 0021570
2024-08-16 12:29 Paul Hunkar Assigned To => Paul Hunkar
2024-08-16 12:29 Paul Hunkar Status new => resolved
2024-08-16 12:29 Paul Hunkar Resolution open => no change required
2024-08-16 12:29 Paul Hunkar Note Added: 0021571
2024-08-16 12:30 Paul Hunkar Status resolved => closed
2024-08-16 12:30 Paul Hunkar Note Added: 0021572