<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is pretty arcane stuff, so I expect that it will only be of interest to those who are deeply involved in creating detailed metadata regarding instrumentation, especially from MARC-encoded metadata. Consider yourself warned.
<span style="font-family:Wingdings">J</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The current model of <instrumentation> is very lax in order to allow liberal mixing of ensemble, instrVoice, and instrVoiceGrp elements –
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><content><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.headLike"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="ensemble"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoice"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoiceGrp"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"></content><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My original thinking on this was that a very loosely structured model would be helpful if <instrumentation> were ever allowed to occur with the textual parts of MEI, say in <p>. However, I believe that it is unlikely that <ensemble> will
ever occur in the presence of the other two possibilities. Therefore, unless someone can prove my hunch to be incorrect, I’m inclined to allow only one sub-element to be used at a time –
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><content><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.headLike"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:optional><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="ensemble"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoice"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoiceGrp"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> </rng:optional><o:p></o:p></p>
<p class="MsoNormal"></content><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Using this approach, one can use <ensemble> to encode the name of a performing group, like “orchestra” or use <instrVoiceGrp> to enumerate the parts/players of the group, but not both.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However, this change re-focuses attention on the relationship between <ensemble> and <instrVoice> – possibly a distinction without a difference, as the expected content of both is text and both provide the same attributes (att.authorized
and att.coded) for connecting the textual content to an authorized list. With this in mind, it might be beneficial to modify the content model even further – <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><content><o:p></o:p></p>
<p class="MsoNormal"> <rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="model.headLike"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:zeroOrMore><o:p></o:p></p>
<p class="MsoNormal"> <rng:optional><o:p></o:p></p>
<p class="MsoNormal"> <rng:choice><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoice"/><o:p></o:p></p>
<p class="MsoNormal"> <rng:ref name="instrVoiceGrp"/><o:p></o:p></p>
<p class="MsoNormal"> </rng:choice><o:p></o:p></p>
<p class="MsoNormal"> </rng:optional><o:p></o:p></p>
<p class="MsoNormal"></content><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">eliminating <ensemble> entirely. The problem with this solution is that some confusion may be created as “instrVoice” doesn’t immediately spring to mind as a way to name an ensemble. Conversely, the “Grp” part of the name “instrVoiceGrp”
may lead the unwary into thinking that it can be used to *<b>label</b>* an ensemble, when in fact it should be used to *<b>describe</b>* an ensemble.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, I’m looking for advice on how to resolve this quandary – a model that’s too lax vs. a model that’s more tightly controlled but with elements that are not completely descriptive of the material we’re trying to encode. At this point,
I’m leaning toward the most restrictive model.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is everyone OK with using <instrVoice>Band</instrVoice> to name an ensemble without enumerating its constituents and using
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><instrVoiceGrp><o:p></o:p></p>
<p class="MsoNormal"> <head>Band</head><o:p></o:p></p>
<p class="MsoNormal"> <instrVoice>Flutes</instVoice><o:p></o:p></p>
<p class="MsoNormal"> <instrVoice>Clarinets</instrVoice><o:p></o:p></p>
<p class="MsoNormal"> etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">to provide detailed instrumentation when needed? Also, has anyone created markup that this change would break?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your input,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">p.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">________________________________<br>
Perry Roland<br>
University of Virginia<br>
</span>P. O. Box 400874<o:p></o:p></p>
<p class="MsoNormal">Charlottesville, VA, 22904<span style="color:black"><br>
434-982-2702 (w)<br>
pdr4h (at) virginia (dot) edu<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>