<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 16.10.2017 um 20:57 schrieb Roland,
Perry (pdr4h):<br>
</div>
<blockquote type="cite"
cite="mid:CY1PR13MB012732D29AE56B26BF92D50C9F4F0@CY1PR13MB0127.namprd13.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Times New Roman",serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Encoding
shape as a substitute for semantics is not good practice.</span></p>
</div>
</blockquote>
<br>
<br>
I fully agree that here's a clear case where visual and semantic
encodings should be separated.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CY1PR13MB012732D29AE56B26BF92D50C9F4F0@CY1PR13MB0127.namprd13.prod.outlook.com">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">It would be
better to explicitly record the fact that a neume is an
oriscus using a Boolean attribute and its visual qualities
and its participation in an “ornamental neume” class
separately.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
<br>
Elaine and me came to the conclusion that some boolean attributes
could be combined because they are mutually exclusive. This is
namely quilisma and oriscus; and we'd also want to see strophicus.<br>
<br>
We suggested an @ncsign attribute at the Cantus Network conference
in Graz that could take on the values "oriscus", "quilisma" and
"strophicus".<br>
<br>
<a class="moz-txt-link-freetext" href="http://cm.notengrafik.com/2017-Graz-Cantus-Network/presentation/presentation.html#code-sign">http://cm.notengrafik.com/2017-Graz-Cantus-Network/presentation/presentation.html#code-sign</a><br>
<br>
Additional values could be the earlier suggested "acutis", "gravis",
"punctus" and "producta" that would make more semantic encoding of
each component possible. Inga reported that at the Cantus Ultimus
wokshop, this suggestion was rejected. The reason seemed to be
terminology. Elaine addressed this to explain that terminology is
not the core of the suggestion but the concept behind it - but so
far, she didn't get a reaction:<br>
<br>
<br>
<div class="moz-cite-prefix">Am 25.09.2017 um 11:19 schrieb Elaine
Stratton Hild:<br>
</div>
<blockquote type="cite"
cite="mid:59C8CA39020000E300067679@gwia01.uni-wuerzburg.de">
<div
id="GroupWiseSection_1506330625000_elaine.stratton_hild@uni-wuerzburg.de_22F7948007F60000A796000000000000_"
class="GroupWiseMessageBody">
<div> <font face="Tahoma, sans-serif">Thomas Weber and I took
the
terms for the basic elements from Anonymous
Vaticanus—because his terms work
(they can be combined to describe any notational sign from
all families) and
because they have a historical basis—but in the encoding,
these basic elements
could be called anything, really. We just need to be able to
encode “the sign
that shows a higher pitch" (acuta), “the sign that shows a
lower pitch and is
usually connected with others" (gravis), “the sign that
shows a lower pitch and
can stand by itself" (punctus), etc. The terms we’re using
for these basic
elements would never need to be used in a musicological
publication; they serve
a purpose for encoding that our usual terms cannot.</font>
<p class="MsoNormal"><font face="Tahoma, sans-serif"> </font></p>
<p class="MsoNormal"><font face="Tahoma, sans-serif">I
understand that the Old Hispanic notation does not have a
sign that musicologists refer to as “acuta”, but the
notation does
have signs with the same meaning. The acuta is simply a
term for the sign that
means “one pitch, usually of higher pitch content than the
preceding pitch”. As
of the twelfth century, especially in German-speaking
regions, the sign was
called “virga” when it appeared by itself (uncombined with
other signs). It
is also the second element of the “pes” and the first of
the “clivis”, in Sankt
Gallen’s notation as well as in Old Hispanic.</font></p>
<p class="MsoNormal"><font face="Tahoma, sans-serif"> </font></p>
</div>
</div>
</blockquote>
<br>
<br>
We applied this to Cardine's table and created the following:<br>
<br>
<a class="moz-txt-link-freetext" href="http://cm.notengrafik.com/2017-Graz-Cantus-Network/cardine-table/cardine_web.xml">http://cm.notengrafik.com/2017-Graz-Cantus-Network/cardine-table/cardine_web.xml</a><br>
<br>
(Here I played with elements instead of an @ncsign attribute, but
that doesn't really matter.) The idea would be that our suggested
classes can be used to break down the signs into their logical
components and and allow them to be identified by their "data
shape", as Andrew called it.<br>
<br>
While the suggested classes give some information about the pitch
contour, they can't be replaced with @intm. @intm would not be well
suited for the "data shape" approach. Depending on the context a
sign appears in, in one case the only info we can give about, say,
its second <nc> might be that it's @intm="su". In another
context, we might be able to give more precise info about that very
same <nc> - we might know it's actually @intm="s" or @intm="u"
(or possibly even a precise interval). This means, because we have
different @intm, we won't be able to identify the sign by its data
shape. The same sign can have different @intm data shapes in
different places.<br>
<br>
<br>
Grüße<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>
<br>
<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>