Is it possible that you have an ItemDef element with OID “SUPPAE.QNAM”? If so, I guess that may cause the issue as OID should be unique within MetaDataVersion element.
Although there is no required naming convention for OIDs, the approach used in Define-XML 2.0 specification is a good one and can help to avoid issues. If it was used, the ItemDef OID for QVAL would be “IT.SUPPAE.QVAL” and ValueListDef OID for it would be “VL.SUPPAE.QVAL”.
Presumably “false positive” …
I think that the algorithm (falsely) assumes that when the 200th byte is a non-blank, there should come more …
And “High risk” is a stupid message … How can such an algorithm even try to quantify a risk …
I am validating define.xml 2.0 and getting this issue, “Missing Value Level metadata for QVAL in Dataset ” for all my SUPPQUAL datasets, and I cannot figure out why. Here’s the definition of SUPPAE.QVAL:
Data Value
It does reference the value list with ID “SUPPAE.QNAM”. This value list is defined too: