Search
5 result(s) for Variants
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.9 VariantVariant is a union of all built-in data types including an ExtensionObject . Variants can also contain arrays of any of these built-in types. Variants are used to store ... value or parameter with a data type of BaseDataType or one of its subtypes. Variants can be empty. An empty Variant is described as having a null value and should
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.2.16 Variantvalue shall not be a Variant but it could be an array of Variants . Many implementation platforms do not distinguish between one dimensional Arrays of Bytes and ByteStrings . For this
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.14 Varianttype defined in 5.3.1.17 . As a result, the functions used to serialize Variants during Service calls can be used to serialize Variant in this file syntax. Variants can contain NodeIds ... NamespaceIndexes and ServerIndexes reference the NamespaceUri and ServerUri tables in the UANodeSet . Variants can also contain ExtensionObjects which contain an EncodingId and a Structure with fields which with any DataType
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub7.2.5.4.2 VerboseEncodingspecification defines a DataSet field encoding for the VerboseEncoding which simplifies the encoding of Variants and ExtensionObjects by omitting UaType and UaTypeId fields with concrete DataType defined in the FieldMetaData ... this case the Variants at the top level are collapsed. Therefore the DataSet fields in a DataSetMessage for VerboseEncoding are encoded like the fields of a Structure where the fields
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAnnex F.14 This subclause provides the following instructions related to NodeIds : " Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames that must be modified, so the NamespaceIndexes and ServerIndexes reference