08/31/2020
For what I understand from the specification of OPC UA, the HasPropety nodes cannot have hasComponents nodes, they are like the leaves of the tree.
But what if you have the following case:
You create ObjectType -> hasComponent – Obj1(Mandatory modelling rule)
Create different node ObjectTest -> hasProperty – NodeProperty
Now if we set the type definition of NodeProperty to ObjectType.
The property node will have now reference Obj1 which came from the type but we cannot have nodes \’under\’ hasProperty.
So what is the right thing to do here? If you cannot understand the case I can try to draw you a graph of the case.
05/30/2017
TypeDefinitions are pretty fundamental and most servers would never allow them to be changed.
If a server does support this feature it has to prevent changes from occurring that would break the information model.
The HasProperty/PropertyType rule is simply one of many rules that could be broken by messing with the type definitions of nodes.
So it is not clear why you are asking such a question.
1 Guest(s)