[MEI-L] encoding orchestra cast with alternative instruments
Benjamin W. Bohl
bohl at edirom.de
Tue Jan 31 12:09:17 CET 2017
Dear Axel and Perry,
thanks for your advice. I like the idea of using @type but it’s not allowed on perfResList in MEI v3.0.0 is that to change in the next release?
For the moment I came up with the following to capture the whole situation:
<perfResList>
<perfResList codedval="wb" count="3">
<head>Oboes</head>
<perfResList count="2" type="performer">
<perfRes codedval="wb" count="2" solo="false">Oboe</perfRes>
<perfResList>
<perfRes codedval="wz" solo="false">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>
How do you like it?
I’m not sure whether I’ll keep @count on the parent <perfResList> but I think I will, in order to provide a "flat processing”.
>> The current schema does not allow nesting <perfRes>
N.B. according to the data dictionary and the schema it is allowed; maybe a mistake? I see your point, that nesting <perfResList> is much more feasible ;-)
> On 25 Jan 2017, at 23:48, Roland, Perry D. (pdr4h) <pdr4h at eservices.virginia.edu> wrote:
>
>
> Hi Benni and Axel, everyone,
>
> This is why <perfResList> is self-nesting and why it is named, perhaps a little obtusely, "performance resource list". It's a way of grouping performing resources, whether they are groups of like instruments, such as strings or woodwinds, or whether they are resources used/supplied (?) by a single performer. I tried to inject a <performer> element in the model, but I remember that it became too complex for my meager faculties to contemplate.
>
> --
> p.
>
>
>> -----Original Message-----
>> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Axel
>> Teich Geertinger
>> Sent: Wednesday, January 25, 2017 4:35 PM
>> To: Music Encoding Initiative
>> Subject: Re: [MEI-L] encoding orchestra cast with alternative instruments
>>
>> Oops: You'll notice that I forgot to change the @codedval values when copy-
>> pasting...
>> Cor anglais should have @codedval="wf" :-)
>>
>> /axel
>>
>> ________________________________________
>> Fra: mei-l [mei-l-bounces at lists.uni-paderborn.de] på vegne af Axel Teich
>> Geertinger [atge at kb.dk]
>> Sendt: 25. januar 2017 22:27
>> Til: Music Encoding Initiative
>> Emne: Re: [MEI-L] encoding orchestra cast with alternative instruments
>>
>> Hi Benni
>>
>> Good question. I would love to see a solution as well. So far we have really just
>> worked around the problem by only mentioning alternative or alternating
>> instruments in plain text like this (using your example):
>>
>> <perfRes codedval="wb" count=“2" solo="false">Oboe / oboe
>> d'amore</perfRes>
>>
>> This is obviously not well suited for any computerized use of the information
>> (which, however, we haven't needed yet).
>>
>> The current schema does not allow nesting <perfRes>, so your suggested
>> approach doesn't validate out of the box. While allowing child elements in
>> <perfRes> may be the way to go, I would perhaps not suggest nesting
>> <perfRes> itself: As you say, simply nesting them doesn't make it clear whether
>> the instruments are possible replacements or one player playing alternating
>> instruments. More specific elements or attributes may be required.
>>
>> The problem may be that <perfRes>is intended to describe a single instrument
>> (or ensemble), not all the instruments played by a single performer. What may
>> be needed is a "performer" grouping device. As <perfResList> is exactly that: a
>> <perfRes> grouping device, perhaps simply adding an attribute such as @type
>> to <perfResList> and <perfRes> may do the trick:
>>
>> <perfMedium>
>> <perfResList>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Oboe
>> d'amore</perfRes>
>> </perfResList>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Oboe
>> d'amore</perfRes>
>> </perfResList>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Cor
>> anglais</perfRes>
>> </perfResList>
>> </perfResList>
>> </perfMedium>
>>
>> However, this would probably require omitting the @count attribute: What
>> would, say, count="2" mean with a single performer? Perhaps that one has to
>> play 2 oboes simultaneously. :-/
>>
>> If you want to group both by performer and instrument family ("Oboe") you
>> might need another <perfResList> to wrap the three performers:
>>
>> <perfMedium>
>> <perfResList>
>> <perfResList codedval="wb">
>> <head>Oboes</head>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Oboe
>> d'amore</perfRes>
>> </perfResList>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Oboe
>> d'amore</perfRes>
>> </perfResList>
>> <perfResList type="performer">
>> <perfRes codedval="wb" solo="false">Oboe</perfRes>
>> <perfRes codedval="wb" solo="false" type="replacement">Cor
>> anglais</perfRes>
>> </perfResList>
>> </perfResList>
>> </perfResList>
>> </perfMedium>
>>
>> I am not sure this is the way to go. Any thoughts?
>>
>> Best,
>> Axel
>>
>> ________________________________________
>> Fra: mei-l [mei-l-bounces at lists.uni-paderborn.de] på vegne af Benjamin
>> W. Bohl [bohl at edirom.de]
>> Sendt: 23. januar 2017 12:35
>> Til: Music Encoding Initiative
>> Emne: [MEI-L] encoding orchestra cast with alternative instruments
>>
>> Dear MEI-L:isteners,
>>
>> can anyone help me how to encode a cast list for an orchestra that gives
>> alternating instruments for the players and potential replacements if certain
>> instruments not being available?
>>
>> E.g.:
>> In the cast list:
>> “3 Oboes – 1. And 2. Also oboe d’amore, 3. Also cor anglais”
>>
>> Amongst other at the end of the cast list:
>> “If necessary, the oboe d’amore can be replaced by an oboe, […]”
>>
>> Simple case ignoring additions:
>>
>> <perfMedium>
>> <perfResList>
>> <perfRes codedval="wb" count=“3" solo="false"></perfRes>
>> </perfResList>
>> </perfMedium>
>>
>> Alternatively trying to capture all instrument info:
>>
>> <perfMedium>
>> <perfResList>
>> <perfRes codedval="wb" count="3" solo="false">
>> <perfRes codedval="wb" count=“3" solo="false">Oboe</perfRes>
>> <perfRes codedval="wz" count="2" solo="false" >Oboe
>> d'amore</perfRes>
>> <perfRes codedval="wz" count="1" solo="false">Cor d'anglais</perfRes>
>> </perfRes>
>> </perfResList>
>> </perfMedium>
>>
>> Nevertheless I can’t capture the idea of alternating instruments for the first
>> two oboes resp. The oboes d’amore or the third oboe and the cor d’anglais…
>>
>> What if I use even a deeper nesting:
>>
>> <perfMedium>
>> <perfResList>
>> <perfRes codedval="wb" count="3" solo="false">
>> <perfRes count="2" solo="false">
>> <perfRes codedval="wb" count="2" solo="false">Oboe</perfRes>
>> <perfRes codedval="wz" count="2" solo="false" >Oboe
>> d'amore</perfRes>
>> </perfRes>
>> <perfRes count="2" solo="false" >
>> <perfRes codedval="wb" count="1" solo="false">Oboe</perfRes>
>> <perfRes codedval="wz" count="1" solo="false">Cor
>> d'anglais</perfRes>
>> </perfRes>
>> </perfRes>
>> </perfResList>
>> </perfMedium>
>>
>> I’m not sure whether this captures the meaning, especially since there is no
>> possibility of stating the exclusive alteration, like e.g. in TEI with @exclude.
>>
>> Any thoughts would be appreciated!
>> Many thanks
>> Benjamin
>>
>>
>> _______________________________________________
>> 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
> _______________________________________________
> 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