Closed martha-thomae closed 3 years ago
The first one (the mei version issue) is affecting both the parts-based and the score-based MEI file.
Oh, and the issue with the 5.0.0 version happened because it was recently decided that the development version was going to be v5.0 (rather than 4.0.1, as it was a few days ago)
Forgot to include that the second issue in the checking list is for me :) (because it happens during the transformation from parts to score)
Hi @martha-thomae and @JRegimbal - is this issue fixed? I'll close the issue if it is.
I think this is done :)
There are just a few more validation errors in the score file (I couldn't see them before because we weren't exporting a score when we were looking into the file with the metadata issues). The remaining validation issues are:
@meiversion
in the<mei>
root element should have a value"5.0.0-dev"
according to the schema version being used (dev/mei-Mensural.rng).<label>
should be the first child of<staffDef>
(at least, it should go before<mensur>
)@dots
are not valid attributes of<note>
or<rest>
elements