7 Common parameter type definitions ToC Previous Next

7.4 ContentFilter ToC Previous Next

7.4.3 FilterOperator ToC Previous Next

Table 119 defines the basic operators that can be used in a ContentFilter. See Table 120 for a description of advanced operators. See 7.4.4 for a definition of operands.

Table 119 – Basic FilterOperator Definition

Operator Number of Operands Description
Equals_0 2 TRUE if operand[0] is equal to operand[1].
If the operands are of different types, the system shall perform any implicit conversion to a common type. This operator resolves to FALSE if no implicit conversion is available and the operands are of different types. This operator returns FALSE if the implicit conversion fails. See the discussion on data type precedence in Table 123 for more information how to convert operands of different types.
IsNull_1 1 TRUE if operand[0] is a null value.
GreaterThan_2 2 TRUE if operand[0] is greater than operand[1].
The following restrictions apply to the operands:
   [0]: Any operand that resolves to an ordered value.
   [1]: Any operand that resolves to an ordered value.
The same conversion rules as defined for Equals apply.
LessThan_3 2 TRUE if operand[0] is less than operand[1].
The same conversion rules and restrictions as defined for GreaterThan apply.
GreaterThanOrEqual_4 2 TRUE if operand[0] is greater than or equal to operand[1].
The same conversion rules and restrictions as defined for GreaterThan apply.
LessThanOrEqual_5 2 TRUE if operand[0] is less than or equal to operand[1].
The same conversion rules and restrictions as defined for GreaterThan apply.
Like_6 2 TRUE if operand[0] matches a pattern defined by operand[1]. See Table 121 for the definition of the pattern syntax.
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a String.
   [1]: Any operand that resolves to a String.
This operator resolves to FALSE if no operand can be resolved to a string.
Not_7 1 TRUE if operand[0] is FALSE.
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a Boolean.
If the operand cannot be resolved to a Boolean, the result is a NULL. See below for a discussion on the handling of NULL.
Between_8 3 TRUE if operand[0] is greater or equal to operand[1] and less than or equal to operand[2].
The following restrictions apply to the operands:
   [0]: Any operand that resolves to an ordered value.
   [1]: Any operand that resolves to an ordered value.
   [2]: Any operand that resolves to an ordered value.
If the operands are of different types, the system shall perform any implicit conversion to match all operands to a common type. If no implicit conversion is available and the operands are of different types, the particular result is FALSE. See the discussion on data type precedence in Table 123 for more information how to convert operands of different types.
InList_9 2..n TRUE if operand[0] is equal to one or more of the remaining operands.
The Equals Operator is evaluated for operand[0] and each remaining operand in the list. If any Equals evaluation is TRUE, InList returns TRUE.
And_10 2 TRUE if operand[0] and operand[1] are TRUE.
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a Boolean.
   [1]: Any operand that resolves to a Boolean.
If any operand cannot be resolved to a Boolean it is considered a NULL. See below for a discussion on the handling of NULL.
Or_11 2 TRUE if operand[0] or operand[1] are TRUE.
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a Boolean.
   [1]: Any operand that resolves to a Boolean.
If any operand cannot be resolved to a Boolean it is considered a NULL. See below for a discussion on the handling of NULL.
Cast_12 2 Converts operand[0] to a value with a data type with a NodeId identified by operand[1].
The following restrictions apply to the operands:
   [0]: Any operand.
   [1]: Any operand that resolves to a NodeId or ExpandedNodeId where the Node is of the NodeClass DataType.
If there is any error in conversion or in any of the parameters then the Cast Operation evaluates to a NULL. See below for a discussion on the handling of NULL.
BitwiseAnd_16 2 The result is an integer which matches the size of the largest operand and contains a bitwise And operation of the two operands where both have been converted to the same size (largest of the two operands).
The following restrictions apply to the operands:
   [0]: Any operand that resolves to an integer.
   [1]: Any operand that resolves to an integer.
If any operand cannot be resolved to an integer it is considered a NULL. See below for a discussion on the handling of NULL.
BitwiseOr_17 2 The result is an integer which matches the size of the largest operand and contains a bitwise Or operation of the two operands where both have been converted to the same size (largest of the two operands).
The following restrictions apply to the operands:
   [0]: Any operand that resolves to an integer.
   [1]: Any operand that resolves to an integer.
If any operand cannot be resolved to an integer it is considered a NULL. See below for a discussion on the handling of NULL.

Many operands have restrictions on their type. This requires the operand to be evaluated to determine what the type is. In some cases the type is specified in the operand (i.e. a LiteralOperand). In other cases the type requires that the value of an attribute be read. An ElementOperand evaluates to a Boolean value unless the operator is a Cast or a nested RelatedTo operator.

Table 120 defines complex operators that require a target node (i.e. row) to evaluate. These operators shall be re-evaluated for each possible target node in the result set.

Table 120 – Complex FilterOperator Definition

Operator Number of Operands Description
InView_13 1 TRUE if the target Node is contained in the View defined by operand[0].
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a NodeId that identifies a View Node.
If operand[0] does not resolve to a NodeId that identifies a View Node, this operation shall always be False.
OfType_14 1 TRUE if the target Node is of type operand[0] or of a subtype of operand[0].
The following restrictions apply to the operands:
   [0]: Any operand that resolves to a NodeId that identifies an ObjectType or VariableType Node.
If operand[0] does not resolve to a NodeId that identifies an ObjectType or VariableType Node, this operation shall always be False.
RelatedTo_15 6 TRUE if the target Node is of type operand[0] and is related to a NodeId of the type defined in operand[1] by the Reference type defined in operand[2].
operand[0] or operand[1] can also point to an element Reference where the referred to element is another RelatedTo operator. This allows chaining of relationships (e.g. A is related to B is related to C), where the relationship is defined by the ReferenceType defined in operand[2]. In this case, the referred to element returns a list of NodeIds instead of TRUE or FALSE. In this case if any errors occur or any of the operands cannot be resolved to an appropriate value, the result of the chained relationship is an empty list of nodes.
Operand[3] defines the number of hops for which the relationship should be followed. If operand[3] is 1, then objects shall be directly related. If a hop is greater than 1, then a NodeId of the type described in operand[1] is checked for at the depth specified by the hop. In this case, the type of the intermediate Node is undefined, and only the Reference type used to reach the end Node is defined. If the requested number of hops cannot be followed, then the result is FALSE, i.e., an empty Node list. If operand[3] is 0, the relationship is followed to its logical end in a forward direction and each Node is checked to be of the type specified in operand[1]. If any Node satisfies this criterion, then the result is TRUE, i.e., the NodeId is included in the sub-list.
Operand [4] defines if operands [0] and [1] should include support for subtypes of the types defined by these operands. A TRUE indicates support for subtypes
operand [5] defines if operand [2] should include support for subtypes of the reference type. A TRUE indicates support for subtypes.

The following restrictions apply to the operands:
   [0]: Any operand that resolves to a NodeId or ExpandedNodeId that identifies an ObjectType or VariableType Node or a reference to another element which is a RelatedTo operator.
   [1]: Any operand that resolves to a NodeId or ExpandedNodeId that identifies an ObjectType or VariableType Node or a reference to another element which is a RelatedTo operator.
   [2]: Any operand that resolves to a NodeId that identifies a ReferenceType Node.
   [3]: Any operand that resolves to a value implicitly convertible to UInt32.
   [4]: Any operand that resolves to a value implicitly convertible to a Boolean; if this operand does not resolve to a Boolean, then a value of FALSE is used.
   [5]: Any operand that resolves to a value implicitly convertible to a Boolean; if this operand does not resolve to a Boolean, then a value of FALSE is used.

If none of the operands [0],[1],[2],[3] resolves to an appropriate value then the result of this operation shall always be False (or an Empty set in the case of a nested RelatedTo operand).

See examples for RelatedTo in B.2.

The RelatedTo operator can be used to identify if a given type, set as operand[1], is a subtype of another type set as operand[0] by setting operand[2] to the HasSubtype ReferenceType and operand[3] to 0.

The Like operator can be used to perform wildcard comparisons. Several special characters can be included in the second operand of the Like operator. The valid characters are defined in Table 121. The wildcard characters can be combined in a single string (i.e. ‘Th[ia][ts]%’ would match ‘That is fine’, ‘This is fine’, ‘That as one’, ‘This it is’, ‘Then at any’, etc.). The Like operator is case sensitive.

Table 121 – Wildcard characters

Special Character Description
% Match any string of zero or more characters (i.e. ‘main%’ would match any string that starts with ‘main’, ‘%en%’ would match any string that contains the letters ‘en’ such as ‘entail’, ‘green’ and ‘content’.) If a ‘%’ sign is intend in a string the list operand can be used (i.e. 5[%] would match ‘5%’).
_ Match any single character (i.e. ‘ould’ would match ‘would’, ‘could’). If the ‘’ is intended in a string then the list operand can be used (i.e. 5[] would match ‘5’).
|Escape character allows literal interpretation
   (i.e. \\ is \, \% is %, \_ is _)
 
[] Match any single character in a list
(i.e. ‘abc[13-68] would match ‘abc1’,’abc3’,’abc4’,’abc5’,’abc6’, and ‘abc8’.
   ‘xyz[c-f]’ would match ‘xyzc’, ‘xyzd’, ‘xyze’, ‘xyzf’).
[^] Not Matching any single character in a list.
The ^ shall be the first character inside on the [].
(i.e. ‘ABC[^13-5]’ would NOT match ‘ABC1’, ‘ABC3’, ‘ABC4’, and ‘ABC5’. xyz[^dgh] would NOT match ‘xyzd’, ‘xyzg’, ‘xyzh’. )

Table 122 defines the conversion rules for the operand values. The types are automatically converted if an implicit conversion exists (I). If an explicit conversion exists (E) then type can be converted with the cast operator. If no conversion exists (X) the then types cannot be converted, however, some servers may support application specific explicit conversions. The types used in the table are defined in OPC 10000-3. A data type that is not in the table does not have any defined conversions.

Table 122 – Conversion Rules

Target Type (To)
 
Source Type (From)
   Target Type (To)


   Source Type (From)
Boolean Byte ByteString DateTime Double ExpandedNodeId Float Guid Int16 Int32 Int64 NodeId SByte StatusCode String LocalizedText QualifiedName UInt16 UInt32 UInt64 XmlElement
Boolean - I X X I X I X I I I X I X E X X I I I X
Byte E - X X I X I X I I I X I X E X X I I I X
ByteString X X - X X X X E X X X X X X X X X X X X X
DateTime X X X - X X X X X X X X X X E X X X X X X
Double E E X X - X E X E E E X E X E X X E E E X
ExpandedNodeId X X X X X - X X X X X E X X I X X X X X X
Float E E X X I X - X E E E X E X E X X E E E X
Guid X X E X X X X - X X X X X X E X X X X X X
Int16 E E X X I X I X - I I X E X E X X E I I X
Int32 E E X X I X I X E - I X E E E X X E E I X
Int64 E E X X I X I X E E - X E E E X X E E E X
NodeId X X X X X I X X X X X - X X I X X X X X X
SByte E E X X I X I X I I I X - X E X X I I I X
StatusCode X X X X X X X X X I I X X - X X X E I I X
String I I X E I E I I I I I E I X - E E I I I X
LocalizedText X X X X X X X X X X X X X X I - X X X X X
QualifiedName X X X X X X X X X X X X X X I I - X X X X
UInt16 E E X X I X I X I I I X E I E X X - I I X
UInt32 E E X X I X I X E I I X E E E X X E - I X
UInt64 E E X X I X I X E E I X E E E X X E E - X
XmlElement X X X X X X X X X X X X X X X X X X X X -

Arrays of a source type can be converted to arrays of the target type by converting each element. A conversion error for any element causes the entire conversion to fail.

Arrays of length 1 can be implicitly converted to a scalar value of the same type.

Guid, NodeId and ExpandedNodeId are converted to and from String using the syntax defined in OPC 10000-6.

Floating point values are rounded by adding 0.5 and truncating when they are converted to integer values.

Converting a negative value to an unsigned type causes a conversion error. If the conversion fails the result is a null value.

Converting a value that is outside the range of the target type causes a conversion error. If the conversion fails the result is a null value.

ByteString is converted to String by formatting the bytes as a sequence of hexadecimal digits.

LocalizedText values are converted to Strings by dropping the Locale. Strings are converted to LocalizedText values by setting the Locale to “”.

QualifiedName values are converted to Strings by dropping the NamespaceIndex. Strings are converted to QualifiedName values by setting the NamespaceIndex to 0.

A StatusCode can be converted to and from a UInt32 and Int32 by copying the bits. Only the top 16-bits if the StatusCode are copied when it is converted to and from a UInt16 or Int16 value.

Boolean values are converted to ‘1’ when true and ‘0’ when false. Non zero numeric values are converted to true Boolean values. Numeric values of 0 are converted to false Boolean values. String values containing “true”, “false”, “1” or “0” can be converted to Boolean values. Other string values cause a conversion error. In this case Strings are case-insensitive.

It is sometimes possible to use implicit casts when operands with different data types are used in an operation. In this situation the precedence rules defined in Table 123 are used to determine which implicit conversion to use. The first data type in the list (top down) has the most precedence. If a data type is not in this table then it cannot be converted implicitly while evaluating an operation.

For example, assume that A = 1,1 (Float) and B = 1 (Int32) and that these values are used with an Equals operator. This operation would be evaluated by casting the Int32 value to a Float since the Float data type has more precedence.

Table 123 – Data Precedence Rules

Rank Data Type
1 Double
2 Float
3 Int64
4 UInt64
5 Int32
6 UInt32
7 StatusCode
8 Int16
9 UInt16
10 SByte
11 Byte
12 Boolean
13 Guid
14 String
15 ExpandedNodeId
16 NodeId
17 LocalizedText
18 QualifiedName

Operands may contain null values (i.e. values which do not exist). When this happens, the element always evaluates to NULL (unless the IsNull_1 operator has been specified). Table 124 defines how to combine elements that evaluate to NULL with other elements in a logical AND operation.

Table 124 – Logical AND Truth Table

  TRUE FALSE NULL
TRUE TRUE FALSE NULL
FALSE FALSE FALSE FALSE
NULL NULL FALSE NULL

Table 125 defines how to combine elements that evaluate to NULL with other elements in a logical OR operation.

Table 125 – Logical OR Truth Table

  TRUE FALSE NULL
TRUE TRUE TRUE TRUE
FALSE TRUE FALSE NULL
NULL TRUE NULL NULL

The NOT operator always evaluates to NULL if applied to a NULL operand.

A ContentFilter which evaluates to NULL after all elements are evaluated is evaluated as false.

Previous Next