New Object "Aliases" in the Opc.Ua.NodeSet2.xml about ua-nodeset HOT 3 CLOSED

The Aliases node is a new addition that is in part 17, I think it might be early, in that it is only an RC, but the definition appears to be correct and it should move to released some time fairly soon.

from ua-nodeset.

Okay Thanks. I will check that out.

from ua-nodeset.

Hi @PaulHunkar,

My concern is that using the object-oriented approach we should use inheritance as the paradigm to expand the existing model. Adding, over and over new stuff makes the model unstable and inevitably causes versioning problems. As a consequence, this could put in danger the interoperability, which must be the main concern of the standardization process.

Partially I know the answer. @PaulHunkar let me recall our discussion many years ago about the fundamental difference between:

• OPC UA Information Model definition - we can carve it in stone
• OPC UA Address Space instance - we need the power supply to keep it alive

Between both there is the ModelCompiler tool. Inheritance makes sense only in the case of the Information Model - "one stone (derived) can refer to another one (base)", so there is no need to reshape the base one. Talking about NodeSet2 we are talking about a formal description of the Address Space instance.

What do you think about returning to this discussion to avoid problems like this in the future?

I am not sure what exactly means "I will check that out" (@prv), but I know many cases where this means I will keep it on hold for the next couple years :(.

The discussion is important for me because as a part of the lab: Programming Technologies - Mobile Devices we will try to use Blockchain as the repository of the custom OPC UA Information Model definitions.

Any comments are welcome.

Mariusz

from ua-nodeset.