-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Object "Aliases" in the Opc.Ua.NodeSet2.xml #54
Comments
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. |
Okay Thanks. I will check that out. |
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:
Between both there is the ModelCompiler tool. Inheritance makes sense only in the case of the
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 |
In the commit cc39b5e of the Schema/Opc.Ua.NodeSet2.xml, there is an inclusion of a new Object "Aliases". Why is it included or is it a bug ?
It makes my server look this way.
![grafik](https://user-images.githubusercontent.com/40856484/75434399-c2952a00-5951-11ea-9428-2c311bd3a5e3.png)
The text was updated successfully, but these errors were encountered: