Well, although I agree in principle, there can be substantial information in the header upon which the body depends. Think of source description and their essential role in making sense of @source attributes across the document, or rendition elements in TEI for @rend, etc. In this context, I don't see a problem with encoding the relations between parts in the header similarly to how one would encode the relations between sources.<div>
<br></div><div>Nonetheless, @prev and @next may be a quick and perfectly valid solution to this problem.</div><div><br></div><div>Best,</div><div>Raffaele<br><br><div class="gmail_quote">On Tue, Oct 30, 2012 at 8:59 AM, Daniel Röwenstrunk <span dir="ltr"><<a href="mailto:roewenstrunk@edirom.de" target="_blank">roewenstrunk@edirom.de</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,<div><br></div><div>from my point of view the header should be some kind of *meta* data to the data itself. In my understanding this means that the data (inside body) should be self-consistent, even if the header is missing. I thought that is way we have staffDef and scoreDef for example inside the data part of MEI.</div>
<div><br></div><div>I agree with Raffaele that <perfMedium> doesn't seem to be the right place. At least if you think from a document centric perspective and I would argue that having parts in an MEI encoding is most of the time because of a document centric approach (and I'm pretty sure some of you find examples against this argumentation ;-) ).</div>
<div><br></div><div>The idea of using @sameas (which is possible on <part>) doesn't convince me, either. The two Violin 1 <part> elements are not the same, the second is the continuation of the first, right? So maybe using @next and @prev are a better choice here. Comments on that?</div>
<div><br></div><div>Cheers, Daniel</div><div><br></div><div><br>
<br><div><div>Am 29.10.2012 um 22:12 schrieb Raffaele Viglianti <<a href="mailto:raffaeleviglianti@gmail.com" target="_blank">raffaeleviglianti@gmail.com</a>>:</div><div><div class="h5"><br><blockquote type="cite">
Hello,<div><span><br></span></div><div></div><div>I agree with Johannes, the place for encodining this is in the header, using @decls to point back to the text. I struggle to find the right place were to do that though. To me perfMedium steps into a different domain, so I'm not sure about it.<span></span></div>
<div><br></div><div><span>This is a very interesting problem and I'm curious to read other suggestions.</span></div><div><span><br></span></div><div><span>Best,<br dir="ltr">
</span></div><div><span>Raffaele<br></span></div><div><br></div><div>On Monday, October 29, 2012, Johannes Kepper wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div>Hi Daniel,</div><div><br></div><div>without access to the schema / guidelines, I'd suggest to describe the performing forces in the header (using <perfMedium>), and then use the @decls attribute to point there from each part / staffDef (or @data in the other direction). Probably not the most convenient way, but right now there is no @sameas or @corresp on staffDef…</div>
<div><br></div><div>Just my first idea, maybe others will come up with other / better suggestions. </div><div><br></div><div>Best, Jo <br><br>Am 29.10.2012 um 17:22 schrieb Daniel Röwenstrunk <<a>roewenstrunk@edirom.de</a>>:<br>
<br></div><div></div><blockquote type="cite">Hi all,<div><br></div><div>I'm looking for a good approach to describe the relationship between <part> elements in different movements. In my actual encoding of the piece (see a very simplified example below) the only possibility to guess the relationship between the Violin 1 in the first ("mdiv1_part1") and second ("mdiv2_part1") movement is by comparing their label attributes. And that is not really a thing I want to rely on when I programmatically read MEI files. </div>
<div><br></div><div>Is there a better and/or more precise way of encoding the relationship?</div><div><br></div><div><br></div><div>By the way, why is <mdiv> surrounding <scrore> or <parts>? Wouldn't it be much more intuitive, at least if you use <mdiv> as containers for movements together with parts, to switch this the other way round? </div>
<div><br></div><div>Cheers and thanks,</div><div>Daniel</div><div><br></div><div><br></div><div>Encoding example:</div><div><br></div><div><body></div><div> <mdiv xml:id="mdiv1" label="Allegro"></div>
<div> <parts></div><div> <part xml:id="mdiv1_part1" label="Violin 1"></div><div> …</div><div> </part></div><div> <part xml:id="mdiv1_part2" label="Violin 2"></div>
<div> …</div><div> </part></div><div> </parts></div><div> </mdiv></div><div> <mdiv xml:id="mdiv2" label="Allegretto"></div><div> <parts></div>
<div> <part xml:id="mdiv2_part1" label="Violin 1"></div><div> …</div><div> </part></div><div> <part xml:id="mdiv2_part2" label="Violin 2"></div>
<div> …</div><div> </part></div><div> </parts></div><div> </mdiv></div><div></body></div><div><br></div><div><br></div><div><br></div><div>
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div><div style="word-wrap:break-word">--</div><div>Dipl. Wirt. Inf. Daniel Röwenstrunk</div><div>Project manager</div><div>BMBF-Project "Freischütz Digital"</div><div><br></div><div>Musikwiss. Seminar Detmold/Paderborn</div>
<div>Gartenstr. 20</div><div>D-32756 Detmold</div><div><br></div><div>Tel.: <a href="tel:%2B49%205231%20975665" value="+495231975665" target="_blank">+49 5231 975665</a></div><div>Mail: <a></a><a>roewenstrunk@edirom.de</a></div>
</div><div>URL: <a href="http://www.freischuetz-digital.de/" target="_blank"></a><a href="http://www.freischuetz-digital.de/" target="_blank">http://www.freischuetz-digital.de</a></div></div><br></div><br>
<br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>mei-l mailing list</span><br><span><a>mei-l@lists.uni-paderborn.de</a></span><br>
<span><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l" target="_blank">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a></span><br></blockquote></div></blockquote></div>
_______________________________________________<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>
</blockquote></div></div></div><br></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>