02/14/2018
I am new in the world of Opc UA and I apologize in advance if I will ask questions that many will take for granted, or worse questions that for many seem ill-posed.
I was studying the OPC UA communication stack and I was struck by the fact that on both the client and server side there is an API layer that is not standardized.
I know that the OPC UA standard standardizes the client and server communication stack and that everyone can develop their own communication stack with their own APIs. So my question is: how can you talk about standards if the communication stack then has non-standardized APIs?
And if I only make a client with my API, how can I then communicate with a server without knowing the server-side APIs? In this case, the server-side and client-side APIs can be developed by two different organizations?
Thanks in advance
05/30/2017
OPC UA defines the wire protocol in the same way HTTP defines the wire protocol that allow browsers developed by different vendors to talk to web servers developed by different vendors.
OPC UA also defines an abstract programming model that can be implemented in different programming languages. This allows vendors developing APIs to leverage the common model while adding features that make the API more usable for the target users.
1 Guest(s)