numDatSetEntries defines the number of DataSet entries.
What happens when a DataSet entry is a composite attribute (e.g. Pos) ? Is only the high level object counted ? If so, protection provided by this attribute is weak, since the number of primitive attributes within the composite attribute is not checked. Wouldn't the number of primitive DA be a better protection ?
Proposal
The combination of DataSet name and software version is sufficient to
check the contents, this field should be skipped as providing an illusory - and therefore dangerous - protection.