<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear list,<br>
<br>
because Elaine and me aren't in Tours, we looked through the draft
together and would like to give our input for the upcoming
meeting. From the perspective of Corpus monodicum, this
definitely is heading in the right direction. There are some
changes we'd suggest:<br>
<ul>
<li><b>Quilisma/Oriscus</b>: So far, we've only encoded whether
something is or is not an oriscus or quilisma - i.e. no more
detailed information about the shape. The project won't
change that, so we'd like to suggest to also offer a simple
"true/false" option, like with @episima. Mixing boolean and
numbers is a little odd, but the alternative would be two
separate attributes, which wouldn't be any handier.</li>
<li>We'd suggest a <b>strophicus</b> attribute. Strophici
could be handled using taxonomies, but they are so common that
we think they deserve their own attribute, just like oriscus
and quilisma.<br>
</li>
<li>We'd need <<b>note</b>> inside <nc> to encode
pitch information for diastematic notation - or alternatively,
@pname/@oct on <nc>. <note> is probably
preferable.</li>
<li>Currently, you can put <<b>accid</b>> inside
<syllable>. I don't think this is the appropriate place
to put an accidental. We have two situations where we have to
deal with accidentals:</li>
<ul>
<li>Accidentals that are "attached to" a neume. It would make
most sense if they were child elements of that <neume>
element.</li>
<li>Accidentals that are not attached to a neume, i.e.
sort-of-but-not-quite key signatures. To use the currently
allowed <keySig> (inside <staffDef>) in these
situations doesn't seem appropriate. It would suggest that
use and implications of these accidentals are identical to
modern key signatures, which as far as I understand is not
the case - or we lack that knowledge. It would be useful to
put them right between the <neume> elements - most of
the time (but not always) immediately after a <sb>.<br>
</li>
</ul>
<li>We need to encode <b>rubrics</b> and would introduce a
<rubric> element inside <layer>, ideally with a
@type attribute that might be an open list with suggested
values feast (e.g. for a rubric "De Sancto Stephano"), service
(e.g. for a rubric "Ad summam missam") and genre (e.g. for a
rubric "Alleluia").<br>
</li>
</ul>
During the last meeting in Tübingen, the <syllable> element
was challenged. I think one motivation was to make the hierarchy
of the neumes and mensural modules more compatible for projects
that have to deal with both. We can't say a lot about that,
though.<br>
<br>
To everybody in Tours: Have a great un-conference day!<br>
Thomas<br>
<br>
<br>
Am 11.05.2017 um 09:26 schrieb Ichiro Fujinaga, Prof.:<br>
</div>
<blockquote type="cite"
cite="mid:B7F77BFF-E906-4A43-9512-F164C69BFEB3@mcgill.ca">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="BodyFragment"><font size="2"><span
style="font-size:10pt;">
<div class="PlainText">Dear List,<br>
<br>
Perry Roland has kindly worked on a new version of the MEI
Neumes Module schema.<br>
This was based on my suggestions, which were based on the
discussions at the last MEI Neumes Interest Group (19
November 2016, Tübingen) and at various Cantus Ultimus
meetings. <br>
<br>
I hope this will be a staring point for fruitful
discussions on this list and at the upcoming Neumes
Interest Group meeting in Tours on Friday 19 May.<br>
<br>
Attached are an ODD file with Perry’s comments at the
bottom; an RNG file; and a test MEI file. All provided by
Perry.<br>
Below is what I provided to Perry.<br>
<br>
================================<br>
<br>
A <neume> element consists of one or more
<neumeComponent> element(s).<br>
<br>
A <neumeComponent> is a single pitched event,
although the exact pitch may not be known.<br>
<br>
Attributes for <neume><br>
@direction (relative to the previous <neume>)
{N|S|L|H|SH|SL}<br>
N: neutral or unknown<br>
H: higher<br>
L: lower<br>
S: same <br>
SH: same or higher (but not lower)<br>
SL: same or lower (but not higher)<br>
@significative letters<br>
@hispanicLoop (not sure about this)<br>
<br>
Attributes for <neumeComponent><br>
@direction: pitch relative to the previous pitch
(<neumeComponent>) within the same <neume>
{N|S|L|H|SH|SL}<br>
N: neutral or unknown<br>
H: higher<br>
L: lower<br>
S: same or unison<br>
SH: same or higher (but not lower)<br>
SL: same or lower (but not higher)<br>
@wavy<br>
@curved (anticlockwise, clockwise)<br>
@angled<br>
@episma<br>
@flat<br>
@jagged<br>
@liquescence<br>
@extended<br>
@diagonal right (up or down)<br>
@quilisma (2 or 3 curves)<br>
@long<br>
@oriscus (curved, flat, jagged)<br>
@connection (gapped, looped) (to the previous
neumeComponent within the same <neume>)<br>
<br>
================================<br>
<br>
Ichiro<br>
<br>
</div>
</span></font></div>
<div class="BodyFragment"><font size="2"><span
style="font-size:10pt;">
<div class="PlainText"><br>
<br>
</div>
</span></font></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mei-neumes-ig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mei-neumes-ig@lists.uni-paderborn.de">mei-neumes-ig@lists.uni-paderborn.de</a>
<a class="moz-txt-link-freetext" href="https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig">https://lists.uni-paderborn.de/mailman/listinfo/mei-neumes-ig</a>
</pre>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="0">--
Notengrafik Berlin GmbH
HRB 15007
UstID: DE 289234097
Geschäftsführer:
Thomas Weber und Werner J. Wolff
fon: +49 30 220661685
Leuschnerdamm 13
10999 Berlin
notengrafik.com</pre>
</body>
</html>