Errata exists for this version of the document.
NodeId values shall be encoded as a JSON object with the fields defined in Table 23.
The abstract NodeId structure is defined in OPC 10000-3 and has three fields Identifier, IdentifierType and NamespaceIndex. The representation these abstract fields are described in the table.
Table 23 – JSON Object Definition for a NodeId
|
Name |
Description |
|
IdType |
The IdentifierType encoded as a JSON number. Allowed values are: 0 - UInt32 Identifier encoded as a JSON number. 1 - A String Identifier encoded as a JSON string. 2 - A Guid Identifier encoded as described in 5.4.2.7. 3 - A ByteString Identifier encoded as described in 5.4.2.8. This field is omitted for UInt32 identifiers. |
|
Id |
The Identifier. The value of the id field specifies the encoding of this field. |
|
Namespace |
The NamespaceIndex for the NodeId. The field is encoded as a JSON number for the reversible encoding. The field is omitted if the NamespaceIndex equals 0. For the non-reversible encoding, the field is the NamespaceUri associated with the NamespaceIndex, encoded as a JSON string. A NamespaceIndex of 1 is always encoded as a JSON number. |