Search

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

23 result(s) for DataEncoding

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

3.1.2 DataEncoding

DataEncoding way to serialize messages and data structures
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 ... JSON Note 2 to entry: A VerboseEncoding is only defined for the JSON DataEncoding
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

4 Overview

Messages are defined in OPC 10000-4 ; however, their format is specified by the DataEncoding and TransportProtocol . For this reason, each Message defined in OPC 10000-4 shall have
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.4 DateTime

latest value that can be represented. If the range supported by the DataEncoding is outside of the range supported by a DevelopmentPlatform then decoders shall replace any below range values ... range supported by a DevelopmentPlatform is outside of the range supported by a DataEncoding then encoders shall replace any below range values with DateTime.MinValue and any above range values with
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.7 Structures and Unions

name value pairs defined by the DataTypeDefinition Attribute in OPC 10000-3 . Each DataEncoding describes how to use the DataTypeDefinition to serialize Structures . Subtypes of Structure extend the parent ... FALSE then the field value is encoded directly according to the rules for the DataEncoding . Note that the StructureField IsOptional flag has an overloaded meaning because it was not possible
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.11 Null, Empty and Zero-Length Arrays

DataEncodings . Decoders shall be able to handle all variations supported by the DataEncoding , however, decoders are not required to preserve the distinction. When testing for equality, applications shall treat null
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.13 Name Encoding Rules

necessary to define a transformation that ensures any Names can be used in the DataEncoding . The following rules are used to convert a DataType Name or a Structure Field Name ... string supported by the Encoding: Any character that is not permitted by the DataEncoding is replaced by an underscore (U+005F); A name with text sequence that
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.1 General

General The OPC UA Binary DataEncoding is a data format developed to meet the performance needs of OPC UA applications. This format is designed primarily for fast encoding and decoding ... encoded data on the wire was also a consideration. The OPC UA Binary DataEncoding relies on several primitive data types with clearly defined encoding rules that can be sequentially written
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.5 DateTime

represent the full range of dates and times that can be represented with this DataEncoding . For example, the UNIX time_t structure only has a 1 second resolution and cannot
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

identifier for a node in the address space of an OPC UA Server . The DataEncoding of a NodeId varies according to the contents of the instance. For that reason ... encoded form indicates the format of the rest of the encoded NodeId . The possible DataEncoding formats are shown in Table 17 . Table 17 through Table 20 describe the structure
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.15 ExtensionObject

encoded as sequence of bytes prefixed by the NodeId of its DataTypeEncoding , the DataEncoding used and the number of bytes encoded. An ExtensionObject may be serialized as a ByteString ... over it . If the Encoding is Binary the Body uses the OPC UA Binary DataEncoding . If the Encoding is XML the Body uses the OPC UA XML DataEncoding . Other DataEncodings
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

General The JSON DataEncoding was developed to allow OPC UA applications to interoperate with web and enterprise software that use this format. The OPC UA JSON DataEncoding defines standard JSON ... often rely on scripting languages to process the incoming messages so artefacts in the DataEncoding that exist to ensure fidelity during decoding are not necessary. For this reason, this DataEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.4.2 Session-less Services

header. The Content-Type header in the HTTP request and response shall specify the DataEncoding of the message. Well known media types should be used to ensure interoperability with standard ... Type Description application/octet-stream application/opcua+uabinary The body is encoded using the OPC UA Binary DataEncoding defined in 5.2 . application/soap+xml The body is encoded using the XML DataEncoding defined
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.4.4 Binary Encoding

body of the HTTP Messages shall be encoding using the OPC UA Binary DataEncoding . The Content-Type shall be "application/octet-stream". An example HTTP request header is: POST /UA/SampleServer ... only used for Session-less Service calls (see 7.4.2 ). If the OPC UA Binary DataEncoding is used for a Session-less Service the HTTP request header is: POST /UA/SampleServer HTTP/1.1Authorization
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.4.5 JSON Encoding

body of the HTTP Messages shall be encoded using the OPC UA JSON DataEncoding and the Content-Type shall be 'application/json'. If the message is compressed the Content-Encoding shall
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

G.1 Overview

Overview The UA JSON DataEncoding defined in 5.4 specifies how OPC UA DataTypes are serialized in JSON. This Annex specifies how to describe the DataEncoding using a machine-readable schema
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.1 General

following parameters (see OPC 10000-4 for details): historyReadDetails timestampsToReturn releaseContinuationPoints nodesToRead [] nodeId indexRange dataEncoding continuationPoint The HistoryReadDetails is an extensible parameter that can be any of the parameters defined
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.3 Continuation Points

same as in the original call. It is permissible to change the dataEncoding parameter with each request. If the HistoryReadDetails parameter or TimestampsToReturn parameter change the Server can ignore
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.8.5.1 ConfigurationFileType

UABinaryFileDataType serialized using one of the DataEncodings defined in OPC 10000-6 . The DataEncoding used depends on the DataEncoding used for the messages sent to the Server . The body
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

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 NetworkMessage are controlled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.4 Connection properties

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 , then it is encoded using the VerboseEncoding OPC UA JSON Data Encoding rules in OPC 10000-6 . Promoted fields can only be sent for fields which are assumed