Update JSON encoding for latest OPC UA 1.05 Part 6 draft #1398
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on mul
2B52
ti-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The JSON encoding defined in part 6 has been modified after feedback from SDK vendors since
OpcUaJsonEncoder
andOpcUaJsonDecoder
were implemented.Instead of "reversible" and "non-reversible" encodings there is now "verbose" and "compact". Where applicable, the "verbose" encoding eschews numeric references for which the receiving application might not have context and includes symbolic names and URIs when possible.
The types for which the encoding has changed include: