Hello,<div><br></div><div>As Andrew said, @source helps, as it expresses the fact that both readings are from one source.</div><div><br></div><div>Though if I understand Thomas' issue correctly, he's also interested in encoding the fact that the two apps can form one apparatus entry.</div>
<div><br></div><div>Imagine for example an apparatus entry that says:</div><div><br></div><div>Measures 1-2; System: Flutes; Comment: values of rests are incorrect in source A; source B has correct values.</div><div><br>
</div>
<div>This can be split in two apps, like in the example that Andrew wrote. However, using only @source wouldn't reflect the fact that the two apps are part of one editorial statement.</div><div><br></div><div>A use case for using @prev and @next would be to be able to generate the apparatus entry above from the encoding (I have seen this done in TEI).</div>
<div><br></div><div>I don't think it's particularly urgent, but I can definitely see value in having @prev and @next on app. At least it would compensates for the fact that one app can contain several staves in one measure at once, but not multiple measures in one staff.</div>
<div><br></div><div>Best,</div><div>Raffaele</div><div> <br><br><div class="gmail_quote">On Sun, Jul 15, 2012 at 1:53 PM, Andrew Hankinson, Mr <span dir="ltr"><<a href="mailto:andrew.hankinson@mail.mcgill.ca" target="_blank">andrew.hankinson@mail.mcgill.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Thomas,<div><br></div><div>I think you're looking for @source on <rdg>. </div>
<div><br></div><div><meiHead></div><div>....</div><div><sourceDesc><br> <source xml:id="sourceA"><br> <pubStmt/></div><div> </source><br> <source xml:id="sourceB"><br>
<pubStmt/><br> </source><br></div><div></sourceDesc></div><div>....</div><div></meiHead></div><div>...</div><div><span style="font-family:monospace"><measure n="1"></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <app></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <rdg source="sourceA"></span><div class="im"><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="1"></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <!-- Some music --></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </staff></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </rdg></span><span style="font-family:monospace"><br></span></div>
<span style="font-family:monospace"> <rdg source="sourceB"></span><div class="im"><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="1"></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <!-- Some variant of the music --></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </staff></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </rdg></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </app></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="2"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="3"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="4"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="5"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="6"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="7"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="8"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="9"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="10"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </measure></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <measure n="2"></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <app></span><span style="font-family:monospace"><br></span></div><span style="font-family:monospace"> <rdg source="sourceA"></span><div class="im"><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="1"></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <!-- Some more music --></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </staff></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </rdg></span><span style="font-family:monospace"><br></span></div>
<span style="font-family:monospace"> <rdg source="sourceB"></span><div class="im"><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="1"></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <!-- Continued variant of the music --></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </staff></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </rdg></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> </app></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="2"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="3"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="4"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="5"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="6"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="7"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="8"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> <staff n="9"/></span><span style="font-family:monospace"><br></span><span style="font-family:monospace"> <staff n="10"/></span><span style="font-family:monospace"><br>
</span><span style="font-family:monospace"> </measure></span></div></div><div><font face="monospace"><br></font></div><div><font face="monospace">@source can take a space-delimited list of xml:ids too.</font></div>
<span class="HOEnZb"><font color="#888888"><div>
<font face="monospace"><br></font></div><div><font face="monospace">-Andrew</font></div></font></span><div><div class="h5"><div><font face="monospace"><br></font><div><div>On 2012-07-15, at 2:24 AM, TW wrote:</div><br><blockquote type="cite">
<div>Dear MEI family,<br><br>how does one encode variant readings that only affect a certain<br>"strand" of events? For example, if we have a full orchestral score<br>where there are different readings of the flute's measures 1 and 2, I<br>
see the following options:<br>1a) One big <app> around measure 1 and 2, containing all staffs twice, like so:<br> <app><br> <rdg><br> <measure n="1"><br> <staff n="1"><br>
<!-- Some music --><br> </staff><br> <staff n="2"/><br> <staff n="3"/><br> <staff n="4"/><br> <staff n="5"/><br>
<staff n="6"/><br> <staff n="7"/><br> <staff n="8"/><br> <staff n="9"/><br> <staff n="10"/><br> </measure><br>
<measure n="2"><br> <staff n="1"><br> <!-- Some more music --><br> </staff><br> <staff n="2"/><br> <staff n="3"/><br>
<staff n="4"/><br> <staff n="5"/><br> <staff n="6"/><br> <staff n="7"/><br> <staff n="8"/><br> <staff n="9"/><br>
<staff n="10"/><br> </measure><br> </rdg><br> <rdg><br> <measure n="1"><br> <staff n="1"><br> <!-- Some variant of the music --><br>
</staff><br> <staff n="2"/><br> <staff n="3"/><br> <staff n="4"/><br> <staff n="5"/><br> <staff n="6"/><br>
<staff n="7"/><br> <staff n="8"/><br> <staff n="9"/><br> <staff n="10"/><br> </measure><br> <measure n="2"><br>
<staff n="1"><br> <!-- Continued variant of the music --><br> </staff><br> <staff n="2"/><br> <staff n="3"/><br> <staff n="4"/><br>
<staff n="5"/><br> <staff n="6"/><br> <staff n="7"/><br> <staff n="8"/><br> <staff n="9"/><br> <staff n="10"/><br>
</measure><br> </rdg><br> </app><br>This already seems like overkill, although I didn't even fill the<br>staffs with music. And facing such a monster, you'd have to look very<br>closely to spot the actual variant readings, so this is certainly not<br>
the way to go.<br><br>1b) To avoid filling the staffs twice, one could of course use @copyof<br>the second time. But this might break ID references.<br><br>2) Split this in two <app>s, like so:<br> <measure n="1"><br>
<app><br> <rdg><br> <staff n="1"><br> <!-- Some music --><br> </staff><br> </rdg><br> <rdg><br> <staff n="1"><br>
<!-- Some variant of the music --><br> </staff><br> </rdg><br> </app><br> <staff n="2"/><br> <staff n="3"/><br> <staff n="4"/><br>
<staff n="5"/><br> <staff n="6"/><br> <staff n="7"/><br> <staff n="8"/><br> <staff n="9"/><br> <staff n="10"/><br>
</measure><br> <measure n="2"><br> <app><br> <rdg><br> <staff n="1"><br> <!-- Some more music --><br> </staff><br> </rdg><br>
<rdg><br> <staff n="1"><br> <!-- Continued variant of the music --><br> </staff><br> </rdg><br> </app><br> <staff n="2"/><br>
<staff n="3"/><br> <staff n="4"/><br> <staff n="5"/><br> <staff n="6"/><br> <staff n="7"/><br> <staff n="8"/><br>
<staff n="9"/><br> <staff n="10"/><br> </measure><br>This looks preferable to me, especially because it allows<br>"overlapping" variants, e.g. when there is another phrase with variant<br>
readings, but this time for the basses from measure 2 to 3.<br>Unfortunately, I don't see a really good way to indicate that any two<br>or more <app> elements form a logical unit. I think that the<br>att.common.anl family of attributes might be useful for this,<br>
especially the @prev and @next attributes because they imply the<br>concept of a "collection". The next best solution might be to use<br>@prev and @next on the contained <lem> and <rdg> elements, but<br>
providing them on <app> would make things much clearer and easier.<br><br>Therefore, shouldn't att.common.anl be allowed on <app>?<br><br>Thomas<br><br>_______________________________________________<br>mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de" target="_blank">mei-l@lists.uni-paderborn.de</a><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></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
mei-l mailing list<br>
<a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><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>
<br></blockquote></div><br></div>