Align JSON encoding with OPC UA 1.05 Compact/Verbose rules#1758
Merged
Conversation
Update the existing Compact/Verbose JSON encoding to match the finalized OPC 10000-6 §5.4 rules, correcting field names and several field-omission behaviors that diverged from the spec. - ExtensionObject and Variant use the 1.05 field names (UaTypeId, UaEncoding, UaBody, UaType, Value); the decoder still accepts the legacy names for backward compatibility. - StatusCode is always a JSON object: Code omitted when Good, Symbol only in Verbose and only when the literal is known. - DiagnosticInfo index fields default to -1 (not 0) on both sides, and InnerStatusCode is omitted when Good per §5.4.2.13. - Array elements are encoded in builtin context so default values (0, false, "") are preserved instead of being dropped. - String and ByteString omit only NULL in Compact; empty values are present and round-trip as "". - A null LocalizedText encodes as JSON null in Verbose, and Guid omits only the all-zero default value. Scalar encoders are now null-safe, and ExtensionObject decoding no longer depends on JSON field order.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the existing Compact/Verbose JSON encoding to match the finalized OPC 10000-6 §5.4 rules, correcting field names and several field-omission behaviors that diverged from the spec.
Scalar encoders are now null-safe, and ExtensionObject decoding no longer depends on JSON field order.