-
Notifications
You must be signed in to change notification settings - Fork 591
Improve OPCUA documentation #1339
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
Comments
@thompson-tomo by "adapter" I assume you mean one of these: https://github.com/cloudevents/spec/tree/main/cloudevents/adapters right? if so, are you willing to volunteer? |
@duglin correct that is what I mean by adapter. I will see if I can get a first pass at a pr done. |
thompson-tomo
added a commit
to thompson-tomo/spec
that referenced
this issue
May 10, 2025
…s doc Signed-off-by: James Thompson <thompson.tomo@outlook.com>
thompson-tomo
added a commit
to thompson-tomo/spec
that referenced
this issue
May 22, 2025
…s doc Signed-off-by: James Thompson <thompson.tomo@outlook.com>
thompson-tomo
added a commit
to thompson-tomo/spec
that referenced
this issue
May 22, 2025
…s doc Signed-off-by: James Thompson <thompson.tomo@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The cloudevents/extensions/opcua.md document reads more like an adapter description as it describes what attribute the opcua property should be mapped to. As such I would like to propose that an adapter spec is written outlining the mapping & within the extension document only retaining the additional attributes needed by the adapter.
This approach is inline with my comment in #1325
The text was updated successfully, but these errors were encountered: