opc.ua.fx.cm.nodeset2.xml have some nodeid with the same 'BrowseName' in the same path

[ReidLi-ra]

For example, both 6029 and 6060 have the same 'BrowseName' and 'ParentNodeId' <UAVariable NodeId="ns=1;i=6029" BrowseName="1:FunctionalEntityNode" ParentNodeId="ns=1;i=5052" DataType="PortableNodeIdentifier" AccessLevel="3"> <DisplayName>FunctionalEntityNode</DisplayName> <References> <Reference ReferenceType="HasModellingRule">i=78</Reference> <Reference ReferenceType="HasTypeDefinition">i=16309</Reference> <Reference ReferenceType="HasComponent" IsForward="false">ns=1;i=5052</Reference> <Reference ReferenceType="HasProperty">ns=1;i=6030</Reference> </References> </UAVariable> and <UAVariable NodeId="ns=1;i=6060" BrowseName="1:FunctionalEntityNode" ParentNodeId="ns=1;i=5052" DataType="PortableNodeIdentifier" AccessLevel="3"> <DisplayName>FunctionalEntityNode</DisplayName> <References> <Reference ReferenceType="HasModellingRule">i=78</Reference> <Reference ReferenceType="HasTypeDefinition">i=16309</Reference> <Reference ReferenceType="HasComponent" IsForward="false">ns=1;i=5052</Reference> <Reference ReferenceType="HasProperty">ns=1;i=6061</Reference> </References> </UAVariable> Another pair is 6030 and 6061 If build with Unified Automation SDK, it will report a lot of node id redefinition warning since it use the browse path to represent the node id.