Some clarification needed regarding the nodeset entry #888
Replies: 2 comments 2 replies
-
Hi Rakshan, concerning (1): I personally haven't seen that divergernce between ns from BrowseName and NodeId before. I think the node is modelled incorrectly since a node can only be present in one ns. Usually that would be the maximum NamespaceId (ns=7 in this case) so the NodeId should be "ns=7;s=Boiler.Unit.Beh". concerning (2): Yes, this describes a node in ns=3. However, a single Nodeset file should only define a single namespace and reference nodes from other namespaces via the NamespaceUris/RequiredModels lists. It's also strange to me that a Temperature would be modelled as a UAObject, it should probably be a UAVariable. Let me guess: This is handwritten XML, right? |
Beta Was this translation helpful? Give feedback.
-
I think it is okay that the BrowseName and NodeId are in separate namespaces. Imagine one namespace that defines a bunch of standard type definitions and names for those types, e.g. a Boiler. Then you have another namespace where you've added instances of Nodes that use those type definitions. It would not be strange in that case for the NodeId of the instance to be in a different namespace than the BrowseName, which would be from the namespace with all the type definitions. |
Beta Was this translation helpful? Give feedback.
-
Hello, I have a sample address space XML file having the entry as below
My question here is,
What does BrowseName indicate here in (1)? I can understand that we have a node present in ns 3, but does the browseName 7:Beh mean that the node Beh is an instance of the node present in ns=7?
Also in (2), does it mean that the Temp is a new object which is only defined in ns =3?
Please let me know.
Regards,
Rakshan
Beta Was this translation helpful? Give feedback.
All reactions