03/04/2015
OPC UA Part 3 claims in 5.2.4:
Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName.
But below claims that BrowseName…
contains a namespace and a string. The namespace is provided to make the BrowseName unique in some cases in the context of
a Node (e.g. Properties of a Node) although not unique in the context of the Server
Well it is possible that node uses references to nodes with BrowseName different only in NamespaceIndex e.g. node <“Bar” : 1> and node <“Bar” : 2 >.
But, is it possible that node with BrowseName <“Foo”: 1> uses references to nodes with exactly the same BrowseName <“Bar” : 1>?
thank you in advance
12/02/2015
<“Foo”: 1> and <“Bar” : 1> not the same 🙂
I found three exceptions:
1. All reference types have unique BrowseNames.
2. All nodes, referenced via HasProperty to single Node, must have unique BrowseNames.
3. All paths in InstanceDeclaration must be unique. But in realizations of InstanceDeclaration paths may be not unique.
1 Guest(s)