Dynamic Addressing using the UA Client driver

Are there any special considerations when using dynamic addressing with the OPC UA Client driver?

If a point should be of type float, the item reference becomes:

ns=2;s=Channel.Device.Tag@Float

Where the @Datatype syntax 'type casts' the point to be of type float (single precision)

When connecting a TOP Server to another TOP Server using the UA client driver, the data type must be specified for ever 'hop' along the way. I.e. in the situation where a client is connecting to TOP Server, which is referencing a different TOP Server via OPC UA, and the second TOP server is communicating with devices the item syntax becomes:

ns=2;s=Channel1.Device1.Channel2.Device2.Tag@Float@Float

Where Channel1.Device1 exist in the first TOP Server (using the UA client driver), and Channel2.Device2 exist in the second TOP Server (the server communicating with devices).

This can repeat as many times as needed; in a situation with three TOP Servers—

Client ---> TOP Server ----> TOP Server ---> TOP Server ---> Devices

—as would be common when using a TOP Server running in a DMZ, the DataType must be repeated three times:

ns=2;s=Channel1.Device1.ns=2;s=Channel2.Device2.ns=2;s=Channel3.Device3.Tag@Float@Float@Float