Search

6 result(s) for DataTypeEncoding

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  DataType points to an Object of type DataTypeEncodingType . Each DataType can have several DataTypeEncoding , for example "Default", "UA Binary" and "XML" encoding. Services ... allow Clients to request an encoding or choosing the "Default" encoding. Each DataTypeEncoding is used by exactly one DataType , that is, it is not permitted for two DataTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  HasEncoding Reference . Each concrete Structured DataType shall point to at least one DataTypeEncoding Object with the BrowseName "Default Binary" or "Default XML" having the NamespaceIndex ... BrowseName of the DataTypeEncoding Objects shall be unique in the context of a DataType , i.e. a DataType shall not point to two DataTypeEncodings having the same BrowseName . Standard Properties NodeVersion
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.38 XmlElement
  always be modelled as a subtype of the Structure DataType with a single DataTypeEncoding that represents the XML complexType that defines the XML element (it is not necessary to have ... access to the XML Schema to define a DataTypeEncoding ). For this reason a Server should never define Variables that use the XmlElement DataType unless the Server has no information about
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.8 ExtensionObject
  Structure DataType . The DataEncodings available for any given Structured DataTypes are represented as a DataTypeEncoding Object in the Server AddressSpace . The NodeId for the DataTypeEncoding Object is the identifier stored ... ExtensionObject . OPC 10000-3 describes how DataTypeEncoding Nodes are related to other Nodes of the AddressSpace . Elements of an array of ExtensionObjects can have different DataTypeEncoding NodeIds specified. In some
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.15 ExtensionObject
  ExtensionObject is 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 ... body. When a decoder encounters an ExtensionObject it shall check if it recognizes the DataTypeEncoding identifier. If it does, then it can call the appropriate function to decode the object
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.9 Messages
  sequence of bytes prefixed by the NodeId of for the OPC UA Binary DataTypeEncoding defined for the Message . Each OPC UA Service described in OPC 10000-4 has a request ... response Message . The DataTypeEncoding IDs assigned to each Service are specified in Clause