[MEI-L] encoding orchestra cast with alternative instruments
Roland, Perry D. (pdr4h)
pdr4h at eservices.virginia.edu
Wed Feb 1 17:00:57 CET 2017
A discussion happening in the MEI Github repo on the topic of encoding order influenced my suggestion here. In this case, however, relying on encoding order inside <perfResList> may not be helpful. So, at present you can use --
<perfResList xmlns="http://www.music-encoding.org/ns/mei" xmlns:svg="http://www.w3.org/2000/svg">
<perfResList codedval="wb" count="3">
<head>Oboes</head>
<perfResList count="2" type="performer">
<perfRes codedval="wb" solo="false">Oboe</perfRes>
<perfResList type="substitution">
<perfRes codedval="wz" solo="false" type="score">Oboe d'amore</perfRes>
<perfRes codedval="wb" solo="false" type="substitute">Oboe</perfRes>
</perfResList>
</perfResList>
<perfRes count="1" type="performer">
<perfRes codedval="wb" solo="false">Oboe</perfRes>
<perfRes codedval="wz" solo="false">Cor d'anglais</perfRes>
</perfRes>
</perfResList>
</perfResList>
which types the <perfRes> elements. This should be sufficient for your needs, but won't be enforce-able across multiple projects.
A @substitute attribute is a good suggestion because it is more machine-processable than the ad hoc values of @type. Naming it @substitutefor or @subfor would make the direction/meaning of the reference explicit.
BTW, the @solo attribute isn't necessary. One can assume that any performing resource not marked with @solo="true" is not a soloist.
--
p.
> -----Original Message-----
> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
> Benjamin W. Bohl
> Sent: Wednesday, February 01, 2017 3:16 AM
> To: Music Encoding Initiative
> Subject: Re: [MEI-L] encoding orchestra cast with alternative instruments
>
> Hi everybody,
>
> yes , as stated in my initial mail I’m trying to take account of the following
> situation.
>
> 3 Oboe players
> - 1 and 2 also play Oboe d’amore that might be substituted by Oboe
> - 3 also plays Cor d’anglais that may not be substituted
>
> The idea is to state somehow, that Oboe and Oboe d’amore (1 and 2) and
> Oboe and Cor d’anglais (3) are in exclusive alteration, AND that in case there is
> no Oboe d’amore available, 1 and 2 might keep playing their Oboe for those
> sections.
>
> In the following suggestion by Perry:
>
> > 6. <perfResList type="substitution">
> > 7. <perfRes codedval="wz" solo="false">Oboe d'amore</perfRes>
> > 8. <perfRes codedval="wb" solo="false">Oboe</perfRes>
> > 9. </perfResList>
>
>
> I miss the indication, which instrument is the “regular” and which one the
> “alternative”. Axels idea of @substitutes is comes way closer to that:
>
> > <perfRes codedval="wb" solo="false" xml:id="ob1">Oboe</perfRes>
> > <perfRes codedval="wz" solo="false" substitutes="#ob1">Oboe
> d'amore</perfRes>
>
> Nevertheless it can be misunderstood I think, as you could read it as verb (1) or
> as noun (2):
> 1) Oboe d’amore substitutes Oboe
> 2) Oboe d’amore has a potential substitute, namely Oboe
>
> Of course that’s something that c an become clear from the documentation,
> but maybe omitting the ’s’ (@substitute) would make it clearer?
>
> Benni
>
>
> > On 31 Jan 2017, at 18:04, Axel Teich Geertinger <atge at kb.dk> wrote:
> >
> > Hi Perry & Benni
> >
> > I am not quite sure about either of your solutions. Especially line 8 bothers
> me. Isn't that redundant? It just repeats the information in line 5 – isn't that
> asking for trouble?
> > Benni, does the @type="substitution" in your version of line 8 mean to say
> explicitly that it is the oboe which may be substituted? I don't see why that is
> necessary (at least not in this simple case).
> > Omitting that line, however, brings us back to my suggestion (slightly
> modified here):
> >
> > <perfResList count="2" type="performer">
> > <perfRes codedval="wb" solo="false">Oboe</perfRes>
> > <perfRes codedval="wz" solo="false" type="substitution">Oboe
> d'amore</perfRes>
> > </perfResList>
> >
> > As long as the situation is not overly complex, this seems to be a far simpler
> solution to me. Or are you trying to take into account the possibility that a
> performer may play more than one instrument, one or more of which may be
> substituted? In that case I do see the need for something more specific.
> However, I would like to omit repeating any instrument declaration. An
> alternative way of making explicit which instrument may be substituted would
> be to invent another attribute to point to that instrument. Then perhaps you
> could even omit @type:
> >
> > <perfRes codedval="wb" solo="false" xml:id="ob1">Oboe</perfRes>
> > <perfRes codedval="wz" solo="false" substitutes="#ob1">Oboe
> d'amore</perfRes>
> >
> > Just an idea.
> >
> > /axel
> >
> > -----Original Message-----
> > From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
> Roland, Perry D. (pdr4h)
> > Sent: Tuesday, January 31, 2017 3:58 PM
> > To: Music Encoding Initiative <mei-l at lists.uni-paderborn.de>
> > Subject: Re: [MEI-L] encoding orchestra cast with alternative instruments
> >
> >
> > Hi Benni,
> >
> > Yes, @type will be added in the next release.
> >
> > Your solution looks good, but may I suggest --
> >
> > 1. <perfResList xmlns="http://www.music-encoding.org/ns/mei"
> xmlns:svg="http://www.w3.org/2000/svg">
> > 2. <perfResList codedval="wb" count="3">
> > 3. <head>Oboes</head>
> > 4. <perfResList count="2" type="performer">
> > 5. <perfRes codedval="wb" solo="false">Oboe</perfRes>
> > 6. <perfResList type="substitution">
> > 7. <perfRes codedval="wz" solo="false">Oboe d'amore</perfRes>
> > 8. <perfRes codedval="wb" solo="false">Oboe</perfRes>
> > 9. </perfResList>
> > 10. </perfResList>
> > 11. <perfRes count="1" type="performer">
> > 12. <perfRes codedval="wb" solo="false">Oboe</perfRes>
> > 13. <perfRes codedval="wz" solo="false">Cor d'anglais</perfRes>
> > 14. </perfRes>
> > 15. </perfResList>
> > 16. </perfResList>
> >
> > This puts the indication of substitution on the <perfResList> rather than on
> the secondary instrument. Also, @count at line 5 has been removed.
> >
> > --
> > p.
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
More information about the mei-l
mailing list