View Issue Details

IDProjectCategoryView StatusLast Update
0009613Part 83: UAFX Offline EngineeringSpecpublic2024-09-16 14:10
ReporterMarco Hoch Assigned ToJim Luth  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.00.02 
Target Version1.00.03Fixed in Version1.00.03 
Summary0009613: Usage of the attribute UaNodeNamespaceUri is unclear
Description

The attribute UaNodeNamespaceUri is mentioned in the text in the Table A.4 of the chapter A.4 NodeClass mapping, but the attribute isn't mentioned as an attribute in the table and it doesn't appear in any AML library. The attribute should be explicitly described.

TagsNo tags attached.

Activities

Jim Luth

2024-09-16 14:07

administrator   ~0021720

"UaNodeNamespaceUri" is not an OPC UA Attribute, hence it does not belong as a row in Table A.4. I changed the column heading in table A.4 from "Attribute name" to "OPC UA Attribute name" to make this more clear.

In the Notes cell where UaNodeNamespaceUri is explained, the rules for what the presumed UA Namespace is when UaNodeNamespaceUri is not present is explained as "...then the presumed value is either the OPC UA Namespace referenced by the SUC library containing the SUC or the default OPC UA Server Namespace (depending on the context of the Node)." For this reason the Opc2Aml converter never needs to populate UaNodeNamespaceUri .

Jim Luth

2024-09-16 14:10

administrator   ~0021721

I changed the column heading in table A.4 from "Attribute name" to "OPC UA Attribute name" to make this more clear.

Issue History

Date Modified Username Field Change
2024-06-20 07:32 Marco Hoch New Issue
2024-06-20 07:32 Marco Hoch Status new => assigned
2024-06-20 07:32 Marco Hoch Assigned To => Jim Luth
2024-09-16 14:07 Jim Luth Note Added: 0021720
2024-09-16 14:10 Jim Luth Status assigned => resolved
2024-09-16 14:10 Jim Luth Resolution open => fixed
2024-09-16 14:10 Jim Luth Fixed in Version => 1.00.03
2024-09-16 14:10 Jim Luth Note Added: 0021721