Actually, there seems to be more confusion about where the DataSetClassID belongs. Under table 126 - DataSetReaderType Definition, the DataSetClassId is mentioned among properties (of the DataSetReaderType) - but there is no such property.

I would argue that the most logical solution (although not backwards compatible) would be to add this DataSetClassId to DataSetReaderType (and DataSetReaderDataType), and remove it from UadpDataSetReaderMessageType/DataType.

Note that filtering by DataSetClassId is also mentioned in Figure 8 (Subscriber message reception sequence) and in the text below it, further enforcing the concept that the DataSetClassid is not tied to specific message mappings.

Adding to the previous note - the DataSetClassId mentioned under Table 126 - DataSetReaderType Definition does not exist on the type, but there is DataSetClassId in the DataSetMetaDataType (the DataSetMetaData property). Given this, there is probably no reason to add DataSetClassId to the DataSetReaderType, but the text below Table 126 - DataSetReaderType Definition should be corrected to refer to the DataSetMetaData.DataSetClassId.

UA WG Lisbon

We generally agreed that this is a missing setting but we do not want to create a new structure at this point in time.
If the structure is revised, we want to add the DataSetClassId. Another candidate is the PublishingInterval

Added DataSetClassId filter for JSON messages:

6.3.2.4.4 DataSetClassId
The parameter DataSetClassId with DataType Guid defines a DataSet class related filter. If the value is null of the paremeter is not set, the DataSetClassId filter is not applied.
The parameter is configured in the DataSetReadProperties with the Key DataSetClaasId.

This is currently configured through DataSetReadProperties. Otherwise we would need a JsonDataSetReaderMessage2DataType. We can include the DataSetClassId if we add a JsonDataSetReaderMessage2DataType in later versions.

Agreed to changes in web meeting.