If the DataSetMetaData of a PublishedDataSet does not equal the DataSetClassId, the DataSetClassId cannot be used for the PublishedDataSet.
This is the basic feature for a DataSetClassId that the metadata is fixed.

This would require that all Variables mapped to the PublishedDataSet must have the Property values that comply with the range and unit properties in the DataSetMetaData.

Discussion at F2F:

• DataSetClassId means FIXED metadata which means field property values are the same for all DataSetWriters
• CS can define common DataSets and assign a qualified Name for the DataSetName and an optional DataSetClassId
• if a user of the wants to reuse the structure by with changing field properties the qualified Name of the CS DataSet is used;
• if a DataSetClassId is defined and a user wants to use the predefined values for the field properties then one metadata message can published for all DataSetWriters
• a shared metadata message can be implement with shared metadata topic in MQTT

Further discussion was to allow field properties to be changed depending on configuration version setting.
DataSetClassId set -> The structure of the message is defined and cannot be changed
ConfigurationVersion is 0/0 -> The complete DataSetMetaData is fixed for all instance, nothing can be changed, including field properties
ConfigurationVersion set -> field property values depend on the configuration version