Search

9 result(s) for TypeId

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.2.1 Overview
  types are defined or new SecurityPolicies are added. The EncryptedSecret format starts with a TypeId , EncodingMask and Length . These values allow a Server to determine how to handle the secret ... TypeId does not resolve to one of the defined EncryptedSecret format DataTypes and a USERNAME UserIdentityToken has been provided then the Server may attempt to handle the secret using
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.2.3 EncryptedSecret Format
  EncryptedSecret Format The EncryptedSecret uses an extensible format which has the TypeId of a DataType Node as a prefix as defined for the ExtensionObject encoding ... layout of the EncryptedSecret is shown in Figure 39 . Figure 39 - EncryptedSecret layout The TypeId specifies how the EncryptedSecret is serialized and secured. For example, the RsaEncryptedSecret requires that
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.15 ExtensionObject
  shown in Table 25 . Table 25 - Extension Object Binary DataEncoding Name Data Type Description TypeId NodeId The identifier for the DataTypeEncoding node in the Server's AddressSpace . ExtensionObjects defined ... body is encoded. Body OctetString The object encoded with the DataEncoding indicated by the TypeId. This field contains the raw bytes for ByteString bodies. For XmlElement bodies this field contains
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.6 Structures
  prefix shown in Table 29 which would make the total length 101 bytes. The TypeId , Encoding and the Length are fields defined by the ExtensionObject . The encoding of the Type2
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.7 Structures with optional fields
  Table 32 and have a total length of 22 bytes. The length of the TypeId , Encoding and the Length are fields defined by the ExtensionObject . Table 32 - Sample
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.8 Unions
  Table 33 and it would have a total length of 17 bytes. The TypeId , Encoding and the Length are fields defined by the ExtensionObject . Table 33 - Sample OPC UA Binary
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.3.1.16 ExtensionObject
  name="ExtensionObject"> <xs:sequence> <xs:element name="TypeId" type="tns:NodeId" minOccurs="0" /> <xs:element name ... encoded body. Other DataEncodings may not be serialized in an ExtensionObject . The TypeId should be the NodeId for the DataTypeEncoding Node . The NodeId of DataType Node may also be used
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.3 Decimal
  ExtensionObject with the JSON object in Table 43 as the Body . The TypeId shall be the NodeId of the Decimal DataType and the Encoding shall
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.7 ExtensionObject
  shown in Table H.6 . Table H.6 - JSON Object Definition for an ExtensionObject Name Description TypeId The NodeId of a DataTypeEncoding Node or a DataType Node formatted using the rules ... encoded as a JSON value containing only the value of the Body field. The TypeId and Encoding fields are dropped. Decoders that support the NonReversibleEncoding need to have