[mei-neumes-ig] MEI-Neumes validation issue

Gabriel Vigliensoni gabriel at vigliensoni.com
Tue May 7 18:48:07 CEST 2019


Dear all,

We are trying to validate files with square-note notation against mei-Neumes
customization. The validator is parsing all musical elements but is
throwing errors for clef and custos (error: element ... not allowed here).
On the contrary, if we use mei-all the validation passes successfully.

We looked at the mei-Neumes customization file and realized that
model.eventLike is being modified (
https://github.com/music-encoding/music-encoding/blob/develop/customizations/mei-Neumes.xml#L113-L120),
with the result that clef and custos elements have to be within syllable
instead of layer. Is this an unintended error or are there any special
motives for this decision?

Thank you,

Gabriel

PS: Attached to this email there is a basic MEI example with neume notation
that cannot be validated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-neumes-ig/attachments/20190507/65b40705/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example-neume.mei
Type: application/octet-stream
Size: 1150 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-neumes-ig/attachments/20190507/65b40705/attachment.obj>


More information about the mei-neumes-ig mailing list