Search

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

24 result(s) for VerboseEncoding

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

3.1.6 VerboseEncoding

VerboseEncoding A DataEncoding where the serialized form does not omit optional or default values and adds additional descriptive text. Note 1 to entry: VerboseEncodings are used when the consumers ... self-describing nature of DataEncodings such as JSON Note 2 to entry: A VerboseEncoding is only defined for the JSON DataEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

Structure values with a value equal to the default value for the type. The VerboseEncoding includes all of these fields. The CompactEncoding and VerboseEncoding replace the ReversibleEncoding and NonReversibleEncoding ... differences are described in Annex H. The VerboseEncoding also supports the RawData mode defined in OPC 10000-14 . In RawData mode, encoders shall omit the following fields: UaType
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.1 General

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 built-in type
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.16 ExtensionObject

default value for an ExtensionObject is 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

omitted from the second Type2 instance because it has a NULL value. The VerboseEncoding is represented in JSON
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.7 Structures with optional fields

JSON. The EncodingMask is not guaranteed to appear as the first field. In the VerboseEncoding the bits in the EncodingMask are determined by the presence of a field ... fields in the order that they are defined. This field is omitted in the VerboseEncoding <FieldName> The field in structure encoded according to the rules defined for their
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.8 Unions

SwitchField":2, "B":3.1415 } and would be represented in the VerboseEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

G.2 JSON Schema Mapping

this document can be found here: https://reference.opcfoundation.org/files/opc.ua.jsonschema.compact.json?u=http://opcfoundation.org/UA/ The JSON Schema for the VerboseEncoding 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

largely the same as the CompactEncoding . The NonReversibleEncoding is largely the same as the VerboseEncoding . The differences are described in the rest of this Annex. Any product that supports
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.4 StatusCode

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 the Symbol
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.10 Unions

represented as: 3.1415 The CompactEncoding is the same as the ReversibleEncoding . The VerboseEncoding always has a JSON object with a name and value for the active field, however, the NonReversibleEncoding
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

ignored. For JSON message mapping the bit is used as an option in VerboseEncoding . If one of the bits 0 to 4 is set, the fields are represented as DataValue ... JSON message mapping, it is used as an option in VerboseEncoding and it can be combined with the other bits. The DataSetFieldContentMask representation in the AddressSpace is defined in Table
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.3.1 DataSetMessageContentMask

Table 112 . Table 112 - Field endcoding configuration FieldEncoding1 FieldEncoding2 Description False True The JSON VerboseEncoding is used for the DataSetMessage field encoding. True True The JSON CompactEncoding is used
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

This value is always present. All fields with a concrete DataType are encoded using VerboseEncoding if FieldEncoding1 is FALSE and CompactEncoding if FieldEncoding1 is TRUE. See the OPC UA JSON
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 ... DataSetMessages . The VerboseEncoding and the following rules for DataSet field encoding ensure that Subscribers without OPC UA knowledge get messages without OPC UA specific information for normal use cases
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.3 VerboseEncoding and abstract type handling

VerboseEncoding and abstract type handling By default, DataSet fields can only be decoded to the original DataType by inferring the schema from the JSON message or if the DataSetMetaData describing ... DataSetReaders may go into Error state. Table 186 provides examples of Variant VerboseEncoding field encoding with the different RawData settings. The ValueRank configured for the DataSet field is Scalar
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.4 Connection properties

String . If the value is not a String , then it is encoded using the VerboseEncoding OPC UA JSON Data Encoding rules
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.8 Message header

String . If the value is not a String , then it is encoded using the VerboseEncoding OPC UA JSON Data Encoding rules in OPC 10000-6 . Promoted fields can only
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.2.2 Overview

included The DataSetMessage header is not included The DataSet field encoding is set to VerboseEncoding with RawData
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.2 RIO Channel Group Configuration

keys and the Values of the serialized fields as JSON literals when using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.3 RIO Channel Process Values

Objects . The JSON snipped shows how the Values in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.4 Energy Measurement Values

JSON snipped shows how the energy data in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.7 Combining SerializationScopes

Variable . The JSON snipped shows how the resulting SerializationValue structure DataType is serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

Name . The PackageMetadata structure and all contained types are encoded using the JSON VerboseEncoding . Note: The following tables describe the package_metadata.json with structures and enumerations as a separate