<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear group,</p>
<p>I think that our discussion has slowly come to a point where it's
possible for us to distill a minimal viable product (MVP) that
could ship with an official MEI release (thanks especially to
Ichiro). Rather than trying to include every aspect of the
ongoing discussion about semantic and paleographic encoding
approaches, I suggest we take everything that we basically already
agreed upon, focus on what still needs to be resolved for a
release and then ship the first incarnation of the new neumes
module. It will only be a first milestone, but it will give us
something to build upon.<br>
</p>
<p>I'm sure that this first incarnation could already cover enough
use cases to be a worthy successor to the existing module. The
semantically pitch oriented encoding of diastematic neumatic
notation should not be a problem. Another use case of relevance
that we did not discuss yet might be incipits where usually the
aim is not a very detailed description. It seems there's
currently no good way of encoding such incipits e.g. for RISM.<br>
</p>
<p>I see that the description of adiastematic neumes is non-trivial
and will need further discussion. This means we have to make sure
that the first incarnation is designed with the required
development in mind.</p>
<p>1. As a summary, I think we agree on the following (copied from
Ichiros's document):</p>
<blockquote><neume> element consists of one or more <nc>
element(s).<br>
A <nc> (neume component) element is a single pitched event,
although the exact pitch may not be known.<br>
A <significativeLetters> element indicates significative
letter(s) attached to a <neume> or a <nc>.<br>
<br>
Attributes for <nc>: <br>
@pname<br>
@oct<br>
@intm (interval melodic; relative to the previous <nc>)
{u|d|s|n|su|sd} (u = up, d = down, s = same, n = neutral/unknown,
su = same or higher (but not lower), sd = same or lower (but not
higher))<br>
@liquescence<br>
@ncsign {oriscus|quilisma|strophicus} a sign that has a pitch,
although the exact pitch may not be known.<br>
</blockquote>
<p>2. What I think still needs discussion for a minimal viable
product:</p>
<ul>
<li>Connection (at least I'm not entirely clear about the meaning
of "@con {{g|l|e} (gapped, looped, extended)", and there has
been another suggestion using spanners/pointers)</li>
<li><syllable>: Still use it as a wrapper? There also has
been discussion (e.g. back in Tübingen).<br>
</li>
</ul>
3. I left out the following:
<ul>
<li> everything paleographic because I'm not sure how much
discussion it still needs</li>
<li>the suggestion by Elaine and me to extend @ncsign to also
include punctus, producta, acutis and gravis as a more
semantical encoding attempt</li>
<li>episema as @artic value (maybe needs some discussion, could be
easy to include in the MVP)</li>
<li>any mechanism that would allow addressing very specific symbol
types, e.g. using something like <symbolTable>/@altsym</li>
</ul>
<p>I'd suggest focusing on point 2., prepare an ODD for the next
possible MEI release and then continue with 3. Do you think
that's a viable approach? Is there anything I missed that still
needs discussion? Is there anything in points 1. and 2. that
could cause problems when discussing 3.?</p>
<p>Best<br>
Thomas<br>
</p>
<blockquote>
<p><br>
</p>
</blockquote>
<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>