<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Am 21.06.2018 um 17:56 schrieb Kate
Helsen:<br>
</div>
<blockquote type="cite"
cite="mid:CANrf7wYCXBu5xcgSCjceE-nOWGjLCzWDOVTx=7vKp2qmSe3Kxw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Looking at the adiastematic neumes in Hartker, I
would say that liquescence is a way of rendering an <nc>
that would otherwise (by "default") look a different way. I
think this means it is naturally described at the <u>attribute</u>
level. <br>
</div>
</blockquote>
<br>
<br>
Though from a musicological perspective, you would call liquescence
an attribute of the a neume component concept, this doesn't
technically mean we have to make it an XML attribute. As you
stated, we can describe liquescence in more detail if we want:<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CANrf7wYCXBu5xcgSCjceE-nOWGjLCzWDOVTx=7vKp2qmSe3Kxw@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>In this type of notation I would start with liquescent <u>forms</u>
such as: "curled" and "hoop" - to indicate that the curl has
closed all the way into a sort of circle." </div>
<div><br>
</div>
<div>The <u>placement</u> of these liquescents is usually at
the 'end' of the note (so often "ne") but sometimes they at at
the "se" - it depends on the shape of the rest of the neume. </div>
<div><br>
</div>
<div>One might also want to think about <u>direction</u> of the
"curl" - 95% of the time I'd say that it's clockwise, but
there the torculus resupinus liquescent bucks the trend by
going the other way... <br>
</div>
</div>
</blockquote>
<br>
<br>
This technically means we should make liquescence an element so that
we can go one level deeper in describing it with attributes.<br>
<br>
I want to suggest to start small with the new neumes module. I
think there are a few fundamental things that are basically agreed
upon. Step by step completing the module over a few releases would
IMO be much better than publishing a schema that no one has tested.
If we only have an abstract schema, I doubt that we really grasp the
technical and musicological implications as this field is so
specialized. I think we really need to discuss practical examples
(with facsimiles and MEI encoding) to avoid too many breaking
changes later on. I have to apologize in advance that I might not
be very actively participating in discussion, though.<br>
<br>
Thomas<br>
<br>
<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>