<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.Code, li.Code, div.Code
{mso-style-name:Code;
mso-style-link:"Code Char";
margin:0in;
font-size:9.0pt;
font-family:"Courier New";}
span.CodeChar
{mso-style-name:"Code Char";
mso-style-link:Code;
font-family:"Courier New";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Times New Roman",serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1763531815;
mso-list-type:hybrid;
mso-list-template-ids:984755946 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Hi Dennis, everyone,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">I’m not sure to what extent I may be able to participate in the next interest group meeting (when is it?), so I offer some comments on the perfRes proposal here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">1. Ambitus – I generally support the idea of adding <ambitus> inside <perfRes>, depending on the details of the implementation, of course. For example, a better way of indicating alternative
ranges than allowing more than 2 <ambNote> elements in <ambitus> would be to permit <ambitus> to occur multiple times within <perfRes>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="Code"><perfRes><o:p></o:p></p>
<p class="Code"> <ambitus><o:p></o:p></p>
<p class="Code"> <ambNote pname="c" oct="4"/><o:p></o:p></p>
<p class="Code"> <ambNote pname="d" oct="5"/><o:p></o:p></p>
<p class="Code"> </ambitus><o:p></o:p></p>
<p class="Code"> <ambitus type="alt"><o:p></o:p></p>
<p class="Code"> <ambNote pname="c" oct="4"/><o:p></o:p></p>
<p class="Code"> <ambNote pname="f" oct="5"/><o:p></o:p></p>
<p class="Code"> </ambitus><o:p></o:p></p>
<p class="Code"></perfRes><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">If necessary (though I think it probably won’t be), @type may be used to make a distinction between the uses of the <ambitus> elements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">2. Tuning – The proposal to use @tune.pname conflicts with the use of this attribute elsewhere, a definite no-no in schema design. It would be better to allow the use of @</span><span style="font-family:"Times New Roman",serif">trans.diat
and @trans.semi to indicate how the instrument transposes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">3. Ad Libitum – I see no problem with adding an @adLib attribute to <perfRes>. It may be useful to also allow it on <perfResList> to allow a *group* of resources to be marked ‘ad lib’.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">4. <perfRes> is allowed to nest in order to accommodate complex situations like this, although I suspect the law of diminishing returns comes into play when you state explicitly that the
piano is to be played with 2 hands, one of which is the left and the other, the right. It does beautifully allow for the very rare circumstance when one is confronted with a composition for a player who has 3 left hands!
</span><span style="font-family:"Segoe UI Emoji",sans-serif">😊</span><span style="font-family:"Times New Roman",serif"> Seriously, I think one must remember that just because it’s possible to record increasing complexity, it’s not always practical or helpful.
It’s called ‘metadata’ for a reason – it’s ‘meta’; that is, it’s at a higher level of abstraction.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">5. <perfResList> vs. <perfResGrp> – The name ‘perfResList’ was chosen as the name here because performing resources are typically ordered in the score. Technically, a list and a group are
conceptually interchangeable, the name taking a back seat to the fact that they both contain a ‘set’ of children. Changing the name now would introduce a backward incompatibility that’s not worth the trouble, in my opinion.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">6. It’s not exactly clear, but by mentioning <desc> in the context of <perfRes>, I presume you’re suggesting replacing the current model –
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="Code"><content><o:p></o:p></p>
<p class="Code"> <rng:zeroOrMore><o:p></o:p></p>
<p class="Code"> <rng:choice><o:p></o:p></p>
<p class="Code"> <rng:text/><o:p></o:p></p>
<p class="Code"> <rng:ref name="model.textPhraseLike.limited" /><o:p></o:p></p>
<p class="Code"> <rng:ref name="perfRes" /><o:p></o:p></p>
<p class="Code"> </rng:choice><o:p></o:p></p>
<p class="Code"> </rng:zeroOrMore><o:p></o:p></p>
<p class="Code"></content><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">with <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="Code"><content><o:p></o:p></p>
<p class="Code"> <rng:zeroOrMore><o:p></o:p></p>
<p class="Code"> <rng:choice><o:p></o:p></p>
<p class="Code"> <rng:ref name="desc" /><o:p></o:p></p>
<p class="Code"> <rng:ref name="perfRes" /><o:p></o:p></p>
<p class="Code"> </rng:choice><o:p></o:p></p>
<p class="Code"> </rng:zeroOrMore><o:p></o:p></p>
<p class="Code"></content><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Doing so would clear up the somewhat messy current content model. However, it would also require an extra bit of hierarchy for those who want to describe resources in a textual fashion;
that is,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="Code"><perfRes><o:p></o:p></p>
<p class="Code"> <desc>Orchestra</desc><o:p></o:p></p>
<p class="Code"></perfRes><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">would be required instead of the currently allowed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="Code"><perfRes>Orchestra</perfRes><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">the simplicity of which comes at the cost of complexity in the model. Making this change, like the one above, would introduce backward incompatibility that must be assessed for practicality.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif">p.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mei-catalog-ig <mei-catalog-ig-bounces@lists.uni-paderborn.de>
<b>On Behalf Of </b>Dennis Ried<br>
<b>Sent:</b> Monday, January 25, 2021 12:10 PM<br>
<b>To:</b> mei-catalog-ig@lists.uni-paderborn.de<br>
<b>Subject:</b> [mei-catalog-ig] Proposal on <perfRes/> (next step)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif">Dear Listeners,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif"><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif">Clemens and I have been working again on the proposal to extend <perfMedium/>. We have now reached a further stage, which we want to share with the interest group again. The
document is read-only, but we would ask you to prepare comments on this paper likely for the next metadata-meeting – on 28th January (I guess).</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif"><br>
<br>
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif">Document:</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif"><a href="https://docs.google.com/document/d/1ykdOncyCFEnU1hhQu5KTccHEHQ53blMYgkg5jtcCPdc/edit?usp=sharing">https://docs.google.com/document/d/1ykdOncyCFEnU1hhQu5KTccHEHQ53blMYgkg5jtcCPdc/edit?usp=sharing</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;font-family:"Arial",sans-serif">See also some Sample-encodings:<br>
<a href="https://github.com/riedde/sample-encodings/tree/feature/perfResSamples/MEI_4.0/Header/PerfMedium">https://github.com/riedde/sample-encodings/tree/feature/perfResSamples/MEI_4.0/Header/PerfMedium</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><a href="https://github.com/riedde/sample-encodings/tree/feature/perfResSamples/MEI_4.0/Header/PerfMedium" target="_blank"><span style="font-size:11.5pt;font-family:"Arial",sans-serif;text-decoration:none"><br>
</span></a><span style="font-size:11.5pt;font-family:"Arial",sans-serif">All the best and stay healthy<br>
Dennis & Clemens<br>
P.S. If you can't join the meeting you can send us your comments directly (if you have some).</span><br>
<br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">Mit freundlichen Grüßen aus Waldsee,<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">__________________________________<br>
</span><span style="font-size:7.0pt;font-family:"Helvetica",sans-serif;color:black"> </span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica",sans-serif;color:black">Dennis Ried, M.A.</span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">Musikwissenschaft | Digital Humanities</span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Helvetica",sans-serif;color:black"> </span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><br>
Weimarer Straße 27<br>
D-67165 Waldsee<br>
</span><span style="font-size:7.5pt;font-family:"Helvetica",sans-serif;color:black"> </span><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">Mobil: +49-176-30 53 57 83<br>
<a href="mailto:ried-musikforschung@mail.de">ried-musikforschung@mail.de</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">__________________________________<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>