[MEI-L] Problem: Encoding omissions
aseipelt at mail.uni-paderborn.de
Thu Feb 9 17:34:36 CET 2017
in my opinion, the equivalent to <supplied> could be, like you have it in your version, <choice> with the elements <orig> and <reg>. So you can encode the slur in the <orig>-Element, because it is the original. And for the omission, what is in your case a regularization, you can encode the notes without the slur in the <reg>-element. Of course, you should add a @resp.
Maybe someone has another solution?
Von: mei-l <mei-l-bounces at lists.uni-paderborn.de> im Auftrag von Rolf Wissmann <Rolf.Wissmann at gmx.net>
Antworten an: Music Encoding Initiative <mei-l at lists.uni-paderborn.de>
Datum: Donnerstag, 9. Februar 2017 um 17:20
An: <mei-l at lists.uni-paderborn.de>
Betreff: [MEI-L] Problem: Encoding omissions
can anyone help me how to encode an editorial decision to omit a slur which is present in the source?
I have some proposals, but I'm not satisfied with anyone.
1.) This version doesn't fit because it's too strong to say that this slur is a mistake. I only would like to say
that it makes no sense in the musical context.
<corr resp="#RW" evidence="conjecture" />
2.) This version doesn't fit because it's my proposal to omit the slur and it's not based on a source.
<lem resp="#RW" reason="Previous measures without slur"/>
<rdg resp="#source" >
If I understand the Guidelines in a right way, than it's not possible to use the <del> element in this case because it's
not a part of the source material.
I couldn't find a equivalent to the element <supplied>.
I hope, someone can help me.
_______________________________________________ mei-l mailing list mei-l at lists.uni-paderborn.de https://lists.uni-paderborn.de/mailman/listinfo/mei-l
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mei-l