Search

Scope: Core (OPC-10000-*) All specs

15 result(s) for CompactEncoding

OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

3.1.8 CompactEncoding

CompactEncoding A DataEncoding where encoding the serialized form omits optional and default values. Note 1 to entry: All DataEncodings are CompactEncodings unless otherwise stated
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

DataEncoding for communication with other OPC UA applications require the artefacts. The CompactEncoding omits all fields in Structure values with a value equal to the default value for the type ... VerboseEncoding includes all of these fields. The CompactEncoding and VerboseEncoding replace the ReversibleEncoding and NonReversibleEncoding . The differences are described in Annex H. The VerboseEncoding also supports the RawData mode defined
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.1 General

field within a JSON object, the field shall be omitted when using the CompactEncoding . When using the VerboseEncoding , the field is encoded as the JSON literal 'null'. Any non-nullable ... shall be encoded if it is an element of an array. When using the CompactEncoding , the field of a Structure or Union is omitted if value is equal
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.16 ExtensionObject

serialized as an empty JSON object in the VerboseEncoding and omitted in the CompactEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.6 Structures

Char* C; }; struct Type1 { Int32 X; Int32 NoOfY; Type2* Y; Int32 Z; }; The CompactEncoding is represented in JSON
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.7 Structures with optional fields

determined by the presence of a field in the JSON object. In the CompactEncoding , EncodingMask indicates which fields are specified because fields are omitted because they have a default value ... Assume that O1 is not specified and the value of O2 is 0. The CompactEncoding would be: { "EncodingMask": 2, "X": 1, "Y": 2 } Where
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.8 Unions

Definition for a Union Name Description SwitchField This field is only present in the CompactEncoding . The identifier for the field in the Union which is encoded as a JSON number ... Byte Selector; { Int32 A; Double B; Char* C; } Value; }; would be represented in the CompactEncoding as: { "SwitchField":2, "B":3.1415 } and would be represented
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

G.2 JSON Schema Mapping

DataTypes defined in the OPC UA namespace. The JSON Schema for the CompactEncoding for all DataTypes released with this version of this document can be found here: https://reference.opcfoundation.org/files/opc.ua.services.jsonschema.compact.json?u=http://opcfoundation.org/UA/&v=1.05.07 ... this document can be found here: https://reference.opcfoundation.org/files/opc.ua.services.jsonschema.compact.json?u=http://opcfoundation.org/UA/ The JSON Schema for the CompactEncoding for all DataTypes, excluding DataTypes used for only for Services, released with this version
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.1 Overview

current versions of the JSON encoding. The ReversibleEncoding is largely the same as the CompactEncoding . The NonReversibleEncoding is largely the same as the VerboseEncoding . The differences are described ... Annex. Any product that supports the OpenAPI mappings defined in G.3 only supports the CompactEncoding . The deprecated encodings published earlier versions of this specification are only used by older products
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.4 StatusCode

Good (0) it is only encoded if it is an element JSON array. The CompactEncoding and VerboseEncoding use the same JSON object as the NonReversibleEncoding. The CompactEncoding always omits
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.10 Unions

Value":3.1415 } In the NonReversibleEncoding , it is represented as: 3.1415 The CompactEncoding is the same as the ReversibleEncoding . The VerboseEncoding always has a JSON object with a name
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.3.1 DataSetMessageContentMask

JSON VerboseEncoding is used for the DataSetMessage field encoding. True True The JSON CompactEncoding is used for the DataSetMessage field encoding. The RawData bit of the DataSetFieldContentMask shall be ignored
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

value is always present. All fields with a concrete DataType defined are encoded using CompactEncoding OPC UA JSON Data Encoding defined in OPC 10000-6 . The fields in the JSON
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

fields with a concrete DataType are encoded using VerboseEncoding if FieldEncoding1 is FALSE and CompactEncoding if FieldEncoding1 is TRUE. See the OPC UA JSON Data encodings defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

VerboseEncoding OPC 10000-6 defines two DataEncodings : CompactEncoding and VerboseEncoding . They have the same structure except VerboseEncoding includes default values. The main use case for the VerboseEncoding is the payload