Log In
Home
03/19/2024
Offline
Hi Team,
Does OPC UA have any OpenAPI specification?
Thanks,
Chirantan
05/30/2017
Offline
Pre-release file is here:
https://opcua-rest-dashboard.a…..stapi.json
still subject to change in the next 2 months.
Will be a normative document released with 1.05.04.
03/31/2020
Offline
Hi Randy,
Thanks for your comment. The API specification mentioned above is based on REST. For sdk-based client server communication, what is the standard and how is the API versioning maintained? I noticed that OPCU JAVA stack is not getting any updates on the GitHub repo while sdk-based for other languages are getting updates. The current Java SDK in OPC UA Foundation follows specification 1.04? Is there any plan or way to update the Java SDK to the latest specification? Does the SDK API version changes when the specification changes?
05/30/2017
Offline
If you need a maintained version of an Open Source Java SDK look here:
12/19/2021
Offline
Hi Randy
Milo Sdk targets to version 1.03 of Opc Ua specification. 1.05 is the most recent version. Is there a significant difference between the sdk APIs from 1.03 to 1.05, or is it just a difference in the message formats and the schema?
If we want to update the sdk to version 1.05, what are all the changes we would need to make to the milo source code or opc ua stack git source code?
05/30/2017
Offline
1.05 is backward compatible with 1.03 if you do not use custom structures.
If you use custom structures then many 1.05 clients are designed to deal with 1.03 servers.
But the real question is what profiles do you need?
That list would tell you what is needed.
03/31/2020
Offline
Hi Randy,
We are we are not looking for profiling here. We are interested in upgrading the sdk. Due to the fact that our client is using the UA-Java-Legacy and is not getting the updates, we would like to know if there is any API versioning. This way, we can keep track of the version increase/progress and take the necessary steps.
Thanks
Pradeep
05/30/2017
Offline
Versioning is done with profiles in OPC UA.
Saying SDK supports 1.03 or 1.04 or 1.05 does not mean much.
An SDK supports a set of profiles that could come from any version.
All it means when an SDK says they support 1.03 is they do not support any profiles released with 1.04+.
12/19/2021
Offline
Thanks Randy,
Let me summarise what I understood.
Sdk versioning is tied to profiles. A particular version of OPC reference docs supports a particular collection of profiles. For example, if we say that sdk is 1.04, that means it supports all the profiles from the 1.04 OPC reference docs, and it is backward compatible. It also means that it does not support profiles released with the 1.05+ version. Versioning of APIs does not exist for SDK. In other words, all SDKs are different in terms of APIs and implementation. The standardization of the opc ua client is tied to profiles and specific version of opc ua specification.
Please confirm my understanding
Thanks
05/30/2017
Offline
An SDK that supports 1.04 supports some subset of the 1.04 profiles and 1.03 profiles.
It does not support 1.05 profiles.
All SDKs have their own APIs. OPC UA only defines the services and information models.
If you build a client you list the profiles that you support rather than the specification version.
You can use the specification version to indicate that the client supports profiles from that version and no later.
1 Guest(s)
Usage Policy