Search

15 result(s) for DataEncodings

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  Integer which is defined in 8.24 . OPC 10000-6 defines a number of DataEncodings which specify how to serialize DataTypes . Some of these DataEncodings are text based and make ... into a String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.51 StructureField
  same as the Structure DataType Node NamespaceIndex . OPC 10000-6 defines a number of DataEncodings which specify how to serialize Structure DataTypes . Some of these DataEncodings are text based ... into a String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.52 EnumField
  field that is unique within the EnumDefinition . OPC 10000-6 defines a number of DataEncodings which specify how to serialize Enumeration DataTypes . Some of these DataEncodings are text based ... into a String that meets the requirements. This will result in text based DataEncodings with Names that are not friendly to human readers
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  3.1.6 VerboseEncoding
  have access to schema information and rely on the 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
  3.1.8 CompactEncoding
  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
  that can be used to implement them. The Mappings are organized into three groups: DataEncodings, SecurityProtocols and TransportProtocols . Different Mappings are combined together to create StackProfiles . All OPC UA applications ... with other OPC UA applications that implement the same StackProfile. This document defines the DataEncodings in Clause 5 , the SecurityProtocols in Clause 6 and the TransportProtocols in Clause
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.1 Overview
  Overview This document defines three DataEncodings : OPC UA Binary, OPC UA XML and OPC UA JSON. It describes how to construct Messages using each of these encodings
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.2 Built-in Types
  Built-in Types All OPC UA DataEncodings are based on rules that are defined for a standard set of built-in types. These built-in types are then used ... Nullable column indicates whether a 'null' value exists for the DataType in all DataEncodings . A 'null' value is a value that is equivalent 'no value specified'. A nullable type with
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.8 ExtensionObject
  represented in a Server address space as sub-types of the Structure DataType . The DataEncodings available for any given Structured DataTypes are represented as a DataTypeEncoding Object in the Server
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.11 Null, Empty and Zero-Length Arrays
  value. A zero-length or empty array is an array with 0 elements. Some DataEncodings will allow the distinction to be preserved on the wire, however, not all DevelopmentPlatforms will ... this reason, null, empty and zero length arrays are semantically the same for all DataEncodings . Decoders shall be able to handle all variations supported by the DataEncoding , however, decoders
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.13 Name Encoding Rules
  Name Encoding Rules Text based DataEncodings such as UA XML ( 5.3 ) or UA JSON ( 5.4 ) make use of Names from the DataType and DataTypeDefinition to create the serialized data
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.15 ExtensionObject
  Encoding is XML the Body uses the OPC UA XML DataEncoding . Other DataEncodings may not be serialized in an ExtensionObject . The serialized form of an ExtensionObject is shown in Table
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.3.1.16 ExtensionObject
  other XML element name shall contain an OPC UA XML encoded body. Other DataEncodings may not be serialized in an ExtensionObject . The TypeId should be the NodeId for the DataTypeEncoding
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.1 ConfigurationFileType
  file is a stream containing an instance of UABinaryFileDataType serialized using one of the DataEncodings defined in OPC 10000-6 . The DataEncoding used depends on the DataEncoding used
• 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