Updated 5.4.2.16 to require the use of the DataType NodeId when ExtensionObjects are encoded within a JSON document.

Agreed to changes in web meeting,

From my colleague Frank:
It is not clear what the condition "If the ExtensionObject is being serialized as part of a JSON document [...]" means.

The binary encoding still uses the EncodingId for JSON bodys, it would be possible to also use the TypeId by adding a
value for JSON bodys to the Encoding byte.

Matthias:
Changing the TypeId to DataType also in binary ExtensionObject would solve also the discussion we had for related issue 0009073 and would eliminate the need for the JSON DataTypeEncoding nodes.

Changed text to:
When serializing a PubSub Message (see XXX), the NodeId of the DataType Node is used instead.

Agreed to changes in F2F.

We reverted Part 6 to allow either the DataType Encoding Node or a DataType Node. Part 14 needs to clarify "When serializing a PubSub Message (see XXX), only the NodeId of the DataType Node is used , never the DataType Encoding node."

7.2.5 JSON message mapping
7.2.5.1 General

Added following text:
The JSON message mapping uses the OPC UA JSON encoding defined in OPC 10000-6. If an ExtensionObject is encoded, the TypeId shall be the DataType NodeId of the contained structure.

Agreed to changes in web meeting.