<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000099"><div>Perry's proposal makes sense to me. <br></div><div><br></div><div>Eleanor<br></div><div><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Perry D. Roland (pdr4h)" <pdr4h@eservices.virginia.edu><br><b>To: </b>mei-l@lists.uni-paderborn.de<br><b>Sent: </b>Monday, March 2, 2015 8:43:03 AM<br><b>Subject: </b>[MEI-L] <instrumentation> within <source>?<br><div><br></div><style><!--
@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;}
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:"Times New Roman","serif";
color:black;}
.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><div class="WordSection1"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;"> </span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;">There has recently been some discussion on mei-devel about the markup of instrumentation/performance medium information. To deal with missing, incomplete, or contradictory info about instrumentation at the work level (the only place this info is currently permitted), the current proposal is to make <instrumentation> and its sub-elements (instrVoice, instrVoiceGrp and ensemble) members of att.edit. This will provide @cert, @evidence, @resp, and @source.</span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;"> </span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;">The second part of the effort, which may be slightly more controversial, centers on allowing <perfMedium> to occur not just within <work>, but also at the manifestation level; that is, within <source>. Currently, <perfMedium> is allowed within <expression>, but not <source> in an effort to encourage the use of FRBR entities and to make a clear separation between expression and manifestation data. But, a compelling case can be made that if <perfMedium> were allowed within <source>, then <expression> could take on more of a grouping role in those cases where there are multiple manifestations of what is essentially the same expression, for instance, when there’s a short score/sketch, a piano reduction (intended for rehearsal) and a full score of a symphonic work. It may be more productive to allow each of these sources to carry instrumentation info and use <expression> to group them as one *version of the work* as opposed to a later revision than to force instrumentation to always be recorded at the expression level, resulting in many cases in a one-to-one relationship between <source> and <expression> without the possibility of grouping at a higher level.</span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;"> </span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;">I’m inclined to make this latter change, but would like to hear from others before moving ahead.</span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;"> </span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;">--</span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;">p.</span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black" data-mce-style="font-size: 12.0pt; font-family: 'Times New Roman','serif'; color: black;"> </span></p><p class="MsoNormal"><span style="font-family:"Times New Roman","serif";color:black" data-mce-style="font-family: 'Times New Roman','serif'; color: black;">__________________________<br> Perry Roland<br> Music Library<br> University of Virginia<br> P. O. Box 400175<br> Charlottesville, VA 22904<br> 434-982-2702 (w)<br> pdr4h (at) virginia (dot) edu</span></p><p class="MsoNormal"> </p></div><br>_______________________________________________<br>mei-l mailing list<br>mei-l@lists.uni-paderborn.de<br>https://lists.uni-paderborn.de/mailman/listinfo/mei-l<br></div><div><br></div></div></body></html>