Search

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

34 result(s) for Variant

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.1 AdditionalParametersType

allows the same name to be used in different contexts. The value is a Variant which allows Structures to be passed in addition to basic types such as Strings. Note
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.2 Built-in Types

default. A data value with an associated status code and timestamps. 24 Variant Yes Null A union of all of the types specified above. 25 DiagnosticInfo Yes No fields specified ... types defined in OPC 10000-3 and OPC 10000-4 . However, the ExtensionObject and Variant types are defined in this document. In addition, this document defines a representation
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.6 Number, Integer and UInteger

these types are used in Structure fields, the field value is encoded as a Variant
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.8 ExtensionObject

DataType as a Service Request or Response ; When encoding a Structure value inside a Variant ; When encoding a field value in a Structure where the field DataType is Structure . When
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.9 Variant

Variant A Variant 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 ... type of BaseDataType or one of its subtypes. Variants can be empty. An empty Variant is described as having a null value and should be treated like a null column
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.10 Decimal

encoded with the least significant byte first. When a Decimal is encoded in a Variant the built-in type is set to ExtensionObject . Decoders that do not understand the Decimal
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.8 XmlElement (Deprecated)

continue processing the stream. For example, if the XmlElement is the body of a Variant or an element in an array which is the body of a Variant then this ... error can be reported by setting value of the Variant to the StatusCode Bad_DecodingError
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.15 ExtensionObject

continue processing the stream. For example, if the ExtensionObject is the body of a Variant or an element in an array that is the body of Variant then this error ... reported by setting the value of the Variant to the StatusCode Bad_DecodingError. A null value for an ExtensionObject is encoded with a TypeId
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.16 Variant

Variant A Variant is a union of the built-in types. The structure of a Variant is shown in Table 26 . Table 26 - Variant Binary DataEncoding Name Data Type Description ... encoding each element shall be decoded in order. The value shall not be a Variant but it could be an array of Variants . Many implementation platforms do not distinguish between
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.5 Arrays

When a multi-dimensional Array is the Value of an Attribute it uses the Variant encoding described in 5.2.2.16 . When a multi-dimensional Array is a field of a Structure
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.1.9 XmlElement (Deprecated)

sequence> </xs:complexType> XmlElements may only be used inside Variant or ExtensionObject values
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.1.17 Variant

Variant A Variant value is encoded as an xs:complexType with the following XML schema: <xs:complexType name="Variant"> <xs:sequence> <xs:element ... element> </xs:sequence> </xs:complexType> If the Variant represents a scalar value, then it shall contain a single child element with the name
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.2 Decimal

NodeId is always the NodeId of the Decimal DataType . When encoded in a Variant the Decimal is encoded as an ExtensionObject . Arrays of Decimals are Arrays of ExtensionObjects . The Value
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.3 Enumerations

restriction> </xs:simpleType> Enumerations that are stored in a Variant are encoded as an Int32 value. For example, any Variable could have a value with a DataType ... NodeClass . In this case, the corresponding numeric value is placed in the Variant (e.g. NodeClass Object would be stored
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

omitted when serialization uses abstract DataTypes such as Structure (i.e. ExtensionObject ) or BaseDataType (i.e. Variant ). OPC 10000-14 specifies the behaviour if a Publisher is misconfigured with metadata that uses
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.17 Variant

Variant Variant values shall be encoded as a JSON object with the fields shown in Table 41 . Table 41 - JSON Object Definition for a Variant Name Description UaType The built
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.18 DataValue

with the fields shown in Table 42 . The DataValue adds additional fields to a Variant (see 5.4.2.17 ). Table 42 - JSON Object Definition for a DataValue Name Data Type Description UaType ... Byte See the UaType field in the Variant . Value * See the Value field in the Variant . Dimensions UInt32 See the Dimensions field in the Variant . Status StatusCode The status associated
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.3 Decimal

description of the Scale and Value fields. When encoding in a Variant , a Decimal value shall be encoded as an ExtensionObject with the JSON object in Table
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.4.1 Compact

shall be encoded as a JSON number. When an Enumeration is encoded in a Variant the Type field is Int32
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.4.2 Verbose

value is encoded as a JSON string. When an Enumeration is encoded in a Variant the Type field is a Int32 and the value is encoded as a JSON number
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.2 UANodeSet

have the NodeId type such as ParentNodeId ( F.7 ) or DataType ( F.8 ). Fields with the Variant type shall not contain UANodeSet aliases. The Extensions are free form XML data that
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.13 DataTypeField

DataTypes that are not subtypes of Structure are encoded as a Variant (see 5.1.9 ). The default value is FALSE. This field is omitted for Enumeration or OptionSet DataTypes
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.14 Variant

F.14 Variant The Variant type specifies the value for a Variable or VariableType Node . This type is the same as the type 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 , ExpandedNodeIds and QualifiedNames which must be modified
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.8 Variant

Variant For the ReversibleEncoding, Variant values shall be encoded as a JSON object with the fields shown in Table H.7 . Table H.7 - JSON Object Definition for a Variant Name Description ... Body (see Table 1 ) encoded as JSON number. If type is 0 (NULL) the Variant contains a NULL value and the containing JSON object shall be omitted or replaced
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.2 DataSetMessage field

status and timestamp. A DataSet field can be represented as a DataValue , as a Variant or as a RawData in the DataSetMessage field. The representation depends on the DataSetFieldContentMask defined ... used if value, status and timestamp are included in the DataSetMessage . The representation as Variant is used if value or bad status should be included in the DataSetMessage . The representation
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

handled in addition: (1) Abstract types always have the built-in type Variant since they can result in different concrete types in a DataSetMessage . The dataType field may provide additional
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

DataSetFieldContentMask Values Value Bit No. Description DataSet fields can be represented as RawData, Variant or DataValue as described in 5.3.2 . If none of the bits are set, the fields ... represented as Variant . If the RawData bit is set for UADP message mapping, the fields are represented as RawData and all other bits are ignored. For JSON message mapping
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

Subscriber . Bit range 1-2: Field Encoding 00 The DataSet fields are encoded as Variant The Variant can contain a StatusCode instead of the expected DataType if the status ... field is Bad. The Variant can contain a DataValue with the value and the statusCode if the status of the field is Uncertain. 01 RawData Field Encoding The RawData field
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.5 Data Key Frame DataSetMessage

DataSetFlags1.Field Encoding of the DataSetMessage Header defined in 7.2.4.5.4 . The default encoding is Variant if bit 1 and 2 are not set. The detailed rules for creating the DataSetMessage status
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

field content are defined in Table 35 . For MessageType "ua-event", only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant ... 0x20 (only the RawData flag is set), the DataSetMessage fields are encoded as Variant . Otherwise the fields are encoded as DataValue . If the MessageType is "ua-event
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.3 VerboseEncoding and abstract type handling

FieldMetaData. The UaTypeId is needed to decode the value. DataSet fields with BuiltInType Variant. The UaType is needed to decode the value. DataSet fields with abstract ValueRank values ... BaseDataType or AllowSubTypes =TRUE. If RawData =FALSE, then the Publisher always includes the full Variant with the UaType or ExtensionObject with UaTypeId when encoding these fields at the top level
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.2 ActionRequest

DataType of the field and the flags specified by the DataSetFieldContentMask. Only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant encoding shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.3 ActionResponse

DataType of the field and the flags specified by the DataSetFieldContentMask. Only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant encoding shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

period fixed profile requires the encoding as a raw value. Other profiles support a variant encoding (which allows for a status to be sent in the case ... fixed DataSetMessages , except that they are always a structure that is encoded as a Variant (see Figure E.20 ). Figure E.20 - Event DataSet data In this version of this document, Events