[MEI-L] Antw.: More "precise" <app>s

Benjamin W. Bohl bohl at edirom.de
Mon Jul 23 09:13:46 CEST 2012


Hi evbdy!
Discussing the lacking possibility to aggregate multiple app elements by means of an attribute, which could be very handy indeed, I'd like to put into consideration that @prev and @next imply an order. This might exactly be what One is looking for, especially when thinking of genetic editions, but something like @corresp might be more applicable in other situations.

Cheers,
Benjamin




----- Reply message -----
Von: "TW" <zupftom at googlemail.com>
An: "Music Encoding Initiative" <mei-l at lists.uni-paderborn.de>
Betreff: [MEI-L] More "precise" <app>s
Datum: So., Jul. 15, 2012 21:27


Hi Raphaele,

2012/7/15 Raffaele Viglianti <raffaeleviglianti at gmail.com>:
> Though if I understand Thomas' issue correctly, he's also interested in
> encoding the fact that the two apps can form one apparatus entry.
>

Exactly.

>
> 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).
>

Thanks for the hint.  I see that TEI's <app> (and also <choice>)
indeed have @next and @prev.  I think I'll create a feature request
issue.

And yes, I'm thinking about the automatic generation of apparatus
entries.  It would be messy to have things chopped up in multiple
entries that actually are logically one entry (like one entry for
measure 1 and a second one for measure two of the flute, although they
form one melodic phrase together).  It would be equally messy to get
one huge entry that contains a lot of "noise" (like a two measure
<app> that presents the whole orchestra, although only the flute
varies).

Wish you a good start into the week ahead
Thomas

_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de
https://lists.uni-paderborn.de/mailman/listinfo/mei-l
-------------- n�chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20120723/c9fac796/attachment.html>


More information about the mei-l mailing list