[MEI-L] Encoding Notre Dame Polyphonic Neumes

[Joshua Stutter]

Dear all,

A week later followup. I've resigned myself to have to customise
MEI-neumes.xml to support this polyphonic neume notation and am trying
to work my way through the sparse documentation. Unfortunately, I've
fallen at the first hurdle.

Attempting to generate the schema without any of my own customisation, I
opened up TEI Roma and uploaded the MEI-neumes.xml customisation direct
from Github (because the "customeization" service appears to have been
broken for over a fortnight now without any sign that it is being
fixed). Roma appears to parse the customization without issue, but fails
when pulling in the SVG elements:

> <error msg="to RNG then Trang to make RNC failed:
> net.sf.saxon.s9api.SaxonApiException: org.xml.sax.SAXParseException;
> systemId:
> http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/svg11.rng;
> lineNumber: 6; columnNumber: 3; The element type "hr" must be
> terminated by the matching end-tag "</hr>"." exclass="class
> java.io.IOException" >java.io.IOException: to RNG then Trang to make
> RNC failed: net.sf.saxon.s9api.SaxonApiException:
> org.xml.sax.SAXParseException; systemId:
> http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/svg11.rng;
> lineNumber: 6; columnNumber: 3; The element type "hr" must be
> terminated by the matching end-tag "</hr>".
>     at
> pl.psnc.dl.ege.tei.TEIConverter.convertDocument(TEIConverter.java:306)
>     at pl.psnc.dl.ege.tei.TEIConverter.convert(TEIConverter.java:154)
>     at
> pl.psnc.dl.ege.component.NamedConverter.convert(NamedConverter.java:44)
>     at pl.psnc.dl.ege.ConversionPerformer.run(ConversionPerformer.java:45)
>     at java.lang.Thread.run(Thread.java:748)
> </error>
Looking through svg11.rng, there is no mention of <hr>. Am I using Roma
correctly here or is this an upstream issue at TEI? The same issue
occurs on MEI-CMN.xml

Joshua.

On 09/03/2019 14:26, Joshua Stutter wrote:
>
> Dear all,
>
> Fairly new MEI user, trying to encode some 13th-century Notre Dame
> notation into MEI for a class. MEI has good support for many neumes,
> but I'm attempting to get them to work in a polyphonic context, align
> correctly and with good semantics. Here is a small example which I'm
> attempting to encode:
>
> Small Notre Dame example.
>
> Most of the neumes can be notated and typed with the exception of the
> complex neume FGBGA which does not have a name. This is fine as this
> music does not stick to the usual neume types.
>
> My first issue arises when trying to show the first tenor note D is
> aligned with the porrectus GFG. How would I go about achieving this
> without using semantically-incorrect spacers or invisible rests or
> durations? What I really wish for is the possibility to encode
> sections of polyphony in groups that are aligned together, i.e. the
> first three neumes in the organal voice in one group, then the
> porrectus in a new group with the tenor virga.
>
> The second issue is the vertical lines. They are not barlines, nor
> always rests. They are divisiones with a complex and context-sensitive
> function. Sometimes they function as rests, sometimes they are
> alignment marks, sometimes syllable marks.
>
> The first attached file 'benedicamus-domino.mei' encodes this example
> naively. Nothing is aligned and I use <barLine> where divisiones are.
>
> The second attached file 'benedicamus-domino-wish.mei' is how I wish
> to encode this file, using a made-up element <alignmentGrp> that can
> contain anything a <section> contains. I have also replaced the
> <barLine> with another made-up element <divisio>.
>
> Needless to say, I'm not concerned with the output in verovio, as very
> little neumatic notation is supported anyway, but instead encoding the
> alignment and elements correctly. Is something like this possible in
> MEI already or will I have to dabble in ODD? If I must, are there any
> links to a good workflow and documentation for using ODD with MEI?
>
> Thanks in advance for responding to this quite complex question,
>
> Joshua Stutter.
>
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190316/fbabf6ce/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: notre-dame-example.jpg
Type: image/jpeg
Size: 74075 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190316/fbabf6ce/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20190316/fbabf6ce/attachment.sig>