The changes in this PR have the effect that some existing manifests don't validate against the xsd any more. In particular it seems not to be allowed any more with the new xsd that a <hash> element comes after a <directoryhash> element. Up to now <hash> and <directoryhash> elements could be mixed.
Is this an intended change?
Attached a (now) failing mhl manifest. The error during validation:
% ascmhl xsd-schema-check [path to]/0001_A002R2EC_2021-12-01_141347.mhl
ERROR: /Users/ptr/Desktop/A002R2EC/ascmhl/0001_A002R2EC_2021-12-01_141347.mhl didn't validate against XSD!
Issues:
/Users/ptr/Desktop/A002R2EC/ascmhl/0001_A002R2EC_2021-12-01_141347.mhl:42:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element '{urn:ASC:MHL:v2.0}hash': This element is not expected. Expected is ( {urn:ASC:MHL:v2.0}directoryhash ).
Error: Verification of files referenced in the ASC MHL history failed
The changes in this PR have the effect that some existing manifests don't validate against the xsd any more. In particular it seems not to be allowed any more with the new xsd that a
<hash>element comes after a<directoryhash>element. Up to now<hash>and<directoryhash>elements could be mixed.Is this an intended change?
Attached a (now) failing mhl manifest. The error during validation:
0001_A002R2EC_2021-12-01_141347.mhl.zip