<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>.EmailQuote {
BORDER-LEFT: #800000 2px solid; PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt
}
</style><style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi="0" fPStyle="1">
<div style="FONT-FAMILY: Arial Unicode MS; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 12pt">
<font size="2"></font>
<div style="FONT-FAMILY: Arial Unicode MS; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 12pt">
<p>Hi, Thomas,</p>
<p> </p>
<p>I think you're asking -- Why are the clef* attributes allowed on <scoreDef> but the <clef> element isn't allowed as a child of <scoreDef>? Is that right?</p>
<p> </p>
<p>I've been waiting for someone else to notice this before I brought it up myself :) because I anticipated that the next request would be for <clef> and <meter> elements and so on until all the attributes on <scoreDef> were duplicated by element children.
I was hoping to limit these requests to those that couldn't be fulfilled by an attribute -- in other words, where more than one value might be needed or where more detailed data was needed, such as explicit placement information on the accidentals in a key
signature.</p>
<p> </p>
<p>But, the tech group could/should discuss adding <clef> (and perhaps <clefGrp>) as well -- these are members of model.staffDefPart. Next, maybe <meter>. These can all be proposed for the next, next MEI revision (2013?). But, we must be careful because if
the list of new elements for <scoreDef> goes much beyond these, then it will have ripple effects throughout the schema that will require much more discussion / work.</p>
<p> </p>
<p>Does this help?</p>
<p> </p>
<p>--</p>
<p>p.</p>
<p> </p>
<p><font size="2">__________________________<br>
Perry Roland<br>
Music Library</p>
</font><font size="2">
<div>
<div class="BodyFragment">
<div class="PlainText">University of Virginia</div>
<div class="PlainText">P. O. Box 400175</div>
<div class="PlainText">Charlottesville, VA 22904<br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu</div>
</font></div>
</div>
<div>
<hr tabindex="-1">
<div id="x_divRplyFwdMsg"><font color="#000000" size="2" face="Tahoma"><b>From:</b> mei-l-bounces@lists.uni-paderborn.de [mei-l-bounces@lists.uni-paderborn.de] on behalf of TW [zupftom@googlemail.com]<br>
<b>Sent:</b> Thursday, December 08, 2011 4:18 PM<br>
<b>To:</b> Music Encoding Initiative<br>
<b>Subject:</b> Re: [MEI-L] @clef* inside scoredef<br>
</font><br>
</div>
<div></div>
</div>
<font size="2"><span style="FONT-SIZE: 10pt">
<div class="PlainText">I'm grave digging an old thread because I noticed that this is still<br>
in MEI 2012:<br>
<br>
2011/7/10 TW <zupftom@googlemail.com>:<br>
> I'm wondering why the @clef* family of attributes is allowed on<br>
> <scoredef>, but the <clef> element isn't.<br>
><br>
<br>
(only with camelCase <scoreDef>). Is there a specific reason?<br>
<br>
Thomas<br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
mei-l@lists.uni-paderborn.de<br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</div>
</span></font></div>
</div>
</body>
</html>