Hi,

This is a known “issue” in the java stack (https://github.com/OPCFoundation/UA-Java/issues/12), which is a low level component, on top of which our java SDK is built, which is in turn used to make the SimulationServer.

You are correct about the specification stating that. This will be eventually fixed, however the fix is more of a performance optimization than a real issue, in my opinion.

However in practice a client should not rely on the namespace uri defining a remote reference, because the serverIndex defines that, not the uri. Therefore it should always check the server index first to determine if the reference is local/remote, then check namespaceuri/index, convert the index to uri if index defined and then check the value.

In general, the namespace indices should not be used for anything other that efficient transmit of the uri, i.e. clients should always convert the indices to uris and code application logic against the uris instead of indices, unless their developer maintains all client accessing that server because the order of the indices is not defined (expect for the 0 and 1 namespace indices) and could e.g. different each restart.

– Bjarne